Website speed test

What is slowing this page down?

Paste a page URL and choose a device. Review loading issues and improvement opportunities, then check real-user data when the page has enough to show.

Device

Before a run we check automatically that you're not a robot, to keep the tool from being abused.

How to use it

  1. 1

    Enter a public page

    Use your homepage, a product page, or an article you want to test.

  2. 2

    Choose mobile or desktop

    Start with the device your audience uses, then review the other device too.

  3. 3

    Review the opportunities

    Start with an issue that matters and check the listed files before changing them.

01 / LINKAZA TOOLS

A current test and past visitor data

Lab results come from a Lighthouse test. When CrUX data is available, you can also review Chrome users’ experience over 28 days. Not every page has enough field data.

02 / LINKAZA TOOLS

Read the Core Web Vitals

LCP measures the main content’s loading, INP measures response to interaction, and CLS measures visual stability. Good thresholds are 2.5 seconds, 200 milliseconds, and 0.1 respectively. Read them alongside the device and available data.

03 / LINKAZA TOOLS

When the score changes between runs

Network conditions, the server, and ads can change between tests. Compare runs under similar conditions, then review real-user data when available before judging an improvement.

Frequently asked questions

01Who runs the speed test?

The test comes from the official Google PageSpeed Insights API. Linkaza displays the results for you to review.

02Why is real-user data missing?

Google may not have enough data for the page or site. Review the lab test without treating it as a record of every visitor’s experience.

03When will the result be ready?

Wait for Google to finish checking the page. Timing depends on the response and service availability.

04Do I need a score of 100?

Use the score to find work worth doing, alongside Core Web Vitals and visitor data when available. Choose a useful fix rather than chasing the number alone.

More free tools

Read speed from loading through interaction

The three metrics answer different questions

LCP covers the largest content’s loading, INP covers interaction responsiveness, and CLS covers visual stability. When available, field results use the 75th percentile over a 28-day window, separating mobile and desktop.

Lighthouse lab tests help diagnose loading and browser work. TBT is a lab blocking measure; it does not establish a real-user INP pass. A performance score and field Core Web Vitals are different results.

Test a change you can compare

Use the same URL, device, and similar conditions, recording the date and result. Start with the image, font, resource, or script identified in the findings, then measure after the change. Do not combine different devices as one experiment.

When field data is absent, do not fill it with a lab score. Review important templates and use Search Console or CrUX data when available to assess real visitors’ experience.

Current good Core Web Vitals thresholds
MetricQuestionGood threshold
LCPWhen does the largest content appear?Up to 2.5 seconds
INPHow quickly does an interaction get a response?Up to 200 milliseconds
CLSDoes the layout shift during use?Up to 0.1

Questions to help you decide

Can I compare development with the live site?

Development includes different tooling and code. Use it to diagnose issues and measure an optimized production build after deployment. Do not present a development score as the live site’s score.

Does speed alone establish a good experience?

Review readability, keyboard use, controls, and forms too. A better speed number does not establish complete accessibility or usability.

START BY COMPARING PUBLISHERS

Find a publisher and review the offer.

Compare language, traffic, and prices, then place your backlink or guest post order from a free account.

Create a free accountReview publishers and offer terms before ordering