Skip to main content
sus.botdocs
  • SEO
  • AI
  • QA
  • Privacy
  • Accessibility
  • Security
  1. Docs
  2. QA
  3. Page resources and script errors
  4. A page loads an image, stylesheet, script or font that fails or arrives the wrong way

QA finding

A page loads an image, stylesheet, script or font that fails or arrives the wrong way

QA Error Severity: Medium

Part of the audit Page resources and script errors. Finding id: qa.failingResources.

What it costs you

The page is not shown the way it was built.

What to do

Put the file back or correct the address in the page. For a redirect, link the final address directly. For a wrong type, make the server send the type that fits the file.

What it checks

  • Image, style, script or font missing
  • File address redirects elsewhere
  • File sent with wrong type

How to fix it

Restore the file or correct the reference

  1. Open [group key] in a browser to confirm the error.
  2. If the file is gone, restore it, or change the reference to the file that replaced it. The initiator in the evidence shows what asks for it.
  3. If the pages share a template_id, the reference is in that template.

How to check: Reload a page from the evidence with the network panel open: the file answers 200.

Send the right Content-Type

  1. Open [group key] in a browser. If you see an HTML page, the file is missing and an error page answers in its place: restore the file.
  2. If you see the file, correct the type the server sends for that file extension.

How to check: Reload a page from the evidence with the network panel open: the Content-Type of the file fits what it is.

Link the final address

  1. Open [group key] with the network panel open and read the address the redirect ends at.
  2. Put that address in the page or template. A common case is http where https is meant.

How to check: Reload a page from the evidence with the network panel open: the file answers 200 without a redirect.

Fix the reference or the file

  1. Open [group key] in a browser and look at the status and the Content-Type header in the network panel.
  2. If the file is gone, restore it or change the reference to the file that replaced it. The initiator in the evidence shows what asks for it.
  3. If it redirects, copy the final address into the page or template.
  4. If the type is wrong, check that the address returns the file and not an HTML page, then correct the type the server sends for that file extension.

How to check: Reload a page from the evidence with the network panel open: the file answers 200 without a redirect and with the right Content-Type.

  • All audits
  • About sus.bot
  • Open the app
  • Contact support