Blog › Adobe Commerce › How Do I Speed Up an Adobe Commerce Store Without Adding Developer Time?
Noibu blog

How Do I Speed Up an Adobe Commerce Store Without Adding Developer Time?

How do I speed up an Adobe Commerce store without adding developer time?

To speed up an Adobe Commerce store without adding developer time, start with changes the Admin already controls: confirm full page cache runs on Varnish or Fastly, turn on Fastly image optimization, set indexers to Update on Schedule and cut unused third-party scripts. Code changes still need a developer, but an AI agent can find, rank and draft them.

Last updated November 20, 2026

How do you speed up an Adobe Commerce store without adding developer time? Adobe Commerce (formerly Magento) is fast when it is configured the way Adobe recommends and slow when it is not, and most of the slowdowns come from a short list of causes: cache misses, heavy extensions, unbundled JavaScript, oversized images, third-party scripts and stores that are not running in production mode. Some of those causes sit in Admin settings a merchandiser or ecommerce manager can change. The rest sit in code, and the goal there is not to skip the developer but to stop spending developer hours on investigation, so developers only review a change that is already found, ranked and written.

Key takeaways

  • Measure Adobe Commerce speed with real-user Core Web Vitals at the 75th percentile: LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less.
  • Adobe recommends Varnish for full page cache, and on Adobe Commerce on cloud infrastructure Fastly caches pages at the edge, so cache misses are the first thing to check.
  • Fastly image optimization, indexer mode and asynchronous email are Admin settings that do not require code changes.
  • Production mode, JavaScript bundling, extension clean-up and theme changes still need a developer or agency, so the time saving comes from removing the investigation, not the review.
  • Noibu's Performance Agent ranks the slowest Adobe Commerce page groups from real shopper traffic, finds the root cause and writes the change for a developer to approve.

Part of: How Do I Monitor an Adobe Commerce Store for Errors That Cost Sales?

Why is my Adobe Commerce store slow?

An Adobe Commerce store is usually slow for one of six reasons, and each one leaves a different signature. Cache problems make every page slow to start responding. Heavy or conflicting extensions add server time and extra JavaScript to specific templates. Unbundled or unminified JavaScript delays interaction. Oversized product images push out Largest Contentful Paint. Third-party scripts compete with the store's own code on the main thread. And a store left outside production mode generates static files at run time instead of serving them from cache.

Adobe's own guidance covers most of these. The Adobe Commerce configuration best practices say Adobe highly recommends Varnish as an efficient production page cache, recommend Update on Schedule for indexers, and recommend third-party tools such as r.js for JavaScript bundling rather than the deprecated settings that merge JavaScript and CSS files. The table below maps each cause to what Adobe recommends and who can usually make the change.

Common Adobe Commerce speed causes and who can change them
CauseWhat it looks likeRecommended actionNeeds a developer?
Full page cache misses (Varnish or Fastly)Slow server response on category and product pages, worst after deploys or cache flushesUse Varnish in production; on cloud, Fastly caches responses at the edgeChecking cache status, no; changing cache rules or uncacheable blocks, yes
Heavy or unused extensionsSpecific templates slow down, often after a module install or upgradeReview modules and customizations that affect performanceYes, to disable or remove safely
JavaScript bundling and minificationMany small script requests, slow interaction and poor INPMinify CSS and JavaScript; bundle with third-party tools such as r.js, not deprecated mergingYes
Oversized imagesSlow LCP on product and category pages, especially on mobileFastly image optimization for resizing and WebP conversion at the edgeNo, if Fastly is already set up; it is an Admin setting
Third-party scriptsLong tasks from tags, chat, reviews and personalization widgetsRemove unused tags and load the rest later where possibleRemoving tags in a tag manager, no; changing load order in the theme, yes
Not in production modeStatic files generated on request, slow first loads, errors shown to shoppersProduction mode for any production systemYes, set from the command line

Third-party scripts deserve their own check because they grow quietly: each marketing or personalization tool adds a tag, and none of them shows up in the Adobe Commerce codebase. How to find which third-party scripts are slowing down your store walks through measuring each one before deciding what to cut.

What does a fast Adobe Commerce store look like?

A fast Adobe Commerce store passes Core Web Vitals for real shoppers, not just in a lab test. Google's Core Web Vitals guidance on web.dev sets the good thresholds as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads and split between mobile and desktop. An Adobe Commerce store that meets those numbers on product, category, cart and checkout pages is fast where it counts.

Speed matters for revenue, not just scores. In the Milliseconds Make Millions study, commissioned by Google and run by 55 and Deloitte across 37 brand sites and more than 30 million sessions, a 0.1 second improvement in mobile site speed raised retail conversion rates by 8.4%. Not every metric moves conversion equally, which is covered in which Core Web Vitals actually move ecommerce conversion, and product pages are usually where LCP problems cost the most, as explained in how to improve LCP on ecommerce product pages.

Which Adobe Commerce speed changes can I make without a developer?

Several Adobe Commerce speed changes live in the Admin and need an administrator, not a code deploy. The first is checking the cache. In System, Tools, Cache Management, every cache type, including Page Cache, should show as enabled. On Adobe Commerce on cloud infrastructure, Adobe's performance optimization guide notes that Fastly caches responses at the edge to reduce load on the origin server, and that a cacheable page returns HIT, or a HIT and MISS pair, on later loads. Pages that keep returning MISS are a signal to pass to a developer.

The second is image optimization. Adobe's Fastly image optimization documentation describes real-time resizing and format conversion at the Fastly edge, including automatic WebP for browsers that support it. An administrator enables it under Stores, Settings, Configuration, Advanced, System, in the Full Page Cache section, once the Fastly module and back end are already configured. Deep image optimization, which hands product image resizing entirely to Fastly, is off by default and worth testing on product images first.

The third is background work. Adobe recommends Update on Schedule for indexers in production, which an administrator can set in Index Management, and asynchronous email notifications move order and checkout email processing out of the shopper's request. Neither change touches the theme, and both reduce the work done while a shopper waits.

Which Adobe Commerce speed changes still need a developer?

Some Adobe Commerce speed work cannot be done honestly without a developer or the agency that holds the code. Production mode is one: Adobe's application modes documentation says production mode is best for deploying Adobe Commerce on a production system, because it serves static view files from cache and never displays errors to shoppers. Switching modes is a command-line change that belongs in the deploy process.

JavaScript bundling, extension clean-up, cache rules for blocks that break full page cache, and theme changes such as preloading the main product image or deferring scripts also need someone with access to the repository. The minify and bundling settings in the Admin Developer tab are only available in Default or Developer mode, and Adobe notes that tab is not available on cloud infrastructure, so on most production stores these are code changes. If an agency maintains the store, how AI agents fit when your agency holds the Adobe Commerce code covers how the review step works.

The developer time that can be removed is the investigation. Finding which page group is slow, for which device, from which cause, and how much revenue flows through it is usually where hours go. When that work arrives already done, with the change written, a developer's job becomes a review.

How do you speed up Adobe Commerce without adding developer time?

The process below keeps developer time to review and deployment. It is the same approach used in how to speed up a BigCommerce store without a developer, adjusted for the Adobe Commerce causes above.

Five steps to a faster Adobe Commerce store with developers only reviewing

  1. 1

    Measure real shoppers

    Collect Core Web Vitals from real traffic by page group and device, at the 75th percentile.

  2. 2

    Rank by revenue

    Order slow page groups by the traffic and orders that pass through them.

  3. 3

    Make Admin changes

    Check cache status, enable Fastly image optimization, set indexers and cut unused tags.

  4. 4

    Hand over a written change

    Give developers the root cause and a ready patch to review, not a ticket to investigate.

  5. 5

    Measure before and after

    Compare the same page group's vitals and conversion once the approved change is live.

Step two is the one most teams skip. A slow store locator page and a slow product page are not equal problems, and ranking by the orders that flow through each page group keeps the developer review queue short and focused on the changes that pay back.

How does Noibu's Performance Agent speed up an Adobe Commerce store?

Noibu's Performance Agent handles the investigation steps for an Adobe Commerce store. It measures Core Web Vitals from real shopper traffic, ranks the worst-performing page groups, such as product, category or cart pages, and identifies the root cause, for example an uncached block, a heavy script or an oversized hero image. It then writes the patch and stages the change for review, so the work does not wait behind a development cycle. A developer or the agency that holds the code approves it, and nothing ships without that approval.

For an Adobe Commerce team, that turns a vague request to make the site faster into a ranked list of slow page groups, each with a cause and a written change ready to review. Developers spend their time checking and deploying, not profiling. The Performance Agent works in the Noibu console and in Claude, ChatGPT and other AI tools through Noibu MCP.

The Performance Agent is one of six supervised agents, alongside the Bug Resolution, CRO, ADA, A/B Testing and ROAS agents, each running the same loop of finding the problem, building the change, waiting for approval and measuring what moved.

The short version

To speed up an Adobe Commerce store without adding developer time, make the Admin-level changes first: confirm full page cache is working on Varnish or Fastly, enable Fastly image optimization, set indexers to Update on Schedule and remove unused third-party tags. Leave production mode, JavaScript bundling, extensions and theme changes to a developer, but hand those changes over already found, ranked and written so the developer only reviews. To see where your store is slow today, start with Noibu's free website audit.

Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.

Frequently asked questions

How do I speed up an Adobe Commerce store without a developer?

Start with Admin settings: confirm every cache type is enabled in Cache Management and that pages return cache hits from Varnish or Fastly, enable Fastly image optimization, set indexers to Update on Schedule, turn on asynchronous email notifications and remove unused third-party tags. Code changes such as JavaScript bundling and theme work still need a developer, so hand them over already diagnosed and written.

What is the most common cause of a slow Adobe Commerce store?

Full page cache problems are among the most common causes, because every cache miss makes the server build the page from scratch. Adobe recommends Varnish as the production page cache, and Adobe Commerce on cloud infrastructure uses Fastly to cache responses at the edge. Heavy extensions, unbundled JavaScript, oversized images and third-party scripts are the other usual causes.

Does Adobe Commerce need to run in production mode to be fast?

Yes. Adobe says production mode is best for deploying Adobe Commerce on a production system, because static view files are generated at deployment and served from cache, and errors are logged rather than shown to shoppers. Changing the mode is a command-line task, so it belongs to a developer or the agency that runs deployments.

Should I turn on JavaScript merging in Adobe Commerce?

Adobe does not recommend the deprecated settings that merge JavaScript and CSS files. Adobe recommends minifying CSS and JavaScript and using third-party tools such as r.js for bundling. Bundling is a developer task, and the result should be checked against Interaction to Next Paint from real shoppers.

What Core Web Vitals should an Adobe Commerce store aim for?

Google sets the good thresholds as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads for mobile and desktop separately. Product, category, cart and checkout pages matter most.

Where should I start speeding up my Adobe Commerce store?

Start with Noibu's free website audit to see which pages are slow for real shoppers. From there, Noibu's Performance Agent ranks the slowest Adobe Commerce page groups, finds the root cause and writes the change for a developer to approve, so developer time goes to review instead of investigation.

Back to all blogs
‍
‍
See what Noibu’s AI agents would change on your store first.
Free website audit
Share

Related blog posts

No items found.

Keep your store running at its best, with AI agents that never clock out.