A Shopify Speed Checklist for the Weeks Before BFCM
Most Shopify stores change more in the six weeks before Black Friday than in the rest of the year combined. Countdown timers get installed. A personalization app gets added for gift recommendations. The homepage banner is swapped for a sale-specific hero image. A theme gets tweaked to make room for a promo bar. Each change is small and reasonable on its own, and each one is usually made under deadline pressure, without a performance check, because the goal is getting the sale live, not measuring page speed.
That's the exact window when a slowdown is most expensive. Traffic is higher, ad spend is higher, and there's no time left to debug once the sale is running. A speed problem that would be a minor annoyance in February becomes a lost afternoon of paid traffic in November. The fix isn't a heroic last-minute audit — it's checking a few specific things before you add anything new, and again before the sale goes live.
Start with a baseline, not a guess
Before you install anything for the sale, know where your store stands right now. Open your Speedscope dashboard and note your current page speed and Core Web Vitals scores — LCP, CLS, and INP — for your homepage, a collection page, and a product page. These are the pages most sale traffic will land on, and they're also the pages most likely to get edited for the promotion.
Without a baseline, you have no way to tell whether a change you make in October actually slowed things down, or whether the store was already sitting close to the edge. "It feels about the same" isn't a comparison. A number from two weeks ago is.
Audit every app before it earns a permanent spot
Seasonal apps are the easiest way to add weight to a store without noticing. Countdown timers, exit-intent popups, gift-wrap upsells, and last-minute personalization widgets all run their own scripts on every page view, and a lot of them are installed once, tested briefly, and then left in place well past the sale.
Before you commit to any new app for BFCM, check its impact using Speedscope's app-impact analysis rather than assuming it's harmless. This tells you how much a specific installed app is contributing to your load time, so you can compare candidates or catch one that's heavier than expected before your traffic peaks — not after.
If an app you're testing shows a meaningful hit to load time, that's useful information to have in October, when you can still swap it for a lighter alternative. It's much less useful in the middle of the sale.
Treat sale-specific theme changes like any other theme change
A promo banner, a new sale-page template, or a tweaked header for the countdown timer is still a theme change, and theme changes are one of the more common ways stores quietly get slower. The image in that new banner is often larger than what it's replacing. A promo bar added to every page template adds a small amount of weight to every single page view on the site, which adds up faster than a one-off homepage tweak.
Check your Core Web Vitals again after any theme edit meant for the sale, specifically LCP if you've changed hero images, and CLS if you've added new elements above the fold. Comparing the after against the baseline you already captured takes a few minutes and catches problems while they're still easy to reverse.
Set alerts before the sale, not during it
The busiest week of the year is not when anyone has time to sit and watch a dashboard. This is what automated alerts are for: set thresholds ahead of time so that if a last-minute app install or theme tweak pushes your load time or Core Web Vitals scores past an acceptable range, you find out immediately instead of discovering it from a support ticket or a drop in conversion you can't yet explain.
Alerts matter most in exactly the window where changes are happening fastest and attention is most divided — which describes the run-up to BFCM for almost every merchant.
Keep the historical record for next year
Once the sale is over, the comparison doesn't have to end. Speedscope's historical tracking lets you look back at how your speed and Core Web Vitals held up across the event, not just whether the site "felt okay." That record is what makes next year's pre-sale checklist faster: you'll know which changes cost you speed last time, and which ones didn't matter as much as they seemed to in the moment.
The pattern to watch for
None of this requires predicting exactly how much traffic you'll get or running a full performance rebuild before the sale. It requires treating every app and theme change made in the name of the sale with the same scrutiny you'd apply the rest of the year — just earlier, and with less room for surprises once the sale is live.
If you're evaluating your setup for the first time, Speedscope gives you the dashboard, app-impact analysis, and alerting to run this checklist without guesswork. Get your baseline now, while there's still time to act on what it tells you.