Tools & Wizards About Us
geographicus.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

geographicus.com

Geographicus Rare Antique Maps

Page Load Speed

2.9 sec in total

First Response

165 ms

Resources Loaded

2.4 sec

Page Rendered

361 ms

geographicus.com screenshot

About Website

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

Rare Antique Map Gallery specializing in original historic cartography from 1500 - 1920.

Visit geographicus.com

Key Findings

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

Performance Metrics

geographicus.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

geographicus.com

165 ms

geographicus.com

196 ms

www.geographicus.com

892 ms

clientside.mvc

197 ms

clientside.mvc

253 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 56% of them (35 requests) were addressed to the original Geographicus.com, 10% (6 requests) were made to Apis.google.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (892 ms) belongs to the original domain Geographicus.com.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geographicus.com main page is 1.3 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 689.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 51.6 kB

  • Original 63.3 kB
  • After minification 62.1 kB
  • After compression 11.7 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 51.6 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 10.3 kB

  • Original 689.6 kB
  • After minification 679.2 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. Geographicus images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 8.6 kB

  • Original 544.0 kB
  • After minification 544.0 kB
  • After compression 535.4 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

-19%

Potential reduce by 225 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 981 B

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. Geographicus.com needs all CSS files to be minified and compressed as it can save up to 225 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (55%)

Requests Now

55

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

geographicus.com

geographicus.com

165 ms

geographicus.com

geographicus.com

196 ms

www.geographicus.com

www.geographicus.com

892 ms

clientside.mvc

clientside.mvc

197 ms

clientside.mvc

clientside.mvc

253 ms

clientside.mvc

clientside.mvc

250 ms

css.php

css.php

250 ms

mailchimp.css

mailchimp.css

35 ms

css

css

52 ms

clientside.mvc

clientside.mvc

328 ms

js

js

75 ms

mailchimp.js

mailchimp.js

45 ms

smoothslides.theme.css

smoothslides.theme.css

221 ms

ddbd6142cb7811b9f7e1a36dd26cf9d698c0b633.js

ddbd6142cb7811b9f7e1a36dd26cf9d698c0b633.js

76 ms

17rgyagem9.jsonp

17rgyagem9.jsonp

38 ms

E-v1.js

E-v1.js

53 ms

vendor.min.js

vendor.min.js

209 ms

plugins.js

plugins.js

221 ms

scripts.js

scripts.js

467 ms

addthis_widget.js

addthis_widget.js

71 ms

js

js

100 ms

smoothslides.min.js

smoothslides.min.js

466 ms

fbevents.js

fbevents.js

15 ms

ce711f90e968aef4f681e58f9.js

ce711f90e968aef4f681e58f9.js

220 ms

f5a7f4a6e42b3c1b70d2dc22a.js

f5a7f4a6e42b3c1b70d2dc22a.js

222 ms

Geo_logo-RARE-WHITE_2.gif

Geo_logo-RARE-WHITE_2.gif

221 ms

LowerCanada-bouchette-1815-M.jpg

LowerCanada-bouchette-1815-M.jpg

309 ms

Europe-dejode-1593-M.jpg

Europe-dejode-1593-M.jpg

248 ms

MississippiSource-glazier-1884-M.jpg

MississippiSource-glazier-1884-M.jpg

220 ms

1115EngineerCombatGrp-ledonne-1945-2-M.jpg

1115EngineerCombatGrp-ledonne-1945-2-M.jpg

307 ms

Manila-gongora-1787-M.jpg

Manila-gongora-1787-M.jpg

306 ms

Wiscasset-stoner-1878-M.jpg

Wiscasset-stoner-1878-M.jpg

384 ms

IndieMoetVrij-keely-1944-M.jpg

IndieMoetVrij-keely-1944-M.jpg

383 ms

HolyLand-fries-1522-M.jpg

HolyLand-fries-1522-M.jpg

516 ms

EasternArmyGuide-magnus-1863-M.jpg

EasternArmyGuide-magnus-1863-M.jpg

362 ms

Shanghai-teikokuzaigo-1932-M.jpg

Shanghai-teikokuzaigo-1932-M.jpg

429 ms

Restoration.jpg

Restoration.jpg

593 ms

MailingLIst.jpg

MailingLIst.jpg

385 ms

WeBuyMaps_2.jpg

WeBuyMaps_2.jpg

591 ms

creditcardlogos.gif

creditcardlogos.gif

593 ms

RapidSSL_SEAL-90x50.gif

RapidSSL_SEAL-90x50.gif

421 ms

modules-v2.js

modules-v2.js

103 ms

font

font

102 ms

font

font

158 ms

ElegantIcons.woff

ElegantIcons.woff

448 ms

Suivant.woff

Suivant.woff

475 ms

platform.js

platform.js

137 ms

js

js

77 ms

jquery.slick.min.js

jquery.slick.min.js

291 ms

analytics.js

analytics.js

73 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

42 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

44 ms

follow

follow

38 ms

collect

collect

45 ms

postmessageRelay

postmessageRelay

52 ms

collect

collect

22 ms

developers.google.com

developers.google.com

354 ms

ga-audiences

ga-audiences

49 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

20 ms

rpc:shindig_random.js

rpc:shindig_random.js

10 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

img_slider_loader.gif

img_slider_loader.gif

29 ms

Accessibility Review

geographicus.com accessibility score

80

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

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

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

geographicus.com best practices score

58

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

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

geographicus.com 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 Geographicus.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 Geographicus.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

geographicus.com

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