Server-side view
The page still returns 200
Status and TTFB can look normal even when more work is happening after the response reaches the browser.
- HTTP 200
- TTFB near baseline
- Server content available
Shopify performance monitoring
Catch Shopify performance regressions before they hurt sales
GO4 Browser Lab loads important storefront pages in a controlled browser and keeps the evidence around each run — timing, resources, JavaScript errors, screenshots and history — so you can see not only that performance changed, but what changed around it.
HTTP 200 is not the whole experience
A Shopify storefront can be online and still get slower
Server-side availability tells you whether a page responds. Browser Lab adds the loaded-page evidence you need when the storefront is technically online but the customer experience has changed.
Loaded-browser view
The page can still regress
New scripts, heavier resources, JavaScript failures or a broken customer-facing widget can change what shoppers actually experience.
- Longer browser load
- New or heavier resources
- JavaScript / resource failures
That gap is why GO4 keeps HTTP/Page monitoring and Browser Lab as separate evidence layers instead of treating them as the same check.
Performance evidence
Measure the signals around the loaded page — not only one speed score
Browser Lab keeps the metrics that help explain a regression and lets you compare them across stored runs.
The total controlled browser load timing for the monitored page.
How long the browser waited for the first byte from the page response.
What happened after the first byte while the page continued loading in the browser.
Long main-thread work captured during the Browser Lab run.
The number of network requests made while loading the page.
How much network data the loaded page transferred during the run.
Browser-side JavaScript errors observed during the controlled run.
Resources that failed while the storefront page was loading.
Historical comparison
Compare patterns instead of guessing from one run
Browser Lab Performance Summary compares stored history with median-based groups so one unusually fast or slow run does not become the whole story.
Latest analysis
Analyze the latest filtered run history for the current Browser Lab check.
Previous → Latest
Compare the earlier run group with the latest group and see how the typical pattern changed.
Custom A/B
Choose exact runs or date/time ranges for Baseline A and Comparison B.
Reference run
Save one real Browser Lab run as a durable reference point for later comparison.
Baseline A5 runs
Comparison B7 runs
Median browser load2.38 s2.91 s+22%
Median TTFB418 ms426 ms+2%
Transferred1.75 MB2.21 MB+26%
JS errors02+2
Measurement settings matter
If the browser profile or relevant measurement settings differ between groups, GO4 shows that mismatch instead of presenting the comparison as perfectly equivalent.
Resource-level evidence
See which resources appeared, disappeared or changed
When evidence level allows it, Browser Lab stores a bounded, privacy-reduced resource snapshot from the network data it already collected. That lets historical comparison surface meaningful changes around a regression.
ResourceChangeEvidence
reviews-widget.jsNewAppears consistently in Comparison B
bundle-app.jsHeavier+220 KB typical transferred size
recommendations.jsSlower+340 ms typical network timing
theme.jsImproved-180 ms typical network timing
NewDisappearedSlowerHeavierMore activeImproved
Resource URLs are reduced before storage: credentials, query strings and fragments are removed, and evidence remains bounded rather than becoming an unlimited raw network dump.
Installed apps & storefront dependencies
A Shopify app can become a storefront problem without disappearing completely
Reviews, sizing, bundles, recommendations, chat, tracking and other apps can add visible widgets, scripts and network requests to the storefront. GO4 gives you more than one way to watch the customer-facing result.
Is the critical app module still visible?
Use Browser Lab assertions or a supported Action Journey to verify an important customer-facing widget or interaction on the loaded storefront.
Did an external dependency change?
External Radar complements browser evidence by tracking third-party apps, widgets, providers and resources important pages depend on.
GO4 monitors observable storefront behavior and dependencies. It does not manage or diagnose the private internals of a third-party Shopify app.
TTFB vs browser-side regression
Separate server delay from what happens after the response starts
A higher TTFB is useful evidence, but it is not automatically the reason the whole page became slower. Browser Lab keeps the total-load context so the verdict stays grounded.
Server or network delay may be contributing to a real whole-page regression. Investigate both the response and the rest of the load.
Look after TTFB: scripts, requests, transferred bytes, failed resources and browser-side work are stronger suspects.
Do not call the whole page slower only because TTFB increased; later loading may have compensated for it.
Before / after evidence
Verify a theme, app or storefront change with evidence from both sides
Browser Lab can capture diagnostic evidence before and after a deliberate change, helping you compare what the browser saw without turning the proof series into normal monitoring status.
Capture the current behavior
- Timing and resource context
- Screenshot evidence when enabled
- Current JavaScript and failed-resource signals
Repeat the browser evidence after the change
- Compare the same target again
- Confirm whether the regression improved
- Keep diagnostic proof separate from normal status
Before/after proof runs are diagnostic: they do not change the normal check status, Dashboard health, incidents or alerts.
Field data + controlled browser evidence
Use Shopify web performance reports and GO4 Browser Lab for different questions
They are complementary, not interchangeable. Shopify reporting helps you understand real visitor performance trends; Browser Lab gives you controlled scheduled evidence that is easier to repeat and investigate.
Field / real visitor view
Shopify web performance reports
Useful for real-user performance signals and Core Web Vitals trends across actual storefront visits.
- Real visitor experience
- Core Web Vitals context
- Aggregate field trends
Controlled monitoring view
GO4 Browser Lab
Useful for scheduled repeatable browser checks, screenshots, JavaScript and resource evidence, historical comparison and before/after proof.
- Repeatable controlled runs
- Resource / JavaScript evidence
- Reference, A/B and historical comparison
Use field data to understand what visitors experience, then controlled Browser Lab evidence to reproduce, compare and investigate what changed.
Shopify performance monitoring questions
What Browser Lab adds to storefront performance monitoring
The goal is not another score. It is repeatable evidence that helps you understand a performance change.
What is Shopify performance monitoring?
It is the ongoing observation of storefront performance signals so regressions can be detected and investigated over time. In GO4, Browser Lab provides controlled browser runs with timing, resource, JavaScript, screenshot and historical evidence.
Can a Shopify store be online and still have a performance problem?
Yes. A page can return HTTP 200 while browser load gets slower, JavaScript errors appear, resources fail or customer-facing app modules change. That is why GO4 keeps server-side checks and Browser Lab as separate monitoring layers.
Can installed Shopify apps make the storefront slower?
They can contribute scripts, widgets, requests and transferred data to storefront pages. Browser Lab can show changes in loaded-page evidence, while External Radar can add visibility into the external apps, providers and resources those pages depend on.
Can GO4 show which resources changed between Browser Lab runs?
When exact-resource evidence is available, comparison can surface meaningful new, disappeared, slower, heavier, more-active and improved resources. Older runs without that snapshot remain comparable through the existing performance and resource-group evidence.
What is TTFB and why is it not the whole page load time?
TTFB measures how long the browser waits for the first byte of the response. The storefront can still spend significant time loading scripts, styles, fonts, images and app resources after that point, so GO4 keeps TTFB and total browser load in the same comparison context.
Can I compare performance before and after a theme or app change?
Yes. Browser Lab supports diagnostic before/after proof so you can capture browser evidence around a deliberate change. Those proof runs stay separate from normal monitoring status, incidents and alerts.
Does Browser Lab replace Shopify web performance reports?
No. Shopify field reporting and GO4 Browser Lab answer different questions. Real-user field data helps show what visitors experience at scale, while controlled Browser Lab runs help reproduce, compare and investigate specific storefront behavior over time.
Turn a slowdown into evidence
See what changed in the browser before performance problems become guesswork
Monitor important Shopify pages with repeatable Browser Lab runs, historical comparison and resource evidence in the same GO4 workflow.
Controlled browser runsHistorical comparisonResource-level evidence