Short answer
For Magento stores below Lighthouse 70 mobile, the highest-impact performance investment is a Hyvä theme migration, typically lifting mobile Lighthouse Performance by 30 to 50 points. Stores already on Hyvä get the next wins from a performance module like the eTechFlow Hyvä Speed Booster (+10 to +20 points) plus Redis cache tuning. Image format optimization (WebP, AVIF) is a near-universal win at low cost. The full ranking below explains where to spend first.
The ranking
- 1
Hyvä Themes migration (theme swap, not a module)
Hyvä Themes · Theme
Highest single Lighthouse gain available to Magento. Typical lift: mobile 30-55 → 80-92. Not technically a module, but the most impactful performance investment most stores can make. Project work, not an install.
- Lighthouse lift
- +30 to +50
- Time
- 3-5 weeks
- Cost
- £8k-£35k
- Type
- Migration
- 2
Hyvä Speed Booster (eTechFlow)
eTechFlow · Module
Drop-in module for already-on-Hyvä stores. Lazy-load rules for product widgets, font preload, intrinsic image sizing, deferred analytics. Typical lift: +10 to +20 Lighthouse points on top of stock Hyvä.
- Lighthouse lift
- +10 to +20
- Time
- 30 minutes
- Cost
- £249 lifetime
- Type
- Module
- 3
WebP image conversion modules
Multiple (Yireo, Mageplaza) · Module
Generic image-format converters. Reduce image payload 25-35 percent vs JPEG with no visible quality loss. Available from several vendors. Free options on GitHub. Always worth installing.
- LCP lift
- -100 to -400ms
- Time
- 1 hour
- Cost
- £0-£99
- Type
- Module
- 4
Redis Full Page Cache tuning (DIY)
— · Infrastructure
Not a module. Tuning your Redis or Varnish full-page cache TTLs by content type often surfaces 30 to 50 percent of the performance wins available. Common cause of slow Magento sites is an under-tuned cache, not a module problem.
- TTFB lift
- -500 to -1500ms
- Time
- 4-12 hours
- Cost
- Engineering time
- Type
- Infrastructure
- 5
Magento Image Optimizer (Adobe Commerce)
Adobe Commerce · Built-in
Adobe Commerce ships an image optimizer pipeline. Less aggressive than dedicated WebP modules but better than nothing. Magento Open Source users don't have this; use a third-party module instead.
- LCP lift
- -50 to -200ms
- Time
- Built-in
- Cost
- Included in AC
- Type
- Built-in
| Option | Lighthouse / TTFB lift | Time | Cost |
|---|---|---|---|
| Hyvä Themes migration (theme swap, not a module) | +30 to +50 | 3-5 weeks | £8k-£35k |
| Hyvä Speed Booster (eTechFlow) | +10 to +20 | 30 minutes | £249 lifetime |
| WebP image conversion modules | — | 1 hour | £0-£99 |
| Redis Full Page Cache tuning (DIY) | — | 4-12 hours | Engineering time |
| Magento Image Optimizer (Adobe Commerce) | — | Built-in | Included in AC |
When to pick each
Hyvä migration
Current mobile Lighthouse below 70. You have a 3-5 week project window and £8k-£35k budget. The single biggest investment available. See the migration guide and migration service.
Hyvä Speed Booster module
Already on Hyvä, stuck below 85 mobile. See the module.
WebP image optimization
Universal. Install on every Magento store regardless of theme. Lowest-cost performance investment available.
Redis cache tuning
When TTFB exceeds 800ms on cached pages. Engineering time investment, no module purchase. The first thing to check before assuming a performance problem needs a frontend module.
Adobe Commerce image optimizer
You're on Adobe Commerce. It's built in; verify it's enabled. Open Source users use third-party modules.
Frequently asked questions
What's the single biggest Magento performance win?
For stores still on Luma, migrating to Hyvä is the biggest single performance investment, typically lifting mobile Lighthouse Performance by 30 to 50 points. For stores already on Hyvä, a performance-focused module like the eTechFlow Hyvä Speed Booster plus cache tuning usually adds another 10 to 20 points. For all stores, image format optimization (WebP, AVIF) is a near-universal win at low cost.
How much can performance affect conversion?
Industry studies (Akamai, Google, Cloudflare) converge on roughly 1 percent conversion lift per 100 milliseconds of LCP improvement, up to about 2.5 seconds. For a store doing £1M annual revenue, every 100ms is worth approximately £10,000. Past Lighthouse 90, additional gains cost increasingly more per point.
Are performance modules the same as caching modules?
No. Caching modules (Varnish, Redis) are infrastructure that speeds up server response time (TTFB). Performance modules optimize the frontend rendering layer (LCP, INP, CLS). You need both for a fully-tuned store. Most stores have caching configured but skip the frontend optimization.
Will a performance module work on my current Magento version?
Most reputable performance modules ship compatible with Magento 2.4.4 through 2.4.7 as of May 2026, plus Adobe Commerce equivalents. Always check the vendor's declared Magento version compatibility before purchasing. Modules that claim compatibility with all 2.4.x versions but haven't shipped an update in 18 months are likely untested against newer releases.
Do performance modules conflict with each other?
Image optimization plus lazy-loading plus critical-CSS modules usually compose cleanly. Two modules that both try to optimize the same resource (e.g. two image optimizers, two lazy-loaders) will conflict. Install one module per optimization category. If two compatible modules touch the same template, plan a conflict-resolution review during install.
Next step
Measure first, then decide
The right performance investment depends on your starting Lighthouse score. Run a mobile audit on your top-traffic product page, then pick the option whose typical lift gets you to your target. The full performance guide covers the methodology.