Tools & Wizards About Us
worldstat.info screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

worldstat.info

Population of the Caribbean | Population of South America | Population of Asia | Population of Africa | Population of North and Central America | Popu...

Page Load Speed

5.2 sec in total

First Response

889 ms

Resources Loaded

4.1 sec

Page Rendered

136 ms

worldstat.info screenshot

About Website

Welcome to worldstat.info homepage info - get ready to check Worldstat best content for Russia right away, or after learning these important things about worldstat.info

Population of the Caribbean and South America, Asia, Africa, North and Central America, Europe and Oceania in 2011. Population growth rate, Density, median age of male and female population, life expe...

Visit worldstat.info

Key Findings

We analyzed Worldstat.info page load time and found that the first response time was 889 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

worldstat.info performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

worldstat.info

889 ms

en.worldstat.info

2352 ms

style.css

150 ms

swfobject.js

283 ms

show_ads.js

71 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Worldstat.info, 24% (6 requests) were made to Apis.google.com and 16% (4 requests) were made to En.worldstat.info. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source En.worldstat.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.0 kB (18%)

Content Size

556.4 kB

After Optimization

454.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldstat.info main page is 556.4 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. 35% of websites need less resources to load. Javascripts take 501.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 40.9 kB

  • Original 50.7 kB
  • After minification 50.2 kB
  • After compression 9.8 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 40.9 kB or 81% of the original size.

Image Optimization

-30%

Potential reduce by 875 B

  • Original 2.9 kB
  • After minification 2.0 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, Worldstat needs image optimization as it can save up to 875 B or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 59.7 kB

  • Original 501.3 kB
  • After minification 501.3 kB
  • After compression 441.6 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 59.7 kB or 12% of the original size.

CSS Optimization

-32%

Potential reduce by 513 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 1.1 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. Worldstat.info needs all CSS files to be minified and compressed as it can save up to 513 B or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (57%)

Requests Now

21

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worldstat.info

worldstat.info

889 ms

en.worldstat.info

en.worldstat.info

2352 ms

style.css

style.css

150 ms

swfobject.js

swfobject.js

283 ms

show_ads.js

show_ads.js

71 ms

widgets.js

widgets.js

45 ms

ga.js

ga.js

21 ms

logo2.png

logo2.png

194 ms

adsbygoogle.js

adsbygoogle.js

136 ms

plusone.js

plusone.js

41 ms

__utm.gif

__utm.gif

26 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

188 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

7 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

24 ms

fastbutton

fastbutton

33 ms

postmessageRelay

postmessageRelay

45 ms

544727282-postmessagerelay.js

544727282-postmessagerelay.js

61 ms

rpc:shindig_random.js

rpc:shindig_random.js

8 ms

developers.google.com

developers.google.com

402 ms

show_ads_impl.js

show_ads_impl.js

383 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

settings

settings

98 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

21 ms

embeds

embeds

34 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

31 ms

Accessibility Review

worldstat.info accessibility score

73

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

worldstat.info best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

worldstat.info SEO score

69

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

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 Worldstat.info 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 Worldstat.info 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

worldstat.info

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