Pinpoint render and interactivity delays
Once the server has responded, script execution and interface rendering decide the experience your users actually get. This dashboard measures exactly when the page becomes ready to interact with, and shows where the slowness builds up — split by device, browser and operating system.
Is the page slow for everyone, or only for a particular group?
A site can look fast at first glance while a share of your users sits through a long wait. Break the numbers down by device to see whether the frustration is concentrated on desktop or on mobile — and spend your budget and engineering time where it actually pays off.
Key point: Aggregate figures tend to hide a whole group's drop in experience; breaking the data down by platform stops you from overlooking the users who genuinely run into a slow site.
What share of your users have a slow experience?
A step-by-step read of front-end performance: from how long the browser spends processing scripts, to the page structure being fully laid out, to the exact share of visits slower than 3 seconds.
Browser processing time
428msGoodThe gap between the first byte arriving and the DOM tree being built — a read on how efficient your JavaScript and front-end computation are.
Page structure ready
1.32sGoodFrom the user's tap to the first render of the page structure (under 1.5s: healthy; 1.5 to 3s: worth investigating).
Poor-visit rate (over 3s)
16.4%Needs improvementThe actual share of visits where the page took longer than 3 seconds to become ready.