Parts of your page fail to load
Broken page resources
What this means
Some files your page asks for come back missing or with an error — an image, a stylesheet, a script or an API call. The page still opens, so the failure is easy to miss, but the visitor sees a broken layout, a missing picture or a button that does nothing.
Why it matters
A failed stylesheet or script breaks the part of the page it powers, and the visitor blames the product, not the file. Search engines see the same broken page you do. Repeated failing requests also slow the page down and waste the visitor's data.
When this is not a problem
Requests to third-party widgets (analytics, chat, ads) can fail for reasons outside your control — ad blockers, for example. Check whether the failing address belongs to you before changing anything.
How to fix it
- Open the page with the browser console on the Network tab and look for red rows — the same requests are listed there.
- Fix or remove references to files that no longer exist; a stale path after a rename is the usual cause.
- If the file moved, add a redirect so old links keep working.
- For failing API calls, make the interface handle the error instead of leaving an empty screen.
The page requests files that return errors. Find the failing references, fix the paths or remove them, and handle failed API calls in the UI.
How to verify the fix: reload the page with the network tab open and confirm no request fails