Performance & SEO
Advanced Technical SEO & Core Web Vitals
We work in the codebase, not on a list of recommendations. Core Web Vitals measured from field data, validated structured data, and performance budgets that break the build before the site degrades.
1 per serviceA page of its own for every service · Dra. Yuly Aldana
Sound familiar?
- Search Console flags URLs with poor Core Web Vitals and you do not know where to start.
- Your site scores well in Google tooling but users complain that it feels slow.
- You publish content consistently and rankings do not move.
- Someone optimised the site a year ago and it has degraded again since.
What Google actually measures
Three things, and none of them is a score. Time until the main element of the page appears, visual stability while it loads, and responsiveness to the first interaction. They are collected from real browsers, not a simulation, and aggregated over a 28-day window.
That is the source of the most common gap: a site with a high lab score and poor field metrics. The lab tests one load on an ideal device; the field includes the person arriving on a mid-range phone over mobile data, who is usually a large share of your real traffic.
Why optimisation unwinds on its own
Because nobody is measuring at the moment it breaks. The site gets optimised, the score is celebrated, and over the following months in come an analytics tag, a chat widget, a new font and three uncompressed images. Each change costs little; the sum returns the site to where it started.
The fix is not repeating the audit every year, it is putting the limit into the process: budgets checked in CI that fail the build when a change degrades the site. The correction now happens before publishing rather than six months later.
And crawling?
This is the part almost nobody looks at, and usually where the immediate headroom is. Filters generating thousands of equivalent URLs, endless pagination, parameters duplicating content: Google spends crawl budget there that it should be spending on the pages that actually sell.
What you get
- Audit prioritised by impact, not a list of 200 warnings with no hierarchy.
- Fixes implemented, not just recommended - we work in your codebase.
- Complete structured data, validated in the rich results tool.
- Performance budgets in CI that break the build when they are exceeded.
- Crawl budget review - what Google is crawling that it should not be.
- Monitoring dashboard with field data and alerts when a metric degrades.
How we work
- 01
Audit
1 to 2 weeksFull crawl, Search Console field data, lab testing and template review. Prioritised by estimated impact, not by warning count.
- 02
Implementation
2 to 6 weeksFixes in your codebase, in batches, measuring after each one. Your development team takes part if you have one.
- 03
Hardening
1 weekPerformance budgets in CI and a monitoring dashboard, so the improvement does not quietly unwind.
Investment
Scoped quote
A costed proposal within 3–5 business days
Scope drives price. Send us the project: within one business day we tell you whether it fits, and the proposal — what is in, what is out and what it costs — arrives within three to five business days.
The range depends on site size and on whether we implement the fixes or hand the audit to your team. The number comes out of the scoping call.
Proof of work
Frequently asked questions
Why is my Lighthouse score good while users complain?
Because they are two different measurements. Lighthouse is lab data: a simulated device, a simulated network, a single load. The Core Web Vitals Google ranks with come from field data - your real visitors, on their own phones and connections, aggregated over 28 days. Optimising against the lab while ignoring the field is the most common reason rankings do not move.
Do you implement or only audit?
We implement. An audit that gets delivered and never executed changes nothing, and that is where most technical SEO work dies. If you have your own team we work with them and leave them the reasoning, not just the patch.
What is a performance budget?
A written limit - JavaScript weight, LCP time, layout shift - checked on every change before publishing. If a change exceeds it, the build fails. It is what stops the optimisation from unwinding on its own within six months, which is what always happens without one.
How long until rankings move?
Field Core Web Vitals are computed over a 28-day window, so the effect is not immediate even when the fix is. Crawling and indexing changes show up sooner, within weeks.
Does this work on a site you did not build?
Yes, that is the most common case. We work on whatever platform you have. If the problem turns out to be structural and fixing it costs more than rebuilding, we say so in the audit instead of billing for patches.