Magento hosting · Performance

Magento performance comes down to memory and caching

Magento runs well with enough memory, a large code cache and Redis for sessions and pages. Solo gives one store 4 GB of memory for £29/month, with PHP already set up for Magento.

Memory by plan

Magento asks for 2 GB. Here is what each plan gives a site.

Each figure is a firm allowance for each site, held for that site alone.

PlanPriceMemory per siteVerdictSuits
Solo£29/mo4 GBRecommendedMost single stores. Twice the memory Magento asks for, with room for reindexing during trading hours.
Solo Plus£59/mo8 GBHeadroomA busy store: large catalogue, heavy admin work, big sale days.
Pro£59/mo2 GBSeveral storesUp to 10 stores or sites, each at Magento's minimum.
Agency£179/mo3 GBSeveral storesAgencies running up to 25 client stores, with team roles.
Business£24/mo1 GBToo smallBelow the 2 GB Magento asks for. Fine for WooCommerce, not recommended for Magento.

Fixed GBP prices. Extra memory is £6 per GB a month, for one site you choose. Compare every plan

What slows Magento down

Three things make Magento heavy. Each has an answer here.

Many database lookups per page

Magento spreads product details across many tables, so one uncached page can need dozens of lookups. On Solo, Pro and Agency your store’s MySQL database runs inside its own container, so those lookups stay close.

A very large codebase

Magento has tens of thousands of PHP files. A small code cache keeps throwing them out and recompiling them. Ours holds up to 60,000 files in 512 MB.

Reindexing while you trade

Rebuilding prices, stock and catalogue rules is hard work for the processor. Your store has its own processor share, so a reindex runs without queueing behind other customers.

PHP settings

Every Magento container starts with PHP set up for Magento

  • A 756 MB PHP memory limit, enough for Magento’s admin and imports
  • A 512 MB code cache (OPcache) holding up to 60,000 files
  • PHP 8.1, 8.2 or 8.3, to match your Magento release
  • Every setting can be changed for each site from the dashboard
PHP defaults in every Magento container

memory_limit = 756M

opcache.memory_consumption = 512

opcache.max_accelerated_files = 60000

# change any of these per site in the dashboard

What to keep in Redis

  • Sessions: logged-in customers and baskets stop hitting the database
  • The back-end cache: settings, layouts and blocks served from memory
  • The full-page cache: Magento's own page cache, so repeat visits skip PHP and the database

Caching

Add managed Redis from £6 a month

Add a managed Redis database to any paid plan from the dashboard. It is charged by its memory: £6 per GB a month, starting at 1 GB. The Redis extension is already switched on in every Magento container, so connecting it is a change to Magento's env.php file.

Together: the code cache keeps Magento's code compiled, Redis keeps sessions and pages out of the database, and ScaleShield stops bots from asking for slow, uncached pages in the first place.

Judge it on your own store's graphs

Your catalogue, extensions and theme decide your store's speed more than any test figure we could print. So we give you the graphs instead: 7 days of memory and processor use per site, and uptime checks as often as every minute, with alerts in your dashboard or to Slack.

Move your store, watch the graphs for a week, and decide. Every paid plan has a 30-day money-back guarantee. Related reading: how slow websites kill conversions.

FAQ

Magento performance questions

Do you include Varnish?

No. Magento's built-in full-page cache stored in a managed Redis database suits most stores and is simpler to clear correctly. If your store needs Varnish, talk to us before you move and we will tell you whether we are the right fit.

Can I change PHP settings myself?

Yes. Memory limit, execution time and PHP extensions can be changed for each site from the dashboard, and you choose the PHP version (8.1, 8.2 or 8.3). The defaults are already set for Magento: a 756 MB memory limit and a 512 MB code cache holding up to 60,000 files.

What happens if my store hits its memory limit?

Each site's memory is a firm limit, so no other site can take yours. The dashboard shows memory and processor graphs for the last 7 days, so you see the limit coming. You can then move to a bigger plan, or add memory to that one site at £6 per GB a month.

How do Magento cron and indexers run?

Set Magento's cron from the dashboard's cron jobs page, so indexers, price rules and emails run on time. You can also run a reindex yourself from the terminal in your browser.

Give your store memory that is held for it alone

4 GB of memory on Solo, PHP set up for Magento, managed Redis when you want it and the graphs to check it is working.