Skip to content
Speed & Core Web Vitals

Find out why your site is slow, then fix that

Not a caching plugin and a hopeful re-test. We profile the page, identify what's actually blocking the render, fix those specific things, and show you the before and after on real mobile hardware.

The short version

Core Web Vitals and page speed optimisation

Speed advice online is mostly generic because the causes are specific. Your slow LCP might be a hero image nobody compressed, a font blocking the first paint, a render-blocking script from a chat widget, or a server taking 900ms to respond. The fix for each is different, and applying all four when you needed one wastes a week.

We start with a real profile: Chrome DevTools traces on throttled mobile, Lighthouse for the summary, and your own field data from Search Console — because lab scores and what your visitors experience regularly disagree. Then we work down the list in order of impact.

Every engagement ends with a report showing the numbers before, the numbers after, and exactly what changed. If we can't move a metric, we say why — sometimes the answer is a platform limitation and no amount of tuning fixes it.

What you end up with
  • LCP, CLS, and INP all in Google's "good" band on mobile where the platform allows it
  • A ranked fix list with effort and expected impact, so you can decide what's worth doing
  • Third-party scripts audited — the usual culprit, and the usual argument
  • A performance budget in CI so the gains don't quietly erode

0.0s

Median LCP improvement

Mobile, throttled 4G.

0

Median Lighthouse gain

Points, mobile performance.

1–3

Weeks per engagement

Depends on template count.

Scope

How we make sites faster

Real profiling

DevTools traces on throttled mobile, plus your Search Console field data. We diagnose from evidence, not from a checklist.

LCP work

Hero image sizing and formats, preloads, font display strategy, and server response time. Usually the biggest single win.

CLS fixes

Dimension attributes on images and embeds, space reserved for ads and banners, and font metric overrides to stop the reflow.

INP and JavaScript

Bundle analysis, code splitting, deferred hydration, and long-task breakup so taps respond immediately.

Third-party audit

Every tag measured for what it costs. Chat widgets, heatmaps, and duplicate analytics are where most of the weight hides.

Performance budget

Lighthouse CI on pull requests with thresholds that fail the build. Keeps a fast site fast after we leave.

How it runs

The process, stage by stage

  1. 01

    Baseline

    Lab and field measurements on your key templates, recorded so improvement is provable rather than felt.

    • Lighthouse runs
    • DevTools traces
    • Search Console field data
    • Real-device tests
  2. 02

    Diagnose

    What's blocking the render, in order. Each item gets an estimated gain and an effort cost.

    • Waterfall analysis
    • Bundle analysis
    • Third-party cost
    • Ranked fix list
  3. 03

    Fix

    Highest impact first, re-measured after each change so we know which fix earned which second.

    • Image pipeline
    • Font strategy
    • Script deferral
    • Caching and CDN
  4. 04

    Verify

    Re-test on real devices and across templates, then confirm nothing broke visually.

    • Real-device retest
    • Cross-template check
    • Visual regression
  5. 05

    Protect

    A budget in CI and a short guide for your team on what tends to undo this work.

    • Lighthouse CI
    • Budget thresholds
    • Team guidance
    • Before/after report
We'd been told our store needed a redesign. Quesiono looked at it and said the design was fine, the problem was eleven apps and a five-step checkout. That was a cheaper answer than the one we expected and it worked — conversion is up 25% on the same traffic.
Sara AliMarketing Manager, Urban Apparel
Investment

What it costs

Fixed price against a defined scope. If a brief isn't specific enough to price properly, we'll say so instead of padding it.

Audit

Diagnosis and a ranked plan. You or your team implement.

$199

Timeline
3 days
Best for
Teams with developers in-house
  • Profiling across up to 4 templates
  • Ranked fix list with effort and impact
  • Third-party script cost breakdown
  • 60-minute walkthrough call
  • Implementation
Scope a audit build
Most chosen

Audit and fix

We diagnose and implement, then prove the gain.

$555 - $999

Timeline
1 week
Best for
Most sites
  • Everything in Audit
  • Implementation of the fix list
  • Image and font pipeline rebuild
  • Caching and CDN configuration
  • Before/after report
Scope a audit and fix build

Fix and protect

Plus the guardrails that stop regression.

$777 - $1299

Timeline
1-2 weeks
Best for
Sites where several people ship changes
  • Everything in Audit and fix
  • Lighthouse CI with failing thresholds
  • Real-user monitoring setup
  • Team training session
  • 90-day re-check
Scope a fix and protect build
Sectors

Where we've done this before

Industry context changes the brief. These are the ones whose pitfalls we already know.

Questions

The things people ask before we start

Core Web Vitals are a ranking signal, but a modest one — relevance and links matter more. Where speed reliably pays is conversion. Sites that drop a second or two off mobile load usually see fewer bounces and more completed forms, and that shows up in revenue before it shows up in rankings.

Next step

Let's talk about speed & core web vitals

Tell us what the site needs to do. You'll get a straight answer on scope, timeline and cost — usually inside one working day.

Rather write first?hello@quesiono.com— we reply within one business day.