Tools & Wizards About Us
worldatlas.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

worldatlas.com

World Map / World Atlas / Atlas of the World Including Geography Facts and Flags - WorldAtlas.com

Page Load Speed

831 ms in total

First Response

60 ms

Resources Loaded

602 ms

Page Rendered

169 ms

worldatlas.com screenshot

About Website

Welcome to worldatlas.com homepage info - get ready to check World Atlas best content for United States right away, or after learning these important things about worldatlas.com

Well-researched and entertaining content on geography (including world maps), science, current events, and more.

Visit worldatlas.com

Key Findings

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

Performance Metrics

worldatlas.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value19.7 s

0/100

10%

TBT (Total Blocking Time)

Value37,090 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value66.8 s

0/100

10%

Network Requests Diagram

worldatlas.com

60 ms

www.worldatlas.com

81 ms

index.css

97 ms

adsbygoogle.js

4 ms

tags.js

346 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 44% of them (17 requests) were addressed to the original Worldatlas.com, 10% (4 requests) were made to Pagead2.googlesyndication.com and 10% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (346 ms) relates to the external source Tags.expo9.exponential.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 365.0 kB (22%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldatlas.com main page is 1.6 MB. 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. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-9%

Potential reduce by 10 B

  • Original 108 B
  • After minification 108 B
  • After compression 98 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. This web page is already compressed.

Image Optimization

-3%

Potential reduce by 35.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. World Atlas images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 242.7 kB

  • Original 412.5 kB
  • After minification 382.6 kB
  • After compression 169.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 242.7 kB or 59% of the original size.

CSS Optimization

-82%

Potential reduce by 87.0 kB

  • Original 106.7 kB
  • After minification 96.0 kB
  • After compression 19.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. Worldatlas.com needs all CSS files to be minified and compressed as it can save up to 87.0 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

34

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worldatlas.com

worldatlas.com

60 ms

www.worldatlas.com

www.worldatlas.com

81 ms

index.css

index.css

97 ms

adsbygoogle.js

adsbygoogle.js

4 ms

tags.js

tags.js

346 ms

jquery.min.js

jquery.min.js

31 ms

jquery.rwdImageMaps.min.js

jquery.rwdImageMaps.min.js

30 ms

gpt.js

gpt.js

59 ms

fbevents.js

fbevents.js

176 ms

analytics.js

analytics.js

56 ms

sdk.js

sdk.js

346 ms

cse.js

cse.js

52 ms

worldatlas-logo.svg

worldatlas-logo.svg

45 ms

root.png

root.png

143 ms

deadliest-plane-crashes.jpg

deadliest-plane-crashes.jpg

162 ms

longest-beaches.jpg

longest-beaches.jpg

143 ms

iceland.jpg

iceland.jpg

143 ms

unfree.jpg

unfree.jpg

69 ms

cybercrime.jpg

cybercrime.jpg

69 ms

greenbicycle.jpg

greenbicycle.jpg

153 ms

education.jpg

education.jpg

159 ms

thinkstockphotos-455248837.jpg

thinkstockphotos-455248837.jpg

157 ms

thinkstockphotos-484964080.jpg

thinkstockphotos-484964080.jpg

162 ms

thinkstockphotos-91460588.jpg

thinkstockphotos-91460588.jpg

158 ms

ca-pub-4694578337353631.js

ca-pub-4694578337353631.js

63 ms

zrt_lookup.html

zrt_lookup.html

64 ms

show_ads_impl.js

show_ads_impl.js

83 ms

icomoon.ttf

icomoon.ttf

116 ms

pubads_impl_81.js

pubads_impl_81.js

27 ms

collect

collect

85 ms

jsapi

jsapi

86 ms

container.html

container.html

65 ms

collect

collect

107 ms

osd.js

osd.js

17 ms

default+en.css

default+en.css

52 ms

default.css

default.css

56 ms

default+en.I.js

default+en.I.js

54 ms

136 ms

default.css

default.css

70 ms

Accessibility Review

worldatlas.com accessibility score

98

Accessibility Issues

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

Best Practices

worldatlas.com 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

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

worldatlas.com SEO score

84

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Worldatlas.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 Worldatlas.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

worldatlas.com

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