Issues with file sources

This report will show you if there are problems with embedded files on your website.

Why you should avoid problems with files on your website:

Files that are needed to render a page should be optimized in the same way as the HTML page itself.

Problems with files can result in the page not rendering correctly. This can have a negative impact on the user experience. It can also negatively affect page speed, which is an important Google ranking factor.

What the error messages ("Problem" column) mean and how to fix them:

• Missing content-type specification: Your server is not providing content-type information when transferring the file, which can lead to rendering problems in the browser. Make sure that there is a content-type specified in the HTTP header for each file.
• File extension mismatch: The file extension does not match the content-type that is specified. Make sure that the two specifications are in line in order to avoid any display problems. For example, a CSS file with content-type "text/css" should end with ".css".
• No http compression (gzip): Text-based files that are 1 KB or larger are being sent without compression. This can make them slower to load. Enable HTTP compression, such as Brotli or gzip, for eligible text-based files including HTML, CSS, JavaScript, SVG, JSON, and XML. Files smaller than 1 KB are ignored in this analysis because the compression benefit is often minimal.
• High load time: The file takes longer than 1 second to load. Check out our blog to find out how to improve your loading speed.
• Redirect: The source URL of the linked file redirects to a different URL. Avoid unnecessary redirects by linking all files directly to the target file.
• Large file size: The file size is very large. Make sure that your images are no larger than 2 MB and that your CSS and JavaScript files are no larger than 0.5 MB.