Example · sample numbers
a-small-bakery.example
Fine on a laptop. Slow enough on a phone to lose the first click.
The page works and Google can read it. It is the loading experience on a phone that is doing damage — nearly five seconds before a visitor sees the thing they came for.
Speed
Accessibility
Best practices
SEO
-
The main thing on screen appears
4.8s
Google calls good under 2.5s
-
It responds to a tap
240ms
Good is under 200ms
-
The page moves under your thumb
0.21
Good is under 0.1
-
First pixel of content
2.1s
Good is under 1.8s
-
Critical Speed
4.2 MB of images load before anyone reads a word
The photos are being sent at full camera resolution and scaled down in the browser. On a phone on mobile data that is most of the five-second wait, and it is the single cheapest thing on this list to fix.
What we would doResize and re-encode to modern formats, load below-the-fold images lazily, and give the hero image a fixed size so it stops the page jumping.
-
Worth fixing Mobile
The layout shifts while it loads
Fonts and a banner arrive late and push the content down. A visitor aiming at the menu link taps the phone number instead — the kind of thing people quietly blame themselves for and then leave.
What we would doReserve space for anything that arrives late and preload the display font.
-
Worth fixing SEO
No meta description on the page Google shows most
Google is writing its own summary of your business in the search results. It is usually a sentence lifted from the middle of the page, and it is rarely the sentence you would have chosen.
What we would doWrite a description per page that reads like a reason to click.
-
Looks right Foundations
HTTPS, mobile viewport and a valid sitemap are all in place
The basics that are miserable to retrofit are already done. This is a site worth speeding up rather than replacing.