Masukkan URL
A page can look fine and still feel slow.
This free checker helps you test a URL’s performance signals — including score-style results and key loading metrics — so you can find what is slowing the experience down.

For meaningful comparisons, test important templates: homepage, category, product, and article pages.
| Section | What it helps you understand |
|---|---|
| Performance score | Overall lab-style speed rating (often 0–100) |
| Core Web Vitals signals | User-experience focused loading/interactivity/stability metrics |
| Lab data | Controlled test results under simulated conditions |
| Field data (when available) | Real-user experience data from Chrome users |
| Opportunities | Specific fixes likely to improve speed |
Field data is not always available for low-traffic URLs. In those cases, rely more on lab results and repeated testing.
LCP (Largest Contentful Paint)
How quickly the main visible content appears.
INP (Interaction to Next Paint)
How responsive the page feels after user interactions.
(Older reports may still reference FID in places; INP is the modern interactivity metric.)
CLS (Cumulative Layout Shift)
How much the layout jumps unexpectedly while loading.
Supporting lab metrics often include First Contentful Paint, Speed Index, Total Blocking Time, and server response indicators.
Aim to improve real user experience — not just chase a perfect vanity score.
Mobile scores are often lower than desktop because mobile tests use stricter network/device conditions.
That is expected. Optimize mobile first when possible.
Also remember: one test can vary. Re-check after changes and compare the same URLs over time.
Most sites improve fastest by fixing media weight, script bloat, and server response first.
A smaller number of high-impact fixes usually beats dozens of tiny tweaks.
Is this PageSpeed Insights Checker free?
Yes. Standard checks do not require an account.
Is the score the same as a Google ranking score?
No. Performance affects user experience and can influence page experience signals, but rankings depend on many factors.
Why is mobile much lower than desktop?
Mobile tests are typically more constrained. Focus on mobile improvements first.
Why is field data missing?
There may not be enough real-user Chrome data for that URL or origin yet.
Should I aim for 100/100?
Useful, but not mandatory. Passing real-user experience thresholds and fixing major bottlenecks matters more than perfection.
Note: Performance results can vary by test conditions, caching, and network factors. Use repeated tests on key URLs for a more reliable improvement process.