X
X
X
X

Knowledge Base

HomepageKnowledge BaseGeneralHow to Find Website Errors with Bro...

How to Find Website Errors with Browser Developer Tools: Console and Network

In short: If a page on your site looks broken, a form does nothing or an image will not load, the reason is often spelled out in your browser's developer tools. In Chrome and Edge, press F12: the Console tab shows error messages and the Network tab shows the status code and timing of every request. This guide walks you through both tabs step by step and shows how to share what you find with support safely.

When is this useful?

  • The page loads but styles (CSS) or images are missing.
  • Nothing happens when you click a button, form or menu.
  • After moving to HTTPS, the padlock does not appear in the address bar.
  • The page is slow and you want to know which file is holding it up.

Step 1: Open the developer tools

Open the problem page in Chrome or Edge and do one of the following:

  • Press F12.
  • Use Ctrl + Shift + I on Windows/Linux or Cmd + Option + I on macOS.
  • Right-click the page and choose Inspect.

When the panel opens you will see tabs such as Elements, Console and Network. The same shortcuts open a similar panel in Firefox.

Step 2: Read error messages in the Console tab

Switch to the Console tab and reload the page. Red lines are errors and yellow lines are warnings. Common messages and what they mean:

Text in the message What it means
Failed to load resource ... 404 A file the page requests does not exist on the server or its path is wrong.
Mixed Content An HTTPS page loads a resource over http://. See our mixed content error article for the fix.
Uncaught TypeError / ReferenceError There is an error in a JavaScript file, usually from a plugin or theme script.
blocked by CORS policy The page is trying to access a resource on another domain and that server does not allow it.

Click the file name on the right of a line to see which file the error comes from. If the path contains something like /wp-content/plugins/plugin-name/, the problem is most likely in that plugin. For a full reference, see the Chrome Console documentation.

Diagram of browser developer tools showing error lines in the Console tab and the request list with status codes and timing bars in the Network tab

Step 3: Inspect requests in the Network tab

  1. Switch to the Network tab.
  2. Tick Disable cache so files are requested from the server again instead of the browser cache (this applies while the panel is open).
  3. If the page redirects, or moves to another page after a form is submitted, also tick Preserve log; otherwise the list is cleared when the page changes.
  4. Reload the page. Every file the page loads appears as a row.

The Status column shows the HTTP status code of each request. To see only failed requests, type status-code:404 or status-code:500 in the filter box at the top. The filter buttons (Doc, CSS, JS, Img, Fetch/XHR) list only certain types. See HTTP status codes explained for what each code means.

Step 4: Look at a single request in detail

Click a row in the list to open its details on the right:

  • Headers: the request URL, status code and response headers. The Remote Address field shows which server IP the request went to; after a DNS change, this tells you whether you are reaching the new server. To try a new server without changing DNS, see our hosts file testing guide.
  • Response: the content the server returned. If a form request returned 500, the error text may appear here.
  • Timing: the stages of the request. A long Waiting for server response means the slowness is on the server side (PHP, database); a long content download means the file is large.

All Network panel features are described in the Chrome Network documentation.

Step 5: Share your findings with support

If you cannot solve the problem yourself, the following information speeds up support considerably:

  • The full address of the problem page and when the problem started.
  • A screenshot of the red lines in the Console tab.
  • The URL and status code of the failing request in the Network tab.

Be careful if you export the network log as a HAR file: by default Chrome produces a "sanitized" log without cookie and authorization headers, but the file can still contain the URLs you visited and form data. For the same reason, remove cookie lines from Copy as cURL output before sharing it. You can send the details by opening a support ticket.

Tips

  • If only you see the problem, first clear your browser cache or try a private window.
  • To test the mobile view, click the device icon in the panel or use Ctrl + Shift + M (Cmd + Shift + M on macOS).
  • If a WordPress site shows a blank page or a "critical error" for every page, the problem is on the server, not in the browser; follow our WordPress critical error article.
 

Frequently Asked Questions

Will changing something in the developer tools break my site?

No. Changes in the Elements tab apply only in your own browser while that page is open and disappear when you reload. Files on the server are not touched.

The Console shows lots of yellow warnings. Is that a problem?

Most warnings are about deprecated features or third-party scripts and do not break the site. Focus on the red error lines first.

Why is the Network tab empty?

The panel only records requests made while it is open. Reload the page after opening the tab.

What if the error only appears for one user?

Ask that user for a Console screenshot from the same page. Browser extensions, an old cache or a different network (such as a company proxy) can cause such differences.

Can't find the information you are looking for?

Create a Support Ticket
Did you find it useful?
(22 times viewed / 0 people found it helpful)

Powered by WISECP
Top