WordPress Health Check
Enter a WordPress site and get a quick health report: is caching working, how heavy is the page, is HTTPS and compression on, is the REST API reachable and are the SEO basics in place. A score, and a plain fix for every issue. Reads only the public home page.
- Loading the home page
- Confirming it runs WordPress
- Checking the REST API
- Measuring performance and page weight
- Checking HTTPS, caching and the content basics
Want your WordPress site running properly?
The checker looks at one public page. We do the full job: speed, caching, updates, security and ongoing care, so the site stays fast and does not break.
- Speed and caching, from the server to the CDN
- Plugin and theme review, updates done safely
- Security hardening and backups
- Fixing what a page builder left bloated
- Ongoing maintenance so it keeps working
Why WordPress sites slow down and break
WordPress runs roughly two in five websites, and most of them share the same handful of problems: no page cache, so every visit runs PHP and the database from scratch; a pile of plugins each adding its own scripts; a page builder producing enormous HTML; and updates left undone until something breaks. None of it is visible until the site is slow, or down.
This check reads the public home page the way a visitor does and reports the signals that point to those problems — a slow first byte, heavy HTML, dozens of separate assets, missing compression — together with the delivery and content basics. It is the quick version of the review we do in full for the sites we maintain.
1. WordPress
Confirms WordPress is running, reads the active theme and checks the REST API that the editor and many plugins depend on.
2. Performance
Response time (is page caching working?), HTML size, the number of scripts and stylesheets, and whether text is compressed.
3. Delivery
HTTPS, caching headers and the content basics — title, description and structured data an SEO plugin should manage.
Questions and answers
What does the WordPress health check look at?
After confirming the site runs WordPress, it reviews performance (response time, HTML size, number of assets, compression), delivery (HTTPS, caching headers), the REST API, and the content basics (title, description, structured data). Everything comes from the public home page, robots.txt and the REST index.
Does it log in to my site?
No. It reads only public pages that any visitor can open, and changes nothing. A full health check, with your permission, also looks at the admin, the database, error logs and every template.
It says my site is not WordPress, but it is. Why?
Some setups hide WordPress behind a full-page cache, a CDN or a headless front end, which removes the usual signals from the HTML. In that case this tool cannot analyse it, though the same caching is often good for speed.
A slow response — what does that mean?
A slow first byte almost always means there is no page cache, so WordPress rebuilds the page with PHP and the database on every request. Adding page and object caching is usually the single biggest speed win.
Need more than a one-page check?
We have been building and maintaining websites and WordPress since 2008. Tell us about your site and we will come back with a plan and an honest estimate.