Skip to content

FIG 01 · Website Speed Optimization

Speed optimization for the scores your real visitors produce

We fix the Core Web Vitals Google measures from real Chrome users, LCP, INP and CLS at the 75th percentile, on WordPress, Shopify and custom sites. Not a lab score that changes every time you rerun it.

Book a callStart a project
See how it works
Performance engineer studying a page-load waterfall chart on a large monitor

FIG 02 · Quick answer

What are website speed optimization services?

Website speed optimization services make pages load and respond faster for real visitors. Elgrith measures your Core Web Vitals in Chrome field data, aiming for LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less at the 75th percentile, then fixes images, scripts, hosting, caching and theme code on WordPress, Shopify and custom sites.

Field data at the 75th percentile, the line Google uses
p75
Projects delivered since 2015
1,000+
Clients across the USA, UK and India
250+
Your code, data and accounts
100%

FIG 03 · Why it matters

Half the web still fails its Core Web Vitals on mobile.

From the HTTP Archive Web Almanac 2025 and web.dev, checked on 23 Oct 2026.

FIG 04 · What passing means

Field data, not lab scores

PageSpeed Insights shows two very different things. The lab score is one simulated load. The field data is what your real Chrome visitors experienced, and it is what the Core Web Vitals assessment is based on.

Field data vs lab data
Field data (Chrome UX Report)Lab data (Lighthouse)
What it isReal visits from Chrome users, collected over timeOne simulated load on a set device and network
Where you see itPageSpeed Insights “real users” section, Search Console Core Web Vitals reportPageSpeed Insights performance score, Chrome DevTools
How it passesLCP, INP and CLS all “good” at the 75th percentileThere is no pass: it is a 0–100 diagnostic score
INPMeasured from real interactionsNot measured; Total Blocking Time is a rough stand-in
Mobile and desktopAssessed separatelyOne run per device setting
Best forKnowing whether you passFinding and debugging the causes

Field data updates over a rolling window, so improvements show up gradually, not the morning after a release. Thresholds from web.dev’s Web Vitals article (updated 31 Oct 2024), checked 23 Oct 2026.

Need crawling, indexing and full technical SEO too? See technical SEO

FIG 05 · What you get

What we fix for LCP, INP and CLS

Eight areas, ranked by what your field data and traces say is slowing real visitors down. We fix the causes, not the score.

Brass stopwatch in front of a laptop showing a page-load waterfall chart
Website Speed Optimization · built in-house

01

Images

AVIF and WebP, responsive sizes, fetchpriority on the hero image, and lazy loading below the fold only, for a faster LCP.

02

Render-blocking CSS and JavaScript

Critical CSS inlined, the rest deferred, and scripts that don’t need to block the first paint moved out of the way.

03

Long tasks and INP

Heavy JavaScript broken up, event handlers trimmed and main-thread work yielded, so taps and clicks respond within 200 ms.

04

Third-party scripts

Tags, chat widgets, pixels and embeds audited; the unused removed, the rest delayed or loaded behind a facade.

05

Fonts

Fewer font files, subsetting, preloading the ones you need and a font-display strategy that avoids invisible text and shifts.

06

Layout shifts

Width and height on media, space reserved for ads, banners and embeds, and no content injected above what people are reading.

07

Server response time

Slow TTFB traced to hosting, database queries, plugins or uncached pages, then fixed at the source.

08

Caching and CDN

Page, object and browser caching set up properly, with a CDN serving static files close to your visitors.

Deliverables

11

deliverables, in writing

Included in every build, written into your fixed quote before work starts.

FIG 06 · Platforms

Speed optimization by platform

The causes differ by platform. These are the ones we see most, and where we start.

  • WordPress

    Usual causes
    Plugin and page-builder bloat, uncached pages, slow hosting
    WordPress Development

  • WooCommerce

    Usual causes
    Cart fragments, heavy product queries, too many extensions
    WooCommerce Development

  • Shopify speed optimization

    Usual causes
    App scripts left behind, heavy theme code, oversized images
    We check
    Shopify’s Web Performance report alongside Chrome field data
    Shopify Plus Development

  • React and Next.js

    Usual causes
    Large JavaScript bundles, hydration cost, client-only rendering
    React & Next.js Development

  • Before or during a redesign

    Usual causes
    A new theme that ships every component on every page
    Website Redesign

  • Keeping it fast

    Usual causes
    New plugins, tags and banners added after launch
    Website Maintenance

FIG 07 · Instant navigations

Instant navigations: bfcache and Speculation Rules

Two browser features most speed services never mention. Both make the next page feel instant, and both are progressive enhancements: browsers that don’t support them simply ignore them. Checked 23 Oct 2026.

04principles

  • Back/forward cache

    When a page is eligible, going back restores it instantly from memory. We find what blocks eligibility on your pages and remove it; web.dev’s advice is to “never use the unload event”.

  • Speculation Rules: prefetch

    A few lines of JSON tell the browser which links to fetch before the click, so the next page arrives early.

  • Speculation Rules: prerender

    For the most likely next page, the browser can render it in the background. We use it carefully, so analytics and ads count correctly.

  • Built into WordPress 6.8

    WordPress 6.8 ships speculative loading where “URLs are prefetched with conservative eagerness”. We check it works with your theme, plugins and caching.

FIG 08 · WordPress

WordPress speed optimization services

Most slow WordPress sites aren’t slow because of WordPress. They are slow because of what was added to it.

05principles

  • Plugin and theme bloat

    Every plugin and theme script measured; what you don’t use is removed, what you need is loaded only where it’s used.

  • Page builders

    Heavy builder output trimmed, or key templates rebuilt as lean blocks when that is the only real fix.

  • Hosting and object cache

    PHP version, page cache, a persistent object cache and database clean-up, on your current host or a better-suited one.

  • WordPress development

    Custom themes and blocks built lean from the start.

    WordPress development

  • WooCommerce stores

    Store-specific fixes for carts, product pages and checkout.

    WooCommerce development

FIG 09 · Rankings

Does speed affect rankings?

Yes, but less than many sellers claim. Google Search Central (page updated 22 Sep 2026) says “Core Web Vitals are used by our ranking systems”, and also that it “always seeks to show the most relevant content, even if the page experience is sub-par”.

04principles

  • A ranking signal, not a shortcut

    Faster pages won’t outrank more relevant ones. Speed helps when you are close to competitors on everything else.

  • People feel it first

    Visitors leave slow, jumpy pages before Google ever weighs them, which is why we judge speed by real-user data.

  • Full technical SEO

    Crawling, indexing, structured data and Core Web Vitals as part of a full technical SEO program.

    Technical SEO

  • Not sure where to start?

    A free audit of your site’s SEO, speed included.

    Free SEO audit

FIG 10 · Measurement

Why we don’t guarantee a PageSpeed number

A lab score moves with the test device, network and even the time of day, and it is not what Google’s Core Web Vitals assessment uses. So we promise a method and report field data, not a vanity score.

How we measure and report speed work
How we do itWhat we won’t do
BaselineChrome field data (p75), Search Console and lab traces, before any changeStart fixing without a baseline
TargetLCP, INP and CLS “good” at the 75th percentile, on mobile and desktopPromise “90+ on PageSpeed”
TestingEvery change on staging, with a rollback readySwitch on aggressive minification on your live site and hope
ProofField data before and after, once the rolling window has caught upShow a single lab run as the result
MonitoringReal-user monitoring or regular CrUX checks after launchLeave when the report is sent

Next step

Faster pages. Now turn them into sales.

Once pages load and respond quickly, our CRO team tests the changes that turn the extra attention into orders and leads.

Conversion rate optimization

FIG 11 · Process · 6 steps

Measure, fix, verify in the field

Baseline, fixes, field-data verification and monitoring: a fixed written quote after a free call, every change tested on staging, and results shown in real-user data.

Book a call
  1. Step 01

    Free call

    Tell us what you want to improve and what you have already tried. We ask about your tools, team, traffic and deadlines first.

  2. Step 02

    Review

    We take a baseline from Chrome field data, Search Console and lab traces of your key templates, and find the scripts, images, plugins and server time behind each failing metric.

  3. Step 03

    Fixed written quote

    A written scope and a fixed quote, with the timeline, tools, access and hand-over agreed before any work starts.

  4. Step 04

    Sprints with weekly demos

    Fixes made on staging in priority order, highest-impact first, with before-and-after traces shown in a weekly demo and nothing released without your sign-off.

  5. Step 05

    Launch

    Changes released with a rollback plan. Field data lags, so we keep checking until the rolling window reflects the new pages, rather than declaring victory on day one.

  6. Step 06

    Support

    Monitoring of real-user Core Web Vitals and alerts when a new plugin, app or tag slows things down again, as agreed in your written scope.

FIG 12 · What you get

Everything included

Written into your fixed quote, so you know exactly what you are paying for before work starts.

11items

  • Written scope and fixed quote
  • Field-data baseline (p75 LCP, INP, CLS) for mobile and desktop
  • Lab traces of your key templates
  • Ranked fix list with the cause of each slow metric
  • Image, CSS, JavaScript and font fixes
  • Third-party script audit
  • Caching, CDN and hosting recommendations
  • bfcache and Speculation Rules checks
  • Every change tested on staging with rollback
  • Before-and-after field-data report
  • Your code and accounts stay yours

FIG 13 · Tech & tools

The tools behind the work

Proven, well-supported tools, chosen for your project and set up in accounts your business owns.

  • PageSpeed Insights
  • Chrome UX Report
  • Search Console
  • Lighthouse
  • Chrome DevTools
  • WebPageTest
  • web-vitals library
  • Speculation Rules API
  • Cloudflare
  • Redis
  • Query Monitor
  • Shopify Web Performance report
  • Next.js
  • WordPress

FIG 14 · Who it’s for

Speed work for sites where every second has a cost.

Same method for every platform: field data first, fixes on staging, proof in real-user data.

4 audiences

Ecommerce

Faster product pages and checkouts.

Shopify, WooCommerce and custom stores, where app scripts and heavy product pages slow down the visitors most likely to buy.

  • App and tag audit
  • Product page LCP
  • Checkout INP
  • Shopify Web Performance report

FIG 15 · Working with us from the USA and UK

Built in New Delhi. Run on your hours.

Every project gets a point of contact in New York or London and an engineering team in New Delhi. Here is how today’s working days line up, live.

Three ways to work together

  1. 01

    Fixed-scope project

    A written scope, one fixed price and a dated plan. Suits websites, apps and MVPs.

  2. 02

    Dedicated team

    Designers and engineers on your roadmap every month, billed monthly.

  3. 03

    White label

    For US and UK agencies: our work, your brand, unbranded deliverables.

Every engagement

  • Fixed quote in USD, GBP or INR after a free 30-minute call
  • NDA before discovery. You own all code, designs and content
  • A working demo every sprint, not status slides
  • Reply within one business day, calls inside your hours
Book a call

Calls on ET or UK hours

FIG 16 · By metric

Core Web Vitals: what slows each one, and the usual fix

Each Core Web Vital fails for different reasons. This is where we look first.

Core Web Vitals: what slows each one, and the usual fix
MetricGood at p75Common causesUsual fixes
LCP (Largest Contentful Paint)Within 2.5 sSlow server, large hero image, render-blocking CSS, late-discovered imagesFaster TTFB, AVIF/WebP, fetchpriority, critical CSS
INP (Interaction to Next Paint)200 ms or lessLong JavaScript tasks, heavy event handlers, third-party scriptsBreak up long tasks, trim handlers, delay tags
CLS (Cumulative Layout Shift)0.1 or lessImages without dimensions, late ads and banners, web fontsSet dimensions, reserve space, tune font loading
Back/forward navigationsInstant when eligibleunload handlers and other bfcache blockersRemove blockers; add Speculation Rules for forward navigations
Speeding up a store? Read the ecommerce CRO checklist for 2026

FIG 17 · Compare

Speed optimization vs technical SEO vs website maintenance

Speed optimization vs technical SEO vs website maintenance
Speed optimizationTechnical SEOWebsite maintenance
Question it answersWhy is the site slow for real visitors?Why don’t pages get crawled, indexed or ranked?Is the site updated, secure and backed up?
Main workLCP, INP and CLS fixes in code, hosting and cachingCrawling, indexing, structured data, site architectureUpdates, backups, security, uptime
EvidenceChrome field data and lab tracesSearch Console, crawls and logsUpdate logs and monitoring
Where to startYou are hereTechnical SEOWebsite maintenance

FAQ

Frequently asked questions

Straight answers about Website Speed Optimization with Elgrith.

They find and fix what makes your pages slow to load, slow to respond or jumpy for real visitors. We measure Core Web Vitals (LCP, INP and CLS) from Chrome field data, trace the causes on your key templates, then fix images, scripts, fonts, hosting, caching and theme code, and verify the result in field data.

FIG 18 · Related

Keep exploring

All services

Free 30-minute call

Fast for real visitors. Proven in the field.

Send us your URL and platform. After a free call you get a field-data baseline, the fixes we recommend and a fixed quote.

Book a callStart a project

connect@elgrith.com+91 96039 20001Start a project

Pick a day for your call

Open

Pick a day. You'll choose a time in your own time zone on the next step.

See all times