Page Performance reports the load speed and visual stability of your store's pages as measured in your shoppers' own browsers. The Triple Pixel takes a measurement on each page view and reports the Core Web Vitals that Google uses to assess page experience.
Because the data comes from real visits, it reflects the devices, connections, and locations your shoppers actually use. A synthetic test such as Google PageSpeed Insights or Lighthouse loads your page once from a data center. Page Performance summarizes thousands of real loads.
You can use it to find which landing pages are slow for real shoppers, compare mobile against desktop speed on the same page, and watch load speed and conversion rate on one timeline to see whether they move together.
Before you start
Page Performance needs all four of the following:
A Shopify store
Page Performance is available for Shopify stores. Other platforms don't show the tab.
The Triple Pixel Theme App Embed enabled
Performance data is collected only while the Theme App Embed is active in your Shopify theme. If you turn the embed off, collection stops. See installing the Triple Pixel on your Shopify store.
At least 10 measurements for the page
Each page needs a minimum of 10 real-user measurements in your selected date range before values appear.
24 to 48 hours after install
Data typically appears within a day or two of enabling the pixel.
Open Page Performance
In Triple Whale, go to Pixel Settings.
Select the Page Performance tab.
Choose a date range, and set the device filter to All Devices, Mobile, or Desktop.
Select a page from the Pages list to see its full breakdown.
The Pages list
The Pages list shows your 20 busiest landing pages for the selected date range and device, ranked by sessions. Each row shows sessions, orders, and conversion rate, and you can sort by any of the three. Selecting a row loads that page's performance underneath.
The performance health score
The health score is a single number from 0 to 100 for the selected page. It combines the three Core Web Vitals, weighted as follows:
Largest Contentful Paint: 50% of the score
Interaction to Next Paint: 30% of the score
Cumulative Layout Shift: 20% of the score
The score maps to a rating:
Score | Rating | What it means |
90 to 100 | Good | The page meets Google's Lighthouse targets for most shoppers. |
50 to 89 | Needs improvement | Some shoppers get a slow or unstable experience. |
0 to 49 | Poor | Most shoppers get a slow or unstable experience. |
A tilde before the score, such as "~72", means the score is partial. The page has no Interaction to Next Paint data, so the score uses Largest Contentful Paint and Cumulative Layout Shift only. Pages that shoppers don't interact with, such as a page they scroll and leave, often have no interaction data.
This score is calculated by Triple Whale from your real-user data. It isn't the Lighthouse or PageSpeed Insights performance score, so the two numbers won't match.
Core Web Vitals
Each metric card shows the value for the selected page, its rating, and the target for a Good rating. In the All Devices view, a bar under each card shows what share of page views were Good, Needs improvement, and Poor.
Largest Contentful Paint (LCP)
How long the largest thing on screen, usually your hero image or headline, takes to appear. This is the closest match to what a shopper means by "the page loaded." A Good rating is 2.5 seconds or less.
Interaction to Next Paint (INP)
How quickly the page responds when a shopper taps or clicks. High values feel like a frozen page, and often show up on pages carrying heavy scripts. A Good rating is 200 milliseconds or less.
Cumulative Layout Shift (CLS)
How much the page jumps around while it loads. Shifting content causes mis-taps, such as a shopper hitting the wrong variant because a banner loaded late. A Good rating is 0.1 or less.
Supporting metrics
First Contentful Paint (FCP)
How long until anything at all appears. This tells you whether a slow Largest Contentful Paint starts with a slow first render. A Good rating is 1.8 seconds or less.
Time to First Byte (TTFB)
How long the server takes to send the first byte of the page. This points at server or app response time rather than anything in your theme. A Good rating is 800 milliseconds or less.
Rating thresholds
Metric | Good | Needs improvement | Poor |
Largest Contentful Paint | 2.5s or less | 2.5s to 4.0s | Over 4.0s |
Interaction to Next Paint | 200ms or less | 200ms to 500ms | Over 500ms |
Cumulative Layout Shift | 0.1 or less | 0.1 to 0.25 | Over 0.25 |
First Contentful Paint | 1.8s or less | 1.8s to 3.0s | Over 3.0s |
Time to First Byte | 800ms or less | 800ms to 1800ms | Over 1800ms |
Trends
The Trends chart plots Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift, and conversion rate over your selected date range. Each metric uses its own scale, so compare the shape of the lines rather than their heights. Use this to check whether a speed change lines up with a conversion change, and to confirm that a theme or app change actually helped.
How the numbers are calculated
Every metric is reported at the 75th percentile, written as p75. A Largest Contentful Paint of 3.1s means 75% of page views loaded in 3.1 seconds or less, and the slowest 25% took longer.
Percentiles are used instead of averages because averages hide your worst experiences. One very fast visit can cancel out one very slow visit in an average, while the p75 tells you what a shopper on the slower end of your traffic actually gets. Google uses the same p75 approach to assess Core Web Vitals, which keeps your numbers comparable to its thresholds.
Sessions, orders, and conversion rate come from your pixel data for that landing page, using the same last-click attribution as the rest of Triple Whale.
Filters
Date range
The date range sets the window for every number on the page. Widen it if a page has too few measurements to report.
Device
The device filter switches all metrics between All Devices, Mobile, and Desktop. Mobile and desktop speed often differ sharply on the same page, so check both before deciding a page is healthy. The Good, Needs improvement, and Poor breakdown bars appear only in the All Devices view.
Ask Moby about page speed
Moby can query your performance measurements directly, which answers questions the tab doesn't cover. Try asking:
"How have my Core Web Vitals changed over time?" Returns Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift by date.
"What are the p75 LCP, INP, CLS, and TTFB measurements for my site?" Returns your 75th-percentile vitals across the whole store.
Moby also reaches three timings the tab doesn't display: First Input Delay, an older responsiveness metric that Interaction to Next Paint replaced; DOM Content Loaded; and Page Load Complete. You can combine performance data with anything else Moby queries, over any date range.
Troubleshooting
"No performance data available"
This appears when no pages have data for your filters. Confirm the Triple Pixel Theme App Embed is enabled in your Shopify theme, then widen your date range. After you enable the embed, allow 24 to 48 hours for the first measurements to arrive. If you filtered to Mobile or Desktop, switch to All Devices, because a store can have too little traffic on one device type to report.
A metric shows a dash instead of a value
The page has fewer than 10 measurements for that metric in the selected date range and device. Hover the dash to see the current sample count. Widen the date range or wait for more traffic.
Interaction to Next Paint is empty
Interaction to Next Paint is recorded only when a shopper taps or clicks. Pages people read and leave without interacting won't report it, and the health score falls back to a partial score marked with a tilde.
A page I care about isn't listed
The list holds your 20 busiest landing pages by sessions for the selected filters. A page below that cut-off doesn't appear. Narrowing the date range to a period when that page had more traffic can bring it into the top 20.
My numbers don't match PageSpeed Insights or Lighthouse
They measure different things and won't agree. Lighthouse runs one simulated load on a fixed device and connection. Page Performance summarizes real page views from your actual shoppers, so it reflects your true traffic mix. Treat Page Performance as the record of what shoppers experience, and Lighthouse as a diagnostic tool for a single page.
I don't see the Page Performance tab
The tab appears for Shopify stores. If your store runs on another platform, it isn't available.
Related reading: installing the Triple Pixel on your Shopify store, which covers enabling the Theme App Embed.





