Speed up an ecommerce website by measuring real-user performance first, finding the failing Core Web Vital on each page template and device, then fixing the largest bottleneck. In most stores, the highest-return sequence is: deliver images and video efficiently, reduce JavaScript and third-party apps, stabilize CSS and fonts, improve cache and edge delivery, and audit checkout extensions. Re-measure field data after each class of change.
Set a measurable speed target
Google’s “good” Core Web Vitals targets are evaluated at the 75th percentile and should be segmented by mobile and desktop:
| Metric | Good target | Poor threshold | What it indicates |
|---|---|---|---|
| Largest Contentful Paint (LCP) | 2.5 seconds or less | More than 4 seconds | How quickly the main content in the initial viewport becomes visible |
| Interaction to Next Paint (INP) | 200 milliseconds or less | More than 500 milliseconds | How quickly the page responds after a user interaction |
| Cumulative Layout Shift (CLS) | 0.1 or less | More than 0.25 | How much visible content moves unexpectedly |
These thresholds come from Google web.dev’s 2025 guidance. Record the result separately for mobile and desktop and for each important template: home, collection, product, cart and checkout. A store can pass on desktop while failing for mobile shoppers, or pass on product pages while a collection template remains slow.
TTFB (time to first byte) and FCP (first contentful paint) are not Core Web Vitals, but Shopify identifies them as useful diagnostics for determining whether an LCP problem begins with server delivery or with browser-side rendering.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Measure real-user performance before editing
- Capture field data. Use PageSpeed Insights or another real-user report to record mobile and desktop LCP, INP and CLS for representative URLs. Save the page template and date with every result.
- Confirm the failing metric in a lab. Run Lighthouse with a throttled mobile profile. Lab tests are repeatable for debugging, but they do not replace field data: INP depends on real interaction, and lab CLS can understate shifts that users experience.
- Find the responsible resource or task. In Chrome DevTools, inspect the Network panel for the slowest image, font, stylesheet and script. Use the Performance panel to identify long main-thread tasks that delay interaction or rendering.
- Separate delivery from rendering. A long TTFB points toward server, cache or origin work; a late LCP after the document arrives usually points toward images, CSS, fonts or JavaScript competing on the browser’s main thread.
- Change one class of issue at a time. Record the before value, make one controlled change, then rerun the same lab profile and check field data again. Do not declare success from a single Lighthouse score.
1. Fix images and video first
Product photography and hero media are frequent sources of LCP delay and page weight. The browser should discover the initial LCP asset early, download an appropriate size and reserve its space before it arrives.
Size media for its actual display
- Set explicit
widthandheight(or an equivalent aspect-ratio constraint) so the browser can reserve layout space and avoid CLS. - Provide responsive
srcsetandsizesvalues so a phone does not download a desktop-sized image. - Use the ecommerce platform’s image CDN to serve compressed, modern formats when available.
- Do not upload a multi-megapixel original when the largest rendered slot is much smaller; resize the source to the largest size the design actually uses.
Prioritize the LCP image
The hero or primary product image in the initial viewport should be discoverable early and loaded eagerly. Shopify’s theme guidance is explicit: “Never lazy-load the LCP image.” Lazy-loading that image can postpone the request until after layout or JavaScript work has started.
Lazy-load everything below the fold
Apply lazy loading to recommendation grids, review galleries, carousels, videos and other media that begin below the initial viewport. This keeps their bytes and decoding work from competing with LCP while preserving the same content as the shopper scrolls.
Prevent media-related layout shifts
Reserve the final box before an image, video poster or review widget loads. A missing dimension lets late content push product information, add-to-cart controls or checkout buttons down the page, producing CLS and causing accidental taps.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRank #2
- Vinyl Hard Cover: Durable grey vinyl hard cover provides long-lasting protection for your notes and records
- 200 Sewn Pages: Features 200 sewn pages with lined rule for organized and secure documentation
- Oilfield Book: Specifically designed for oilfield use with standard industry specifications
- Directional Drilling: Tailored for directional drilling operations and pipe tally marking on oil rigs
- Standard Driller Size: Measures 8.25 inches tall and 3.5 inches wide, the dimensions used by professional drillers
2. Reduce JavaScript, apps and tags
Shopify Help Center guidance identifies excessive JavaScript from theme code, app code and third-party or tag-manager code as a common cause of poor INP. Every script competes for download, parse, compile and main-thread time.
Remove code that no longer serves a page
- Delete unused app snippets, old tracking integrations and abandoned theme features rather than merely hiding their UI.
- Load a script only on the templates that need it. A product-review script should not execute on a static policy page, and checkout-only code should not load on home, collection or product pages.
- Defer noncritical scripts so essential content and interactions can become ready first.
- Limit tag-manager containers, social embeds, chat tools and recommendation widgets to the journeys where their benefit justifies their cost.
Audit the main thread for INP
In DevTools Performance, look for long tasks triggered by clicks, typing, filtering, variant selection or opening a cart drawer. Break up unnecessary work, avoid running several widgets in response to one event and remove features that repeatedly re-render large product grids.
Check installed apps, not just visible widgets
An app can continue to inject code after its visible block has been removed. Review the theme’s app embeds, script tags and custom code, then uninstall or fully remove integrations that are no longer used. Recheck the page source and Network panel after cleanup.
3. Control CSS, fonts and layout stability
Keep essential styles available early
Reduce the number and size of stylesheets, and make the styles needed for the initial viewport available without waiting for unrelated components. Large CSS files can delay the point at which the browser knows how to paint the LCP element.
Rank #3
- EASY FORGOT YOUR PASSWORD? - This small password journal allows you to save all your passwords, account & login details in one place. Managing your online web account information & user data safe. The set comes with 2 password logbooks one to keep at work and one at home. Never forget your passwords again.
- SIMPLE & PRACTICAL - Wire bound password journals with durable plastic cover the sturdy plastic cover resists rips, tears, and folds. Features alphabetic tabs to help organize your data and navigate your accounts easily.
- POCKET SIZE - 2 pack 5"x7" and 3.5"x5.25" mini password journal with A-Z tabs and 120 pages each, lots of space, easy to write, there's even room to add to your password journal.
- DURABLE - Thick frosted poly covers will protect your password book from damage. Made out of premium paper great for fountains pens and ink. No feathering and bleeding. Thick paper & Strong Binding.
- GUARANTEED QUALITY - High quality, heavy-duty and BUILT TO LAST! Made by Excello Global Products. We are a family owned USA company and we have been making quality products for over 50 years.
Avoid layout-triggering effects
Animations that change dimensions, insert banners above existing content or replace skeletons with differently sized components can create CLS. Animate properties that do not force surrounding layout, and reserve space for consent notices, review summaries, recommendations and other late content.
Make font loading predictable
Reduce the number of font families and weights. Where the platform permits it, self-host the fonts required by the storefront and use font metric controls to reduce a swap that changes line breaks or pushes buttons. Check product titles, prices and navigation at the moment the final font appears; those regions are especially prone to visible shifts.
4. Improve CDN, caching and delivery
Cacheable assets should be served from an ecommerce platform CDN or another edge CDN rather than repeatedly fetched from a distant origin. Shopify documents automatic Brotli and gzip compression, HTTP/3, TLS 1.3, global edge caching and versioned asset URLs for platform-hosted assets.
For a self-hosted store
- Set long-lived
Cache-Controlheaders for immutable or versioned images, CSS and JavaScript. - Use compression for text assets and serve them from edge locations close to shoppers.
- Change the asset URL when its contents change so a long cache lifetime does not serve stale code.
- Measure cache-hit and cache-miss behavior separately; a fast edge hit does not prove that the origin is healthy.
Do not add an unmeasured proxy
Proxy and script-rewriting layers can appear to improve a score while delaying execution or breaking module loading. Shopify warns that rewriting may introduce both problems. Test any proxy, optimizer or CDN rule against real-user LCP, INP and CLS, and keep a rollback path.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Treat dynamic requests differently
Images, stylesheets and versioned scripts are generally cacheable. Cart, account, session and checkout requests contain user-specific state and need different cache rules. Never cache personalized responses as if they were public assets.
Rank #4
- Used Book in Good Condition
5. Audit checkout extensions
Checkout performance matters after a shopper has already shown purchase intent. Shopify states that checkout UI extensions load JavaScript bundles on every checkout pageview, including extensions installed but not assigned to an active surface.
Remove unused and overlapping extensions
- List every checkout UI extension, its active surface and its business purpose.
- Remove extensions that are installed but unused, duplicated or no longer supported.
- Combine overlapping trust badges, upsells, surveys and payment messages instead of loading several apps that perform the same job.
- Check the checkout pageview cost after each removal; cumulative bundles can affect interaction even when each individual extension seems small.
Keep checkout-specific code out of storefront templates, and avoid adding a new extension to solve a problem that can be handled by existing checkout settings or content.
Diagnose common symptoms
| Observed symptom | Likely investigation | First corrective action |
|---|---|---|
| Mobile LCP is poor, while desktop LCP is acceptable | Inspect the hero image’s requested dimensions, discovery timing and mobile network waterfall. | Use responsive srcset/sizes, serve a compressed mobile-appropriate resource and do not lazy-load the LCP image. |
| INP is poor on filters, variant selectors or cart controls | Find long main-thread tasks and event handlers in the Performance panel. | Remove unnecessary widgets, defer noncritical scripts and reduce the amount of DOM work after the interaction. |
| CLS rises when the page finishes loading | Watch for images, fonts, banners, review blocks or recommendation modules that change size. | Declare dimensions or reserved space before those resources load and stabilize font metrics. |
| TTFB is high on cache misses | Compare edge hits, edge misses and origin responses; inspect server or database work. | Improve origin response time and cache stable assets at the edge without caching personalized responses. |
| A score improves but shoppers report no change | Compare field data by device and template; check whether the test URL represents the failing journey. | Use real-user LCP, INP and CLS as the outcome measure and repeat the same controlled test after each change. |
| Checkout becomes slower after installing an app | Inspect checkout extension bundles and active surfaces, including extensions not currently assigned. | Remove unused or overlapping extensions and remeasure checkout interactions. |
Use a repeatable optimization cycle
- Baseline: save field LCP, INP and CLS for mobile and desktop on each key template.
- Trace: use PageSpeed Insights, Lighthouse and DevTools Network and Performance views to connect the failing metric to a resource or task.
- Prioritize: fix the largest blocking image, script, layout shift or server delay rather than making many low-impact edits.
- Verify: rerun the same throttled lab profile and confirm that the intended resource or task changed.
- Observe: check field data after the change and compare the same template and device segment.
- Document and roll back: keep the old theme, asset configuration or extension list available until field results confirm the change; record what changed and which metric moved.
Compare platforms or proposals on the factors that affect speed
A fast demo page is not enough when choosing an ecommerce platform, CDN or optimization service. Compare these dimensions using mobile and desktop field data:
- LCP, INP and CLS by template, not one homepage score.
- Image and video resizing, responsive delivery and CDN behavior.
- Controls for theme JavaScript, app snippets, tag managers and third-party widgets.
- Origin response time, cache-hit behavior and cache-miss handling.
- Checkout extensibility and the JavaScript cost of each extension.
- Monitoring, change isolation and rollback procedures.
The practical goal is not a perfect laboratory score. It is a measurable reduction in the delay and instability experienced by real shoppers, especially on mobile product, collection and checkout journeys.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
