Tools & Wizards About Us
natgeomaps.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

natgeomaps.com

National Geographic Maps

Page Load Speed

2.9 sec in total

First Response

56 ms

Resources Loaded

2.5 sec

Page Rendered

372 ms

natgeomaps.com screenshot

About Website

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

National Geographic Maps makes the world’s best wall maps, recreation maps, travel maps, atlases and globes for people to explore and understand the world.

Visit natgeomaps.com

Key Findings

We analyzed Natgeomaps.com page load time and found that the first response time was 56 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

natgeomaps.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value1.065

2/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

natgeomaps.com

56 ms

www.natgeomaps.com

335 ms

d6e1ec5be55b20eb132e8aa47fe1146e.css

31 ms

styles-l.css

61 ms

custom.css

67 ms

Our browser made a total of 196 requests to load all elements on the main page. We found that 82% of them (161 requests) were addressed to the original Natgeomaps.com, 14% (27 requests) were made to Images.natgeomaps.com and 2% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Natgeomaps.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.3 kB (5%)

Content Size

3.9 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Natgeomaps.com main page is 3.9 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. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 176.3 kB

  • Original 199.3 kB
  • After minification 196.3 kB
  • After compression 23.0 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 176.3 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 7.7 kB

  • Original 3.2 MB
  • After minification 3.2 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. Natgeo Maps images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.1 kB

  • Original 344.2 kB
  • After minification 344.0 kB
  • After compression 339.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 1.2 kB

  • Original 141.4 kB
  • After minification 141.4 kB
  • After compression 140.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. Natgeomaps.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 120 (63%)

Requests Now

190

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

natgeomaps.com

natgeomaps.com

56 ms

www.natgeomaps.com

www.natgeomaps.com

335 ms

d6e1ec5be55b20eb132e8aa47fe1146e.css

d6e1ec5be55b20eb132e8aa47fe1146e.css

31 ms

styles-l.css

styles-l.css

61 ms

custom.css

custom.css

67 ms

css

css

74 ms

css

css

92 ms

css

css

97 ms

css

css

97 ms

bootstrap.optimized.min.css

bootstrap.optimized.min.css

248 ms

animate.optimized.css

animate.optimized.css

69 ms

type14.css

type14.css

59 ms

custom.css

custom.css

82 ms

design_default.css

design_default.css

77 ms

settings_default.css

settings_default.css

78 ms

Family_RoadAtlas.png

Family_RoadAtlas.png

106 ms

39df534082eabcfd5ed0c065a4ddc8bd.js

39df534082eabcfd5ed0c065a4ddc8bd.js

80 ms

otSDKStub.js

otSDKStub.js

109 ms

DYH0000125_1_SM.jpg

DYH0000125_1_SM.jpg

210 ms

Icon_NewDealer.jpg

Icon_NewDealer.jpg

181 ms

Collage_TrailMaps_2100px.jpg

Collage_TrailMaps_2100px.jpg

179 ms

Collage_TravelMaps_2100px.jpg

Collage_TravelMaps_2100px.jpg

167 ms

Collage_WallMaps_2100px.jpg

Collage_WallMaps_2100px.jpg

155 ms

Collage_BooksAtlases_2100px.jpg

Collage_BooksAtlases_2100px.jpg

223 ms

TI00000201_0_SM.jpg

TI00000201_0_SM.jpg

202 ms

TI00000202_0_SM.jpg

TI00000202_0_SM.jpg

199 ms

TI00000229_0_SM.jpg

TI00000229_0_SM.jpg

234 ms

TI00000200_0_SM.jpg

TI00000200_0_SM.jpg

218 ms

TI00000214_0_SM.jpg

TI00000214_0_SM.jpg

232 ms

TI00000206_0_SM.jpg

TI00000206_0_SM.jpg

231 ms

RE01020374_1_SM.jpg

RE01020374_1_SM.jpg

223 ms

TI00000261_0_SM.jpg

TI00000261_0_SM.jpg

329 ms

TI00000216_0_SM.jpg

TI00000216_0_SM.jpg

330 ms

TI00000215_0_SM.jpg

TI00000215_0_SM.jpg

329 ms

RE00620115_1_SM.jpg

RE00620115_1_SM.jpg

328 ms

DM01021308_0_SM.jpg

DM01021308_0_SM.jpg

332 ms

DC01020377_0_SM.jpg

DC01020377_0_SM.jpg

330 ms

GM01020352_0_SM.jpg

GM01020352_0_SM.jpg

330 ms

TI01021293B_0_SM.jpg

TI01021293B_0_SM.jpg

334 ms

TI01021294B_0_SM.jpg

TI01021294B_0_SM.jpg

331 ms

TI01021295B_0_SM.jpg

TI01021295B_0_SM.jpg

332 ms

TI01021312B_0_SM.jpg

TI01021312B_0_SM.jpg

332 ms

TI00004003_0_SM.jpg

TI00004003_0_SM.jpg

333 ms

TI00004004_0_SM.jpg

TI00004004_0_SM.jpg

333 ms

NG_Maps_logo_trans-no-padding.png

NG_Maps_logo_trans-no-padding.png

74 ms

trails-illustrated-maps.png

trails-illustrated-maps.png

80 ms

topographic-map-guides.png

topographic-map-guides.png

80 ms

Family_DayHikes.png

Family_DayHikes.png

86 ms

taril-maps.png

taril-maps.png

95 ms

local-trails.png

local-trails.png

96 ms

fishing-and-river-map-guides.png

fishing-and-river-map-guides.png

95 ms

adventure-maps.png

adventure-maps.png

90 ms

city-destination-maps.png

city-destination-maps.png

104 ms

travel-maps.png

travel-maps.png

103 ms

benchmark-maps.png

benchmark-maps.png

114 ms

destination-maps.png

destination-maps.png

114 ms

guide-maps.png

guide-maps.png

110 ms

reference-maps.png

reference-maps.png

118 ms

kids-maps.png

kids-maps.png

128 ms

map-archive.png

map-archive.png

468 ms

wall-maps.png

wall-maps.png

134 ms

book1.jpg

book1.jpg

128 ms

book2.png

book2.png

131 ms

book3.jpg

book3.jpg

151 ms

book4.jpg

book4.jpg

144 ms

book5.jpg

book5.jpg

142 ms

globes.png

globes.png

148 ms

kids.png

kids.png

160 ms

pdf-quads.png

pdf-quads.png

170 ms

recreation-atlases.png

recreation-atlases.png

167 ms

nps_logo_30x30.png

nps_logo_30x30.png

141 ms

globe_30x30.png

globe_30x30.png

133 ms

NatGeo-rectangle-icon-bw.png

NatGeo-rectangle-icon-bw.png

135 ms

IIMG_3873-2000_1.jpeg

IIMG_3873-2000_1.jpeg

150 ms

adventure.png

adventure.png

135 ms

mapping.png

mapping.png

136 ms

world_classic_banner_crop.jpg

world_classic_banner_crop.jpg

135 ms

societyseal.png

societyseal.png

130 ms

ng-logo.png

ng-logo.png

142 ms

bullet.png

bullet.png

1102 ms

ba1d2bb4-84f3-43fb-b52b-f441f2b7ea27-test.json

ba1d2bb4-84f3-43fb-b52b-f441f2b7ea27-test.json

146 ms

GeographRegular.woff

GeographRegular.woff

20 ms

porto-icons.woff

porto-icons.woff

466 ms

fa-brands-400.woff

fa-brands-400.woff

459 ms

main.js

main.js

17 ms

jquery.js

jquery.js

40 ms

common.js

common.js

40 ms

dataPost.js

dataPost.js

100 ms

bootstrap.js

bootstrap.js

99 ms

app.js

app.js

98 ms

form-key-provider.js

form-key-provider.js

100 ms

mage-translation-dictionary.js

mage-translation-dictionary.js

99 ms

theme.js

theme.js

97 ms

sw_megamenu.js

sw_megamenu.js

98 ms

owl.carousel.min.js

owl.carousel.min.js

107 ms

weltpixel_quickview.js

weltpixel_quickview.js

99 ms

domReady.js

domReady.js

22 ms

jquery-mixin.js

jquery-mixin.js

21 ms

main.js

main.js

30 ms

bootstrap.js

bootstrap.js

32 ms

template.js

template.js

353 ms

confirm.js

confirm.js

46 ms

widget.js

widget.js

51 ms

text.js

text.js

77 ms

types.js

types.js

75 ms

layout.js

layout.js

91 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

84 ms

smart-keyboard-handler.js

smart-keyboard-handler.js

101 ms

mage.js

mage.js

108 ms

jquery.lazyload.js

jquery.lazyload.js

116 ms

location

location

35 ms

wrapper.js

wrapper.js

117 ms

underscore.js

underscore.js

112 ms

knockout.js

knockout.js

317 ms

knockout-es5.js

knockout-es5.js

318 ms

scripts.js

scripts.js

316 ms

engine.js

engine.js

313 ms

bootstrap.js

bootstrap.js

314 ms

observable_array.js

observable_array.js

313 ms

bound-nodes.js

bound-nodes.js

314 ms

otBannerSdk.js

otBannerSdk.js

19 ms

translate.js

translate.js

304 ms

modal.js

modal.js

304 ms

version.js

version.js

370 ms

js-translation.json

js-translation.json

347 ms

main.js

main.js

273 ms

registry.js

registry.js

256 ms

console-logger.js

console-logger.js

254 ms

knockout-repeat.js

knockout-repeat.js

20 ms

knockout-fast-foreach.js

knockout-fast-foreach.js

20 ms

events.js

events.js

30 ms

modal-popup.html

modal-popup.html

227 ms

modal-slide.html

modal-slide.html

93 ms

modal-custom.html

modal-custom.html

230 ms

key-codes.js

key-codes.js

32 ms

core.js

core.js

272 ms

z-index.js

z-index.js

45 ms

local.js

local.js

62 ms

observable_source.js

observable_source.js

77 ms

renderer.js

renderer.js

98 ms

resizable.js

resizable.js

100 ms

i18n.js

i18n.js

158 ms

scope.js

scope.js

116 ms

range.js

range.js

130 ms

mage-init.js

mage-init.js

147 ms

keyboard.js

keyboard.js

159 ms

optgroup.js

optgroup.js

175 ms

after-render.js

after-render.js

174 ms

autoselect.js

autoselect.js

192 ms

datepicker.js

datepicker.js

192 ms

outer_click.js

outer_click.js

214 ms

fadeVisible.js

fadeVisible.js

206 ms

collapsible.js

collapsible.js

224 ms

staticChecked.js

staticChecked.js

227 ms

simple-checked.js

simple-checked.js

441 ms

bind-html.js

bind-html.js

240 ms

tooltip.js

tooltip.js

245 ms

color-picker.js

color-picker.js

241 ms

arrays.js

arrays.js

257 ms

compare.js

compare.js

262 ms

misc.js

misc.js

261 ms

objects.js

objects.js

286 ms

strings.js

strings.js

483 ms

template.js

template.js

275 ms

logger.js

logger.js

276 ms

entry-factory.js

entry-factory.js

282 ms

console-output-handler.js

console-output-handler.js

280 ms

formatter.js

formatter.js

271 ms

message-pool.js

message-pool.js

260 ms

levels-pool.js

levels-pool.js

253 ms

logger-utils.js

logger-utils.js

249 ms

class.js

class.js

243 ms

async.js

async.js

245 ms

loader.js

loader.js

241 ms

spectrum.js

spectrum.js

112 ms

tinycolor.js

tinycolor.js

116 ms

tooltip.html

tooltip.html

191 ms

data.js

data.js

108 ms

disable-selection.js

disable-selection.js

117 ms

focusable.js

focusable.js

129 ms

form.js

form.js

127 ms

ie.js

ie.js

138 ms

keycode.js

keycode.js

148 ms

labels.js

labels.js

148 ms

jquery-patch.js

jquery-patch.js

154 ms

plugin.js

plugin.js

179 ms

safe-active-element.js

safe-active-element.js

161 ms

safe-blur.js

safe-blur.js

174 ms

scroll-parent.js

scroll-parent.js

174 ms

tabbable.js

tabbable.js

182 ms

unique-id.js

unique-id.js

415 ms

entry.js

entry.js

177 ms

moment.js

moment.js

157 ms

dom-observer.js

dom-observer.js

130 ms

bindings.js

bindings.js

126 ms

print.css

print.css

13 ms

Accessibility Review

natgeomaps.com accessibility score

70

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

natgeomaps.com SEO score

81

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

High

Tap targets are not sized appropriately

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

natgeomaps.com

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