Know where you stand with Google
Pass or fail for Loading, Responsiveness and Visual stability, measured on your real shoppers with the 75% rule Google uses.
CartHacker Free Tools
Store Speed Test A one-time speed report for any page
Paste any page of your store and get a one-time report: Google's real-visitor data and a PageSpeed Insights lab test, analyzed by CartHacker. It names the apps holding up your page and the fix for Shopify, WooCommerce or any other platform.
Tested from
Google, field and lab data
Real Chrome visits where they exist, a measured page load where they do not
Device
Mid-range mobile phone
Throttled connection, the profile Google itself tests on
Your plan
Free to use
One test a day, and more of them with an account
One page, one test
Every visit, every day
Core Web Vitals Monitoring
Track your Core Web Vitals from real shoppers, every day, for free
A Store Speed Test is a one-time report on one page. Core Web Vitals Monitoring measures every real visit, every day, and emails you when your store gets slower.
Set up in about two minutes
-
Open Core Web Vitals Monitoring
Enter your site address in your dashboard and copy the snippet.
-
Paste the code into your theme
On Shopify, paste it into the theme.liquid file. On WooCommerce, add it with the free WPCode plugin. Every other platform takes the same one line.
-
Open your store once
Visit any page of your store. That first visit starts your monitoring.
Your snippet comes with a free CartHacker account. No credit card.
Create a free accountWhat you get
Catch a slowdown the day it starts
A daily speed chart shows the exact day your store got slower, and an email alert lets you know.
Traffic and speed in one report
Page views, visitors, devices and browsers, plus your Core Web Vitals, all counted without cookies.
Speed Test vs Monitoring
Store Speed Test
- One page, one moment
- Google's real-visitor data and a PageSpeed Insights lab test, analyzed by CartHacker
- A full report with the apps to fix and the setting that fixes them
Core Web Vitals Monitoring
- Every real visit, every day
- Pass or fail by Google's 75% rule, plus your traffic
- A free email alert when your store gets slower
Free vs Premium
Free account
$0 no credit card
- Core Web Vitals from real visitors
- 7 days of history
- 1,000 page views a day, reset at midnight UTC
- Traffic, devices and browsers
- Slowdown email alert
CartHacker Premium
Everything in Free, plus
- Speed for your 50 busiest pages
- Speed by page type: product, category, cart
- Weekly automatic tests, not counted in your quota
- 180 days of history
- 50,000 page views a day
Also in CartHacker Premium
- 50 trust badges, shown in 30 languages
- Unlimited access to all 39 PDF tools
- Create and track up to 200 QR codes
- No ads anywhere on CartHacker
- Read new guides 2 weeks earlier
- New tools included as they launch
How to test your store speed
Four simple steps requiring only your public web address. Google's PageSpeed Insights loads your live page on simulated mobile hardware, and CartHacker analyzes the result.
-
Paste your store address
Enter your public store URL. Test your product pages rather than just your home page, because product templates carry image galleries, review widgets, and upsell apps that your home page never loads.
-
Run the mobile speed scan
Google's PageSpeed Insights loads your URL on a simulated mid-range phone over a throttled connection. This exposes how a real customer on a cellular network experiences your store.
-
Review your core scores
Check your Loading, Responsiveness, and Stability ratings directly against the 2.5-second, 200-millisecond, and 0.1 thresholds Google enforces inside Search Console.
-
Apply recommended platform fixes
Review the itemized performance findings listed by severity. Each finding identifies the exact app or script causing the delay and gives you the specific setting to change on your platform.
What each measurement actually means
Three of these metrics are official Core Web Vitals used by search engines. The other two are causes rather than scores: they pinpoint the server delay and the script lockup that produce the first three, which is why fixing one of them often moves several numbers at once. Each one explains what is being measured, why it costs you sales, and the specific setting that fixes it. The cards are ordered by impact. Start at the top.
How long until the main content appears
Largest Contentful Paint
- Aim for
- 2.5 seconds or less
What it measures
This measures the exact moment your largest visible element renders on the screen. On a product page, that is almost always the main product photo. On a home page, it is the hero banner. It captures what a shopper actually sees, not just when your server finishes sending data. The rest of the layout can load quietly in the background, making this a measure of perceived speed rather than total processing time.
What it costs you
Mobile shoppers abandon slow pages instantly. If your primary product photo takes several seconds to show up, a buyer assumes the store is broken and leaves. A product photo loading in under 2.5 seconds is the single biggest lever you have to keep a visitor from bouncing.
Usually caused by Uncompressed product photos, render-blocking stylesheets, or a hero image missing the fetchpriority="high" flag.
How quickly the page reacts to taps and clicks
Interaction to Next Paint
- Aim for
- 200 milliseconds or less
What it measures
The delay between a shopper tapping an element and the screen giving visual feedback. It evaluates the worst interaction delays across the entire visit, not just the first tap. Tapping "Add to Cart" and seeing no response for half a second triggers this penalty.
What it costs you
A page that ignores taps feels broken. Shoppers tap repeatedly when nothing happens, causing duplicate orders or an abandoned checkout because they assume the button failed. Two hundred milliseconds is the threshold of human perception - stay under it, and the store feels instant.
Usually caused by Excessive JavaScript execution locking up the browser thread. While an external app processes background tasks, your buttons simply cannot respond to user taps.
How much page elements shift during loading
Cumulative Layout Shift
- Aim for
- 0.1 or less
What it measures
A numerical score measuring visual movement after elements become visible on screen. Late loading promotional banners, font swaps, and popups that push existing content down all penalize your visual stability score.
What it costs you
Unexpected page shifts cause accidental misclicks. A customer aims for Add to Cart, a banner renders late, and their finger lands on an unrelated link instead. A single accidental tap on the wrong element is often the last interaction before a shopper leaves for good.
Usually caused by Images and banners missing explicit width and height attributes, preventing the browser from reserving layout space before assets download.
How long your server takes to send initial data
Time to First Byte
- Aim for
- 800 milliseconds or less
What it measures
The total time elapsed between a browser requesting your URL and receiving the first byte of HTML data. Every image, script, and stylesheet on the page waits behind this number, because none of them can start downloading until the HTML arrives.
What it costs you
Slow server responses delay everything that depends on them. A server that takes an extra 500 milliseconds to answer pushes your product photos and stylesheets back by that exact same 500 milliseconds. A slow first byte is the one delay that ruins every other measurement on this page.
Usually caused by Uncached database queries on WooCommerce or heavy Liquid processing on complex Shopify theme templates.
How long the browser thread sat locked during load
Total Blocking Time
- Aim for
- 200 milliseconds or less
What it measures
The cumulative time during page load where browser execution was blocked by code. Lighthouse uses this number as its best available proxy for Responsiveness, standing in until real visitors generate their own Interaction to Next Paint data.
What it costs you
It predicts future interaction delays for real buyers. High thread blocking means unoptimized frontend scripts will cause severe input lag once actual shoppers start tapping on mobile devices. Cutting thread lockup now is what prevents that tap delay from ever reaching a live checkout.
Usually caused by Multiple third-party marketing apps, chat widgets, and tracking pixels executing heavy JavaScript simultaneously during page boot.
What this speed test cannot tell you
Every diagnostic tool has specific boundaries. We document ours directly so you know exactly what automated page scans can and cannot evaluate. A limitation you find out about here costs you nothing. One you discover later, after trusting a wrong number, costs you an afternoon.
Testing one URL does not represent your whole store
We analyze only the exact address you provide. Product pages are almost always slower than the home page because of heavy image galleries, review widgets, and dynamic upsell scripts.
Responsiveness score uses estimated lab data for smaller stores
Automated scanners cannot tap screen elements. We display official Google visitor data when available, and clear lab approximations when your store lacks public traffic datasets.
Estimated time savings are diagnostic models, not a stopwatch
Every millisecond figure on this page comes from a savings model, not a stopwatch measurement of a before-and-after fix. Fixes often overlap. Fixing five issues that each promise 200 milliseconds rarely yields a full second once combined.
Password pages produce misleadingly high scores
Testing a password-protected storefront measures only the simple password prompt. Remove the password, or test a direct link to a live product page, to get a score that actually means something.
What you see on the free tier, and what an account adds
The measurement engine is identical for everybody. A free account shows you the exact names of the apps slowing you down and raises your daily scan limit.
Not signed in
1 test a day
- Your three headline scores
- How many problems we found
- What they cost you in total
- The exact problems themselves
Free account
5 tests a day, 50 a month
- Your three scores and the total cost
- Every finding, named and explained
- Which apps are costing you time
- The fix for your platform
- The snippet to measure real visitors
CartHacker Premium
50 a day, 1,500 a month
- Every finding and fix from a free account
- Every app named, not just the 5 heaviest
- 180 days of history and per-page detail
- Speed broken down by page type
- Table of individual pages opened
- Automatic tests on 50 busiest pages
Also in CartHacker Premium
See Premium
- 50 trust badges, shown in 30 languages
- Unlimited access to all 39 PDF tools
- Create and track up to 200 QR codes
- No ads anywhere on CartHacker
- Read new guides 2 weeks earlier
- New tools included as they launch
Frequently asked questions
What are Core Web Vitals in simple terms?
Three official performance metrics Google uses to judge how your store feels to a shopper, not just how fast it loads. They measure visual load time, tap responsiveness, and layout stability. Passing all three proves to Google your site is built for humans, not just quick to request.
Why does my speed score change between tests?
Every test is a live network request, not a static snapshot. Server response times fluctuate, third-party apps take longer to wake up, and network routing changes from one test to the next. A few points of variance is standard. Focus on the long-term trend and specific findings, not chasing a perfect 100.
Does mobile speed matter more than desktop speed?
Absolutely. Google indexes your store using the mobile version (mobile-first indexing), and the vast majority of e-commerce traffic is mobile. Desktop hardware hides performance bottlenecks that a phone user feels instantly.
Will a slow speed score directly lower my search rankings?
Not directly, and anyone selling a ranking guarantee based on a speed score is misreading the algorithm. Relevance and authority are still the primary ranking factors. Speed acts as a tie-breaker between similar stores, but more importantly, it directly moves your conversion rate on every single visit.
Why is real visitor data missing for my store?
Google only publishes Core Web Vitals field data for domains with significant Chrome visitor volume over a 28-day window. Smaller or newer stores simply do not generate enough traffic to appear in the public dataset. When this happens, we rely on lab data (a single simulated load) as the next best diagnostic tool.
Can I test a password-protected store?
No. Testing a password-protected store only measures the lightweight password form page. That temporary page will score near perfect, feeding you completely inaccurate performance feedback.
Will running a speed test affect my store analytics or traffic?
No. The test is a single automated page load run by Google's PageSpeed Insights. It does not modify your store files, install tracking code, or skew your sales funnel data.
Why cannot automated tests measure true responsiveness?
Automated test tools load pages without tapping buttons or filling forms. Responsiveness requires real human interaction data from actual shoppers on your store. Speed tests use main thread blocking as a lab stand-in until real visitor tracking is enabled.
Can I fix speed issues on Shopify if I do not control the server?
Yes. While Shopify locks down the backend server, you have full control over your Liquid theme code, image payloads, and third-party app scripts. The vast majority of Shopify speed bottlenecks are caused by heavy apps, not the server.
How does this tool differ from Google PageSpeed Insights?
Google outputs generic developer tasks like "reduce unused JavaScript". CartHacker identifies the exact e-commerce apps by name and provides direct instructions to fix the bottleneck in your specific platform dashboard.
Free CartHacker tools
Next, answer shoppers' doubts with free trust badges
A faster page still loses the sale when a shopper doubts the store. Show your shipping, returns and checkout promises under Add to cart, with no card and no access to your store admin.
Trust Seals & Badges
Do shoppers hesitate at Add to cart?
Show the promises that settle doubts, from free shipping to a money-back guarantee, right under the Add to cart button. One line in your theme.
- 8 badges in 2 styles, free
- Premium: 50 badges, 30 languages
- View counts from the first shopper
Build my trust badges
Design them without signing up.
Also free
39 PDF Tools
Convert, merge and sign in your browser. Your files are never uploaded.
QR Code Generator
Change the link after printing and count the scans. 5 tracked codes on a free account, static codes unlimited.
- Logo and colors
- SVG for print
- Wi-Fi and business cards