Core Web Vitals and speed

Two seconds on a phone or you do not pay the second half

A measured before, a fixed list of fixes, and a measured after you can check yourself

Roughly six in ten mobile sites fail Core Web Vitals, and every one of them loses visitors before the page paints. This is a fixed price job with a number at the end: field and lab measurements before, the fixes, and the same measurements after, on your own URL, in a tool you control.

Short answer

What do you guarantee exactly?

A target written into the contract before we start, based on what your platform can reach. Typically Largest Contentful Paint under 2.5 s and Cumulative Layout Shift under 0.1 on the templates in scope, measured on a phone profile. If the target is not met, half the fee comes back. What I cannot guarantee is a ranking, because speed is one factor among many.

What a slow site actually costs you

People leave before the page appears, and analytics records it as a visit you paid for.

Core Web Vitals fail, so pages that deserve position four sit at eleven.

Ads cost more per conversion because the landing page loses a third of the clicks you bought.

The checkout is the slowest page on the site, which is the worst possible place for it.

Every plugin added since launch made it slower and nobody measured.

It feels fast on your laptop on office wifi, which is not where your customers are.

What gets done, in order of impact

Images, the usual culprit

Modern formats, correct dimensions, lazy loading below the fold and a real priority hint on the hero. This alone commonly halves Largest Contentful Paint.

Fonts without the flash

Self hosted, subset to the characters you use, preloaded, with a fallback matched so the layout does not jump when the real font lands.

JavaScript you do not ship

Third party scripts audited one by one, chat widgets and trackers deferred or dropped, unused bundles removed. The fastest script is the one that never loads.

Layout that stays still

Reserved space for images, ads and embeds, so Cumulative Layout Shift stops being the reason people tap the wrong thing.

Server and cache

Time to first byte, caching headers, compression and a CDN in front. On a rented platform I fix what the platform allows and tell you plainly where the ceiling is.

Numbers before and after

PageSpeed Insights, a phone profile with an empty cache, and the field data in Search Console tracked for six weeks. You get the raw numbers, not a screenshot of a green circle.

Fixed price, with the result tied to a number

Speed audit

€300
  • Lab and field measurements on up to 5 templates
  • Every finding with the seconds it costs you
  • A prioritised fix list you can hand to any developer
  • A realistic target for your platform
  • Delivered in 3 working days
Get a speed audit
Most chosen

Audit and fixes

from €900
  • Everything in the audit
  • Images, fonts, scripts, layout shift and caching fixed
  • Retested on the same profile
  • Six weeks of field data watched in Search Console
  • Half the fee back if the targets in the contract are not met
Get a speed audit

Shop or large site

from €2,200
  • Category, product and checkout paths
  • Third party and tag manager cleanup
  • Component level fixes so new pages stay fast
  • A budget your team can hold afterwards
  • Priced after a call, with a written target
Get a speed audit

What the numbers mean, in plain words

Largest Contentful Paint
What it measures
when the main thing appears
Passing
under 2.5 s
The usual cause when it fails
an unoptimised hero image, a slow server, render blocking CSS
Interaction to Next Paint
What it measures
how fast the page reacts to a tap
Passing
under 200 ms
The usual cause when it fails
too much JavaScript running on the main thread
Cumulative Layout Shift
What it measures
how much the page jumps while loading
Passing
under 0.1
The usual cause when it fails
images and embeds with no reserved space, late loading fonts
Time to first byte
What it measures
how long the server thinks
Passing
under 0.8 s
The usual cause when it fails
shared hosting, database queries, no caching

Google grades these on real visitor data from the last 28 days, not on the score from a single test run, which is why a green lab score alone proves nothing.

What the market charges

Published 2026 pricing for the same work: around 500 to 1,500 dollars for a one off pass on a growing business site, and 1,800 to 4,800 a month at larger agencies that bill hourly and carry overhead. Roughly 40 percent of mobile sites pass Core Web Vitals, so most of the market is a customer.

The audit here is 300 euro and the fixes start at 900, with the target written into the contract. The difference is structural, not a discount: one person, no account management, and no retainer to renew.

When speed is not your problem

  • If the site already passes on real field data, do nothing. I will show you the Search Console chart and refund the audit if I sold you one you did not need.
  • If the platform itself is the ceiling, the money is better spent moving: WordPress to Next.js migration.
  • If people arrive and leave because the page does not answer their question, that is content, not milliseconds: AI search visibility.

How to get an exact price

Send the URL of your slowest important page. I will run it before quoting, so the first thing you get back is a number rather than a proposal. The form is three fields, or Viber on 087 727 5750, and the answer comes within 24 hours.

Questions about speed work

What do you guarantee exactly?
A target written into the contract before we start, based on what your platform can reach. Typically Largest Contentful Paint under 2.5 s and Cumulative Layout Shift under 0.1 on the templates in scope, measured on a phone profile. If the target is not met, half the fee comes back. What I cannot guarantee is a ranking, because speed is one factor among many.
Will my rankings improve?
Sometimes, and rarely on their own. Core Web Vitals are a tiebreaker: when two pages answer a query equally well, the faster one wins. If your page does not answer the query, making it fast makes it a fast page nobody wants. I will tell you which of the two problems you have.
How long does it take?
Three working days for the audit. One to two weeks for the fixes on a normal site, longer for a shop with a complicated checkout. Field data in Search Console needs about 28 days to reflect the change, which is why I watch it for six weeks.
Can you speed up WordPress?
Yes, and often dramatically, by removing plugins, fixing images and getting the theme to stop loading everything on every page. There is a ceiling: a page builder generating heavy markup will not reach what a server rendered site does. I will say where that ceiling is and what it would take to pass it.
What about Shopify, Wix or Squarespace?
I fix what those platforms allow: images, apps, scripts, fonts and layout shift, which is usually most of the gap. I cannot change their server or their core bundle, and I will not pretend otherwise.
Will it stay fast?
The fixes live in the code and the components, so new pages inherit them. What breaks it later is a new tracking script or a big image uploaded without resizing, which is why the report ends with a short budget your team can check in two minutes.
Why is this cheaper than the agencies?
Agencies charge 500 to 1,500 for a pass or run 1,800 to 4,800 a month on a retainer, and both numbers carry account management and sales. There is no agency here. There is also no retainer, because speed work is a project with an end, not a subscription.
Do I need this if my site is new?
If it was built in the last year on a modern stack and already passes, no, and I will say so after the audit rather than invent work. Send the URL and I will run it before you pay for anything.

Send me your slowest page

I measure it before quoting. If it already passes, I will tell you and there is nothing to buy.

Get a speed audit

Targets in the contract, half the fee back if they are not met.