Skip to content

AI-powered

Website Speed Test: See what makes a page slow, on a phone and a desktop

A website speed test that loads a page in our own browser on a phone and a desktop, and shows what makes it slow.

AvailableReady to use.

Open the tool
example.com/pricingSample data
MeasurePhoneDesktop
LCP3.9 s1.6 s
TBT420 ms60 ms
CLS0.020.01
Page weight2.8 MB2.8 MB

AI in this tool

AI turns the measurements into a short fix list. The numbers come from our own browser, not from AI.

What you can do

  • Test any public page on a phone sized browser and on a desktop.
  • See paint times, blocking time and layout shifts as lab numbers.
  • Find the heaviest images, scripts and fonts.
  • See which files block the first view.
  • Get screenshots of the page as it loaded.

What happens during a test

  1. Load on a phone

    A phone sized browser with a slower processor loads the page.

  2. Load on a desktop

    The same page loads on a desktop browser.

  3. Measure

    Paint times, blocking time, layout shifts and every file are recorded.

  4. Explain

    What to fix first, with the files behind each number.

Default settings

Devices
Phone and desktop
Numbers
Lab tests in our own browser
Time
About 30 seconds for both
Outside services
None

Coming next

  • Compare with competitor pages
  • Speed across the whole site
  • History of each test

What is a website speed test?

A website speed test loads a page the way a visitor's browser does and measures how long it takes to show, respond and settle. Ours loads the page in our own browser twice: once as a phone with a slower processor and once as a desktop.

The results are lab numbers: the same page, the same conditions, every time. That makes them good for finding causes and checking fixes. Real visitors on real networks can see different numbers.

What do the numbers mean?

LCP is when the largest piece of content appears. FCP is when anything appears at all. TBT is how long scripts block taps and clicks. CLS is how much the layout jumps while loading. TTFB is how long the server takes to answer.

Next to the numbers you see the page weight by file type, the heaviest files and the files that hold back the first view.

What usually makes a page slow?

Large images that are bigger than the space they fill, too many scripts loaded before the content, web fonts that block text, and a slow server reply are the most common causes.

Fix the biggest file first, then delay scripts that are not needed for the first view. Test again to confirm the change helped.

Why test on a phone?

Most visits come from phones, and phones have slower processors than laptops. A page that feels fast on a desktop can feel slow on a phone, so the phone result usually matters most.

Questions, answered

Are these Google's numbers?

No. They are lab numbers from our own browser. Google's real user data can differ.

Why is the phone result slower?

The phone test uses a slower processor and a smaller screen, like many real phones.

Do you store my page?

Only the measurements and screenshots of the result.

Can I test a page behind a login?

No. Only public pages can be tested.