Tools & Wizards About Us
geographic.org screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

geographic.org

Geographic.org home page - Geography, climate, countries, Maps, Flags, Population

Page Load Speed

1.3 sec in total

First Response

111 ms

Resources Loaded

1 sec

Page Rendered

219 ms

geographic.org screenshot

About Website

Visit geographic.org now to see the best up-to-date Geographic content for United States and also check out these interesting facts you probably never knew about geographic.org

Geographic.org home page - Geography, climate, countries, Maps, Flags, Population

Visit geographic.org

Key Findings

We analyzed Geographic.org page load time and found that the first response time was 111 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

geographic.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value24.6 s

0/100

10%

TBT (Total Blocking Time)

Value40,990 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value55.3 s

0/100

10%

Network Requests Diagram

geographic.org

111 ms

adsbygoogle.js

15 ms

darkbluebgr.gif

59 ms

line2.gif

59 ms

show_ads.js

11 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 31% of them (21 requests) were addressed to the original Geographic.org, 10% (7 requests) were made to Pagead2.googlesyndication.com and 10% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (905 ms) relates to the external source Bestweb.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.8 kB (10%)

Content Size

958.5 kB

After Optimization

862.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Geographic.org main page is 958.5 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. Images take 821.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.5 kB

  • Original 42.3 kB
  • After minification 42.0 kB
  • After compression 8.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 33.5 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 51.1 kB

  • Original 821.0 kB
  • After minification 769.9 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. Geographic images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 11.2 kB

  • Original 95.2 kB
  • After minification 95.0 kB
  • After compression 83.9 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 11.2 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (45%)

Requests Now

64

After Optimization

35

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

geographic.org

geographic.org

111 ms

adsbygoogle.js

adsbygoogle.js

15 ms

darkbluebgr.gif

darkbluebgr.gif

59 ms

line2.gif

line2.gif

59 ms

show_ads.js

show_ads.js

11 ms

white

white

138 ms

line2.gif

line2.gif

55 ms

geographic_banner_2.jpg

geographic_banner_2.jpg

56 ms

all.js

all.js

137 ms

widgets.js

widgets.js

27 ms

in.js

in.js

28 ms

deep_water_gulf_of_mexico_drilling.png

deep_water_gulf_of_mexico_drilling.png

249 ms

earthquakes.png

earthquakes.png

187 ms

geographic_names.jpg

geographic_names.jpg

335 ms

world_photos.jpg

world_photos.jpg

200 ms

streetview.png

streetview.png

370 ms

volcano_photos.jpg

volcano_photos.jpg

196 ms

quickmaps.jpg

quickmaps.jpg

243 ms

ca-pub-7437757543052749.js

ca-pub-7437757543052749.js

51 ms

zrt_lookup.html

zrt_lookup.html

49 ms

show_ads_impl.js

show_ads_impl.js

56 ms

248 ms

brand

brand

44 ms

Count.cgi

Count.cgi

905 ms

flags.jpg

flags.jpg

245 ms

pipeline_maps.jpg

pipeline_maps.jpg

255 ms

airport_codes.jpg

airport_codes.jpg

245 ms

geographic_feedback.jpg

geographic_feedback.jpg

258 ms

nautical_charts.png

nautical_charts.png

407 ms

pixel.gif

pixel.gif

257 ms

brand

brand

160 ms

ads

ads

256 ms

error.html

error.html

191 ms

secureAnonymousFramework

secureAnonymousFramework

96 ms

plusone.js

plusone.js

225 ms

osd.js

osd.js

58 ms

241 ms

pla

pla

59 ms

xd_arbiter.php

xd_arbiter.php

149 ms

xd_arbiter.php

xd_arbiter.php

212 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

159 ms

ping

ping

260 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

102 ms

share

share

99 ms

sprite_connect_v14.png

sprite_connect_v14.png

118 ms

error.html

error.html

69 ms

like.php

like.php

191 ms

tweet_button.6a78875565a912489e9aef879c881358.en.html

tweet_button.6a78875565a912489e9aef879c881358.en.html

43 ms

13136601043150711013

13136601043150711013

60 ms

abg.js

abg.js

64 ms

m_js_controller.js

m_js_controller.js

90 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

106 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

68 ms

fastbutton

fastbutton

133 ms

s

s

36 ms

x_button_blue2.png

x_button_blue2.png

75 ms

postmessageRelay

postmessageRelay

79 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

188 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

205 ms

jot

jot

140 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

16 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

46 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

36 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

118 ms

api.js

api.js

53 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

73 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

67 ms

Accessibility Review

geographic.org accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

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

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

geographic.org best practices score

58

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

geographic.org SEO score

93

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

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geographic.org 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 Geographic.org 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

geographic.org

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