Measured 2026-09-18 · re-runnable

Everything on this page is our own site, timed with the before and the after.

A studio selling speed on a domain it has never measured is the thing this page is against. So: five seconds, drawn flat. Our pages are marked where they actually answer, Google’s line is drawn where Google draws it, and one real local business is marked where it landed. Every figure came out of a script in this repository that anyone can run again.

Run the clock

A service page answers in

0.26s

Google stops calling it good

2.50s

Teardown 01 answers in 4.44s

Largest Contentful Paint

Where do our pages land in five seconds?

Largest Contentful Paint — the moment the biggest thing on screen has finished arriving. Read from the browser’s own performance timeline, on a phone viewport, one load each.

0.26s A service page answers Largest Contentful Paint on /services/, measured over twelve routes.

0.59s The pricing page answers The heaviest data page on the site, and still inside six tenths of a second.

1.31s The home page answers Three live 3D canvases, and it is the slowest thing we ship.

2.50s Google stops calling it good The Largest Contentful Paint threshold. Everything past this line is a page somebody is waiting on.

4.44s Teardown 01 answers A real local business, measured the same way, on the same kind of phone. Not a competitor and not named.

The ledger

What moved this month, and what did it?

Both columns, not the flattering one. The point of a before is that you are allowed to check it.

Before and after figures for this site, measured 2026-09-18
WhatBeforeAfterWhat did it
The home page 2,850 KB 2,262 KB three.js shipped as its 1,243 KB development build; the same file minified is 652 KB.
The work page 3,669 KB 1,006 KB eight laptop plates were 17,673 KB of PNG between them, and 1,315 KB as WebP.
Images with no declared box 24 0 every one now states its real width and height, read from the file.
Images served stale-able 17 0 a cache-buster on every theme image, so a re-export is never served from last month.
Console errors, 12 routes 0 0 it was already clean. Said because a page about speed should show what it did not have to fix.

The order

How does a page get faster, in the order it happens?

  1. Measure before touching anything

    Every figure on this page came out of a script that anyone can re-run. A studio that cannot show you the before is showing you an opinion.

  2. The biggest file first, always

    One PNG was two megabytes of a single page. Nothing else on that page was worth looking at until it was gone.

  3. Declare every box

    An image with no width and height moves the page while it loads. It is the cheapest fix in this list and almost nobody does it.

  4. Then measure again, and publish

    Both numbers, not the flattering one. The whole point of a before is that you are allowed to check.

Yours next

We will time yours the same way

Send the address and you get the same reading on the same kind of phone, with the before written down before anything is touched. A reply comes within one business day. If you would rather see the whole procedure first, the teardown is all nine checks on a real site.

Time my site

What we have written on this

Related: Teardown.