daveambrose.com
Theme

Dave Ambrose / Implementation

Test this page

Open DevTools and run Lighthouse. Try a throttled mobile connection, follow the links with the keyboard, then zoom to 400% and inspect the heading and link lists with a screen reader.

Build output

What this page loads

Stylesheet, gzip estimate
3.11 KB
Theme script, gzip estimate
0.53 KB
Document and asset requests
3
Framework JavaScript
0
Webfont files
0
Third-party page requests
0

These figures are generated from the emitted files. Gzip figures use Node's level-nine compression and are estimates, not a measurement of the production server. Request counts cover the document and its linked rendering assets; browser icons and link-preview images are excluded.

Download this build's measurements. The JSON also includes raw and Brotli sizes. No production Lighthouse score is claimed here.

Human checks

What a score leaves out

An automated accessibility scan finds detectable rule violations. It cannot decide whether the writing is understandable, whether a heading describes the section beneath it, or whether a link makes sense when read outside its paragraph.

Use the page's actual controls for these checks:

  • Tab to the skip link first. Activate it and confirm that focus moves into the main content.
  • Follow the links and theme controls. Check that the focus ring is visible and the order follows the page.
  • Open the tooling and earlier-experience disclosures on the home page with the keyboard.
  • Zoom to 400% and read without horizontal scrolling. The large title should reflow with the rest of the page.
  • Compare light, dark and system themes. Check borders, links and focus indicators as well as paragraph text.
  • Enable reduced motion and follow links between pages. Read the page with JavaScript disabled; only the theme override depends on it.

Implementation

Choices in the build

Astro produces static HTML. There are no hydrated components or client-side router. The theme control uses a small external script, and the same stylesheet is shared across pages through a content-hashed URL.

The typography uses fonts installed on the reader's device. That removes font requests and font-loading shifts, but letter shapes vary between operating systems. The layout allows for those differences.

Cross-document transitions use the browser's native support and are disabled when the reader prefers reduced motion.

The build checks file-size budgets and prevents private contact details from entering the output. Server behavior still needs a separate check after deployment: valid HTTPS, response headers, asset MIME types, redirects and the custom 404 response.