Skip to content
Codewright

How fast is this site?

Anyone can say their site is fast. These are the measured numbers for this one, how I took them, and where they’re weaker than they look.

Measured 18 October 2026 with Lighthouse 13.5 against the live site, on a simulated mid-range phone over slow 4G. Median of three runs from Cape Town. Run the same test yourself and, if your numbers differ, trust yours.

Google Lighthouse scores

  • 98

    Performance

  • 100

    Accessibility

  • 100

    Best practices

  • 100

    SEO

Out of 100.

The speed measurements Google ranks on

Core Web Vitals are part of how Google ranks pages. They’re also a fair measure of whether a site is pleasant to use.

MeasureThis siteGoogle’s target
Largest Contentful PaintHow long until the main content is visible.2.1 sunder 2.5 s
Total Blocking TimeHow long the page is too busy to respond to a tap. The lab stand-in for INP.30 msunder 200 ms
Cumulative Layout ShiftHow much the page jumps around while loading. Zero means it doesn’t.0under 0.1
First Contentful PaintHow long until anything appears at all.1.8 sunder 1.8 s

409 KB to load the home page

That’s everything, compressed, as it actually travels over the network.

  • JavaScript176 KB
  • Fonts (headings and handwriting)58 KB
  • HTML, including the drawn sketches16 KB
  • CSS8 KB
  • Google Analytics (loads after the page)151 KB

Where these numbers flatter me

Google Analytics is the biggest download

Google's analytics scripts are 151KB, more than everything else on the page except the framework. They load only once the page has finished and the browser is idle, so they don't slow down what you see. They do use your data allowance.

First paint is right on Google's line

In this test the first thing appears at 1.8 seconds, exactly at the edge of Google's 'good' threshold. Most of that is the test's simulated slow connection setting up a secure link to the server; the server itself answers in about 70 milliseconds. I'd rather show you the real figure than the faster one I get on my own machine.

Most of the JavaScript isn’t mine

Almost all of it is the React and Next.js runtime, which every site built this way ships. The pages themselves have one interactive part, the contact form. Everything else arrives as plain HTML.

These are lab numbers

Lighthouse simulates a mid-range phone on a slow connection. That makes it a fair, repeatable comparison, but it isn’t the same as measuring real visitors. Once there’s enough traffic, Google Search Console reports real-world figures, and those are the ones that count.

How it stays this way

Sites get slower and harder to use over time unless something stops it. These checks run before every release, and a failure stops the release. Your project gets the same setup.

Colour contrast

Reads the real colours from the stylesheet and blocks the release if any text falls below the WCAG 2.2 AA contrast level.

Nothing wider than the screen

Loads every page at phone, tablet and desktop sizes in a real browser and blocks the release if anything spills sideways.

The contact form

39 automated tests, including what happens when the database or the email service is down. A message must never be lost or falsely confirmed.

Code quality

Type checking, linting and formatting on every change, with no warnings allowed.