Core Web Vitals fix
I make your site fast myself, whatever it's built on. I work on a copy first and measure the result in your real visitor data. You know the price before I start.
Some of the teams I've worked with
Red in Search Console and no developer to call
Most slow sites are slow for a handful of reasons, and most of them are configuration. WordPress, Shopify, Next.js, Nuxt or a PHP site somebody built in 2012: the browser doesn't care what built the page, and the browser is where I work.
- Search Console
Core Web Vitals assessment failed
Search Console sends the email, PageSpeed Insights is red on mobile, and there's nobody in-house to look at it. Often it's two or three settings: the hero image is lazy loaded, the caching plugin skips the pages that matter, or the fonts come from three places at once.
- Apps and plugins
Every app you added made it slower
Reviews, chat, a product filter and a few tracking pixels. Each one loads its scripts on every page, and together they make every tap feel slow. You keep the apps. I change where and when they load.
- The last attempt
You paid for speed before and it didn't stick
A plugin or a freelancer promised 90+. The score went up because your scripts now wait until someone scrolls, and your real visitors never noticed. I take the trick out and fix what was underneath.
What a fix with me looks like
A fix is for a site with a few clear problems. I find them, fix them on a copy of your site, and check afterwards that your real visitors got faster.
-
I measure first
Before I change anything I look at your p75 on mobile for LCP, INP and CLS, and at which pages Search Console flags. I add CoreDash to your site, so we see every change land in real visitor data within a day.
-
I fix it on a copy
I work on a staging site, a copy of your theme or a branch of your code, so your live site keeps running while I change things. Settings first, then code: the right hero image preloaded, app scripts only where they're needed, one source for your fonts.
-
You check it, then it goes live
You click through the copy and see it's still your site, only faster. When you're happy, it goes live.
-
I check your field data
After the release I follow your real visitors in CoreDash for three months and send you the before and after. Search Console catches up more slowly, because it shows the last 28 days.
What I usually find, per platform
- WordPress
Elementor, Divi, Astra
A page builder loading its CSS and JavaScript on every page, and a caching plugin that skips the pages that matter. More in my WordPress guide.
- Shopify
Dawn, Horizon, Prestige and the rest
Apps injecting scripts on every template, and a hero slider that hides the LCP image from the browser until the slider script runs. More in my Shopify guide.
- Next.js and React
Hydration and third parties
Hydration blocking the first tap, the LCP image rendered on the client, and third-party scripts loaded with the wrong strategy.
- Nuxt and Vue
Payload and hydration
A big page payload the browser has to parse before anything works, and components that hydrate even though they never change.
- Angular
Change detection
Change detection running through the whole app on every tap, and a main bundle that has to load before the first click does anything.
- Magento
The server and RequireJS
Full-page cache misses on the pages that sell, and dozens of RequireJS modules loading before the first tap works.
- Webflow and Framer
Animations on load
Elements that start invisible until an animation script fades them in, which pushes back the LCP, and custom code embedded on every page.
- Laravel and custom PHP
Time to first byte
A server that takes a second to answer before anything else can start, often one slow query that runs on every request.
If I help, I help
Before I take a job, I look at your site. Most of what makes a site slow is configuration: a lazy-loaded hero image, a caching plugin set up wrong, apps loading their scripts on pages that don't need them. That's what I fix. Some sites I can only make fast by stacking workarounds on top of what's there. Page builders are the usual example: every fix I add makes the site harder to maintain. Then it costs you more than it brings back, and I'll tell you what I'd do instead. I want your site fast after I leave, and still easy to work on.
What does a Core Web Vitals fix cost?
From €600 for a site that can be fixed quickly, up to about €2,800 when there's more to untangle. Once I've looked, you get the price for your site before I start. That's the most you'll pay: if it goes quicker, you pay less, and if I underestimate, I finish at my own expense.
- Me, doing the work myself
- The price for your site before I start
- Every change tested on a copy first
- CoreDash included, before and for three months after
- The before and after from your real visitors
- A short note of what I changed and why
The price before I start
For the problems that matter most on your site.
€600 to €2,800 excl. VATthe most you'll pay
Send me your URL
A line about what's slow is enough to start.
-
Tell me what's going on
Your URL, what's slow, and which theme and apps you use. If there's a deadline, like Black Friday or a campaign, mention it.
-
I look and send you a price
Usually within a day you get the price for your site, or a straight answer that a fix isn't the right route for it.
-
I get to work
You give me access to a copy of your site, I make the changes, and you approve them before they go live.
What a fix looked like at Nina.care
A fast-growing childcare platform on WordPress
Nina.care matches families with childcare workers, and it grew fast. Every new feature and every new country added a bit more to the WordPress site, until all three Core Web Vitals failed. I got the call while I was hiking in the Ardennes.
First I added CoreDash, so we could see what real visitors were waiting for. Then I did the programming myself and checked every change in their field data. LCP improved by 90%, INP by 45%, and the layout shift that made them fail Core Web Vitals is gone.
Jasmijn mailed afterwards: "Thank you so much for all that you have done for me and the boys! You feel like a part of the company and I like it."
The fix
Which platforms do you work on?
Pretty much all of them: WordPress with Elementor, Divi or Astra, Shopify, Next.js, React, Nuxt, Vue, Angular, Magento, Webflow, Framer, Laravel and custom PHP. The problems repeat across platforms more than you'd think.
Can you speed up a Wix or Squarespace site?
A bit. On Wix and Squarespace you can't touch the platform's own code, so I can only work on what you added: images, fonts, apps and embeds. I'll tell you up front whether that's enough to be worth my price.
Do you guarantee a 90+ score?
No. I make your site faster for real visitors, and that's what Google measures. A 90 in Lighthouse is easy to fake by holding back your scripts, and on some sites my first advice is to take out the plugin that does it.
Will you install a speed plugin?
Only if it's the simplest way to do it well. Most of the time I change settings and a bit of code in your theme, and nothing new gets installed.
Can you fix our Shopify apps?
I can't change an app's own code. I can change where and when it loads, and that's where most of the delay comes from. If an app is still too heavy after that, I tell you what it costs you, and you decide.
Do you take on every site?
No. I look first, and I only give a price when I'm sure the fix is worth it for you. Some sites need more work than a fix can cover, and then my hours would cost more than they bring back. I'll tell you what I'd do instead.
How is this different from an audit?
An audit tells you what to fix, and your developer builds it. With a fix I do the building myself. No developer of your own? Then this is the one.
Price and afterwards
What do you need from us?
Access to a staging site, your theme or your code repository, and someone who can say yes when the changes are ready. I set up the rest.
What happens when we update the theme?
On WordPress I put my changes in a child theme, so a theme update doesn't overwrite them. On Shopify a new theme version means some changes have to go in again, and my note says which ones. On Next.js, React, Nuxt or Vue the changes are in your own code, so they stay.
When will Search Console turn green?
Search Console shows the last 28 days, so it catches up gradually over the weeks after the release. CoreDash shows your real visitors the day after, so you don't have to wait to see if it worked.
What happens after the three months?
CoreDash can keep running, and I'd recommend it. A new app, a plugin update or an extra tracking script can undo a fix without anyone noticing. Real user monitoring tells you the day it happens, while Search Console needs weeks to show it.