Cloud · Service

    Faster.
    Measured.

    An audit shows where the seconds go. Caching, CDN rules, images and JavaScript are fixed in that order, and a Lighthouse report before and after shows what changed.

    See pricing
    At a glance
    From $0
    Typical Cloud plan: 2–3 weeks
    0+
    Lighthouse target, on a phone
    0+
    Projects since 2019
    WHAT'S INCLUDED

    The audit. The fixes. The proof.

    The Starter package covers the audit and fixes for up to five pages on one site, with two rounds of changes after the first report. More pages and templates are quoted in writing.

    The audit
    01
    Lighthouse on a phone profile for every page in scope
    02
    Waterfall analysis in WebPageTest and Chrome DevTools
    03
    Core Web Vitals: LCP, INP and CLS
    04
    Every third-party script listed, with what it costs
    05
    Written findings, ranked by time saved
    The fixes
    01
    Cache rules for static files, dynamic pages and API responses
    02
    CDN configuration, with cache purge on deploy
    03
    Images converted to WebP or AVIF, sized per screen, loaded lazily
    04
    Code splitting and lazy loading for JavaScript
    05
    Each change measured before the next goes in
    The proof
    01
    Lighthouse reports after, on the same pages and settings
    02
    A performance monitoring dashboard
    03
    Alerts when a score or a vital slips
    04
    A written record of every change, and how to undo it
    WHAT IT COSTS

    From $199.

    The Starter package covers the audit and the fixes for up to five pages and two rounds of changes. More pages, templates and the state of the code are quoted in writing.

    $0
    Starting package
    Audit, fixes and before and after reports for up to five pages, two rounds of changes.
    0–3 wk
    Typical plan
    Audit in week one, fixes in week two, monitoring after. The scope sets the date.
    0 min
    First call
    The pages that matter and what is slow today, then a written scope.
    HOW LONG

    Audit first. Fixes second.

    The Cloud craft's typical plan. A large site, or code nobody has touched in years, moves it.

    01
    Week 1

    Performance audit

    Lighthouse, waterfall analysis and Core Web Vitals on every page in scope. Bottlenecks written down.

    02
    Week 1

    Cache strategy

    What is cached, where, for how long, and what clears it. Agreed before any rule is set.

    03
    Week 2

    Implementation

    Caching, CDN, images and code, one change at a time, each measured on staging.

    04
    Weeks 2–3

    Monitoring

    After reports run, dashboard built, regression alerts switched on.

    IF IT GOES WRONG

    Every change can be undone.

    And each is measured before the next.

    01

    Staging first

    Every optimisation is tested on staging before it reaches production.

    02

    Rolled back at once

    Each change is recorded with how to reverse it. A cache rule comes off in a minute.

    03

    One change at a time

    Changes are measured one by one, so a problem points to a single cause.

    04

    Work continues until it moves

    If the after reports show no measurable improvement, work continues at no added fee.

    05

    Scope in writing

    Pages, targets and test settings are agreed first. A change is priced before it is made.

    06

    Alerts on regression

    Monitoring stays on after handover, so a new script that slows the site is caught.

    WHO IT'S FOR

    Slow on a phone. Worth fixing.

    If the second list sounds closer, start with the page it names.

    This service fits

    • 01
      A site slow on a phone

      Pages that take seconds to show anything on a mobile connection.

    • 02
      Failing Core Web Vitals

      Search Console reports poor LCP, INP or CLS on pages that earn traffic.

    • 03
      A Shopify store weighed down

      Scripts, app embeds and images reviewed in the theme. Shopify's own CDN stays.

    • 04
      Sale days and traffic spikes

      Cache rules that keep the origin from answering every request itself.

    Start somewhere else

    • 01
      A site on a slow host

      No cache rule fixes a server that answers late. Cloudflare Hosting & Deployment or Linux & WordPress Hosting moves it first.

    • 02
      A theme past repair

      When the audit finds the theme is the cause, Shopify Theme Development or Complete Redesigns is the shorter road.

    • 03
      A site that goes down

      Outages are a monitoring question. See Analytics & Tracking.

    STANDARDS YOU CAN CHECK

    Same test. Before and after.

    The reports come with the handover, and anyone can run them again.

    01

    One test profile

    Lighthouse on a phone profile with the same throttling, before and after, on the same pages.

    02

    Google's thresholds

    LCP within 2.5 seconds, INP within 200 milliseconds, CLS within 0.1. The scope states which pages are held to them.

    03

    Images sized and modern

    WebP or AVIF, width and height set, a size per screen, lazy below the fold.

    04

    Cache rules written down

    For each content type: where it is cached, for how long, and what clears it.

    05

    Every script accounted for

    Each third-party script listed with its owner, its purpose and its cost in load time.

    06

    Regression alerts on

    Monitoring tracks the pages in scope and alerts a named person when one slips.

    BEFORE YOU BRIEF

    Before the audit.

    It depends on where the time goes today, and the audit shows that. The working targets are a Lighthouse score of 90 or more on a phone and a load time under two seconds. The scope sets the targets page by page, once the audit is in.
    Each change is tested on staging before it reaches production, and each can be rolled back at once. Changes go in one at a time, so a problem points to a single cause.
    The before and after reports use the same pages and the same test settings. If they show no measurable improvement, work continues at no added fee until they do.
    The audit and the fixes are a project. Sites slow down again as scripts, apps and images are added, so monitoring with alerts on regression is set up at the end. Ongoing cover is quoted in writing.
    Yes, with a different toolset. Shopify runs its own CDN, so the work is in the theme: scripts, app embeds, images and fonts. If the theme itself is the cause, the audit says so and points to a theme build.
    No. The audit, the image work and the code work apply on any host. Cache and CDN rules are set on Cloudflare, so a site not yet behind it moves its DNS there first. Cloudflare's entry plan, which costs nothing, covers that.
    Core Web Vitals are one of Google's page experience signals. Passing them removes a reason to rank lower. It does not promise a position.
    Lighthouse reports before and after for every page in scope, a written record of each change and how to undo it, a monitoring dashboard, and alerts for when a score slips.

    Your site.
    Faster.

    A 30-minute call about the pages that matter most. A written scope after it.

    See pricing