Free Website Speed Test for Ecommerce: Find and Fix What's Slowing Sales

You've run your store through Google PageSpeed Insights. You got a score of 58. Now what? For reference, the median Shopify store scores around 47 on mobile and 65 on desktop, based on our benchmark of 1,533 stores.

PageSpeed gives you a number and a list of 20-plus technical audits. It might say "Eliminate render-blocking resources" or "Reduce unused JavaScript." But it won't tell you which of those matters for an ecommerce store, what to actually do about it on Shopify, or whether real shoppers are bouncing because of it.

That gap is exactly what the EcomHint store speed test is built to fill. It runs the same Lighthouse analysis underneath, then translates the results into ecommerce-specific verdicts, actionable fix groups, and platform-aware steps. This guide walks through how to use it and how to read what you get back.

If you want the full technical picture of why speed matters and how to fix it from the ground up, the ecommerce site speed optimization guide covers that in depth.

What Google PageSpeed Insights Doesn't Tell You

Google PageSpeed Insights detects your platform through Stack Packs, so it does know you're on Shopify. But the platform-specific tips it surfaces are technical descriptions, not instructions. It won't say "install TinyIMG" or "remove these two plugins causing the delay." It describes the problem; it doesn't guide you through your dashboard.

The second issue is framing. A score of 65 on a personal blog and a score of 65 on a product page with 3,000 monthly visitors are very different problems. PageSpeed doesn't distinguish between them. It has no concept of what your site is for.

The third issue is volume. Lighthouse runs over 20 audits and surfaces most of them when there are issues. For someone without a development background, this reads as an overwhelming list of vague tasks with no clear priority order.

Real user data is also present in PageSpeed. The Chrome User Experience Report data shows how actual visitors experienced your site over the past 28 days. But it's easy to miss, hard to read, and presented without context about what a particular number means for your conversion rate.

How the EcomHint Store Speed Test Works

The tool calls the PageSpeed Insights API and requests both mobile and desktop analyses in parallel. It gets the same underlying data that PageSpeed Insights shows you: Lighthouse lab metrics, real user data from Chrome, platform detection. Then it transforms that output.

That transformation is the whole point. Instead of 20-plus raw audit items, you get around eight grouped fix items with ecommerce context. Instead of a score with no explanation, you get a verdict that tells you what that score likely means for shoppers on your site. Instead of generic suggestions, you get steps filtered to your platform.

The analysis typically takes around 30 seconds and the tool is free with no account required. Results are saved, so you can share a link with your developer or agency.

Run it at ecomhint.com/tools/website-speed-test.

How to Read Your Results

The Score and Verdict

At the top of your results you'll see two performance scores: one for mobile and one for desktop. Toggle between them with the device selector above the gauge.

Below each score is a verdict. These are written specifically for ecommerce:

• 90 and above: "Fast for ecommerce": speed isn't holding shoppers back
• 70 to 89: "Room to improve": for mobile shoppers, slower load times tend to increase bounce risk
• 50 to 69: "Slower than average": Shopify's 2024 data shows bounce rates climb from 8% at under 3 seconds to 38% at 5 seconds
• Below 50: "Hurting mobile sales": Portent's analysis found that ecommerce sites loading in 1 second achieve roughly 2.5x the conversion rate of sites loading in 5 seconds

The mobile verdict and desktop verdict are worded differently because the consequences differ. A slow desktop experience is a problem. A slow mobile experience is usually the more pressing one.

Performance Metrics

Below the hero score, the tool shows lab data from Lighthouse and, when available, real user data (CrUX) for key metrics. LCP, CLS, and INP are the official Core Web Vitals. FCP, TBT, and Speed Index are additional Lighthouse lab metrics shown alongside them. Each card has two layers of data.

The first is lab data. Lighthouse simulates a page load under controlled conditions and measures each metric. This is what the overall performance score is based on.

The second, when available, is field data from the Chrome User Experience Report (CrUX). This shows how the page actually performed for real visitors over the past 28 days, expressed as the 75th percentile value. That means 75% of your real users had a result at or better than this number, and the other 25% had worse.

Field data isn't always available. For lower-traffic pages, Google doesn't have enough data to report it. When it is available, it's the more important number. Lab scores can vary by conditions. Real user data tells you what shoppers actually experienced.

For a detailed explanation of what each metric measures and the thresholds that define good, needs improvement, and poor ratings, the guide to reading Lighthouse reports for ecommerce covers each one.

The Fix Checklist

The "What to Fix" section is where the tool differs most from a raw Lighthouse report.

Lighthouse audits like "Properly size images," "Serve images in next-gen formats," and "Defer offscreen images" are three separate items that all point to the same underlying problem: your images are too heavy. The EcomHint tool groups these into a single "Page Weight" fix item with a combined view of the savings, the affected resources, and the steps to address it.

Fix items are labeled High Priority, Medium Priority, or Low Priority. High Priority means the issue is likely having a noticeable effect on your performance score and your Core Web Vitals. Medium and Low Priority items still matter, but addressing High Priority items first will move your score the most. For Shopify stores specifically, the speed audit walkthrough for Shopify stores ranks 8 platform-specific issues by detection priority.

Priority is also adjusted for context. If your LCP is already in the "good" range, fix items targeting LCP savings get downgraded. If your overall score is above 70, you won't see a High Priority item for something minor. The tool avoids burying useful information under an avalanche of low-impact tasks.

Each fix item has an analysis section explaining what was found on your specific page, a target metric showing which Core Web Vital it affects, and a "How to Fix" section with platform-filtered steps.

Platform-Specific Steps

When Lighthouse detects your platform through Stack Packs, the fix steps adjust accordingly.

For a Shopify store with an image weight problem, you'd see steps referencing apps like TinyIMG or Crush.pics. For a WordPress or WooCommerce site, you'd see plugins like ShortPixel or Imagify instead. For stores on other platforms or custom builds, you'd get tool recommendations that work universally.

The tool also detects which third-party scripts are loaded on your page: Google Tag Manager, Klaviyo, TikTok pixel, Hotjar, Google Fonts, and others. If a fix step is only relevant when GTM is present, it only appears when GTM is detected. This keeps the checklist focused on what's actually relevant to your setup.

Platform-Specific Diagnostics

Some patterns come up repeatedly by platform. Knowing them helps you anticipate what your report might show.

Shopify

Shopify stores commonly score lower on JavaScript performance. The platform loads theme code, app scripts, and storefront JavaScript, and every installed app that injects scripts adds to this. The tool's resource detection will flag which third-party scripts are contributing to Total Blocking Time, which is the metric most affected by JavaScript load.

Image weight is the other common issue. Shopify product images uploaded at full resolution get resized for display but the original files can be large. Metafield images and section images sometimes bypass compression entirely.

The fix steps for Shopify stores will reference the admin directly: which app to install, where to find the setting, how the theme's lazy loading can be configured.

WordPress and WooCommerce

WordPress stores often accumulate plugin overhead over time. Each plugin can add CSS and JavaScript that loads site-wide even when it's only needed on one page type. The tool groups unused CSS and unused JavaScript together, so you can see the combined size impact.

Caching configuration also affects WooCommerce stores more than most. Cart and checkout pages can't be cached the same way as static pages, and misconfigurations lead to unnecessary full-page loads. The fix steps will include plugin recommendations for caching that account for WooCommerce's dynamic pages.

Generic and Headless Stores

For custom-built stores or headless setups where no platform is detected, the tool surfaces the same metrics and fix groups but provides platform-agnostic steps and universal tool recommendations. Manual image compression, script loading patterns, and server response time improvements are the most common focus areas here.

From Diagnosis to Action

Once you have your results, the fix checklist gives you a starting point: start with High Priority items, work through each fix group in order.

If your fix list is long and you're not sure where your time will have the most impact, the ecommerce site speed best practices post ranks the most common fixes by conversion impact. Images and third-party scripts tend to appear near the top regardless of platform.

For technical work, including CDN setup, hosting changes, and caching configuration, the site speed optimization guide has step-by-step coverage of each area.

One practical use of the shareable result URL: run the test, copy the link, and send it to whoever handles your development or performance work. They'll see exactly what was found, the priority breakdown, and the suggested steps without needing to re-run anything.

The Deloitte "Milliseconds Make Millions" study found that a 0.1-second improvement in mobile load time corresponded to an 8.4% lift in conversions and a 9.2% lift in average order value for retail sites. You don't need to get from a 58 to a 95. Meaningful progress on the top two or three items in your fix list can close most of the gap.

Frequently Asked Questions

Is the tool free?

Yes, free with no account required. Results are saved and you get a shareable link for each analysis.

How is this different from Google PageSpeed Insights?

Both use the same Lighthouse data. The difference is in the output. PageSpeed shows raw audit results with generic descriptions. The EcomHint tool groups those results into ecommerce-relevant fix items, adds platform-specific instructions for Shopify and WordPress, shows verdicts framed around shopper behavior, and highlights real user data in a readable format.

Does it work for any ecommerce platform?

Yes. Platform detection is automatic. Shopify and WordPress get platform-specific fix steps. All other platforms get universal recommendations. The speed metrics and Core Web Vitals apply to any site regardless of platform.

How accurate are the results?

The Lighthouse lab data is a simulated analysis. It gives a consistent, comparable baseline but won't match every real-world visit exactly. The field data from Chrome's User Experience Report, when available for your URL, reflects actual visitor experiences over the previous 28 days and is the more reliable measure of real performance.

How often should I run a test?

After making performance changes, run a new test to see what moved. For ongoing monitoring, running it once a month is usually enough unless you're actively working through fixes. Seasonal traffic spikes or major theme updates are also good prompts to recheck.

Where are my results stored?

Results are saved on EcomHint's servers with a unique URL. No account is required. The report doesn’t include customer or order data. We store the tested URL and the performance analysis results so you can access a shareable report link.