Core Web Vitals optimisation
LCP targets, INP budgets, CLS fixes grounded in field data where available.
Core Web Vitals · Speed · Bundles
Website optimisation that improves experience and ranking
Most slow sites are a stack of fixable decisions: oversized JavaScript, weak caching, blocking third parties, and layouts that fight the browser. I help teams improve website speed with a senior engineer’s lens: Core Web Vitals optimisation, bundle discipline, and instrumentation you can trust.
The problem (and why it compounds)
If you are asking why is my website slow, the answer is rarely one line in DevTools. It is usually a mix of:
Google’s Core Web Vitals (LCP, INP, CLS) are not vanity metrics. They track how users perceive quality, and they are a practical forcing function to reduce page load time in ways that actually matter.
For motion and micro-interactions, see Animation or selected websites.
- Heavy client bundles that delay interactivity
- Render-blocking resources and unoptimised fonts
- Third-party scripts that hijack the main thread
- Layout instability that makes clicks feel unreliable
- Weak caching and edge strategy on repeat visits
What I do
Measurable, maintainable work aligned with your stack, not random micro-optimisations. If your team ships React, Next.js, or Astro, I work in-repo and leave things cleaner than I found them. See also templates.
Bundle size reduction
Dependency audits, tree-shaking discipline, safer imports, smarter build output.
Lazy loading & code splitting
Route-level and component-level splits that do not wreck UX.
Static-first delivery
Pre-rendered HTML where it fits, lean islands when you need them, and fewer moving parts so performance stays predictable.
Image optimisation
Modern formats, explicit dimensions, responsive srcsets, and LCP-friendly loading so visuals stay sharp without tanking scores.
Process
- 01 Step 1 of 4
Audit
Baseline with Lighthouse (lab) and field data (RUM, CrUX, or analytics). Map critical journeys: landing, signup, checkout, dashboards.
- 02 Step 2 of 4
Identify bottlenecks
Prioritise by impact and risk: LCP/INP/CLS, JS execution time, repeat-visit performance.
- 03 Step 3 of 4
Implement fixes
Incremental changes with clear rollback paths. Fewer, higher-leverage edits over noisy churn.
- 04 Step 4 of 4
Measure improvements
Re-check vitals, watch regressions, and set guardrails: budgets, CI checks, monitoring alerts.
Results you can realistically expect
I will not promise magic numbers without measuring your site, but I will promise clarity: what is broken, what to fix first, and what “good” looks like for your business.
Load time
Faster templates
Especially when the baseline is heavy client-side JavaScript.
Core Web Vitals
Higher pass rates
After tightening third parties, images, fonts, and layout shifts.
SEO
Stronger signals
When speed and stability improve crawl efficiency and engagement.
Conversion
More reliable UX
When checkout and signup paths stay fast on real mobile hardware.
Case study
Independent · 2025
mymlancatamaran.com
Luxury Privilège catamaran charter site built with Astro, Tailwind, and bespoke video. Also listed on websites.
Context
A brochure-style site with full-bleed imagery and video: strong brand presence, but hero media and font loading risked slow LCP on mobile and unnecessary main-thread work on first paint.
Changes
Tighter image pipeline (dimensions, modern formats, responsive loading), disciplined video and third-party embed strategy, font subsetting and display rules, and static-first delivery so repeat visits stay cheap.
Outcome
A calmer first seconds on real devices: hero content becomes eligible for LCP sooner, less jank before scroll, and a codebase that stays easy to tune as the campaign evolves.
Ready to improve website speed?
If you want a senior frontend performance expert who can talk to founders and engineers in the same conversation, start with an audit. Broader delivery: Web Development.