Magento speed and performance optimisation.

A store that loads and responds quickly on your customers’ phones, measured the way Google measures it.

We start from what your real customers get and trace where the time goes. Then we fix the causes, from the cache and the server to scripts, images and the theme. Where Luma is the cause, we’ll show you what a move to Hyvä would change.

For
Magento Open Source, Adobe Commerce and Mage-OS stores, on Luma or Hyvä
Measured by
Google’s real-user data where it exists, lab tests to find causes
Price
A written estimate before any change; £80 an hour plus VAT
First step
We read your store’s real-user data and test its main pages

Why merchants ask us to look at speed.

Usually one of these.

  • Google Search Console says our pages fail Core Web Vitals on mobile.

    What it usually means

    That report is built from real visits. It shows which kinds of page fail and on which measure, which is where we start.

  • The store feels slow on a phone, but the speed score our developer quotes looks fine.

    What it usually means

    A lab score is one run on one page. Your customers are on real phones and real connections.

  • Category pages and search are slow, and it gets worse when we run a promotion.

    What it usually means

    Those pages are often the ones the cache can’t serve. We find out why, and whether traffic from bots is taking capacity your customers need.

What we measure and fix.

In the order we usually look at it.

  • Real-user data

    Google’s Chrome UX Report for the store, and for its busiest pages where Google has enough visits, on phones and desktops.

  • Cache and server

    How often the full-page cache serves a page, why it misses, and how long the server takes to answer when it does.

  • Scripts

    Tag managers, chat, reviews and tracking: what each one costs on a phone, and which can load later or go.

  • Images and fonts

    Sizes, formats, lazy loading and the main image on each page type, which often decides when the page looks ready.

  • The theme

    How much JavaScript the phone has to run before the page responds. On Luma this is often most of the problem.

  • Indexers, cron and queries

    Background jobs and database queries that slow the store down at the busiest times.

The same store, with and without us.

Without us
  • Scripts nobody remembers adding, loading on every page
  • Category pages the cache never serves
  • Hosting upgrades bought to fix a theme problem
  • Fixes that help one test run and nothing else
With Refined Commerce
  • Before and after figures from the same sources
  • The scripts listed, with what each costs and who needs it
  • Cache misses found and explained
  • The cause named before money is spent
  • Changes tested on a staging copy, then deployed with a way back

From measurement to fix.

Each step ends with something you can check.

  1. Step 1: Measure

    We read the real-user data, test the main page types and trace where the time goes.

    What you receive
    A short report of what’s slow, why, and what each fix should change.
  2. Step 2: Agree the fixes

    We list the fixes in order of effect and cost, with a written estimate.

    What you receive
    You choose what goes ahead.
  3. Step 3: Fix on staging, then live

    Changes are made on a staging copy of the store first, tested there, and deployed at a quiet time.

    What you receive
    The changes on live, with a way back.
  4. Step 4: Check what changed

    Lab results straight away, Google’s real-user figures over the following weeks where your store has them.

    What you receive
    Before and after figures.

Is this the right service for your store?

This is for you if

  • Your Magento store fails Core Web Vitals, or feels slow on a phone
  • You want to know the cause before paying for hosting or a rebuild
  • You want before and after figures you can check yourself

If your situation is different

  • You need marketing or advertising work rather than the store itself

We price the work, not the clock.

This service
Priced as a project: a written estimate once we have examined the store.
How you pay
Usually spread across the length of the project.
Our standard rate
£80 an hour plus VAT.
Never charged
Account management, or the first look at your store.

An estimate in writing before any change.

We measure first, then give you a written estimate for the fixes you choose, so you know the price before anything on the store changes.

What happens first
  1. We read your store’s real-user data and test its main page types.
  2. We trace where the time goes on each of them.
  3. You get the findings and an estimate, or a question, in writing.
How our pricing works

Proof, from real stores.

Tile Merchant: a category page on desktop
Tile Merchant on a phone
Tiles and flooring, IrelandMagento 2 and Hyvä

Tile Merchant

A Magento store on Hyvä trading into Ireland, Northern Ireland and Great Britain: the main content loads in 1.1 seconds on a phone for real customers.

Passes Core Web Vitals on mobile
  • LCP1.1 s
  • INP128 ms
  • CLS0

Core Web Vitals from Google’s real-user data, mobile. Marks show Google's thresholds.

… We no longer feel like we are in perpetual development. We are growing and improving and Rowan has been key to this success. …

Rob LOutdoorLiving.ieGoogle review

Why merchants bring this work to us.

About Refined Commerce
  • 2008

    On Magento since its early releases

    Decades of collective experience across Magento 1, Magento 2, Adobe Commerce, Hyvä and Shopify. Very little about your store will be new to us.

  • 1

    Point of contact, and senior engineers only

    You deal directly with the founder. No juniors learning on your store and no account managers between you and the people doing the work.

  • 5.0

    On Google, from 23 merchant reviews

    Small stores and large ones, described in their owners' words. The reviews are quoted on this site word for word.

Questions merchants ask about this.

Which speed figures matter?

The ones Google collects from real Chrome visitors to your store, in the Chrome UX Report: Largest Contentful Paint (how long the main content takes to appear), Interaction to Next Paint (how quickly the page responds to a tap or click) and Cumulative Layout Shift (how much the page jumps while it loads). A page passes when at least three quarters of visits meet each of the three: 2.5 seconds or less, 200 milliseconds or less and 0.1 or less. Phones and desktops are judged separately.

What if our store has too few visitors for Google’s data?

Google only publishes real-user figures for stores and pages with enough Chrome visits. Where there are none, we measure the same pages with repeatable lab tests before and after the work, and we tell you that’s what the figures are.

Is our hosting the problem?

Sometimes. We measure how long the server takes to answer before anything else, and if that’s slow on cached pages we’ll tell you. We also look at the pages the cache can’t serve, the scripts added over the years, the images and the theme, because hosting is only one of the places time goes.

Do we need Hyvä to be fast?

Some Luma stores can be made reasonably quick, and if yours is one of them we’ll tell you. Where most of the time goes on the phone running Luma’s JavaScript, moving the frontend to Hyvä is usually the fix that lasts.

Will the work change how the store looks?

Most of it doesn’t. Cache, server, image and script work is invisible to shoppers. If a change alters something they see, such as how a gallery loads, you see it on staging first.

How long until we see a difference?

Lab tests change the day a fix is deployed. Google’s real-user figures cover the last 28 days of visits, so they move over the following weeks. We report both.

Not sure speed is the main problem? Start with the free health check.

One page on where your store stands: release, support status, PHP, headers, hosting and any sign of a hijack, read from its public pages and sent by email within two working days. Nothing is accessed or tested.

  • Magento Open Source, Adobe Commerce and Mage-OS stores
  • Read from public pages only, and free
  • Written up by an engineer who read the store
Free store health checkOne page, by email

5.0 from 23 Google reviews

Free, with no obligation. We read only what your store serves publicly; nothing is accessed or tested, and it is not a security guarantee. Privacy notice.
What you receiveExample report
Magento Security and Upgrade Health Check
example-store.co.ukNeeds attention
Platform
Magento Open Source 2.4.4-p3
Adobe support
ended 12th April 2025
PHP
8.1, end of life
Frontend
Luma
Security headers
2 of 6 present
Hijack indicators
none found

What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.

Free health check