Speed

The Speed page tells you how fast your site feels to the people using it, measured on their real devices and connections, not on a fast machine in an office. A page that loads instantly for you on office wifi can crawl for someone on a phone with a weak signal. This page shows you the real experience, and it puts the slowest pages first so you know where to spend your effort.

Think of it like measuring a restaurant by how long real customers wait for their food, not by how fast the kitchen thinks it is. What matters is what people actually feel.

What you see

• A page title that reads “Speed”, with the date range shown nearby.
• A set of speed measures for your site, described in plain terms: how quickly the main content appears, how quickly the page responds when someone taps or clicks, and how much the page jumps around while it loads. Each is the kind of thing a visitor notices without knowing the name for it.
• A per-page breakdown with the slowest pages at the top, so you can see which specific pages feel slow rather than just an overall score.

How to read it

Read the measures for the site as a whole first, then find the slow pages.

The three things that matter to a visitor are simple. First, how long until the main thing they came for shows up. Second, how quickly the page reacts when they try to do something, like tap a button. Third, whether the page holds still or jumps around as it loads, which is the annoying moment when a button moves just as you go to press it. Good scores on all three mean the page feels smooth. A bad score on any one is a specific, fixable annoyance.

These numbers come from real visits, so they reflect the mix of devices and connections your actual audience has. That is why the page can look slower here than in your own testing: your testing is one fast device, and this is everybody.

Customize it

• Set the date range. Use a short range to check whether a change you made helped or hurt, and a longer range for a stable picture that is not thrown off by one unusual day.
• Scope to one website. If you track more than one site, look at one at a time so their speeds are not blended.
• Start with the slowest pages. The per-page list is sorted so the worst offenders are at the top. Fix those first, since they frustrate the most people.

Use cases

• Find the page that is quietly losing you visitors. Open the slowest pages and see whether any of them are important, like a product or checkout page. Action: a slow key page costs you real business, so make it your first speed fix and re-check after.
• Check the effect of a change. After you add something heavy, like a new video or a third-party widget, set a short range and see whether your speed measures got worse. Action: if they did, the new thing is the likely cause, so weigh whether it is worth the slowdown.
• Prioritize with data, not guesses. Instead of guessing which pages feel slow, read the list. Action: spend your effort where the numbers say people are actually waiting.

Tips

• Real visitors, not your machine. This page reflects your audience’s real devices and connections, which is why it can differ from how fast the site feels to you. Trust it over your own impression.
• Fix the worst first. The slowest pages at the top of the list annoy the most people. Work down from there rather than polishing already-fast pages.
• The page jumping around counts as slowness too. If things shift while loading and people mis-tap, that is a real, fixable problem even if the page technically loads quickly.
• Give it enough visits. Speed measured from very few visits can swing around. A longer range gives you a steadier read before you act.