KKazım Şahin
Menu
← Back to home
Quality of this site

I apply my testing approach
to this site too.

The local static export and the live Cloudflare Pages deployment are measured under separate conditions. These results must not be read as current results for the displayed project repositories.

Live deployment

Cloudflare Pages acceptance result

· Source commit efecbe1 · Live site ↗

11/11Live pages opened directlyHTTPS · 404 · mobile navigation
97Live mobile Lighthouse / 100 (median)Three runs: 99 · 97 · 96
PassedFirst GitHub Actions run17 min 52 sec

Live Lighthouse: accessibility 100, best practices 100, SEO 100. FCP 1020 ms, LCP 1855 ms, CLS 0.000, TBT 167 ms.

Live acceptance record: JSON report ↗

Approach

Validate the visitor's path

01 / Flow

From the home page to evidence

I check access to a project story, its public repository, and a contact route across three browsers.

02 / Access

Keyboard and layout

I check visible focus, reduced motion, mobile navigation, heading structure, and overflow at different screen sizes.

03 / Measurement

Record the result and its limit

I store automated accessibility and Lighthouse results with their date, version, conditions, and known limits.

Latest local run

Measured results

· Version 0.1.0 · Next.js 16.3.8 · Source SHA-256: b6cedb5642a8

18Passed browser checksChromium · Firefox · WebKit
0Critical/serious automated accessibility findingsFive representative pages
91Mobile Lighthouse performance / 100 (median)Target 90 · simulate throttling

Three consecutive mobile runs: 88 · 91 · 93. Range 88–93; median 91. These local measurements are sensitive to device load.

Mobile Lighthouse: accessibility 100, best practices 100, SEO 100. FCP 1217 ms, LCP 2215 ms, CLS 0.000, TBT 278 ms.

9 checks were intentionally skipped in the browser matrix; 0 failed. Details: JSON report ↗

Limits

What do these results not prove?

  • Lighthouse ran three times against a gzip-enabled local static server with mobile simulation; the median and range are reported. This is not live visitor speed or a hosting result.
  • Automated axe scanning does not prove complete accessibility. The keyboard flow was checked in Chromium and Firefox; this specific check was skipped in Windows Playwright WebKit because Tab focus on links was unavailable.
  • This report belongs to the portfolio; tests in the displayed GitHub project repositories were not run.
  • GitHub Actions is verified separately; this local report alone does not show the status of a remote CI run.
  • Lighthouse ran three times on the live Cloudflare Pages address with mobile simulation; the median and range are reported. The result does not guarantee a visitor's device or connection speed.
  • The measurement computer's default DNS had not yet seen the new pages.dev record, so Chrome was routed to a verified Cloudflare IP. The HTTPS hostname, certificate, and live content were preserved; the record was also verified through 1.1.1.1 and Google Public DNS.
  • The automated accessibility score does not replace a manual WCAG 2.2 AA assessment.
  • This record applies only to the portfolio site; it is not a current test result for the displayed project repositories.