Access stats2.com.

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

stats2.com

279 ms

badge.gif

5 ms

56965.js

145 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 33% of them (1 request) were addressed to the original Stats2.com, 67% (2 requests) were made to Static.getclicky.com. The less responsive or slowest element that took the longest time to load (279 ms) belongs to the original domain Stats2.com.

Content Size

426 B

After Optimization

224 B

In fact, the total size of Stats2.com main page is 426 B. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 426 B which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 202 B

Original 426 B
After minification 425 B
After compression 224 B

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 202 B or 47% of the original size.

Requests Now

After Optimization

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stats 2. According to our analytics all requests are already optimized.

Accessibility Issues

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.

High

Document doesn't have a <title> element

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

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Search Engine Optimization Advices

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

High

Document doesn't have a <title> element

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stats2.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Stats2.com 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

stats2.com

Open Graph description is not detected on the main page of Stats 2. 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: