Example report. Harbourside Dental is a made-up client and every number below is invented, to show the shape of what we send.
Scores run from 0 to 100 and come from a single mobile test on a throttled connection, so they move a few points between runs. Treat them as a temperature reading, not a stopwatch.
The short version
Your appointments page takes about 4.1 seconds to show a visitor something useful on a phone. That is roughly twice as long as it should, and most of the wait comes from one thing: a large photograph at the top of the page that has to download in full before anything else appears.
Nothing here is broken. Someone on a good connection will not notice much. But on a normal mobile signal — a patient looking you up in a car park — the page is blank long enough that a share of them will leave before it finishes. Fixing the header image and two scripts would bring the wait down to about a second and a half without touching the design.
The three numbers that matter most
4.1s
How long until the biggest thing on screen — here, the header photo — has finished loading. This is the number a visitor feels as “the site is slow”.
Target: under 2.5s0.04
How much the page jumps around while it loads. Yours is steady — nobody is going to tap the wrong button because the layout moved under their thumb.
Target: under 0.1310ms
How long the page ignores taps and scrolls because it is busy running scripts. Around a third of a second here, which reads as a slight stickiness rather than a freeze.
Target: under 200msWhat is costing you the most time
Ordered by how much each one adds to the wait. The bars are relative to the slowest item.
-
01
The header photograph is far larger than it needs to be 1.9s
The image is served at 3200 px wide and 2.4 MB, then scaled down to fit a phone screen. Exporting it at 900 px in WebP would cut it to roughly 120 KB with no visible difference.
-
02
The booking widget loads before the page is drawn 0.8s
The third-party appointment script runs first and holds everything else up, even though the button it powers sits below the fold. Loading it after the page has drawn would hand that time back.
-
03
Three tracking scripts run on every page 0.5s
Analytics, a heatmap tool, and a chat widget. All three are useful, none is urgent — deferring them until after the page is interactive costs nothing in the data they collect.
-
04
Fonts arrive late and text flashes 0.3s
Four font files download before any text can be styled. Preloading the two that are actually used above the fold would remove the flash of unstyled text on first visit.
If you only do one thing
Re-export the header photograph. It is a single file swap with no code change, no design change, and no risk — and on its own it takes the page from 4.1 seconds to roughly 2.2, which moves Largest Contentful Paint from a fail to within touching distance of a pass.
Best ratio of impact to effort on this page by a wide margin. Everything else on the list is worth doing, but it can wait for the next round of work.
Prepared by Northwind Digital for Harbourside Dental.
Questions about anything in here? Reply to the email this arrived in and we will walk you through it.