Tools & Wizards About Us
statcounter.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

statcounter.com

Web Analytics Made Easy - Statcounter

Page Load Speed

1.4 sec in total

First Response

23 ms

Resources Loaded

875 ms

Page Rendered

522 ms

statcounter.com screenshot

About Website

Visit statcounter.com now to see the best up-to-date Statcounter content for India and also check out these interesting facts you probably never knew about statcounter.com

StatCounter is a simple but powerful real-time web analytics service that helps you track, analyse and understand your visitors so you can make good decisions to become more successful online.

Visit statcounter.com

Key Findings

We analyzed Statcounter.com page load time and found that the first response time was 23 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

statcounter.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

statcounter.com

23 ms

statcounter.com

265 ms

js

132 ms

statcounter-eb1eefc683.css

32 ms

modal.app.css

236 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 88% of them (53 requests) were addressed to the original Statcounter.com, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (265 ms) belongs to the original domain Statcounter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.4 kB (21%)

Content Size

307.8 kB

After Optimization

242.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Statcounter.com main page is 307.8 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. 55% of websites need less resources to load. Javascripts take 208.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 17.5 kB

  • Original 22.7 kB
  • After minification 19.9 kB
  • After compression 5.2 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. This page needs HTML code to be minified as it can gain 2.8 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.5 kB or 77% of the original size.

Image Optimization

-27%

Potential reduce by 7.5 kB

  • Original 27.9 kB
  • After minification 20.4 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. Obviously, Statcounter needs image optimization as it can save up to 7.5 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 29.8 kB

  • Original 208.6 kB
  • After minification 208.6 kB
  • After compression 178.8 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 29.8 kB or 14% of the original size.

CSS Optimization

-22%

Potential reduce by 10.6 kB

  • Original 48.6 kB
  • After minification 48.6 kB
  • After compression 38.0 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. Statcounter.com needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (41%)

Requests Now

54

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

statcounter.com

statcounter.com

23 ms

statcounter.com

statcounter.com

265 ms

js

js

132 ms

statcounter-eb1eefc683.css

statcounter-eb1eefc683.css

32 ms

modal.app.css

modal.app.css

236 ms

sticky-nav.css

sticky-nav.css

71 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

74 ms

jquery-ui.min.js

jquery-ui.min.js

78 ms

statcounter-758f2ac613.js

statcounter-758f2ac613.js

60 ms

sc-perf-15d6a5f857.js

sc-perf-15d6a5f857.js

74 ms

sticky-nav-inline.jquery.js

sticky-nav-inline.jquery.js

75 ms

scroll-with-stickynav-inline.jquery.js

scroll-with-stickynav-inline.jquery.js

75 ms

rating_capterra.png

rating_capterra.png

73 ms

rating_trustradius.png

rating_trustradius.png

77 ms

rating_g2crowd.png

rating_g2crowd.png

90 ms

home_hero.svg

home_hero.svg

94 ms

home_sessionreplay.svg

home_sessionreplay.svg

89 ms

icon_home_sessionreplay.svg

icon_home_sessionreplay.svg

106 ms

home_livevisitorfeed.svg

home_livevisitorfeed.svg

108 ms

icon_home_livevisitorfeed.svg

icon_home_livevisitorfeed.svg

127 ms

home_analytics.svg

home_analytics.svg

117 ms

icon_home_analytics.svg

icon_home_analytics.svg

115 ms

check-exposure.svg

check-exposure.svg

124 ms

howitworks_signup.svg

howitworks_signup.svg

163 ms

howitworks_insertcode.svg

howitworks_insertcode.svg

165 ms

howitworks_getinsights.svg

howitworks_getinsights.svg

167 ms

base-triangle-no-border.png

base-triangle-no-border.png

170 ms

logo_hoowla.png

logo_hoowla.png

171 ms

logo_freerangestock.png

logo_freerangestock.png

170 ms

logo_happyhealthy.png

logo_happyhealthy.png

171 ms

logo_tumblr.svg

logo_tumblr.svg

174 ms

logo_blogger.svg

logo_blogger.svg

172 ms

logo_wordpress.svg

logo_wordpress.svg

174 ms

logo_squarespace.svg

logo_squarespace.svg

178 ms

logo_smugmug.svg

logo_smugmug.svg

180 ms

logo_google.svg

logo_google.svg

176 ms

logo_weebly.svg

logo_weebly.svg

180 ms

logo_wix.svg

logo_wix.svg

181 ms

logo_joomla.svg

logo_joomla.svg

184 ms

logo_godaddy.svg

logo_godaddy.svg

187 ms

logo_drupal.svg

logo_drupal.svg

184 ms

logo_shopify.svg

logo_shopify.svg

162 ms

js

js

130 ms

analytics.js

analytics.js

125 ms

icon_lock-06430d6b46.svg

icon_lock-06430d6b46.svg

109 ms

logo-statcounter-arc-blue-9e7352a20d.svg

logo-statcounter-arc-blue-9e7352a20d.svg

110 ms

navicon_blue-4acc37e738.svg

navicon_blue-4acc37e738.svg

108 ms

icon_ios_app-c80d17bd08.svg

icon_ios_app-c80d17bd08.svg

107 ms

icon_android_app-7832311597.svg

icon_android_app-7832311597.svg

105 ms

icon_windows_app-dbceb3f512.svg

icon_windows_app-dbceb3f512.svg

105 ms

icon_facebook-93dcea8762.svg

icon_facebook-93dcea8762.svg

112 ms

icon_twitter-b22ab5bb2d.svg

icon_twitter-b22ab5bb2d.svg

111 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

152 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

150 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

210 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

111 ms

counter_test.js

counter_test.js

94 ms

collect

collect

33 ms

t.php

t.php

82 ms

recorder.js

recorder.js

38 ms

Accessibility Review

statcounter.com accessibility score

82

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

statcounter.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

statcounter.com SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Statcounter.com 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 Statcounter.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

statcounter.com

Open Graph data is detected on the main page of Statcounter. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: