A Shopify store does not need a perfect speed score before a campaign, but it does need a stable buying experience. Sale periods add traffic, campaign scripts, promotional graphics, reviews, pop-ups and merchandising changes at exactly the moment when the team has the least appetite for technical surprises.
A Shopify speed checklist should therefore focus on the pages customers will actually use and the changes made in the weeks before launch.
Establish a performance baseline before changing anything
Record the current performance of the homepage, a high-traffic collection page and one or two important product pages.
Shopify’s web performance reporting uses real visitor data and Core Web Vitals such as loading speed, interactivity and visual stability. Use that trend to understand whether performance is improving or declining over time.
Do not judge the store from one synthetic score alone. The important question is whether real customers can browse and buy without unnecessary delay or unstable layouts.
The broader Shopify maintenance checklist explains how performance fits into recurring store care.
Review recent changes first
If the store became slower recently, start with what changed.
Check new app installations, theme customisation, tracking scripts, videos, large images, product review tools, chat widgets and campaign code.
Performance diagnosis is much easier when the team keeps a change log. Without one, every installed app becomes a suspect even when the real cause is a new hero video.
Audit app loading
Apps can add scripts, blocks, embeds and external requests to the storefront.
Use the Shopify app audit to identify which apps are essential, which overlap and which are no longer used. Do not remove apps solely for speed without understanding the business function they provide.
A feature that improves conversion may justify some performance cost. A feature nobody uses probably does not.
Optimise campaign images
Sale periods often introduce large hero graphics, promotional tiles and product imagery.
Use appropriately sized images rather than uploading oversized originals and relying on the browser to scale them down. Avoid unnecessary image-heavy sections above the fold.
If the campaign design includes several banners, check mobile separately. A visually impressive desktop asset may create a slow mobile experience if it is not adapted properly.
Be cautious with video
Autoplay video can add significant weight to a page, particularly on mobile connections.
Ask whether the video is important to the campaign or simply decorative. If it is useful, load it in a way that does not block the main content. If it is not critical, consider a static image or a video that starts only after user interaction.
The objective is not to remove rich media. It is to make sure it earns its place.
Review the theme before the campaign
Duplicate the current theme before major campaign customisation. Test changes on the copy rather than editing the live theme immediately.
Look for sections that load everywhere even when they are needed only on one page. Review custom scripts and old campaign code that may still be present.
After publishing, test as a normal customer on mobile and desktop, not only through the theme editor.
Check product and collection pages
Campaign traffic often lands directly on products or collections rather than the homepage.
Test the pages that will receive paid, email and social traffic. Check image loading, variant selection, add-to-cart behaviour, filters and product recommendations.
If a collection page contains hundreds of items, review how the theme loads them and whether filters or scripts are creating unnecessary work in the browser.
Check cart and checkout responsiveness
A fast homepage is not useful if the cart becomes sluggish when demand increases.
Test cart updates, discount codes, shipping estimates and checkout entry. If apps add upsells or gifts in cart, check whether they delay interaction.
Do not introduce several new cart apps in the final days before a major sale unless there is enough time to test the combined behaviour.
Review tracking and marketing scripts
Advertising campaigns often add pixels, analytics, heatmaps and conversion tools.
Check which scripts are genuinely required for the campaign and avoid duplicating tags through several tools. If a platform has been replaced, remove obsolete tracking rather than leaving it to load indefinitely.
Coordinate with marketing before removing anything so reporting does not disappear unexpectedly.
Check Core Web Vitals in context
Core Web Vitals measure loading, interactivity and visual stability. They are useful because they describe parts of the experience customers can feel.
Use them as diagnostic signals, not as a game where the only goal is reaching 100. A store with useful features and strong real-world performance can be more valuable than a stripped-down store built only for a score.
Watch for large layout shifts from banners, pop-ups or late-loading content, especially during campaign changes.
Review third-party services outside Shopify
Some of the slowest requests on a storefront can come from services that are not managed directly in the theme, such as chat, reviews, advertising, personalisation or external analytics. Review which third-party requests load on the campaign pages and whether they are still required. Coordinate with marketing before removing measurement tools.
Test under realistic mobile conditions
Do not judge campaign performance only from a fast office connection. Open the main landing pages on a real phone and, where possible, test under a normal mobile connection. Watch how quickly the primary image, product information and add-to-cart controls become usable. A page that feels instant on a developer workstation may feel very different to a customer.
Avoid high-risk changes just before launch
The final 24 to 48 hours before a major campaign should focus on verification, not experimentation.
Avoid replacing the theme, installing a stack of new apps or rewriting checkout logic unless the campaign genuinely depends on it.
If performance work requires a large change, schedule it earlier so the store can be observed under normal traffic first.
Prepare support coverage
Performance problems can appear only under real traffic or after a third-party service slows down.
Confirm who can access Shopify, the theme, analytics and critical apps during the campaign. If the sale runs across a weekend or holiday, make sure technical coverage matches the campaign schedule.
For stores that need help investigating slowdowns or theme and app issues, Shopify support can provide a direct escalation route without waiting for normal office hours.
Recheck after the campaign begins
Compare live performance with the baseline. Look at actual user data, conversion rate, error reports and customer feedback.
If a new feature appears to cause a problem, assess its commercial value before removing it. Speed optimisation should protect the buying journey, not reduce it to an empty page.
Frequently asked questions
What slows down a Shopify store?
Common contributors include theme code, apps, third-party scripts, analytics, large images, videos and complex page sections. The real cause varies by store, so review recent changes and real performance data.
Should I remove apps before Black Friday?
Remove only apps that are genuinely unnecessary and after checking dependencies. A rushed uninstall can break theme elements, workflows or data. Audit the app stack early rather than the night before a sale.
What Shopify pages should I test for speed?
Test the homepage, major collection pages, high-traffic product pages, cart and the path into checkout. Prioritise pages that will receive campaign traffic.
Is a perfect Shopify speed score necessary?
No. Focus on a fast, stable customer experience and healthy Core Web Vitals rather than chasing a perfect synthetic score at the expense of useful store functionality.
Final takeaway
Shopify speed work before a sale should be measured, not frantic. Establish a baseline, review recent changes, control apps and scripts, optimise campaign assets and test the actual pages customers will use.
The safest campaign is one where performance has been improved before launch and the team is available to respond if real traffic reveals a problem.
