Website Speed Optimization That Shows Up in Field Data
Audit-first Core Web Vitals work on the site you already have: we find what is actually slow, fix it in priority order, and verify the result in Chrome UX Report data — not just a lab score screenshot.
The score is not the problem
A PageSpeed Insights number is a lab measurement of one page, on one simulated device, at one moment. Google ranks on something different: the Core Web Vitals experienced by real Chrome users over the previous 28 days, at the 75th percentile, grouped by URL. A site can score 90 in the lab and still fail in the field — because the lab never sees your logged-in users, your slower markets, or the third-party tag that only fires after consent.
So we start from the field. The audit pulls your CrUX data per page group, reproduces the failures on a throttled mid-range Android, and traces each one to its cause: an uncompressed hero image, a render-blocking font, a layout that jumps when the cookie banner loads, a click handler stuck behind a 400 ms analytics bundle. Every finding comes with the expected gain and the cost to fix, ranked.
Then we fix them in that order and stop when the numbers pass. Sometimes that is a day of image and caching work; sometimes it means re-templating a theme or retiring a page builder. You get the plan and the price before we touch anything, and a report 28 days after we finish showing the field data move. If the honest answer is "rebuild", we say so and point you at web development instead.
What we fix
Each of the three Core Web Vitals fails for different reasons. The audit says which ones apply to you; the work covers only those.
Core Web Vitals Audit
CrUX and Search Console data per page group, reproduced in the lab, with every failure traced to a specific cause and ranked by impact and cost to fix.
LCP — Largest Contentful Paint
Hero images resized and served as AVIF/WebP with the right fetch priority; render-blocking CSS and fonts taken off the critical path; slow server responses fixed at the source.
INP — Interaction to Next Paint
Long JavaScript tasks broken up or removed, third-party tags deferred or dropped, event handlers made cheap — so taps and clicks respond in under 200 ms.
CLS — Cumulative Layout Shift
Dimensions on every image and embed, reserved space for banners and ads, and font loading that does not reflow the page after it has painted.
Server & Caching Layer
Time to first byte fixed with proper page and object caching, HTTP/2 or HTTP/3, compression, Cloudflare edge rules, and database queries that stop repeating the same work on every request.
Third-Party Script Diet
An inventory of every tag, pixel, chat widget and embed with its cost in milliseconds — then a recommendation on what to keep, defer or remove entirely.
What you receive
- A prioritised audit report: cause, expected gain and fix cost for every item
- Fixes implemented on staging, verified on a throttled real device, then deployed in one release
- Before/after lab reports (Lighthouse and WebPageTest) for every template
- Field-data verification 28 days after completion, from CrUX and Search Console
- Cloudflare, caching and image-pipeline configuration documented for your team
- A short list of rules that keep the site fast: image sizes, plugin policy, tag governance
Audit, fix, verify
You see the ranked list and the price before any change is made.
Field data first
We pull CrUX and Search Console Core Web Vitals by page group and identify which templates fail, and on which metric.
Reproduce and trace
Each failure is reproduced on a throttled mid-range device and traced to a root cause, not a symptom.
Fixed-price plan
A ranked list with the expected gain per item and one price for the set that gets you to "Good".
Implement on staging
Changes are made and measured on a copy of the site, then deployed in one controlled release.
Verify in the field
28 days later we report the real-user numbers and fix anything that did not move as predicted.
Is this the right service for you?
We would rather tell you now than three weeks in.
A good fit if…
- Search Console shows "Poor" or "Needs improvement" URLs and nobody can say why
- You have already installed a caching plugin and the field data did not move
- You send paid traffic to pages that load slowly — every 100 ms is costing you conversions
- You want the fix done, not a 60-page PDF describing it
Probably not, if…
- The site is on a closed platform (Wix, Squarespace) where the theme cannot be edited — we can advise, but not fix
- You are about to rebuild anyway — put the budget into the new build instead
- You need a guaranteed lab score of 100 — we optimise for field data, which is what Google actually uses
Fixed price, quoted after a free audit
The audit is fixed-price and quoted after a free 15-minute look at your field data. Implementation is priced per ranked item, so you can stop at any point and still have the biggest wins in hand.
Questions we are asked most
What are Core Web Vitals?
Three measurements Google takes from real Chrome users: Largest Contentful Paint (how quickly the main content appears — "good" is under 2.5 seconds), Interaction to Next Paint (how quickly the page responds to a tap or click — good is under 200 milliseconds), and Cumulative Layout Shift (how much the layout jumps around — good is under 0.1). Google assesses them at the 75th percentile of visits over a rolling 28-day window, per group of similar URLs.
Why does my PageSpeed score look fine but Search Console says "Poor"?
Because they measure different things. The score is a lab test of one load on a simulated device. Search Console reports field data from real users, who have slower phones, worse connections, cookie banners, logged-in sessions and third-party tags the lab never sees. We work from the field data because that is what affects rankings and what your visitors actually experience.
How much faster will my site get?
It depends entirely on what is wrong. Image and font fixes alone commonly halve Largest Contentful Paint. A page-builder theme with forty plugins may need re-templating to pass Interaction to Next Paint. The audit gives you the expected gain per item before you commit to any of it, so there are no surprises in either direction.
Do you work on WordPress and Shopify sites?
Yes — most speed work is on WordPress, WooCommerce and Shopify, because that is where most slow sites live. We also fix Laravel, Next.js and fully custom builds. Closed platforms where the theme cannot be edited are the one place we can only advise rather than implement.
How long until Google sees the improvement?
Lab results are immediate. Field data updates daily but is assessed over a 28-day window, so Search Console typically shows the full effect three to five weeks after the fixes go live. That is why our verification report is scheduled for day 28 rather than day one.
Will faster pages improve my rankings?
Core Web Vitals are a confirmed ranking signal, and slow pages also convert worse and get crawled less often. Speed alone rarely moves a page from position 30 to position 3 — content and links do that — but it removes a penalty and improves every visit you already get. Our article on speed and conversion rate has the numbers.
Related services
Further reading
Find out which of your pages are failing — and why
Send your URL. We check your field data and come back within 48 hours with the failing templates, the causes, and a fixed price to fix them.