Appreciate everyone’s hard work and effort in moving us forward!
Alex Brynou
Director of Systems Architecture
Magento performance optimization
Checklists make demos fast. Engineering makes stores fast. We take Magento stores into the green and keep them there, 95+ PageSpeed, live, on real catalogs.
Adobe Commerce gold partner
#1 Adobe Commerce partner worldwide
Hyvä Platinum Partner
40+ projects delivered
ISO certification
9001 & 27001
Most certified Hyvä agency worldwide
200+ Adobe Commerce Certifications
12 years running live stores. Since 2014
Trusted by brands globally
Slow is a business decision you didn't mean to make
Speed is one of the few levers that moves conversion, SEO and ad efficiency at once.
Conversion follows speed
Shoppers don't wait, they leave. When we rebuilt a store fast, conversion doubled.
Google measures your store
Core Web Vitals are a ranking signal, and a slow store gets crawled less. Speed is SEO you can engineer.
Every ad click costs more on a slow site
Paid traffic bouncing off a five-second page is budget burned twice.
Peak is when slow becomes down
The store that crawls in November falls over on Black Friday. Performance work is peak insurance.
Why Magento stores get slow
Magento isn't slow. Neglected Magento is, and six patterns cause most of it.
- 1
The extension pile
Forty modules, each "lightweight," collectively a traffic jam on every page load.
- 2
A frontend from another era
Luma-generation themes ship megabytes of JavaScript to render a product title. No tuning outruns the architecture.
- 3
Media nobody resized
4,000-pixel hero images on mobile connections, the cheapest fix nobody made.
- 4
Indexers fighting the store
Reindexing and cron churning through business hours, admin crawling, caches invalidating faster than they warm.
- 5
Search that scans instead of finds
Catalog search grinding the database at scale, every query a small outage.
- 6
A checkout that saves the worst for last
The slowest page in the funnel is the one holding the money. Checkout drag is conversion loss, distilled.
Stores are slow for two different reasons
A brand store and a 100,000-SKU catalog lose their seconds in different places, and get them back through different work.
Slow to render
Typical of brand and DTC stores. Seconds hide in theme JS, render-blocking assets, oversized media and third-party scripts.
Slow to respond
Typical of large catalogs and B2B. Seconds hide in indexers, database queries, cache topology and catalog search.
Most stores are some of both
The audit says which, and where the budget goes.
How we make a store fast
Measured at the start, proven at the end, locked in after.
Every fix, measured
The same five pages and the same instruments, before and after, so you see exactly what each change bought.
- 1
Measure five pages, three ways
Homepage, category, product, cart and checkout, baselined in lab, field and server data before any work starts.
- 2
Trace every slow second to its cause
The audit names culprits, not symptoms, like a 4 MB hero image or a slow category query, each with its gain and cost.
- 3
Ship the cheap fixes in the first sprint
Image compression, script deferral, cache and cron settings go live in the first sprint, so scores move within weeks.
- 4
Price the big fixes separately
If the theme, checkout or an indexer is the real ceiling, it becomes its own scoped and priced project, never a hidden rebuild.
- 5
Make regressions impossible to miss
Page-weight and score limits join the release process, and monitoring checks the store every 5 minutes.
The technical playbook, layer by layer
Magento gets slow in layers, and gets fast the same way. This is the actual work, named.
Current PHP with OPcache tuned, production mode verified (you'd be surprised), PHP-FPM workers sized to real traffic, MySQL and MariaDB configuration, sessions in Redis, queue consumers actually running.
Varnish full-page cache with a warming strategy so it's never cold when it counts, Redis backend and L2 cache, cache-tag and invalidation hygiene, hole punching that doesn't punch holes in performance, Brotli and HTTP/2 and 3.
The slow-query log emptied, not ignored. Indexers on schedule instead of on save, cron untangled from business hours, asynchronous operations where the admin blocks, and custom indexers built when catalog scale outgrows Magento's own.
Magento's default JS bundling replaced with an approach that actually helps, critical CSS inlined and the rest deferred, fonts preloaded with sane fallbacks, third-party tags governed, the LCP element preloaded, CLS and INP engineered, not hoped for.
WebP and AVIF with responsive srcset, lazy loading below the fold and never on the LCP image, a CDN configured for your markets, Fastly on Adobe Commerce Cloud tuned rather than tolerated.
Elasticsearch and OpenSearch tuned for your catalog's shape, layered navigation queries tamed, category and listing pages that stay light at ten thousand SKUs.
Profiling, not guessing
Optimization without measurement is redecorating. Every engagement runs on instruments.
APM in production
Application monitoring on live stores, so slow transactions are named, not suspected.
Code-level profiling
Profilers on the hot paths: which block, which query, which loop. The fix targets the function, not the vibe.
Lab and field, both
Lighthouse shows what a robot sees, real-user data shows what Google ranks on. We report against both.
Before and after, in writing
Every fix lands with its measured gain against the baseline. You see what each dollar bought.
The admin can be fast too
Half our large-catalog conversations start with "and the admin is unusable." Backoffice speed is real performance work.
Indexers off the save path
Saves that trigger full reindexes make every edit a coffee break. Scheduled indexing fixes it.
Async grids and exports
Order grids, reports and exports moved off the request path, so operations don't freeze the team.
Imports at catalog scale
Product and stock imports built for volume, finishing in minutes, not overnight-and-failed.
The admin extension audit
Backoffice modules pile up quieter than frontend ones, and cost just as much. We weigh them too.
Infrastructure that scales when your traffic does
We engineer both ends: tuned code and right-sized infrastructure.
Hosting audit, included
Sometimes the cheapest second you'll ever buy is a config change. Every engagement checks.
Sized from evidence, not fear
Capacity planned from real traffic and load tests, so you're not paying December's bill in March.
Autoscaling when it matters
AWS architectures that scale out for the drop and Black Friday, then back in after the surge.
Adobe Commerce Cloud, actually tuned
Environment sizing, Fastly configuration and deploy strategy tuned to your store.
Deploys that don't drop traffic
Release strategies engineered so shipping never means downtime, even at peak.
Load-tested before peak
The store meets Black Friday having already survived it in a rehearsal.
Team that knows the code
We operate AWS infrastructure for production stores, so "code or server" stops being a blame game.
Hyvä, the structural fix when patching stops paying
There's a point where optimizing an old theme is bailing water. Hyvä replaces the hull.
Led by numbers, not zeal
If the audit shows the theme is the ceiling, we say so in writing, no sugarcoating: what tuning can still buy, what only Hyvä can deliver, and what each path realistically costs.
The most certified team doing it
55+ Hyvä certifications, the most certified and experienced Hyvä team worldwide.
Rebuilt without losing the store
Stores move from legacy themes to Hyvä with business logic and design intact, faster stores, same brand.
Green by default
Hyvä storefronts we ship hold 90+ Core Web Vitals in production, across regions, through peak.
Speed that stays fast
Plenty of stores are fast for a week after the invoice. Ours stay fast, because staying fast is part of the service.
A performance budget, enforced
Page-weight and score thresholds in writing, and every new feature measured against them.
Watched every 5 minutes
Real application pages checked around the clock, so regressions surface as alerts.
Regression gates on every release
Performance checks run in our quality system, so a slowing feature is caught in review.
Load-tested before it matters
Peaks and launches stress-tested in advance, so the store meets them already proven.
The numbers, in production
The UK store of a global coffee icon, rebuilt fast.
- PageSpeed from around 60 to 95+
- Conversion up 100% after the rebuild
- Built and live in one month
A global brand's storefronts, fast in every region.
- 90+ Core Web Vitals across 15+ storefronts worldwide
- One codebase, every region, through every peak
- World Traveler Award, Meet Magento NYC
A US luxury lighting and furnishings brand, fast without losing the editorial look.
- Image-heavy editorial pages engineered to load fast
- Hyvä storefront replacing the theme that capped performance
- Core Web Vitals in the green on a design-led catalog
America's neighborhood hardware stores, kept fast for years.
- A continuous Core Web Vitals program on a 100+ store network
- Store pickup, finder and rewards kept fast at national scale
- Speed maintained for years, not achieved once
What partners say about us
Magebit feels like part of our own team. They know our store inside out, handle our busiest gifting peaks, and keep raising the bar.
Sam Slater
eCommerce Manager
What I value most is consistency. Magebit knows our store inside out, responds fast, and keeps it running smoothly year after year.
Marian Gaidoš
CEO
Within just two to three months, they resolved issues that previously seemed unresolvable.
Tim Johnson
CTO
Why ambitious brands choose Magebit
#1 Adobe Commerce partner worldwide
The top-ranked Adobe Commerce agency on the planet, by Adobe themselves.
55+ Hyvä Certificates
The most certified Hyvä agency in the world. Confirmed by Hyvä themselves, twice.
Venta, our own Hyvä theme
A proven-fast foundation under dozens of live stores.
100+ brands’ stores actively managed
Speed maintained across all, with monitoring and regression gates.
Baymard and CXL certified team
So the fast version converts, speed and UX engineered together.
ISO certified
ISO 9001 & 27001 for quality and security, independently audited yearly.
Scrum Alliance certified team
Agile delivery that ships speed work in weeks, not quarters.
Every slow store is losing money on schedule
Merchants come to us with a PageSpeed screenshot & leave with a conversion story. We'll show you where the seconds go, what each one costs you and the exact plan to take them back.
Reviewed by Kristaps Rjabovs
Co-founder of Magebit, Forbes 30 under 30
Frequently asked questions
If you can't find the answer you're looking for, feel free to reach out to us. We're here to help!
We guarantee process, not a number, and anyone promising a specific score before seeing your store is selling a template. The audit establishes your realistic ceiling on the current theme, what tuning gets you there, and what a rebuild would add. Our production track record, 95+ PageSpeed and 90+ field vitals at global scale, is public and verifiable.
Scoped on the first call against catalog size, templates and whether peak testing is included, then quoted as a fixed price before anything starts. Remediation is quoted separately once findings show what's actually needed.
Only when the numbers say so, and the report shows what tuning can still buy on your current theme so you can compare. Plenty of stores get where they need to be without a rebuild, and we'd rather tell you that than sell the bigger project.
That's one of the most common reasons to commission this audit. Core Web Vitals only measure anonymous visitors on cacheable pages, so a store can pass them while checkout takes four seconds, logged-in browsing crawls and cron has been stuck for a fortnight. We profile the uncached journeys, the background work and the admin as standard.
Where peak readiness is the concern, yes, by agreement and at a time you choose. Steady-state numbers don't predict Black Friday, and pretending otherwise is how stores get surprised in November.
Yes, an anonymised sample on request. You should know what you're buying before you buy it.
None. Measurement and profiling are read-only and rate-limited. Remediation only happens if you commission it separately.
Show us your slowest page
Your store, your scores, your worst offender. One conversation gets you an honest read on where the seconds go and what they cost, before any pitch.
- 1
A real specialist replies
Not a sales script.
- 2
An honest speed read
Your ceiling, your quick wins, your structural calls.
- 3
No obligation
The findings are yours to keep.