Performance Tools

Performance Health Score

Get a quick health check of the server-side factors that make a website fast or slow.

Not sure what to enter? Try an example: wikipedia.org

Free & instant No signup How to use FAQ

642 ms

wikipedia.org

Compression

Disabled

HTTP Version

HTTP/1.1

Keep-Alive

Disabled

CDN

Not Detected

Last checked: 3 minutes ago Cached

Download JSON Download PDF

35/100

Result Summary

Warnings

Serves HTTP/1.1

No Cache-Control header

Keep-Alive not detected

No CDN detected

Failed

No compression enabled

How to Fix

Enable GZIP - compressing responses can significantly reduce page load times.

Upgrade to HTTP/2 or HTTP/3 - both allow multiplexed, faster connections than HTTP/1.1.

Improve Cache Headers - add Cache-Control so browsers and CDNs can cache this response.

Enable Keep-Alive - persistent connections reduce overhead for visitors loading multiple resources.

Use a CDN - distributing content closer to visitors can meaningfully improve load times.

Enter a URL to check response time, compression, HTTP version, keep-alive and CDN use together, with a clear list of what to improve.

What does the performance health score measure?

It combines the server-side signals that most affect loading speed - response time, compression, HTTP version, keep-alive and CDN usage - into one score with what to improve first. It measures the server and network setup, not in-browser rendering.

How to get a performance health score

Enter the domain in the box above.
Click Get Performance Score.
Review the score and each check that did not pass.
Fix the biggest wins first: compression, HTTP/2 and caching behind a CDN.

Related checks

To find render-blocking CSS and JS, use the Render-Blocking Resources Checker.
To check images, use the Image Optimization Checker.

JustChecker tracks your website's performance signals continuously and alerts you if anything regresses.

Frequently Asked Questions

No - this checks the server and delivery settings that PageSpeed assumes are right. Fixing these first often improves PageSpeed and Core Web Vitals scores too.

Slow server response and missing compression usually give the biggest gains, followed by moving to HTTP/2 and adding a CDN for visitors far away.

If response times stay slow after caching and plugin clean-up, the server itself is too slow. Moving to faster hosting is often the single biggest speed upgrade.

Share this tool:

Need a website for your business? Only $599