Test Website Page Speed by URL

Enter a public URL, choose mobile or desktop and review a PageSpeed Insights report. Lighthouse scores come from a simulated test; real-user LCP, INP and CLS appear only when Google has enough data.

Public page URL

Public HTTP/HTTPS URLs only. A new run may take over a minute; the server caches reports for 30 minutes by default.

Advanced settings and comparison

Measurement location / region The current API does not select a country. Results do not represent global or Vietnam-specific speed.

Machine profile Mobile and desktop are simulated; PageSpeed does not accept a custom CPU strength setting.

Network conditions The current API cannot set bandwidth, latency or packet loss. Reported simulation settings will be shown when available.

Run and compare both mobile and desktop

Comparison requests 2 independent reports; either may come from cache. Unsupported countries and profiles remain marked “Not measured”.

—Lighthouse

Lighthouse performance score

Simulated device:

Measurement conditions

Source / test node: —
Device: —
Viewport / DPR: —
User agent: —
Simulated network: —
Reports / measured at: —

These settings come from the Lighthouse report. The device is emulated, not a physical phone or computer. API request duration is not page-load time.

Regional measurement availability

PageSpeed does not offer selectable country test nodes. No map is shown because no node coordinates are available; the cells below are not measurements from your browser.

Region	Node / provider	TTFB	Page load	Performance	Measured at	Runs
Unknown region	Google PageSpeed Insights · node unspecified	—	—	—	—	1
Vietnam	No measurement node	—	—	—	—	0
Singapore	No measurement node	—	—	—	—	0
Japan	No measurement node	—	—	—	—	0
United States	No measurement node	—	—	—	—	0
United Kingdom	No measurement node	—	—	—	—	0
Germany	No measurement node	—	—	—	—	0

LCP, INP and CLS by data source

Real-user data covers the recent 28 days when enough samples exist. Otherwise, LCP and CLS may use lab values; INP remains unavailable.

LCP—

—

Largest Contentful Paint

INP—

—

Interaction to Next Paint

CLS—

—

Cumulative Layout Shift

Accessibility

—

Best practices

—

SEO

—

Lab metrics and diagnostics

Compare this simulated run with available real-user data before choosing what to fix.

LCP — Largest Contentful Paint—

—

CLS — Cumulative Layout Shift—

—

TBT — Total Blocking Time—

—

SI — Speed Index—

—

FCP — First Contentful Paint—

—

TTFB — Server response time—

—

Optimization ideas

Check each suggestion against the actual page before making changes.

—

Audit details

—

Recently tested URLs

Up to 10 URLs, devices, scores and timestamps are stored in this browser. Select one to run it again; full reports are not stored here.

How to test a web page’s speed

Choose the exact page and device

Paste the public HTTP/HTTPS URL of the exact page, then choose Desktop or Mobile. Private URLs and pages Google cannot access will not produce a report.

Read speed metrics by their source

What you see	What it means	What to do next
Lighthouse score and lab metrics	One simulated run for the selected Mobile or Desktop mode; its 0–100 score does not represent every user.	Review the audits, fix relevant resources and retest the same URL and device.
LCP, INP, CLS labeled CrUX	Real-user data from roughly the last 28 days, for the URL or origin as labeled on each card.	Prioritize metrics needing improvement; an origin value is not specific to the entered URL.
A metric has no CrUX data	There may be too few samples. LCP/CLS may show separately labeled lab values; INP stays unavailable.	Use lab data for diagnosis; TBT can flag responsiveness work but does not replace INP.

Choose improvements from the report

Find resources affecting LCP

If an audit points to the main image or render-blocking resources, check image dimensions, above-the-fold loading and critical CSS/JavaScript. Audit savings are estimates for that run, not guaranteed score gains.

Stabilize layout and reduce work

For CLS, reserve space for images, ads and late content. For high TBT, inspect unused JavaScript and long tasks. After a fix, retest with the same strategy and watch real-user data when available.

Where are reports and history stored?

The browser sends the URL and selected device to KitoTool, whose server calls Google PageSpeed Insights. New reports are cached by URL/device (30 minutes by default); a clearly labeled fallback can use cached data up to seven days old when the service fails. This browser stores only the 10 latest URLs, devices, scores and timestamps; that history is not continuous real-user monitoring.

Comments & feedback

Rate this tool

Loading ratings…

Write a commentNo account needed

Test Website Page Speed by URL