01
Field data, not just lab scores
What real visitors experienced over the last 28 days, pulled from Google's own dataset, alongside the synthetic test.
A slow site loses enquiries before anyone reads a word
A fixed-fee audit is £650. You get a written report inside a week: what is slow, why, what to fix first, and how much of it you can do without me. If you want me to do the fixing, I quote that separately once we both know the size of it.
- £650 fixed
- Report inside 5 working days
- Yours to keep and share
- Fixes quoted separately
What the difference actually feels like
Everyone nods along at “a few seconds slower”. Almost nobody has sat and watched it. These bars run on the real clock, so the slow one genuinely takes 6.2 seconds. Roughly what a bloated WordPress homepage does on 4G, and two and a half times Google’s threshold.
6.2 seconds0.0s
Blank screen
By four seconds a good share of visitors have gone. They do not tell you, and they do not come back.
0.9 seconds0.0s
Blank screen
Inside Google's 2.5 second threshold with room to spare. The panel at the foot of this page shows the real figure for the page you are on.
Two durations, not a case study. I am demonstrating six seconds, not claiming a particular client result. Your own numbers come from the £650 audit.
What gets measured
Google’s three Core Web Vitals, on real devices rather than a laptop on office wifi. Largest Contentful Paint for how long the main content takes to appear, Interaction to Next Paint for how quickly the page responds when someone taps, and Cumulative Layout Shift for whether things move under their thumb while it loads.
Then the boring causes underneath: image weight, render-blocking scripts, font loading, server response time, and how much of your JavaScript is running on pages that never use it. I test on a mid-range Android on a throttled connection, because that is what a lot of your visitors actually have.
02
A prioritised list
Ordered by time saved per hour of work. The first three items usually account for most of the gain.
03
Plain English
Written so you can hand it to whoever maintains the site, including a developer who is not me.
What usually turns out to be wrong
Images nobody resizedA 4,000-pixel photo displayed at 600 pixels wide. The single most common problem I find, and usually the quickest win.
Plugin sprawlSliders, popups, chat widgets and analytics tools, each loading everywhere whether the page uses them or not.
Fonts loaded three timesOnce by the theme, once by a plugin, once by an embed. Text sits invisible while the browser waits.
Cheap shared hostingSometimes the code is fine and the server is the problem. Moving host is occasionally the whole fix.
Layout that jumpsBanners and adverts inserted after paint, shoving the content someone was about to tap.
An honest note about numbers
You will find agencies advertising specific uplifts, along the lines of a fixed percentage more conversions for every tenth of a second saved. I am not going to quote you one. The correlation between speed and revenue is real and well documented at large scale, but nobody can honestly promise you a number for your particular site before looking at it. What I can promise is a measurable before and after on the vitals themselves, and I will show you both.
Questions people actually ask
Is a 100 PageSpeed score the goal?
No, and chasing it wastes money. Passing the three Core Web Vitals on real visitor data is the goal. A site can score 100 in the lab and still feel slow to someone on a train.
Can you fix it as well as audit it?
Yes. I quote the fixes after the audit, so you are never paying for work before either of us knows what it involves. Plenty of clients take the report and do it themselves, which is fine.
How long do fixes take?
Small ones, an afternoon. A theme that needs rebuilding, three or four weeks. The report tells you which situation you are in.
Do you audit Shopify and Squarespace too?
Shopify yes. Squarespace and Wix, partly. On closed platforms there is a ceiling to what anyone can change, and I will tell you where that ceiling is instead of billing you to hit it.
Find out what is actually slowing it down.
Get a quote in four questions
hello@madebykestrel.co.uk · replies inside one working day
This page, measured in your browser
Your deviceLCPMeasuring…
–
How long until the main content appears. Google wants under 2.5 seconds.
INPMeasuring…
–
How quickly the page answers when you tap. Under 200ms is the target.
CLSMeasuring…
–
How much the layout moves while loading. Under 0.1, ideally zero.
Real numbers from your device and connection, not a screenshot of a score I chose. Nothing is sent anywhere. The measurement happens in your browser and stays there. If one of these ever reads amber on my own site, you will see it, which is rather the point. I audit these for £650.