PERFORMANCE & SCRIPT INTELLIGENCE
Your store feels slow.
Find where to look.
Go beyond a single speed score. Follow real-shopper performance into the page, device, script and request evidence your team can investigate.
The heaviest script isn’t always the slowest.
Switch the ranking to see which resource deserves a closer look. Load duration and transfer size answer different questions.
PRODUCT PAGES · MOBILE
Find the work behind the wait.
Scripts worth inspecting
- 01reviews-widget.jsReviews app842 ms
- 02recommendations.jsRecommendations app617 ms
- 03theme.jsStorefront theme328 ms
Load duration p75 · Observed resource loading, not JavaScript execution time.
- 01theme.jsStorefront theme412 KB
- 02reviews-widget.jsReviews app284 KB
- 03recommendations.jsRecommendations app196 KB
Transfer size p75 · Inspect bytes alongside the page and loading context.
Start with the shopper’s experience.
LCP, INP and CLS keep loading, interaction and visual stability visible together. Scope the view to a storefront area, device and observation window, then compare browsers, operating systems, viewports, connection types and device memory. Connection and memory come from Chromium browsers; others count as unknown. Compare the current period with the previous one, then open a metric’s distribution, trend and affected pages.
Connect the page to a journeySee each page in its own traffic.
The Pages view compares every page group with the store: sessions, landings, purchase rate, error rate and the share of good, needs-work and poor LCP. A page’s detail shows where its shoppers came from, whether they started there, where they went next or left the store, and the issues and segments that stand out against the page’s own baseline.
Open the issues on that pageInspect the work behind the wait.
Rank scripts by load duration or transferred bytes. Check the page’s loading footprint, then compare resource patterns across good and poor performance observations. Browser stalls and endpoint health add context when a page looks loaded but shoppers still struggle to use it.
Bring the evidence to developmentKeep the comparison in scope.
A theme update, an added app or a new page layout can change the shopping experience. Use release context and like-for-like page and device views to examine what moved. Metric-specific browser evidence helps narrow an investigation without treating a large file as automatic proof of the cause.
Watch performance after a releaseA LITTLE MORE DETAIL
Good questions.
Useful answers.
Can I see the slowest and largest scripts?
Yes. The performance view ranks observed scripts by load duration and transfer size. Inspect both rankings alongside the page footprint and resource patterns to decide which script to investigate.
What does responsiveness add to Core Web Vitals?
Responsiveness makes browser stalls visible alongside page loading and interaction measurements. It helps you investigate an experience that feels stuck even when the main content is already on screen.
Which pages do shoppers land on, and where do they leave?
Pages shows landings and bounce for each page group, the pages shoppers arrive from and the pages they go to next, including starting there or leaving the store. Use it to find an entry page that loses shoppers before they reach a product.
Can I investigate a specific storefront area?
Scope performance to an area such as product pages or the cart, choose the device and observation window, and follow the metric into affected pages and captured environment patterns.
CONNECTED PRODUCT WORKFLOWS
Follow the next connection.
An issue, a journey, a page or a release. Each view gives you a way into the next.PUT YOUR STOREFRONT IN FOCUS
Your store.
Your next useful fix.
Bring the shopper journey you want to improve and the person who ships your changes. We’ll connect the first evidence and work through the findings together.
Book a demo Estimate your price and contact us · Guided setup