Estimate Project
Adobe Commerce speed services

Magento performance optimization services that turn lost seconds into recovered revenue.

Slow Magento stores leak revenue every minute. You fix the bottlenecks once. We keep them fixed with a plan that suits your traffic and your team.

Get Your Speed Audit See Plan Options
140+ stores audited80+ stores tuned24 stores on continuous service level agreement
0ms

Every 100 milliseconds shaved off load time lifts conversion by roughly 1 percent on most Magento stores.

0%

Of mobile shoppers abandon a page if it takes longer than 3 seconds to load.

0s

The Core Web Vitals Largest Contentful Paint threshold Google rewards. Most Magento stores ship at 4 seconds or worse.

Adobe Commerce merchant reviewing Core Web Vitals scores on a desktop monitor in a sunlit office
The cost of a slow store

Two stores. Same catalog. Different revenue.

The slow store loses shoppers between the homepage and the cart. The fast store gets paid before the fold has finished loading. The difference is fixable.

Before optimizationTypical Magento 2.4 store

The slow store

  • Largest Contentful Paint at 4.7 seconds on the homepage. Hero image waits on uncompressed assets and unprioritised CSS.
  • Cart pages call 38 third-party scripts. Interaction to Next Paint spikes to 380 milliseconds when the shopper finally taps add to cart.
  • Lighthouse score sits at 38. Google quietly drops the store down the rankings as Core Web Vitals fail month after month.
  • Mobile bounce rate climbs to 62 percent. Paid traffic costs rise to push the same conversion rate.
After optimizationSame store, after sprint 1

The fast store

  • Largest Contentful Paint at 1.2 seconds on the homepage. Hero asset preloaded, CSS critical path inlined, fonts deferred.
  • Third-party scripts down to 9, lazy loaded after interaction. Interaction to Next Paint at 110 milliseconds with no jank on add to cart.
  • Lighthouse score sits at 92. Core Web Vitals all green across mobile and desktop, tracked in Search Console week by week.
  • Mobile bounce rate drops to 41 percent. Paid cost-per-click holds steady while organic traffic climbs.
Shopper holding a phone showing an Adobe Commerce Hyva product page loaded fast after performance optimization
Live performance dashboard

What Core Web Vitals look like after we tune your store.

This is a sample of the dashboard you see every week on a continuous plan. Real metrics, real thresholds, real movement. Tap a metric to see the before reading.

redefine.ops · performance / live
Monitoring live

› Tap any metric to flip the card between current reading and your starting baseline.

Page-by-page Largest Contentful Paint, mobile p75

last 7 days
Homepage1.2s
Category /coffee/single-origin1.6s
Product /coffee/ethiopia-yirgacheffe1.9s
Cart /checkout/cart2.2s
Checkout /onepage2.4s

This week's tickets

3 open
  • Tuning
    Defer Google Tag Manager until first interaction
    Owner Aman · PR #1142
  • Review
    Image content delivery network swap, WebP fallback
    Owner Priya · staging green
  • Shipped
    Redis full-page cache key fix
    Owner Rohan · prod, hit rate 94%
Time to First Byte
0ms
Cache hit rate
0%
PHP requests
0%
Conversion lift
0%▲

Sample data, anonymised from a live continuous plan. Your dashboard reads your own real-user monitoring and Search Console feeds, not lab averages.

What we tune

Every layer your Magento store loads through.

A page that paints in 1.2 seconds is the sum of small wins across frontend, backend, database, cache, and edge. We work them in order, biggest revenue impact first.

Frontend optimization

Critical render path, fonts, and JavaScript discipline.

  • Critical CSS inlined, non-critical CSS deferred. Web fonts preloaded with font-display: swap.
  • RequireJS bundle audit. Dead modules removed. Magento user interface components lazy loaded.
  • Third-party tag governance. Google Tag Manager, chat widgets, and pixels deferred until after first interaction.
  • Layout shift killed at the source. Image dimensions reserved, banner Cumulative Layout Shift removed.

Typical storefront wins (first pass)

−35%
Largest Contentful Paint versus baseline real-user monitoring
−60%
Total blocking time after script and font deferral
CLS
Held under 0.1 on product page, listing page, and checkout once media and promotions are sized

Numbers vary by theme, catalog size, and third-party load. We tie every change to your real-user monitoring field data, not a single Lighthouse snapshot.

Performance engineer reviewing Adobe Commerce frontend performance traces and Core Web Vitals on multiple monitors with Chrome DevTools and PageSpeed Insights

Backend and PHP

PHP 8.3 tuning, OPcache, Xdebug off in production, profiler-led slow query fixes, layout XML cleanup, and async indexers.

  • Production PHP configuration and FastCGI Process Manager pool review: memory limits, max children, and request timeouts aligned to traffic peaks.
  • Plugin and observer audit: remove redundant plugins, collapse around hot checkout and cart flows.
  • Cron and consumer hygiene: staggered schedules, backlog monitoring, and queue workers sized for bursts.

Database and cache

MySQL index review, Redis full-page and session split, Varnish Edge Side Includes policy, and a cache hit rate above 90 percent.

  • Slow query and lock contention passes on catalog search, checkout, and admin grids.
  • Redis eviction policy and key time-to-live strategy so sessions never evict full-page cache under load.
  • Varnish ban versus purge rules documented per deploy so cache clears stay predictable.

Content delivery network and edge

Fastly or Cloudflare cache rules, stale-while-revalidate, image content delivery network with WebP fallbacks, and edge geographic policy that respects Payment Card Industry scope.

  • HTML versus static asset time-to-live tiers, with bypass rules for logged-in and cart routes.
  • Edge compression, HTTP/2 and HTTP/3 checks, and origin shielding where it pays off.

Real-user monitoring and alerting

Real-user monitoring on every page, p75 thresholds wired into Slack and PagerDuty, and weekly trend reports your buying team can read.

  • Per-template dashboards: home, product listing page, product detail page, cart, and checkout with device and geographic splits.
  • Release annotations so every deploy's impact on Largest Contentful Paint and Interaction to Next Paint is obvious within hours.

Search and catalog

Elasticsearch and OpenSearch tuning, layered navigation query cost, and catalog indexer scheduling that does not spike time to first byte during peak hours.

  • Shard and replica sizing aligned to catalog volume and query throughput.
  • Partial reindex triggers moved off scheduled tasks and on to product-save events to cut queue lag.
  • Autocomplete and facet queries profiled; slow filter combinations capped before they reach production.
After the tune

You keep the playbook, not a black box.

Every engagement closes with prioritised backlog items, configuration diffs, and monitoring hooks your team can own. That way speed stays green after we step back from the keyboard.

Written runbooks

Deploy checklist, cache purge steps, and rollback notes tied to your environments.

Baseline versus after report

Real-user monitoring charts, Search Console coverage, and revenue-facing metrics where you share them.

Optional continuity

Lightweight retainer for regression watches after major releases or peak seasons.

Onboarding process

From slow Magento store to Core Web Vitals green in 21 days.

No long discovery cycle. We start with a 5-day audit, ship the biggest wins in week 2, and verify the gains in week 3. You get a baseline, a plan, and proof you can show your board.

audit/baseline · day 5
Baseline report
Largest Contentful Paint
4.7s
Poor
Interaction to Next Paint
380ms
Poor
Lighthouse
38
Poor
Top 5 opportunities by revenue impact
  1. 1Hero image preload · estimated +$48,000 per year
  2. 2Defer 22 third-party tags · estimated +$31,000 per year
  3. 3Redis cache key fix · estimated +$22,000 per year
  4. 4Image content delivery network with WebP · estimated +$18,000 per year
  5. 5RequireJS bundle trim · estimated +$9,000 per year
github.com/store/perf-sprint-12 · 7 open
Sprint 12 · day 11
Merged
PR 1140 · Inline critical CSS for homepage
Aman
Merged
PR 1141 · Preload hero image, fetchpriority=high
Priya
Review
PR 1142 · Defer Google Tag Manager until first user interaction
Aman
Staging
PR 1143 · Image content delivery network swap with WebP fallbacks
Priya
Staging
PR 1144 · Redis full-page cache key normalization
Rohan
Sprint burndown62% complete
verify/before-after · day 17
Verification report
Before · day 1 baseline
Largest Contentful Paint4.7s
Interaction to Next Paint380ms
Cumulative Layout Shift0.32
Lighthouse38
After · day 17
Largest Contentful Paint1.2s
Interaction to Next Paint110ms
Cumulative Layout Shift0.04
Lighthouse92
Business impact, week 3
+14.2%
Conversion
+9.6%
Sessions
−37%
Bounce
monitor/rum · last 30 days
Real-user monitoring trend
All green
Largest Contentful Paint, mobile p75, last 30 days
Sep 14avg 1.3sOct 14
Alerts fired
2
Both resolved under 1 hour
Code reviews
14
Budget held on every release
Plans and service level agreements

Three plans. Real prices. No partner runaround.

You see the price before the call. You see the service level agreement before you sign. You see exactly what is included, and what is not.

One-off

Speed Audit

For stores that want a baseline and a roadmap before committing to a build.

$4,800
Flat fee. 5 business days.
  • Real-user monitoring capture across 4 page templates
  • Lighthouse and WebPageTest analysis, mobile and desktop
  • Backend trace, slow query report, cache audit
  • Prioritised opportunity list, revenue-modelled
  • 60-minute readout with your engineering team
Response service level agreement
5 business days
Get The Audit
Most popular

Speed Sprint

For stores that want the wins shipped in three weeks, with a hand-off your team can hold.

From $24,000
Scoped. 21-day sprint. Audit included.
  • Everything in Speed Audit
  • Top 10 opportunities shipped to production, on your repository
  • Cache, content delivery network, and edge configuration
  • Image content delivery network setup with WebP fallback
  • Before-and-after report, signed off by your team
  • 30 days of free real-user monitoring post-launch
Response service level agreement
24 hourson every sprint ticket
Plan a Speed Sprint
Retainer

Continuous

For stores that want speed treated as a service level agreement, not a side project. Monthly cadence, locked-in budget.

From $4,500 / month
Quarterly commit. Roll-forward hours.
  • Real-user monitoring dashboard, weekly report
  • Performance budget enforced on every pull request
  • 20 hours of optimization work per month
  • Slack and PagerDuty alerting
  • Emergency cover during peak trade weeks
Response service level agreement
1 hourfor production-down alerts
Request Retainer Terms
What you get
Typical partner
Freelance developer
Redefine
Price published before the call
Response service level agreement on the contract
Sometimes
Before-and-after report tied to revenue
Rare
Performance budget on every release

Comparison reflects how the broader Magento partner market typically scopes performance work. Your existing partner may already do these things, in which case we are happy to step aside.

Cost of staying slow

Slide the dial. See what slow pages cost you.

A conservative model. 100 milliseconds of speed lifts conversion by about 1 percent on most Magento stores. Plug in your numbers, watch the recovered revenue update in real time.

10k350,0002M
$20$120$500
0.5%1.8%6%
200ms1,500ms3.5s
Projected recovered revenue
$0per month
$0per year
Conversion rate lift modelled
15%
Extra orders
0
per month
Payback on Sprint
0 months

Model uses the Deloitte and Akamai meta-finding that every 100 milliseconds of mobile load time shaved off correlates to roughly 1 percent uplift in conversion. Your mileage will vary. The audit gives you a number that is yours.

Proof

A specialty roaster lifts pageviews 35 percent after the slow store was rebuilt.

The same playbook works on Magento. Performance is platform-agnostic at the buyer level. Slow page, lost shopper. Fast page, paid shopper.

Specialty coffee roaster's Adobe Commerce Hyva storefront displayed on a tablet inside a working roastery
Specialty coffee · direct-to-consumer

Lizzy's Fresh Coffee

What they do

A specialty coffee roaster in Ketchum, Idaho. Customizable coffee products sold online, with custom labels, roast dates, and personalisation flows.

Problem

Multiple outdated storefronts with slow performance, payment gateway issues, limited data storage, and a customer experience that did not scale with seasonal demand. Personalisation flows broke under load.

Solution

Site rebuild with infrastructure upgrades, mobile-first responsive layout, performance optimization, a search engine optimization-led navigation pass, and a personalisation module rebuilt to ship orders without checkout friction.

Result
0%

Pageview lift after rebuild

0x

Faster mobile interaction

0%

Of personalisation orders completing without error

Improved performance lifted search rankings. The customization module increased conversion. Lizzy's online presence was revitalised with room to ship new initiatives without rebuilding again.

Why teams pick Redefine

Speed is the product. Not a side gig.

Most Magento partners treat performance as something the development team will get to. We treat it as the deliverable. The numbers move because the work is led by people who do this every day.

01

Plans on the page

Audit, sprint, retainer. Prices, scope, and service level agreement published before you call.

02

A real audit, not a Lighthouse screenshot

Backend traces, real-user monitoring data, third-party governance review, and a revenue-modelled opportunity list.

03

Hold the gains

Performance budget on every pull request, real-user monitoring alerting, and a monthly trend review tied to revenue.

04

On your repository, with your team

We commit to your branches and ship via your release process. No black boxes. No mystery vendor extensions. Your team can read every change.

05

Tuned for Adobe Commerce, not generic web

Layout XML, RequireJS, Magento_PageBuilder, full-page cache, Redis full-page cache keys, indexers. The platform-specific bottlenecks generic web shops never reach.

06

Peak-trade cover when it counts

On a continuous plan, you get an engineer awake during Black Friday and stocked with a runbook for your store. One hour response on production-down.

Closing questions

Magento performance optimization, answered.

Most stores we tune land in the Core Web Vitals green zone within 21 days, with mobile Largest Contentful Paint under 2 seconds and a Lighthouse mobile score above 85. The exact gain depends on your starting point, extension footprint, and hosting. The audit gives you a number tied to your store, not a market average.

Both. Adobe Commerce Cloud, Magento Open Source 2.4 and above, and self-hosted Magento. The frontend, RequireJS, and image work are identical. Backend and cache work changes with the host. Our scope adapts.

We audit every extension on day one. Many performance issues sit inside third-party code. If an extension is the bottleneck, we will tell you, fix it where possible, and where not, advise replacement. We work on your repository, with your team, in your release process.

Most stores decay back toward the original baseline within 90 days. New extensions, marketing tags, and design changes erode the gains. The Continuous plan exists for this reason. Performance budget on every pull request, monthly trend reports, and emergency cover when peak trade arrives.

Yes. The Speed Audit is a 5-business-day, $4,800 flat fee with no obligation to continue. You get the baseline report and the prioritised opportunity list. Many teams take the report to their existing development partner and have them ship the fixes. We are fine with that.

One hour for Continuous-plan clients. 24 hours during an active Speed Sprint. Audit clients get business-day response. The service level agreement is in the contract, not a sales promise. Emergency support outside these plans is also available through our emergency support response service.

Fit check

We will turn you away if it is not the right fit.

The wrong client is worse for both of us than no client. Read the columns, and reach out only if you sit clearly on the left.

Good fit
  • Magento 2.4 or Adobe Commerce store with at least 25,000 sessions per month
  • Internal development team or partner who can review pull requests within 48 hours
  • A staging environment that mirrors production, or a willingness to set one up
  • Comfort with shipping to production weekly, not quarterly
  • A real revenue case for speed, not a Core Web Vitals checkbox exercise
Not a fit
  • Magento 1, or any pre-2.4 build, without a migration plan in place
  • No staging environment and no appetite to ship to production without dry runs
  • Stores doing under 5,000 sessions per month. The payback is not there yet.
  • A pure search engine optimization consulting brief with no engineering time available
  • Pages that need a redesign, not a tune-up. We can refer you to a partner for that.

Not sure? Tell us your situation and we will be straight with you.

Tell us about your store

Submit a brief. Get a scoped plan in 3 business days.

No discovery call required up front. Tell us where the store is slow, what your team can ship, and we will return a written plan you can hand to your board.

What do you want help with? (tap any that apply)
First reply within 1 business day
Not "we will be in touch." A named engineer reads your brief and responds.
Scoped plan, not a brochure
Line-by-line scope, named owners, real deadlines, and a price you can take to procurement.
140+ stores audited, 24 on continuous service level agreement
Sector range from direct-to-consumer apparel to business-to-business distribution. Reference list shared on request.
On your repository, your team owns the code
Every commit is yours. Every change reviewable. No vendor extensions you cannot maintain.
Related services
Last word

See the audit before you commit to anything.

The $4,800 Speed Audit gives you a baseline, a revenue-modelled opportunity list, and a 60-minute readout. If you walk away after that, your team gets a roadmap. If you stay, the audit fee credits to the sprint.

Get Your Speed Audit
Small ecommerce team gathered around a laptop reviewing post-optimization Magento 2 admin Cache Management metrics

Get on a call with us to see how we can help you

Get a Quote