Home › Services › Page speed

WooCommercepage speed.

Speed up WooCommerce where it counts. We find where the time goes on your store, fix it in your theme, hosting and plugins, then measure again on real visitors. You get a written scope, a price and a date before we start.

yourstore.com/category/armchairs/
Example furniture store, category page while it loads
4.1 sbefore the photos show
PageSpeed reportyourstore.com/category/armchairs/ · mobile
38Performance
81Accessibility
74Best practices
85SEO
0/3Core Web Vitals
Measured before and after
Your theme stays
Written scope and a date
No lock-in the code is yours
The problem

Slow pageslose the sale.

Most stores are fast on the home page and slow where people buy: the category list, the product page with its gallery, the cart. That is where we look first.

Average mobile load 4.2 s
PageLCPINPCLS
Example numbers for a typical WooCommerce store. Yours come from the audit.
yourstore.com/category/coffee/
Example coffee store, category page while it loads
4.8 sphotos still loading on a phone
How it works

Measure, fix,measure again.

Four steps, usually two to four weeks. You see the list before any work starts, and the numbers after it ends.

Where the time goes

yourstore.com/category/armchairs/ · mobile, 4G

2 files block the page2.4 MB photo, not compressedcart reloads, uncachedfont preloadedproduct photos lazy
Fix list

Sorted by what it saves

CACHEDSKIPPEDPage cache that skips the cart −1.6 s
2.4 MB180 kBWEBPImages resized and lazy below the fold −0.9 s
<script src="slider.js" defer></script>Defer the slider script −0.4 s
AUTOLOAD1.2 MB → 90 kBClean 1.2 MB of autoload options server
On a copy first

Nothing touches the live store until you approve it

yourstore.comstaging.yourstoreStaging copy done
themes/storefront/storefront-child/functions.phpSAFETheme changes in a child theme done
do not cache:/cart/ /checkout//my-account/Cache rules, cart and checkout excluded in progress
03:000024Go live, off-peak next
Before and after

Field data, 28 days later

BeforeCore Web Vitals: Failed
LCP · Largest Contentful Paint4.1 s
31%27%42%
INP · Interaction to Next Paint380 ms
48%30%22%
CLS · Cumulative Layout Shift0.21
39%22%39%
After 28 daysCore Web Vitals: Passed
LCP · Largest Contentful Paint1.8 s
86%10%4%
INP · Interaction to Next Paint160 ms
91%7%2%
CLS · Cumulative Layout Shift0.03
94%4%2%
GoodNeeds improvementPoorShare of real visits, last 28 days, mobile

What is included

The whole store,not one score.

Field data firstChrome UX Report and Search Console, not one lab run.

Page cacheSet up on what you have: LiteSpeed, Nginx, Cloudflare.

ImagesRight sizes, WebP or AVIF, lazy below the fold.

Theme codeScripts deferred, unused CSS removed, fonts preloaded.

DatabaseAutoload, transients, old revisions and sessions.

Cart and checkoutFast without caching what must stay personal.

Plugin auditWhat loads on every page and does not need to.

A warm cacheUruz Cache Warmer set up so no visitor gets a cold page.

Included
  • A written fix list with the time each item saves
  • All work on a staging copy first
  • A before and after report at 28 days
  • Notes on what to keep doing, in plain words
Where the line sits
  • A new theme or redesign is a separate project
  • Hosting moves are quoted on their own
  • Third-party scripts you need stay; we only load them later
Works with

The hostingyou already have.

We tune the cache and server you pay for. A move is only on the list when the host is the problem.

LiteSpeedLiteSpeedLSCache
CloudflareCloudflareAPO, rules
NGINXNginxFastCGI cache
VarnishVarnishVCL
SucuriSucurifirewall cache
20i20iStackCache
In the wild

One switch,two seconds.

phone accessories store
A WooCommerce store home page
Server response3.0 s on every page, before any image
Phone accessories store · WooCommerce

One switch cost two seconds.

A page optimization feature rebuilt the HTML on each visit. We turned it off, moved what it did into the theme, and let the page cache do its job.

Server response3.0 s0.9 s
Work2 days
Price

Quoted per store,in writing.

No two stores are slow for the same reason. The price follows the fix list, and you can leave out any line.

What moves the number

The four things that decide the size of the job.

How many page templates home, category, product, cart
The theme builder or hand-coded
The hosting cache available or not
Plugins that load everywhere sliders, chat, builders
2 to 4 weeksof work, on a copy first
28 daysuntil Google shows the change
1 reportbefore and after, in writing

Get a quote

A written scope, a price and a date, usually within two working days.

Not sure yet? Start with the free audit
Questions

Beforeyou ask.

Do you need access to the live store?

Not for the audit. For the work we need an admin account and hosting access, and we make a staging copy first.

Will my PageSpeed score hit 100?

Maybe, but that is not the goal. Google ranks on field data from real visitors, so that is what we move and what we report.

Do I have to change the theme?

No. We work in a child theme or a small plugin, so updates keep working.

How long does it take?

Two to four weeks of work, then 28 days until Google's field data shows the change.

What if a plugin is the problem?

We tell you which one and what it costs in seconds. You decide whether it stays, goes or loads only where it is needed.

Do you work on Shopify or Wix?

No. Only WordPress and WooCommerce. If you want to move, see migrations.

Get a quote

Send the URL,get a written plan.

  • Scope, price and a dateIn writing, usually within two working days.
  • Leave out any lineThe price follows the fix list, item by item.
  • No lock-inThe code stays yours, in a child theme or a small plugin.

Your store

Three fields. We reply by email.

Not sure yet? Start with the free audit
Page speedQuoted per store
Get a quote