What does Magento speed optimisation involve?
Magento speed optimisation covers profiling, caching, server, code and extensions, frontend and proof. Magento has many layers where speed can be lost: misconfigured caching, slow hosting, heavy extensions, unindexed queries, oversized images and a frontend that loads far more than it needs. Anthony McGrath does the work himself, with 22 years in digital marketing, for businesses in the UK, the US, Dubai and Australia.
Why Magento stores get slow
Magento has many layers where speed can be lost: misconfigured caching, slow hosting, heavy extensions, unindexed queries, oversized images and a frontend that loads far more than it needs.
Guesswork does not fix it. I profile real requests, find the bottlenecks and fix them in order of impact, from Varnish and Redis setup to custom code and the theme, then measure the result for real shoppers.
- Best for
- Magento 2 and Adobe Commerce stores with large catalogues, B2B or complex integrations
- What you get
- Profiling, Caching, Server, Code and extensions, Frontend, Proof
- First step
- Audit: code, extensions, hosting, speed and security checked, with a plain-English report on the risks.
- Where
- The UK, the US, Dubai and Australia, working remotely across time zones
- Who does the work
- Anthony McGrath, hands-on, with 22 years in digital marketing
What's included
A full performance fix across the whole Magento stack.
Profiling
New Relic or Blackfire traces; Slow query log analysis; Extension impact report; Real user Core Web Vitals.
Caching
Varnish full page cache; Redis for cache and sessions; Cache hole punching fixed; Cache warming.
Server
PHP-FPM and OPcache tuning; MySQL and OpenSearch tuning; CDN and image delivery; Hosting advice if needed.
Code and extensions
Slow custom code rewritten; Heavy extensions replaced; Indexers on schedule; Cron jobs tidied.
Frontend
JavaScript bundling and deferral; Critical CSS; Images in WebP and AVIF; Or a full move to Hyvä.
Proof
Before and after report; Monitoring and alerts; Tracking checked; A plan to keep it fast.
Before and after
An example of a performance project on a Magento 2 store with 20,000 products.
An example of the kind of change this work aims for, based on typical starting points. It is not a promise or a specific client result: every business starts somewhere different.
How it works
- AuditCode, extensions, hosting, speed and security checked, with a plain-English report on the risks.
- Plan and priceA staged plan with priorities, timings and fixed costs, so nothing is open-ended.
- Build and testWork done in a proper development and staging setup, with orders, integrations and indexing tested.
- Deploy and supportZero-downtime deployment, monitoring, patches and a developer on hand each month.
Questions
Why is my Magento store so slow?
Usually a mix of caching that is not working fully, heavy extensions, slow database queries and a heavy frontend. Profiling shows which matters most for your store.
Do I need to move to Hyvä?
Not always. Server and code fixes give big gains on their own. For the best mobile scores, Hyvä is usually the next step.
Do I need new hosting?
Sometimes. If hosting is the limit I will show you the evidence and the options.
Will changes affect live orders?
All work is tested in staging first and deployed carefully, with the live store monitored.
Platforms and tools
Losing sales to a slow Magento store?
Send me your store. You get a clear view of what is slowing it down and a fixed price to fix it.
Get your store speed checked