Tools & Wizards About Us
historygeo.com screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

historygeo.com

Where Historical Maps and Family History Meet! (HistoryGeo.com)

Page Load Speed

832 ms in total

First Response

236 ms

Resources Loaded

440 ms

Page Rendered

156 ms

historygeo.com screenshot

About Website

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

HistoryGeo is a family history website providing online genealogy software tools allowing you to search original land records and old maps for where your ancestors lived.

Visit historygeo.com

Key Findings

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

Performance Metrics

historygeo.com performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

historygeo.com

236 ms

hg_site_main.css

7 ms

homepage.css

9 ms

jquery_ui_hg.css

11 ms

jquery.fancybox.css

8 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 89% of them (17 requests) were addressed to the original Historygeo.com, 11% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (236 ms) belongs to the original domain Historygeo.com.

Page Optimization Overview & Recommendations

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

Content Size

275.8 kB

After Optimization

262.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Historygeo.com main page is 275.8 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. Images take 130.1 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 7.0 kB

  • Original 10.3 kB
  • After minification 9.2 kB
  • After compression 3.3 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. This page needs HTML code to be minified as it can gain 1.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 7.0 kB or 68% of the original size.

Image Optimization

-3%

Potential reduce by 4.5 kB

  • Original 130.1 kB
  • After minification 125.6 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. History Geo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 137 B

  • Original 122.6 kB
  • After minification 122.6 kB
  • After compression 122.5 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

-15%

Potential reduce by 2.0 kB

  • Original 12.7 kB
  • After minification 12.7 kB
  • After compression 10.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. Historygeo.com needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (39%)

Requests Now

18

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

historygeo.com

historygeo.com

236 ms

hg_site_main.css

hg_site_main.css

7 ms

homepage.css

homepage.css

9 ms

jquery_ui_hg.css

jquery_ui_hg.css

11 ms

jquery.fancybox.css

jquery.fancybox.css

8 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

20 ms

jquery-ui-1.9.2.min.js

jquery-ui-1.9.2.min.js

36 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

13 ms

homepage.js

homepage.js

12 ms

ga.js

ga.js

63 ms

hg_logo.png

hg_logo.png

5 ms

featured_container_bg.jpg

featured_container_bg.jpg

32 ms

featured_container_searchbox_bg.jpg

featured_container_searchbox_bg.jpg

35 ms

btnFrontPageStartSearchBtn.png

btnFrontPageStartSearchBtn.png

32 ms

Video_Thumbnail_FLO.png

Video_Thumbnail_FLO.png

32 ms

Video_Thumbnail_ZAM.png

Video_Thumbnail_ZAM.png

32 ms

facebookLink_01.png

facebookLink_01.png

33 ms

twitterLink_01.png

twitterLink_01.png

33 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

historygeo.com accessibility score

91

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

Links do not have a discernible name

Best Practices

historygeo.com best practices score

75

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

SEO Factors

historygeo.com SEO score

98

Search Engine Optimization Advices

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

historygeo.com

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