How long does a phone visitor wait for your page?
Paste the page your ads or search results send people to. We get Google's phone test for it, place the result in Google's own bands, and show what the page makes a browser download.
Want to see what the page shows on a phone? Try the mobile-friendly test.
Updated
We ask Google PageSpeed Insights to test your page on its phone profile: an emulated mid-range phone on a slow mobile connection. From that test we read when something first shows (First Contentful Paint), when the main content shows (Largest Contentful Paint), how much the layout jumps while it loads (Cumulative Layout Shift), how long the page is too busy to respond (Total Blocking Time), and Google's performance score. We place Largest Contentful Paint in Google's own bands: under 2.5 seconds is good, 2.5 to 4 seconds needs improvement, 4 seconds or more is poor. Separately, our own browser visits the page and adds up the images and scripts it downloads. If Google doesn't answer for your page, the speed lines say "not measured" instead of showing a guess. Each check is a full FlowScan scan, so you also get a free report on the rest of the page.
| Check | How we measure it |
|---|---|
| When the main content shows on a phone (Largest Contentful Paint) | Google PageSpeed Insights, phone lab test |
| When something first shows, layout jumps, time too busy to respond | Google PageSpeed Insights, phone lab test |
| Google's performance score on a phone | Google PageSpeed Insights, phone lab test |
| Total page weight | Google's phone test, or our own browser if Google doesn't answer |
| How much is images and how much is scripts | Our browser's record of what the page downloaded |
| Files that hold up the first paint, and WebP or AVIF images | Google's test and what the page loaded |
Google's bar for Largest Contentful Paint, the moment the main content shows, is 2.5 seconds or less. Up to 4 seconds needs improvement; over 4 seconds is poor. Google judges a site by the 75th percentile of real visits, so most visits should come in under 2.5 seconds.
The speed numbers come from Google PageSpeed Insights' phone test. We put them in plain words, add how heavy the images and scripts are, and say so when Google gave us no reading.
Google's phone test models a mid-range phone on a slow mobile connection. A laptop on office wifi has far more power and bandwidth, and it may already have your page's files saved from an earlier visit.
Three places: large images (resize, compress, serve WebP), scripts that must run before anything shows (defer them), and widgets from other companies such as chat, video and reviews (load them when a visitor taps). The result shows how heavy your images and scripts are, which tells you which to try first.
Google has said since 2018 that landing page speed is a factor in Google Ads' landing page experience. Whatever the platform, the wait happens after the ad has already done its job.
Google didn't return a phone reading for your page while we checked. We show that rather than a number we didn't get. Try again later; if it keeps happening, something may be stopping Google's test from loading the page.
After each change you make for speed, so you can see whether it moved. Lab results vary a little from run to run, so look for a move between bands, not a tenth of a second.
No, we never submit your form. We don't log in or create accounts either, and the ad tracking on your page is stopped inside our browser, so our check isn't counted as a lead in your ad accounts.