An audit on real-user data and the fixes shipped in code —
so the site is fast on your customer’s phone, not just in Lighthouse.
Three numbers Google collects from your visitors
Core Web Vitals are three measurements Chrome collects from real people visiting the site: LCP (how fast the main content appears, good up to 2.5 s), INP (how fast the page responds to a tap or click, good up to 200 ms) and CLS (whether the layout jumps while loading, good up to 0.1). Google judges the page by the 75th percentile over the last 28 days — how it works for the slower part of your audience, not on your laptop.
That is why Lighthouse can show 95 while Search Console still reports “poor URLs”. I start the audit from field data and use lab traces to find the cause: a specific image, font, script or element that shifts the layout.
Speed is one ranking signal, not the main one — the real gain is fewer people leaving before the page loads. If the site runs on WordPress, the WordPress speed-up is the simpler and cheaper route. If it is past fixing, see web development. And if the site also has to meet WCAG, the accessibility audit covers the other half of the same code.
The audit, or the audit with the fixes
Net prices, “from” — the quote depends on the number of templates and third-party scripts, not on the page count. Quote within 24 h.
Core Web Vitals audit
I find what slows the site down for real users and you get a list of fixes.
- Field data: the CrUX report and Search Console, not just Lighthouse
- LCP, INP and CLS separately on mobile and desktop
- The cause of every issue: image, font, script, element
- Prioritised fixes with an effort estimate
- What you can do yourself and what needs a developer
Audit + fixes in code
The audit, then I ship the fixes in the site code and check the result.
- Everything in the audit
- Images, fonts, the loading order of CSS and JS
- A stable layout: space reserved for images, banners and embeds (CLS)
- Faster response to taps: shorter JavaScript tasks (INP)
- Third-party scripts trimmed, agreed with you
- Measured before and after, then field data checked after 28 days
WordPress speed-up
Running WordPress? There is a separate fixed-price service for that.
- Caching, images and a plugin clean-up
- Fixes aimed at Core Web Vitals
- Measured before and after
I audit any platform. I ship the fixes wherever I have access to the code or the theme; on closed platforms (Wix, Shopify, a bought theme) you get a list of changes for the vendor and I check the result.
What you get
A report that says what to fix and in which order
Not a PageSpeed Insights screenshot — causes and fixes, starting with the ones that pay off most.
Field data
The CrUX report and Search Console show how the site works for real people. That is where I start, because those are the numbers Google judges.
LCP — the main content
What delays the largest element: a slow server, a heavy image, a font, render-blocking CSS.
INP — response to a tap
Which scripts keep the browser busy when someone taps the menu, a button or a form. Most often third-party ones.
CLS — the jumping layout
Images without dimensions, cookie banners, ads and fonts that move the content under the user’s finger.
Fixes in your code
The changes go into your site, its templates and styles. No plugins that promise “100 points” in one click.
Measured before and after
Lab data right after the release, field data after 28 days. You see what changed, in the same numbers Google uses.
What I do, and what I do not promise
Speed is the state of a site at a point in time, not a badge. Every new plugin and every new script can undo it.
What I do
I find the causes of slow loading and fix them in the site code.
- • An audit on field and lab data
- • Fixes in templates, styles and the way scripts load
- • Measured before and after in the tools Google uses
- • Short guidelines so new content does not undo the fixes
What I do not promise
I do not sell “100 in PageSpeed” — that is a lab score, and Google judges real-user data.
- • No promise of higher rankings — Core Web Vitals are one signal among many
- • No plugins that only improve the test score
- • Chat widgets, ads or analytics sometimes cannot be sped up, only trimmed — your call
- • On closed platforms some changes depend on the vendor
How it works
From the site address to the 28-day check
The audit usually takes 2–4 working days, the fixes a week or two. Field data needs 28 days to show the full effect.
Request and quote
Send the site address and what it runs on. You get a quote and a date within 24 h.
Audit
Field data first, then lab performance traces for the key templates.
Report
A prioritised list of causes and fixes. We go through it by email or on a short call.
Fixes
The changes go into the site code, highest impact first. Lab measurement right after the release.
28-day check
I check the field data and the Search Console report once new measurements come in.
FAQ
Frequently asked questions
What are Core Web Vitals, in plain terms?
Three speed measurements Chrome collects from real users: LCP says how fast the main content appears (good up to 2.5 s), INP how fast the page responds to a tap or click (good up to 200 ms), and CLS whether the layout jumps while loading (good up to 0.1). Google looks at the 75th percentile over the last 28 days.
How much does Core Web Vitals optimization cost?
The audit is from €169 net, the audit with the fixes in code from €449 net. The quote depends on the number of templates and third-party scripts, not on the page count. WordPress sites have a separate speed-up from €200 net.
Will better Core Web Vitals raise my Google rankings?
They can help, but I do not promise it. Core Web Vitals are part of how Google assesses a page, while content and relevance weigh far more. The surer gain is fewer people leaving before the page loads — especially on phones and weak connections.
Lighthouse says 95, Search Console says “poor URLs”. Why?
Because they are two different measurements. Lighthouse tests one page load in controlled conditions; Search Console shows data from real users on different phones and connections, with and without cache. Google judges the second, so that is where I start.
What if my site has little traffic and no CrUX data?
Then I work from lab measurements of the key templates and, if you want, add a lightweight real-user Core Web Vitals measurement to your analytics. After a few weeks you have field data of your own.
Will the fixes change how the site looks?
Usually not. Most changes are invisible: loading order, image formats and sizes, the way fonts and scripts load. Sometimes small things show — space reserved for an image or a banner that no longer pushes the content down.
Which platforms do you work on?
I audit any site. I ship fixes in code on hand-written sites, Astro, Vue, Laravel and themes I have access to. WordPress has its own speed-up service, and on Wix or Shopify you get a list of changes for the vendor.
How long does it take?
An audit of a typical company site takes 2–4 working days, the fixes a week or two. The lab result shows immediately; field data and Search Console catch up after about 28 days, because that is their window.
Get a Core Web Vitals quote
Send the site address and what it runs on — I will reply with a quote within 24 hours.