Landing Page Views Are the Speed Test PageSpeed Insights Can't Run

Here is a take that will annoy a certain kind of Shopify consultant: the most useful mobile speed test for a paid-traffic store is not PageSpeed Insights, but the ratio between Meta Ads link clicks and landing page views, watched over the last 14 days of spend, broken down by device. If you run ads and you do not check that ratio, you are measuring the wrong thing.

The number PageSpeed cannot explain

A merchant in the Shopify Community forums (thread 637964, June 2026) posted this: 1,516 Meta link clicks in a reporting window, 315 landing page views. That is a 20.8 percent ratio on a store PageSpeed Insights scored 64 for mobile, with a measured mobile LCP of 9.9 seconds. Healthy stores land at 75 to 85 percent. This one was losing four out of every five clicks that Meta charged for.

Another merchant (r/shopify, 107 link clicks producing 29 Shopify sessions) was sitting at 27 percent. Cozytown's April 2024 post reports 846 clicks and 118 landing page views, or roughly 14 percent. Fairix in March 2022 watched the same store go from 95 percent to 2.5 percent with no configuration changes. The stories cluster: severe gaps, all traceable to real charges Meta made, none of them visible in the lab-score column of the store's PageSpeed report.

You can rerun PageSpeed Insights ten times on that landing page URL. The score will bounce a few points. It will not tell you that four out of five paid mobile visitors are giving up before your pixel gets a chance to fire.

Lab test versus field data

PageSpeed Insights runs one synthetic request from a Google server on a simulated Moto G4 with a throttled connection. It generates a number. That number is stable, comparable, and useful when you are A/B testing two theme versions of the same page. It is a lab test in the strict sense: controlled inputs, controlled hardware, one measurement per run.

Your landing page views count is field data. Every ratio unit is one real person, on their actual phone, on their actual carrier network, with their actual browser configuration, at the moment they clicked. If they closed the tab before Meta's PageView event fired, they show up as a missing landing page view. Meta charged you for the click. Shopify never saw a session. Your PSI score has no comment on this because PSI was never there.

Two of Facebook's own engineers confirmed the mechanism back in 2021 (Shopify Community threads 47218 and 47434). Their finding: PageView and ViewContent events on slow Shopify pages were "taking longer than usual to load." That has nothing to do with attribution and nothing to do with Pixel misconfiguration. The page is simply taking too long, and the visitor leaves before the code that would have counted them runs.

This is why the LPV ratio outperforms a lab score for a store that spends money on Meta. The score is a proxy for the number that actually matters. The ratio is the number that actually matters.

What can fake a speed problem

The counter I hear most often is that the LPV gap is a tracking artifact rather than a real speed signal. Half true, and worth taking seriously before you touch a theme file.

Meta's "link clicks" denominator is broad. It counts video pauses, carousel swipes, and ad expansions as clicks in some campaign types. Switching your campaign optimization goal from Link Clicks to Landing Page Views, and switching the reporting column from Link Clicks to Outbound Clicks, can close 15 to 25 percent of the apparent gap on its own. Shopify's Customer Privacy setting matters too: if it is set to "Collection after consent," the pixel will not fire for visitors who did not tap accept, and the ratio drops accordingly.

And since January 13, 2026, Shopify has been silently defaulting all App Pixels to a mode called Optimized, in which the platform throttles pixel data when it decides your pixel is not driving results. On Safari, where click IDs are stripped, "not driving results" is often the platform failing to read a signal that never existed to begin with. Independent analyses have put the resulting conversion drop at 15 to 40 percent for stores that did nothing wrong. The fix is a two-minute flip in Settings > Customer events > App Pixels > Data column, back to Always On.

Check those first. They cost minutes. They can close the gap without any front-end work. If you fix all three and your mobile LPV ratio is still under 50 percent while desktop looks fine, you are looking at a page load problem, and PageSpeed will finally have something useful to say. If you want a second pair of eyes on that intake sequence before you touch your theme, the first 15 minutes with a help1 expert is free and it is usually enough to sort a bad ratio into "tracking" or "speed" without guessing.

I do want to flag one thing I do not fully understand. A March 2026 Reddit thread (1rys24r) documented a merchant running identical ads on Shopify and WooCommerce simultaneously, and getting a 10 to 20 percent LPV ratio on Shopify while WooCommerce ran at 50 to 60 percent. Page speed was fast on both. CAPI was configured to maximum. No one in the thread had a mechanism. Neither do I. If your ratio caps out around 50 percent after you have fixed everything fixable, that ceiling may be a Shopify platform artifact and not something you can chase away with more optimization work.

When PageSpeed is still the right tool

I still open PageSpeed Insights every week. Its diagnostic panel is genuinely good at telling you which specific script is blocking your render, which image is oversized, which font is Flash-of-Unstyled-Texting the header. Once your LPV ratio tells you speed is the problem, PSI is what you use to find the specific file responsible. It is a good second step. It is a bad first step, because it cannot show you whether the problem is worth fixing at all.

That is the ranking. Meta report first, PSI second. Or, if you want a shorter version: field data tells you whether. Lab data tells you what. Reversing the order is why merchants spend seven days deferring a CSS file that never moved the ratio, which is exactly what happened in thread 637964. I have watched clients do this and I have done it myself on my own store.

If you have not yet, install help1's diagnostic app and check what the health score flags for render-blocking scripts on your landing page templates; that is the same signal you would get from PSI, without leaving your Shopify admin. Then go read the LPV column in your Meta report. There is more on the same lab-versus-real-users tension in our earlier writeup, which covers the CrUX-versus-lighthouse split on the score itself.

Here is the question I would ask before you touch anything else. Pull your last 14 days of Meta Ads spend. Break it down by device. What is your mobile landing page views ratio? If it is under 60 percent and you have never looked at it before, what have you been optimizing?