Some Shopify speed optimization services never make your store faster. They add a few lines to your theme that recognise Google’s testing tool and hand it a stripped-down page, so the score jumps while shoppers keep loading the same slow store. We check for that code in every store we scan. This guide shows what it looks like, how to find it in your own theme, and how to hire a speed expert who will not use it.

Key Takeaways
1
A fake speed fix detects Lighthouse, GTmetrix or the Linux machines they run on, then serves those tools a lighter page than your visitors get.
2
Real-user data in PageSpeed Insights cannot be faked this way, so a great lab result next to poor field data is the clearest warning sign.
3
Search your theme for document.write, Chrome-Lighthouse, navigator.platform and YETT_BLACKLIST, then check what each match does before deleting anything.
4
Before hiring a speed service, ask which files they will change and how they will prove the result with real-user data.

How Does a Fake Shopify Speed Optimization Work?

A fake speed optimization checks who is loading the page before the page appears. When the visitor looks like a testing tool, the code swaps in a near-empty document or blocks the theme’s scripts. Real shoppers never see that version, so their experience does not change at all.

The code usually sits near the top of theme.liquid, where it runs before anything else. It reads the user agent, the short text every browser sends to identify itself, and looks for names like Chrome-Lighthouse or GTmetrix. On a match it calls document.open and document.write to replace the page with a bare shell. The test measures that shell and reports a fast load. The merchant gets a screenshot of a result no customer will ever experience. In the stores we scan, this cheat turns up on about 1 in 130 Shopify stores we scanned. That makes it uncommon, but common enough to check for before you pay anyone to speed up your store.

What Versions of the Speed Cheat Show Up on Real Stores?

Three versions show up in the stores we scan. The oldest names the testing tool outright. A second hides those names inside encoded text. A newer one never names a tool at all and blocks scripts on Linux machines instead.

The User Agent Swap

This is the version merchants have described for years in the Shopify Community threads about speed scams. The code checks the user agent for Chrome-Lighthouse, GTmetrix or Google Page Speed Insights. When it finds one, it writes a replacement page. Some copies serve the test a blank page with a single dot on it. Others strip out the theme’s JavaScript, sliders and app embeds but keep enough layout for the test to look normal.

The Encoded Version

Sellers who expect merchants to search their theme hide the giveaway words. The tool names are written as hexadecimal escapes, strings like \x43\x68 that spell out letters, or kept in a scrambled list that a separate block of code reads later. A plain search for “Lighthouse” finds nothing, even though the same swap is running.

The Linux Platform Check

Newer copies skip tool names entirely. PageSpeed Insights runs its tests on Linux servers, while most shoppers browse on Windows, Mac, iPhone or Android. So the code checks navigator.platform for Linux x86_64 and, on a match, stops theme and app scripts from loading. It often borrows a legitimate script-blocking library called yett, or watches the page and renames scripts so they never run. Some copies are packed into one unreadable line that starts with eval(function(p,a,c,k,e.

Does a Fake Speed Score Help Your Shopify SEO?

No. Google Search judges page experience on Core Web Vitals collected from real Chrome users, not on the lab result a testing tool produces. A cheat only changes what the testing tool sees, so your rankings get none of the benefit you paid for.

It can also cost you. Blocking scripts for every Linux visitor breaks menus, sliders and carts for real shoppers on Linux desktops. The actual causes of a slow store, such as oversized images, heavy apps and render-blocking code, stay exactly where they were. If your store is genuinely slow, start by diagnosing a slow Shopify theme.

How Can You Tell If Your Shopify Speed Score Is Fake?

Compare the lab result with the real-user data in the same PageSpeed Insights report. A cheat can fool the lab test but not the field data. A strong lab result sitting above failing Core Web Vitals is the clearest sign that something is gaming the test.

  1. Read the real-user section first. Run PageSpeed Insights on your homepage and look at the top of the report, which shows what real visitors experienced over the last 28 days.
  2. Check the screenshots. Scroll to the filmstrip and the final screenshot. If the test saw a blank page, a single dot or a store with no header and no images, it measured a different page from the one your customers get.
  3. Load the store yourself. Open your homepage on a mid-range phone over mobile data. A store that feels slow while the report says fast deserves a closer look at the code.
  4. Compare with your theme’s real-world results. Our Shopify theme speed rankings show how often live stores on each theme pass Core Web Vitals. A flawless lab result on a theme whose live stores usually struggle is worth investigating.

How Do You Find the Cheat Code in Your Shopify Theme?

Search your theme code for the few words every version needs. Duplicate the theme first, then search theme.liquid and the snippets folder, because that is where sellers put code they want to run before anything else on the page.

  1. In Shopify admin, go to Online Store, then Themes, and choose Duplicate on your live theme so you have a clean copy to return to.
  2. Choose Edit code on the live theme and open layout/theme.liquid.
  3. Search the file for each of these terms, one at a time:
    • document.write and document.open
    • Chrome-Lighthouse, Lighthouse and GTmetrix
    • navigator.platform and x86_64
    • YETT_BLACKLIST and javascript/blocked
    • eval(function(p,a,c,k,e
    • long runs of \x followed by two letters or digits
  4. Repeat the search in the snippets folder and in any file the seller told you they edited.

A single match is not proof. The cheat needs two things in the same block of code: a check for a testing tool or for Linux, and an action that rewrites the page or stops scripts from loading. When both sit together, you have found it.

Which Legitimate Scripts Look Like a Speed Cheat?

Plenty of honest code mentions Lighthouse or reads navigator.platform. When we checked flagged stores by hand, the false alarms came from apps and from Shopify’s own code, where a testing tool’s name sits in a list or a setting rather than in a check that changes the page.

  • Bot and crawler lists. Security, analytics and bot-blocking apps keep long lists of user agents to recognise, and Lighthouse is usually one of them.
  • Page builder settings. PageFly includes a setting named forceByPassGoogleLightHouse in its page configuration, so the word appears on PageFly pages whether or not the option is switched on.
  • Shopify’s own browser checks. Storefront code that Shopify adds reads navigator.platform to tell Apple devices from others. It never tests for Linux and never rewrites the page.
  • Country and fraud blocking apps. Some apps use document.write to show a blocked-region message. That rewrite depends on the visitor’s location, not on a testing tool.

Delete only code you can explain. If a match belongs to an app, it normally disappears when you uninstall that app. Removing an app you still use can break features your customers rely on.

What Should You Do If You Find a Speed Cheat on Your Store?

Remove it from a duplicate theme, confirm the store still works, then publish that copy. Save the code and your messages with the seller first, because you will need both if you ask for a refund or report the service.

  1. Copy the suspicious code into a text file with today’s date, then delete it from the duplicate theme.
  2. Preview the duplicate on desktop and mobile. Check the menu, product images, cart and every app widget.
  3. Publish the cleaned theme and run PageSpeed Insights again. Expect the lab result to fall, because the test now measures your real page.
  4. Ask the seller what else they changed, and request a refund for work that did not improve real-user speed.
  5. If you hired through a marketplace or installed an app from the Shopify App Store, report the listing there.

Then fix what actually slows the store down. Slow Shopify stores usually come down to heavy apps, unoptimized images and theme code that loads more than the page needs. Our guide to Shopify page speed apps covers tools that do the work properly, and moving to one of the fast Shopify themes often helps more than any script.

What Should You Ask a Shopify Speed Optimization Service Before Hiring?

Ask how they will prove the result with real-user data, which files they will change and what stays behind when they finish. An honest speed expert talks about images, apps and code, and treats the lab result as a rough guide rather than the thing being sold.

  • Will you show me Core Web Vitals field data before and after? Field data covers weeks of real visits, so anyone promising proof within a day or two is selling a lab result.
  • Which theme files and apps will you change? Ask for a written list and a copy of every file they edit.
  • Do you guarantee a specific score? Treat a guaranteed score with suspicion, because honest improvements depend on the store.
  • Will anything load differently for bots or testing tools? The only acceptable answer is no.
  • What happens if I cancel or remove your app? Real optimizations stay in your theme. A cheat usually lives in the seller’s own code and vanishes with it.

How Do You Get a Speed Result You Can Trust?

Trust the result that describes the store your customers actually load. If a test looks too good, read the real-user data, search your theme for the terms above and remove anything that treats testing tools differently from shoppers. For other theme problems, from layout glitches to broken navigation, our Shopify theme troubleshooting guide walks through the fixes.