Free tool
Find out what is actually slowing your store down
Enter a URL and this measures server response time, checks whether compression and caching are configured, detects page builder bloat, and reviews image formats and on-page SEO. Results appear immediately. No signup, no email required.
Fetches one public page. Nothing is stored, and no email address is required.
What this checks
Server response time
Time to first byte and total transfer. The single most informative number, because nothing renders until the server responds and no front-end optimisation can hide it.
Compression and caching
Whether gzip or brotli is enabled and whether a Cache-Control policy exists. These are server configuration changes rather than code changes, and they are frequently just missing.
Front-end weight
HTML document size, stylesheet and script counts, image count. High counts usually mean plugins loading assets on pages that never use them.
Platform and builder detection
Identifies WordPress, WooCommerce, Shopify, Magento, and whether Elementor, Divi, WPBakery or Beaver Builder is adding weight.
Image formats
Whether WebP or AVIF are in use and whether lazy loading is applied. On a product catalogue this is often the largest single saving available.
On-page SEO basics
Title tag, meta description and viewport tag — the three that most commonly go missing after a migration.
Common questions
What is TTFB and why does it matter more than the total load time?+
Time to first byte is how long the server takes to think before anything at all reaches the browser. Nothing can render during that window — no HTML, no images, no fallback. It is the one metric you cannot optimise around on the front end, because it happens before the front end exists. Under 0.3 seconds is good; above about 0.6 seconds usually means no page caching, slow database queries, or an overloaded host.
Why does this flag my page builder?+
Builders like Elementor, Divi and WPBakery load stylesheets and scripts for every feature they support, not only the ones a given page uses. That is a reasonable trade when a non-technical client needs to edit their own pages. It is an expensive one when nobody edits the site and the weight is being paid on every visit by every customer.
Is this the same as PageSpeed Insights?+
No, and it is not a replacement. PageSpeed runs a full Lighthouse audit in a real browser and measures Core Web Vitals — run it too. This checks the things that are usually the actual cause: server response time, whether compression and caching are configured at all, how much the front end is loading, and whether images use modern formats. It answers "what is wrong" rather than "what is the score".
Does this work on Shopify, Magento or a custom site?+
Yes. Platform detection recognises WordPress, WooCommerce, Shopify, Magento and BigCommerce, but every check — response time, compression, caching, request counts, image formats, SEO basics — applies to any site regardless of what it runs on.
Does it check pages behind a login?+
No. It fetches one public page as an anonymous visitor, exactly as a customer or a search engine would.
Is my data stored?+
No. The page is fetched, analysed in memory, and the result is returned to your browser. Nothing is saved and no email address is required.
Who built this
I’m Naeem Safdar. I build and fix commerce systems — order automation, payment integration, performance work. This checker looks for the problems I find most often when someone tells me their store feels slow, which are usually configuration rather than code.
Also try the email deliverability checker →