Page Speed Checker

A PageSpeed Insights check with your own API key: performance score, lab (Lighthouse) and field (CrUX) data for LCP, INP and CLS against the official thresholds, and mobile versus desktop.

Workspace

How the result is calculated

The URL is sent to pagespeedonline.googleapis.com/v5/runPagespeed with your key and the performance category. The result is split into lab data (a single Lighthouse simulation: LCP, CLS, TBT, FCP, Speed Index) and field data (CrUX: real users, 75th percentile) from loadingExperience. Official thresholds: LCP good ≤ 2.5 s and poor > 4 s, INP ≤ 200 ms / > 500 (INP replaced FID in March 2024), CLS ≤ 0.1 / > 0.25, FCP ≤ 1.8 s / > 3, TTFB ≤ 800 / > 1800 ms. Performance score: 90+ good, 50–89 needs improvement, below 50 poor. The history (last 30 measurements) is stored in your browser only.

Limits: You need your own API key (free from Google Cloud; without one Google replies with a 429 quota error, as I tested). I could not test the tool with a real key, so the response shape the code parses is based on the API documentation and on test data I constructed — tell me about any field that differs. Field data is unavailable for low-traffic pages. Lab measurements vary from run to run. INP is not measured in the lab (field only). We do not store the key; restrict it by referrer in Google Cloud because the page runs in your browser.

FAQ

Where do I get the key?

From Google Cloud Console: enable the PageSpeed Insights API, create a key and restrict it to your site’s referrer.

Why do field and lab differ?

Lab is a single simulation and field is real users over 28 days; Google relies on the field data.

Newest tools

Recently added free tools — they run in your browser without uploading your data

All tools →

Remove image backgrounds in the browser with the small U²-Net model through ONNX Runtime Web, with a colour or image replacement and transparent PNG download

Local model

Build a valid n8n workflow JSON with a wizard: pick the trigger, steps and error handling with the latest node versions from the catalog

Local

Search n8n nodes (430+) by name, type and versions, read explanations of the common ones, and paste a workflow to explain its nodes and spot older versions

Local

Paste an OpenClaw log line (gateway, config, cron, heartbeat, channels) to get the likely cause, fix steps and a useful command, with a local gateway test

Local