Tools & Wizards About Us
flagcounter.me screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

flagcounter.me

Flag Counter - Free Visitors Counter for your Webpage

Page Load Speed

1.8 sec in total

First Response

284 ms

Resources Loaded

1.3 sec

Page Rendered

207 ms

flagcounter.me screenshot

About Website

Visit flagcounter.me now to see the best up-to-date Flag Counter content for Japan and also check out these interesting facts you probably never knew about flagcounter.me

Flag Counter is a free visitors counter for your webpage. Our service will allow you to track website traffic and visitors details. Its really simple and reliable counter!

Visit flagcounter.me

Key Findings

We analyzed Flagcounter.me page load time and found that the first response time was 284 ms and then it took 1.5 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

flagcounter.me performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

flagcounter.me

284 ms

flagcounter.me

485 ms

js

74 ms

css

55 ms

css

91 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 45% of them (13 requests) were addressed to the original Flagcounter.me, 34% (10 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (485 ms) belongs to the original domain Flagcounter.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.4 kB (53%)

Content Size

342.9 kB

After Optimization

162.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flagcounter.me main page is 342.9 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. 25% of websites need less resources to load. Javascripts take 155.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 18.8 kB

  • Original 22.2 kB
  • After minification 15.4 kB
  • After compression 3.5 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 6.9 kB, which is 31% 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 18.8 kB or 84% of the original size.

Image Optimization

-34%

Potential reduce by 11.5 kB

  • Original 33.7 kB
  • After minification 22.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. Obviously, Flag Counter needs image optimization as it can save up to 11.5 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 41.1 kB

  • Original 155.1 kB
  • After minification 153.8 kB
  • After compression 114.0 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 41.1 kB or 27% of the original size.

CSS Optimization

-83%

Potential reduce by 109.1 kB

  • Original 131.8 kB
  • After minification 128.9 kB
  • After compression 22.7 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. Flagcounter.me needs all CSS files to be minified and compressed as it can save up to 109.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (59%)

Requests Now

17

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flagcounter.me

flagcounter.me

284 ms

flagcounter.me

flagcounter.me

485 ms

js

js

74 ms

css

css

55 ms

css

css

91 ms

font-awesome.min.css

font-awesome.min.css

51 ms

bootstrap.min.css

bootstrap.min.css

279 ms

bootstrap-colorpicker.min.css

bootstrap-colorpicker.min.css

254 ms

theme.css

theme.css

344 ms

jquery.min.js

jquery.min.js

43 ms

adsbygoogle.js

adsbygoogle.js

66 ms

bootstrap.min.js

bootstrap.min.js

439 ms

bootstrap-colorpicker.min.js

bootstrap-colorpicker.min.js

439 ms

theme.js

theme.js

285 ms

logo.png

logo.png

97 ms

bg.png

bg.png

96 ms

premium-bg.png

premium-bg.png

95 ms

load.gif

load.gif

106 ms

178 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

28 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff

34 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff

49 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff

62 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff

63 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff

62 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff

62 ms

Accessibility Review

flagcounter.me accessibility score

81

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.

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

flagcounter.me best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

flagcounter.me SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flagcounter.me can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Flagcounter.me 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

flagcounter.me

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