Practical guide
How to fix slow Shopify stores
Slow Shopify stores are usually caused by heavy themes, too many apps, large images and third-party scripts.
The work to plan together
A scope shaped around this requirement.
- Audit apps and remove unused onesScope
- Compress and resize imagesReview
- Limit third-party scriptsCheck
The useful starting point
Look for the templates and assets causing the delay. Review theme code, apps, media and external scripts, then test changes under comparable conditions. Keep required commerce functions working throughout.
What to review
- Audit apps and remove unused ones
- Compress and resize images
- Limit third-party scripts
- Test with PageSpeed Insights
A practical sequence to follow
Find the affected journey
Test representative collection, product and cart pages on a phone-sized view. Compare repeatable lab observations with available real-user data. A single homepage score cannot explain how the whole store behaves for shoppers.
Review app dependencies
List installed apps and scripts, their purpose and the journey they support. Remove an unused tool only after checking dependencies and saving a rollback route. Duplicate trackers or overlapping features can add work without helping the customer.
Optimise the actual assets
Use suitable image sizes and loading behaviour for the layout. Check fonts, video and third-party embeds alongside images. Preserve important product detail and do not hide necessary functionality simply to improve a test score.
Retest the purchase path
Compare the same pages after a controlled change and complete representative shopping journeys. Record what changed, any regression and the next bottleneck. Performance improvement and sales uplift need separate evidence.
What to avoid or interpret carefully
Do not promise a perfect score or remove useful functionality just to improve one lab test. Real-user performance and buying experience both matter.
Practical detail
Diagnose one slow buying journey
Use a representative product page and the same mobile test conditions. A homepage score alone may miss the part that shoppers use.
| Part of the work | Example output | How to review it |
|---|---|---|
| First image | Dimensions, transfer size and loading priority | Preserve useful product detail while reducing unnecessary weight. |
| Apps/scripts | Purpose, loading behaviour and effect on the task | Review whether the feature is needed before removing code. |
| Retest | Repeated lab runs and available real-user evidence | Check product selection and checkout still work. |
Keep an inventory of changed theme/app resources and a recovery route. A temporary best score is not proof that every real shopper’s experience has improved.
Diagnose a representative store page before installing another app
A slow store can involve the theme, images, apps or external scripts. Start with a collection or product journey that matters to customers. A homepage test cannot describe every buying path.
Record the baseline
Use comparable device and test conditions, and available field information. Note the page, theme and relevant assets. A single run is a diagnostic sample, not the entire user experience.
Isolate the dependency
Review large media and scripts that affect the page. Check what a dependency does before removing it. An app may supply an essential purchase feature even when it also adds load.
Retest the journey
After an approved change, compare performance and test product selection, cart and contact paths. Keep rollback and deployment ownership clear. Faster tests should not conceal broken functionality.
How to interpret this guidance
Prioritise confirmed bottlenecks and record remaining limits. A score increase cannot by itself establish higher sales or rankings.
Can a theme switch be the first speed fix?
It may be relevant, but review the current causes and migration effort first. A new theme still needs content, app compatibility and journey checks. Do not replace a whole store to avoid diagnosing one dependency.
Should we remove all apps to improve speed?
No. Identify their business purpose and actual performance effect. Removing a useful buying function can make the store worse.
Can Tangensys help with the next step?
Yes. Share your website, goal and the issue you are investigating. We can discuss the relevant service and provide a custom quote within 2 working days.
Related reading and services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days