Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

awstats.org

AWStats - Open Source Log File Analyzer for advanced statistics (GNU GPL)

Page Load Speed

2.6 sec in total

First Response

162 ms

Resources Loaded

2.1 sec

Page Rendered

339 ms

awstats.org screenshot

About Website

Welcome to awstats.org homepage info - get ready to check AWStats best content for India right away, or after learning these important things about awstats.org

AWStats Official Web Site - Compile and generate advanced graphical web, ftp or mail statistics with a logfile analysis (For IIS, Apache,... distributed under GNU GPL).

Visit awstats.org

Key Findings

We analyzed Awstats.org page load time and found that the first response time was 162 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

awstats.org performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

84/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

awstats.org

162 ms

www.awstats.org

515 ms

check.js

32 ms

misc.js

57 ms

styles.css

59 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 26% of them (19 requests) were addressed to the original Awstats.org, 9% (7 requests) were made to Apis.google.com and 9% (7 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (552 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.9 kB (36%)

Content Size

542.0 kB

After Optimization

347.1 kB

In fact, the total size of Awstats.org main page is 542.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 249.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 31.5 kB

  • Original 43.6 kB
  • After minification 40.5 kB
  • After compression 12.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.5 kB or 72% of the original size.

Image Optimization

-5%

Potential reduce by 13.3 kB

  • Original 249.6 kB
  • After minification 236.3 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. AWStats images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 145.5 kB

  • Original 242.7 kB
  • After minification 239.5 kB
  • After compression 97.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 145.5 kB or 60% of the original size.

CSS Optimization

-75%

Potential reduce by 4.5 kB

  • Original 6.0 kB
  • After minification 4.7 kB
  • After compression 1.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Awstats.org needs all CSS files to be minified and compressed as it can save up to 4.5 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (42%)

Requests Now

71

After Optimization

41

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AWStats. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

awstats.org accessibility score

56

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

awstats.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

awstats.org SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awstats.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Awstats.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of AWStats. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: