SEO
eTilbudsavis
Technical SEO across borders
SEO analysis and technical optimisation focused on indexing, landing pages and visibility in Google.
Visit etilbudsavis.dk
Core Web Vitals
Core Web Vitals put right where the problem actually sits
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
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 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.
The work in practice
View all casesHow it works
Four steps. You know what happens when, and you can stop after any of them.
- 01
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.
- 02
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.
- 03
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.
- 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
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.
- 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.
- 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.