
A faster Magento store, measured on real visitors
We find what is slowing your store down, fix it, and report before and after numbers from Google’s field data.
Get a speed reviewWhat’s includedFree · No obligation · Reply within one business day
- Core Web Vitals: LCP, INP and CLS
- Breeze and Hyvä frontends
- Varnish, Valkey and server tuning
Stores we have built and run
Magento performance optimization finds what slows your store for real visitors and fixes it: heavy frontend JavaScript, missing full-page cache, oversized images and slow database queries. We measure Core Web Vitals (LCP, INP and CLS) from Google’s field data before and after, so you can see the change.
The targets we work to
Google’s “good” thresholds for Core Web Vitals, measured at the 75th percentile of real page loads. Source: web.dev.
Why it matters
What faster pages change for your business
Breeze, Hyvä or Luma?
| Luma | Breeze | Hyvä | |
|---|---|---|---|
| Approach | Default | Lighter Luma | New frontend |
| Extensions | Native | Mostly work | Need compat |
| Effort | – | Lower | Higher |
This site runs on Breeze. We work with both and recommend what fits your extensions and budget.
How it works
What’s included
Measured on real visitors
Google’s Core Web Vitals come from real Chrome users. We report field data, so you see what customers actually experience.
- LCP: how fast the main content appears
- INP: how quickly the page responds
- CLS: how stable the layout is
Is this right for you?
- Your pages feel slow on mobile or fail Core Web Vitals in Search Console
- You run the default Luma theme
- Add-to-cart, search or checkout is slow at busy times
- You want to know whether Breeze or Hyvä is right for you
- Your server is badly undersized: fix hosting first
- You want a perfect lab score only: we optimise for real visitors
- Speed audit with field data
- Prioritised fix list with effort
- Implemented fixes on staging, then live
- Before and after report
How it works
You see the findings, the scope and the price before any code changes.
AuditWe review code, extensions, hosting and speed.
Plan & priceA fixed scope and price, or a retainer.
Build on stagingTested on a copy of your store, never live.
Launch & supportA planned release, rollback ready, then monitoring.
For your technical team
How we build it
The stack, standards and handover your developers can expect.
- Chrome UX Report field data, 28-day window
- Targets: LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1
- Lighthouse lab checks on staging
- Varnish 8 full-page cache, Valkey 9 cache and sessions
- PHP 8.5 with OPcache
- OpenSearch 3 and indexers on schedule
- Breeze or Hyvä in place of Luma JavaScript
- Critical CSS and deferred scripts
- WebP images at the right sizes
Questions before you book
Frequently asked questions
What are Core Web Vitals?
Google measures loading (LCP), responsiveness (INP) and visual stability (CLS) from real Chrome users. They are part of how Google evaluates page experience.
Should I switch to Hyvä or Breeze?
Breeze keeps your Luma-based theme and extensions with smaller changes. Hyvä is a new frontend that needs compatible modules. We compare both for your store.
How quickly will I see results?
Lab tests change immediately. Google field data is a 28-day rolling average, so the full effect shows in Search Console after about a month.
Is Varnish still needed with Breeze or Hyvä?
Yes. The theme makes pages lighter in the browser; Varnish makes the server answer faster. They solve different problems.
Will performance work cause downtime?
Most changes need no planned downtime. Everything is built and tested on staging, then released in an agreed window with a rollback path.
Do you need access to our server?
For server and cache tuning, yes, or we give your host a written list of changes. Frontend work only needs the code repository and a staging site.
Related services
Is your store slow?
Send us the URL. We will look at your field data and tell you the three biggest wins.
Free · No obligation · Reply within one business day




