How to use the Website Doctor
- Enter the full address of the page that has a problem, for example
example.com/contact/. Checking the exact page matters, because problems are often on one page only. - Choose Mobile or Desktop. Most layout problems show up on Mobile.
- Press Diagnose. Our server downloads the page and checks its scripts, stylesheets and images one by one. Google PageSpeed renders the page in a real browser to catch JavaScript errors and layout shifts. This can take up to a minute.
- Read the problems from the top. Red items break features or layout, amber items are worth fixing next.
- Copy the suggested patch, apply it on a staging copy or after a backup, and run the check again.
What the report shows
| Check | What you learn |
|---|---|
| Page loads and redirects | HTTP status, the full redirect chain and server response time. |
| Site error messages | Critical error, database error, maintenance mode, out of memory and blank pages. |
| PHP errors on the page | Warnings and notices printed to visitors, with the plugin or theme file that raised them. |
| Broken files | Scripts, stylesheets and images that return 404 or fail, grouped by plugin or theme. |
| Mixed content and HTTPS | Insecure http files that browsers block on https pages. |
| Mobile layout | Viewport, text size, tap targets and images without size. |
| Real-browser checks | JavaScript console errors, failed requests, layout shift, load time and page freezes. |
| Search basics | Accidental noindex, wrong canonical, missing title and charset. |
Tips for better results
- Run the check on the exact page where something breaks, not only on the homepage.
- After any fix, purge every cache (cache plugin, CDN, browser) before testing again, or you may still see the old page.
- Apply code patches on a staging site or after a full backup.
- If a problem only appears after you click something or log in, use the Plugin Conflict Detective and paste the browser console errors there.
Limits to know about
- The tool checks one page load. Problems that appear after a click, inside wp-admin, behind a login or on other pages are not covered.
- Real-browser checks run through Google PageSpeed from a Google data centre. Sites that block bots or need cookies may not render.
- Up to about 45 files per page are checked from our server, so very large pages are checked partly.
- Suggested patches are common fixes, not changes made to your site. Review them before you apply them.
Frequently asked questions
What does the Website Doctor check?
It checks whether the page loads, follows redirects, finds PHP errors printed on the page, broken scripts, styles and images, mixed content, mobile layout problems and, through a real browser render, JavaScript errors, failed requests, layout shift and slow loading.
Why is my menu or slider not working?
The most common causes are a JavaScript error, a missing script file, or jQuery loaded twice or deferred. The report shows each of these with the file that causes it.
How do I fix "There has been a critical error on this website"?
Use the recovery link that WordPress emails to the admin, or rename the folder of the last updated plugin through your hosting file manager. Then turn on the debug log to see the exact cause.
Is it safe to apply the code patches?
They are standard fixes, but every site is different. Take a backup or use a staging site, apply one change at a time and run the check again.
Does the tool change anything on my website?
No. It only reads the public page and its files. Nothing is installed or changed.
Related tools
- WordPress Plugin Conflict Detective
- Website Technology Detector
- Free Page Load Time Tester
- Website SSL Certificate Checker
About this tool: free, no sign-up, works on phone and desktop. Last reviewed: November 2026.