I find out why your site is slow
For teams with one or two developers, or a site an agency builds for you. I look at what your real visitors wait for, find the cause, and write down the fixes in the order to build them. Then we go through it together. One fixed price, done within a week.
Some of the teams I've worked with
What an audit with me looks like
An audit answers three questions: what's slow, why, and what to fix first. I answer them with your field data, and I write the answers down for whoever builds your site.
-
Your field data first
I start with what your real visitors experience at the 75th percentile: the CrUX data Google uses, and your own RUM data if you have it. No RUM? Then I add CoreDash while I audit, so I can see which element, script or image each problem comes from.
-
Template by template
Then I go through the templates that make you money: home, category, product, article, checkout. I trace them in Chrome, request by request, until I know what causes each problem and which fixes depend on each other.
-
A report your developers can build from
Each finding gets the cause, the effect and the fix, with code examples. In order: what goes first, what can wait, and what only pays off once something else is done. Written for a developer, with a one page summary on top for you.
-
We go through it together
Then we sit down with whoever builds your site: your developer, your agency, or both. They can ask me anything, and they leave knowing what to build on Monday.
What does a Core Web Vitals audit cost?
One fixed price, agreed before I start. You get it within a week once I have access. If I find something big and simple on day one, you hear about it on day one.
- Me, not a junior consultant with a checklist
- Your field data and your templates, one by one
- Each problem with its cause, its effect and the fix
- Code examples your developer or agency can use
- The fixes in the order to build them
- A call to go through it with whoever builds your site
One fixed price
For a typical site with a handful of templates. Several domains, a lot of languages or a big platform? Then you get a quote after our first call.
€1,500 fixedwithin a week
It starts with your URL
Fill in the form with your site and what's going on. It lands in my own inbox. Before we talk I look at your CrUX data, so the call is about your site.
-
Send me your URL
Tell me what's bothering you and who builds the site: your own developer, an agency, or both. I reply within a day.
-
A 20 minute call
I've already looked at your data, so we spend the time on what worries you and on what your team can take on.
-
A fixed price and a start date
You know what the audit covers and what it costs before I start. And if the call shows you don't need an audit, I'll tell you.
Written for your developer or your agency
Whoever builds your site gets the same thing from me: specific fixes, in order, and a call to go through them.
One or two developers can't know everything
They build features all week, and performance is one of fifty things they're expected to know. The audit tells them where to look and why, so they spend their time fixing instead of searching. And they get to ask me the questions they couldn't google.
Specifics instead of "the site is slow"
An agency builds for a lot of clients, and a vague complaint is hard to act on. The audit gives them the element, the script and the fix, and I'm happy to go through it with them directly. I work with agencies all the time. It also gives you something to check: each fix is in writing, and your field data shows whether it worked.
The audit
What is a Core Web Vitals audit?
I measure where your real visitors wait, find out why, and write down what to fix, in the order to fix it. It's based on your field data, the same data Google uses, and it ends with a call where we go through it with whoever builds your site.
Is the audit based on Lighthouse?
No. Lighthouse is one simulated phone on one connection. Google looks at what your real visitors experience at the 75th percentile, and so do I. I use lab tools to find out why something is slow, not to decide whether it is.
How long does an audit take?
Within a week from the moment I have access. Bigger sites take longer, and you know how long before I start.
What do you need from us?
Your URL, access to Search Console if you have it, and your analytics. Access to the code helps, but it isn't required. Most of what I need happens in the browser.
Our site runs on Shopify or WordPress. Can you audit it?
Yes. On a hosted platform you can't change the platform itself, but the theme, the apps and the scripts they add are yours, and most of the problems are in there. The same goes for a WordPress theme and its plugins.
Can you audit a site that isn't live yet?
Yes, on staging. Without real visitors there's no field data, so I lean on lab tests and on what I've seen break on similar sites. Once it's live, the field data tells us if I was right.
After the audit
Do you fix the problems yourself?
No. The audit tells you what to fix, and your developer or agency builds it. If you want me there while they build, that's consultancy.
Our site is built by an agency. Does that work?
Yes. I write the findings so a developer who has never met me can build them, and I'm happy to go through them with the agency directly. They get specifics, you get something to check them against.
What if questions come up while they build?
Mail me. A fix that turns out harder than it looked, or a result that doesn't match what I expected: that's part of the audit, not an extra.
How often should we get an audit?
Usually once, and again after a redesign, a new theme or a platform migration. With RUM and alerts you know when something gets slower, so you don't need an audit every year.
