Skip to content
08 / Services

Make the site fast on a real phone

Core Web Vitals, page speed and server tuning for WordPress, WooCommerce and Shopify — measured on mid-range devices and real connections, not on a developer’s laptop.

Projects delivered
50+
Years of experience
10+
Countries served
15+
Typical project
1–3 wks
Page speed and Core Web Vitals report

SPEED IS A FEATURE YOUR CUSTOMERS FEEL

Nobody visits a website to admire how quickly it loads — they simply leave when it does not. On mobile data, a few extra seconds is enough for a meaningful share of visitors to give up before they have seen anything, and for an online store that is measured directly in orders that never happened.

Search engines measure it too. Core Web Vitals are part of how Google evaluates a page: how quickly the main content appears, how soon the page responds to a tap, and whether things jump around while it loads. The scores are not the point — they are a proxy for whether the experience feels solid.

Speed work is also unusually measurable. We take a baseline on real devices, fix in order of impact, and show you the before and after, so you can see exactly what changed rather than trusting a green number in a tool. Most sites do not need a rebuild to get faster; they need the heaviest few problems removed.

SIGNS YOU NEED SPEED WORK

If any of these are true, visitors are almost certainly leaving before they see what you offer.

Ask for a speed audit
  • Common warning signs
  • Search Console reports URLs failing Core Web Vitals
  • The site feels fine on office wifi and slow on mobile data
  • Pages jump around while they load
  • Taps do nothing for a moment after the page appears
  • Ad campaigns get clicks but the landing page loses them
  • The site was fast at launch and has grown heavier since

WHERE THE TIME ACTUALLY GOES

Almost every slow site we audit loses its seconds in the same three places.

Page speed and Core Web Vitals report
Images & media

The heaviest thing on the page

Huge uploads served at full size, no modern formats, and video that loads whether it is watched or not. Correct sizing, compression and lazy loading usually produce the single biggest gain, and nobody can see the difference.

Website performance and Core Web Vitals
Scripts & third parties

Code that blocks the page

Chat widgets, tag managers, analytics, A/B tools and plugin scripts all compete with your content for the same moment. We measure what each one costs and load, defer or remove them accordingly.

Custom website design shown across devices
Server & caching

The wait before anything renders

Slow hosting, uncached database queries and a bloated theme delay the very first byte. Proper caching, tuned queries and the right hosting fix a problem that no amount of front-end work can hide.

WHAT THE WORK INCLUDES

A speed project is measurement, then fixes in the order that helps most.

Real-device baseline

We measure Core Web Vitals on a mid-range phone and a normal connection, plus real user data where it is available.

Prioritised findings

A written list of what is costing you time, ordered by impact and effort, so you can decide how far to go.

Front-end fixes

Images, fonts, CSS and JavaScript trimmed, sized and loaded in the right order.

Script & plugin audit

Third-party tags and plugins measured individually, then deferred or removed.

Server & caching

Hosting, caching layers and database queries tuned to cut time to first byte.

Verification

Before-and-after numbers on the same devices, plus monitoring so gains do not quietly disappear.

Most sites do not need rebuilding to be fast. They need their three heaviest problems removed.

Get a speed audit

HOW A SPEED PROJECT RUNS

Five short stages, usually inside two or three weeks.

  1. 01

    Measure

    Baseline on real devices and connections, plus field data from Search Console and analytics.

  2. 02

    Diagnose

    We identify what is actually costing time, separating front-end weight from server delay.

  3. 03

    Agree the plan

    A prioritised list with expected gain and effort, so you choose how far to take it.

  4. 04

    Fix

    Changes applied on staging and verified one by one, so nothing breaks silently.

  5. 05

    Verify & monitor

    Before-and-after numbers, then monitoring to catch regressions from new content or tags.

HOW LONG SPEED WORK TAKES

Most speed projects run 1–3 weeks. Heavier work — a hosting move or a theme rebuild — is quoted separately after the audit.

Stage Typical time What you receive
Measurement 1–2 days Baseline scores on real devices, field data review
Diagnosis 2–3 days Prioritised findings with expected impact
Front-end fixes 3–5 days Images, fonts, scripts and CSS work
Server & caching 2–4 days Caching, queries and hosting configuration
Verification 1–2 days Before-and-after report, monitoring set up

SPEED PROJECTS WE TAKE ON

Performance work rarely looks the same twice. These are the usual shapes.

Core Web Vitals fixes

Failing LCP, INP or CLS in Search Console, fixed and verified.

Store performance

Product and category pages on WooCommerce or Shopify, where slowness costs orders directly.

Plugin & theme clean-up

Removing accumulated weight from a site that was fast when it launched.

Hosting migration

Moving to hosting that suits your traffic, with caching configured properly.

Pre-launch tuning

Getting a new site fast before it goes live, rather than after complaints.

Ongoing monitoring

Monthly checks so new content and new tags do not undo the work.

WHAT WE OPTIMISE

We work on the platforms we build on, so fixes go deeper than plugin settings.

WordPress

Themes, plugins, queries and caching, including sites we did not build.

WooCommerce

Cart and account pages that cannot be cached the usual way.

Shopify

Theme weight, apps and image handling within Shopify’s limits.

Custom / headless

Bundle size, rendering strategy and CDN configuration.

WHAT SPEED WORK COSTS

Speed work is quoted after the audit, because that is when the size of the job is known. Many sites get most of their gain from a short, focused project rather than a rebuild.

Get your estimate
  • What moves the price
  • How many templates need work, not how many pages exist
  • Whether the theme or platform is the bottleneck
  • Number of third-party scripts and plugins to untangle
  • Whether hosting needs to change
  • Store pages, which cannot be cached like normal pages
  • Whether you want ongoing monitoring afterwards

SITE SPEED QUESTIONS

What people ask before commissioning performance work.

Still have a question? Ask us on WhatsApp
Three measurements Google uses to judge experience: how quickly the main content appears (LCP), how soon the page responds to interaction (INP), and how much the layout shifts while loading (CLS). They are a proxy for whether a page feels fast and stable.
Speed is one ranking signal among many, so it rarely transforms rankings on its own. What it reliably improves is how many visitors stay and convert, which is usually worth more than the ranking change.
Usually not. Most sites get the majority of their improvement from images, scripts and caching. We only recommend a rebuild when the theme or platform itself is the bottleneck, and we say so after measuring.
Lab scores vary with network, device and server load. That is why we measure on consistent real devices and also look at field data from real visitors, which is what Google actually uses.
Yes, though stores need a different approach: cart, account and checkout pages cannot be cached like ordinary pages, so the work focuses on queries, object caching and hosting.
We give an expected range after the audit rather than a promise beforehand. The honest answer depends on what is slowing it down, and the audit is what tells us.
No. A speed project keeps the design as it is. If the design itself is the problem — huge hero videos, for example — we will tell you and let you decide.
Only if nothing undoes it. New tags, large image uploads and new plugins all add weight over time, which is why we offer monitoring as part of a care plan.
Yes, most speed projects are on sites built by someone else. We document what we change so your team or your developer can follow it.
The audit usually starts within a week, and the whole project is normally done inside two to three weeks.

Let's build something that moves your business forward.

Tell us what you're trying to build, improve or automate.

Start your project
  • Free 30-minute discovery call
  • NDA available
  • Response within 24 hours
Client Client Client Client
4.9 / 5.0

Trusted by 50+ founders & tech leaders worldwide

Get your project estimate
Step 1 of 4
What do you need?
What's your budget?
When do you want to start?
Where should we send your estimate?