Audisto File Size Checker

How to detect file size related issues on your website

The file size directly influences a website's performance parameters like loading speed as well as maintenance cost for traffic. By influencing the loading speed, the file size also influences the user experience and therefore the rate of user engagement. This can have a direct impact on your sales.

With this hints section you can identify the most common issues that lead to an increased file size of a website.

Example: Audisto File Size Check with the size hint reports for the current crawl

Audisto File Size Check with the size hint reports for the current crawl

Here is the list of all specific hints related to file sizes, that can be identified with the help of the Audisto Crawler.

Table Of Content

Hints

<html> is more than 100 KB in size

Description

If a document is more than 100 KB in size, the URL is flagged with this hint. Use this report to find all HTML documents on the crawled website that have more than 100 KB of markup.

Examples

HTML markup contains a lot of:

  • inline css
  • inline javascript
  • inline images
  • inline fonts
  • whitespace
  • HTML comments
  • bloated markup
Importance

Having more than 100 KB of code in an HTML document is usually a sign of bloated markup and adds to traffic volume, loading time and rendering time. Reducing the size of the HTML document will result in less traffic volume for the user and the webmaster. It will also enhance performance and optimize the user experience of the website.

Operating Instruction

You may want to reduce the size of the document. This can be done by consolidating inline elements into external files, reducing HTML comments or markup optimization depending on your site's core markup.

<script> more than 3 KB within HTML

Description

If more than 3 KB of JavaScript is found within the HTML, the URL is flagged with this hint. Use this report to identify all occurrences of inline JavaScript with more than 3 KB in total.

Importance

If more than 3 KB of inline JavaScript is found in one HTML document, this usually indicates unnecessarily bloated code. 3 KB may not seem like a lot, but the numbers can add up if this occurs on larger websites. This leads to:

  • waste of bandwidth
  • lower performance
  • poor overall user experience

Moving inline JavaScript to separate files is a best practice for performance optimization.

Operating Instruction

JavaScript should be placed in a separate file whenever this helps to improve performance.

CSS <style> content larger than 0.5 KB

Description

If more than 0.5 KB of CSS is found within <style> tags, the URL is flagged with this hint. Use this report to identify all occurences of inline style sheets with more than 0.5 KB in total.

Importance

If more than 0.5 KB of inline CSS is found in one HTML document, this usually indicates unnecessarily bloated code. 0.5 KB may not seem like a lot, but the numbers can add up if this occurs on larger websites. This leads to:

  • Waste of bandwidth
  • Lower performance
  • Poor overall user experience

Moving inline CSS to seperate files is a best practice for performance optimization.

Operating Instruction

CSS should be placed in a separate file whenever this helps to improve performance.

CSS <style> found

Description

If CSS is found within a <style> tag, the URL is flagged with this hint. CSS should be placed in a separate file whenever it is used across multiple webpages.

Example
<style>
h1 { color: green; }
</style>
Importance

Inline CSS can indicate poorly written markup. CSS definitions should usually be in an external file that can be cached by clients and, once requested, be used for multiple page views. This reduces the size of the actual HTML document and improves the website's performance. If inline CSS is used excessively, this can lead to:

  • Waste of bandwidth
  • Lower performance
  • Poor overall user experience

Moving inline CSS to external files is a best practice for performance optimization.

Operating Instruction

CSS should be placed in a separate file whenever it is used across multiple webpages. By doing this, you can make the CSS cacheable and deliver HTML documents that have lower file sizes.

CSS style attribute found

Description

If CSS is found as a style attribute, the URL is flagged with this hint. CSS should be placed in a separate file whenever it is used across multiple webpages. Use this report to identify all URLs that contain style attributes in the HTML markup.

Example
<p style="text-decoration:bold;">text</p>
Importance

Style attributes in HTML tags are usually not the most optimal way to achieve styling of certain elements. Best practice suggests to put CSS definitions into separate CSS files that can be cached by clients across multiple page views. This reduces the size of the actual HTML document and improves the website's performance.

Operating Instruction

Style defintions should be placed in a separate file whenever this helps to improve performance.

Compression not enabled

Description

Content compression was not enabled, or the gzip/deflate compression is not supported by the server.

Example

Request Header asking for gzip, deflate or sdch:

GET /page.html HTTP/1.1
Host: example.com
...
Accept-Encoding: gzip, deflate, sdch

Response Header with gzip compression:

HTTP/1.1 200 OK
...
Content-Encoding: gzip
Content-Length: 1140

Response Header without gzip compression:

HTTP/1.1 200 OK
...
Content-Length: 4726
Importance

Compression can reduce bandwidth usage dramatically and is recommended. Compression was introduced with HTTP 1.1. HTTP 1.0 does not support compression. Compression affects the data volume that needs to be transfered and can improve the performance of your website. Better performance equals a better user experience.

Operating Instruction

We recommend that you globally enable compression like gzip or deflate on your website.