Skip to main content

Get your Core Web Vitals in order

Core Web Vitals are Google's measures of how fast and stable your website feels to real visitors. I have worked with speed optimisation since 2010 and fix the causes in the code instead of chasing a test score. You get measurements before and after, so the effect can be documented.

  • I usually reply the same day
  • Written estimate before work starts
Mikkel Tschentscher

star reviews

Read every review
  • Sets the standard for other suppliers

    Warning: work with Mikkel and you risk damaging your relationship with every other supplier you have. It happens because he sets, by nature, an extraordinary standard for flexibility, decency and not least delivery time.

    Thomas Von BigumInstructor(translated from Danish)
  • Carries the project all the way through

    When you work with Mikkel, you can be certain the project gets carried 100% of the way.

    Simon Bille Hjort MartinsenColleague at Bigum&Co(translated from Danish)
  • The most solution-oriented developer

    In Mikkel's world there are challenges rather than problems.

    Michael Roscoe PedersenEntrepreneur(translated from Danish)

Core Web Vitals

LCP is the metric that fails most often

The large image at the top of the page is behind most of the poor LCP numbers I meet. Either it is uploaded at far too high a resolution, or it sits behind several layers of JavaScript that must run before it shows.

The solution is rarely complicated: scale the image correctly, serve it in a modern format, prioritise its loading, and drop the carousel that waits for an entire library.

Typical tasks in a speed optimisation

  • Images scaled, compressed and served in modern formats like WebP or AVIF.
  • Third-party scripts mapped, and the ones nobody uses removed or deferred.
  • INP improved by moving heavy JavaScript off the main thread.
  • CLS eliminated with fixed dimensions on images, banners and embeds.
  • Fonts loaded so text does not jump or stay invisible while the page loads.
  • Field measurement set up so the improvements can be read off real visitors.

Measuring before and after

Before I change anything, I set up measurement on real visitors. That gives us a baseline, and we avoid arguing over a lab score that swings from test to test.

The Chrome UX Report gives a solid picture on sites with enough traffic. If the traffic is too small, I set up a simple measurement of my own instead, which costs nothing to run.

What are Core Web Vitals?

Core Web Vitals are three measurements Google uses to judge the experience of a website: LCP for how quickly the largest content appears, INP for how quickly the page reacts to taps and clicks, and CLS for how much the layout jumps during loading. The numbers are collected from real Chrome users and feed into Google's assessment of the page.

Everyone with a website should know their numbers, but the need for optimisation is greatest for webshops and lead-generating sites, where slow pages directly cost revenue. Mobile visitors have short patience, and they leave long before a five-second page has finished.

Speed optimisation is offered by many, but part of the market consists of installing a caching plugin and calling it a solution. Caching helps the server's response time and does nothing about the megabyte of JavaScript the browser still has to chew through. The real causes sit in images, scripts and loading order, and they require someone who can change the code.

That is the kind of work I have done since 2010, on everything from WordPress and Shopify to custom-built Next.js solutions. You get a review of what really slows the page, a prioritised plan and the fixes themselves, implemented by me.

INP: when the page is slow to respond to clicks

INP stands for Interaction to Next Paint and measures how long it takes from a visitor clicking, tapping or typing until the page shows a response. The measurement covers all interactions during the visit, and it is one of the slowest that counts. INP replaced FID as a Core Web Vital in March 2024. FID only measured the delay on the first click, so a site may well have passed on FID and still fail on INP.

The threshold for a good INP is 200 milliseconds, and above 500 milliseconds counts as poor. The cause is almost always JavaScript occupying the browser's main thread. While a script runs, the page cannot respond, and a task taking more than 50 milliseconds is called a long task. Typical culprits are third-party scripts for chat, tracking and A/B testing, heavy page builders, and menus or filters that recalculate the whole page on every click.

The fix is to give the browser breaks. Long tasks are split up so the page can respond in between, scripts not needed straight away wait until the page has loaded, and third-party scripts nobody uses are removed. It also helps to show a response immediately, for example the button changing appearance while the heavy work runs afterwards. This is work in the code, and a plugin can rarely solve it.

CLS: when the content jumps

CLS stands for Cumulative Layout Shift and measures how much the content moves while the page loads and is used. You will know it from the article where the text suddenly drops because a banner appears just as you are about to tap a link. A good CLS is 0.1 or below, and above 0.25 is poor. Shifts that happen right after the visitor has clicked do not count.

The classic causes are few and well known. Images and videos without set dimensions, so the browser does not know how much space they need before they have loaded. Ads, cookie banners and newsletter boxes inserted above the content instead of having a reserved space. And web fonts swapped in once they have loaded, so the text suddenly takes up more or less room and pushes the rest of the page.

The fixes are just as concrete. Set width and height on all images and embeds, or give them a fixed aspect ratio in CSS. Reserve space for banners and ads before they load, and lay the cookie banner over the page instead of pushing it down. Load the fonts early and pick a fallback font with the same proportions, so the swap cannot be seen. Animations should use transform, which does not move the layout.

How to read the Core Web Vitals report in Search Console

The Core Web Vitals report in Search Console shows field data for the whole site at once, split into mobile and desktop. Every URL gets one of three statuses: Good, Needs improvement or Poor. The status is set by the worst of the three metrics, so a page with fine LCP and CLS but poor INP is listed as poor. The numbers are based on the 75th percentile of visits over the last 28 days.

The report does not show every page on its own but gathers similar URLs into groups, typically pages built on the same template, and gives the group one overall assessment with a few examples. That is an advantage, because the problem nearly always sits in the template rather than the individual page. If a page has too few visits for its own data, it is assessed from its group. If the whole site has too little traffic, the report is empty.

Once a fix has gone live, you can ask Search Console to validate it. Search Console then follows the group for 28 days before passing it, because the field data has to be replaced first. That is why you see no effect in the report the next day. In the meantime you can use the lab test in PageSpeed Insights to confirm the fix works, while the field data slowly follows.

Core Web Vitals optimisation across Denmark

Speed optimisation happens in code and measurement data, so I help companies across the whole country from my base in Glostrup near Copenhagen. Clients include webshops and company sites in Copenhagen, Aarhus, Odense and Aalborg plus a handful outside Denmark.

The process needs no physical meetings: I get access to the code and the measurement tools, make a plan, and we take decisions over video or email. If you are in the Copenhagen area and prefer to meet, we do that of course.

The tasks typically come from shops whose mobile pages pass in the lab but fail in the field, from marketing departments told the site is too slow without anyone able to say why, and from development teams wanting an extra pair of hands specialised in performance.

As a freelancer I skip the layers: no relaying between consultant and developer, because I am both, and no ongoing contract beyond the agreed task. Call +45 22 51 31 79 if you want to talk through your site's numbers.

Lab and field are not the same

PageSpeed Insights shows two sets of numbers, and most people look at the wrong one. The big coloured score is a lab test: a simulated load on a simulated phone over a simulated connection. It is good for debugging because it is reproducible, but it does not say how the page feels to real people.

The field data above it, from the Chrome UX Report, is what Google actually uses. It comes from real visitors on real devices, collected over 28 days, and it is what decides whether the page passes.

The distance between the two can be large. I have seen sites with a lab score of 95 and field data that fails, because the users sit on older Android phones on the train. The reverse exists too: a mediocre lab score and fine field numbers, because the visitors come from offices with fast connections.

The consequence is simple. Optimise for the field numbers, and use the lab test as a magnifying glass when the cause needs finding. That is how I work, and it is why measurement comes before the fixes.

What you get

Concrete deliverables, not a report of recommendations someone else has to find time for.

  • Field measurement

    Numbers from real visitors before we change anything, so the improvements can be documented instead of debated.

  • An improved LCP

    The image at the top scaled, converted and prioritised in loading, where the biggest win almost always sits.

  • Scripts cleaned up

    A map of what loads when, and what can be deferred or removed without anyone missing it.

  • Before-and-after documentation

    The same field measurement repeated once there are enough visits for the numbers to be trustworthy, typically after about four weeks.

View all cases

How it works

Four steps. You know what happens when, and you can stop after any of them.

  1. 01 / 04

    Crawl and data review

    I crawl the entire site and go through Search Console for indexing errors, coverage and search terms. That gives a picture of how far from your potential you are before anyone touches anything.

  2. 02 / 04

    Prioritised by impact

    The findings go into a list sorted by what moves the most for the least work. Each item comes with its reasoning, so you can challenge the priorities if you disagree.

  3. 03 / 04

    Implementation in the code

    The fixes are written and shipped by me: redirects, canonical tags, structured data, speed. If you have your own dev team, I deliver precise, testable tickets for them instead.

  4. 04 / 04

    Measuring the effect over time

    Rankings and organic traffic are tracked in the weeks that follow, and you get a short status every month. If a number goes the wrong way, I dig into why instead of dressing up the graph.

Brands I've worked with

  • MT Højgaard Danmark
  • Egmont
  • NNIT
  • Visma
  • Lomax
  • Pascal
  • able.
  • OOONO
  • Novo Nordisk Fonden
  • Energii
  • Maersk Tankers
  • Nordkysten Entreprenørfirmaet

Frequently asked questions

What does Core Web Vitals optimisation cost?

The price depends on how many page types need optimising, which platform the site runs on, and how much third-party code is involved. Send a URL, I will look at the numbers and come back with a concrete quote the same day.

How do I test Core Web Vitals?

Start with PageSpeed Insights. At the top you see data from real Chrome users over the last 28 days, if the site has enough traffic, and below that a lab test of a single load. The Core Web Vitals report in Search Console shows the numbers across the whole site, grouped into similar URLs. Lighthouse in Chrome's developer tools gives a score from 0 to 100 but is only a lab test. It is useful for finding causes, while the assessment itself is decided by the field data.

What is a good LCP score?

Google counts an LCP under 2.5 seconds as good, between 2.5 and 4 seconds as needing improvement, and over 4 seconds as poor. The good threshold for INP is 200 milliseconds and for CLS 0.1. The target applies to 75 percent of visits, so it is the slow phones that decide it, not your own computer.

What is INP?

INP (Interaction to Next Paint) is the Core Web Vital that measures how quickly the page responds when someone clicks, taps or types. A good INP is 200 milliseconds or less, and above 500 milliseconds is poor. INP replaced FID in March 2024, and a poor INP is most often caused by heavy JavaScript or third-party scripts blocking the browser.

What is CLS?

CLS (Cumulative Layout Shift) is the Core Web Vital that measures how much the content jumps while the page loads. CLS should be 0.1 or lower, and above 0.25 counts as poor. The most common causes are images without fixed dimensions, banners pushing the content down, and fonts that swap once they have loaded.

How do you pass the Core Web Vitals assessment?

The assessment in Search Console and PageSpeed Insights is based on real users' data from Chrome over the last 28 days. To pass, all three metrics, LCP, INP and CLS, must be good for at least 75 percent of visits. That is why a fix only shows up in the assessment a few weeks after it goes live.

What do Core Web Vitals cover?

Three measurements from Google: LCP for loading speed, INP for responsiveness to clicks and taps, and CLS for visual stability. They are collected from real Chrome users and show how the page is actually experienced, not how it does in a test.

Why does PageSpeed Insights show something different from Search Console?

Because they show different slices of the data. PageSpeed Insights shows field data for the individual URL, or for the whole domain if the URL has too little traffic, plus a lab test of a single load. Search Console gathers similar URLs into groups and assesses each group as a whole. Both are based on the Chrome UX Report over 28 days, so it is usually the lab score that differs.

Do you optimise sites for companies outside Copenhagen?

Yes, speed work only requires access to code and measurement data, so I have solved tasks for clients in Aarhus, Odense, Aalborg and further away. In-person meetings are an option in the Copenhagen area, never a requirement.

How quickly can you see results from SEO?

Speed improvements are felt by visitors immediately, but in Google's field numbers it takes up to 28 days before the effect is fully visible, because data is collected on a rolling basis. Any movement in rankings must, like all other SEO, be measured over months.

Do Core Web Vitals matter for rankings in Google?

Somewhat, but less than many think, and I will not oversell it. The big gain is in conversion: people who wait buy less, especially on mobile. I would optimise speed even if Google did not measure it.

Is a caching plugin not enough?

It improves the server's response time but does not touch the JavaScript the browser must execute or the images that are too large. Most sites I see already have a caching plugin, and the problem sits elsewhere.

How much can the numbers realistically improve?

On an average WordPress or Shopify site, halving LCP is not unusual, because the first fixes are the easiest. After that it gets progressively harder, and I will say so when we reach the point where the effort no longer matches the gain.

Can speed be improved without changing the design?

In the vast majority of cases yes, because it is about what loads when, not how the page looks. If the design has a five-image carousel at the top I might suggest trimming it, but that is a recommendation you are free to decline.

Define the scope of your task

Send your website URL, what you need solved and your desired deadline. I will assess the next step and describe what the quote includes. Larger investigations are agreed separately before work begins.

Describe your task

Your next step

Get a quote for Core Web Vitals

Tell me about your project. I’ll get back to you with questions, options and a concrete next step.