How to Read the Browser Console and Network Tab to Find Website Problems
A beginner's guide to F12 developer tools: finding broken files, blocked requests and script errors in a few minutes.
Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
Developer tools are built into every desktop browser. Press F12 (or right-click and choose Inspect).
Console tab
Shows errors and warnings from the page's JavaScript. Red lines are errors. The text names the file and line.
- "Failed to load resource: 404": a file is missing. See our 404 guide.
- "Mixed Content": an http file on an https page. See our mixed content guide.
- "X is not defined": a script ran in the wrong order or failed to load. See our JavaScript guide.
- CORS error: a page asked another site for data without permission from that site. The fix is on the other site's server.
Network tab
Reload the page with it open. It lists every file, with its status code and time.
- Red rows are failures.
- Sort by time to find slow files, and by size to find heavy ones.
- Click a row to see headers and the response.
Tips
Tick Disable cache while tools are open, and test in a private window. Copy the exact error text when you ask for help, it saves a lot of guessing.
Related guides
- WordPress White Screen of Death: How to Fix a Blank Page
- WordPress Theme Broke the Site: Switch Back to a Default Theme Without Dashboard Access
- WordPress Posts or Pages Show 404 Not Found but the Homepage Works
- WordPress Pages Show 404 Not Found (Posts Work, Pages Do Not)
Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.