Tools & Wizards About Us
hearthstonelegacy.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

hearthstonelegacy.com

Genealogy, County History, Maps, Missouri, Arkansas, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, North Carolina, Ohio, Tennessee, Texas incl...

Page Load Speed

1.4 sec in total

First Response

169 ms

Resources Loaded

661 ms

Page Rendered

520 ms

hearthstonelegacy.com screenshot

About Website

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

Hearthstone Legacy Publications publishes County History, Genealogy and Maps with emphasis on Missouri, Arkansas, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, North Carolina, Ohio, Tennessee,...

Visit hearthstonelegacy.com

Key Findings

We analyzed Hearthstonelegacy.com page load time and found that the first response time was 169 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

hearthstonelegacy.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value4,870 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.15

76/100

15%

TTI (Time to Interactive)

Value10.7 s

23/100

10%

Network Requests Diagram

hearthstonelegacy.com

169 ms

adsbygoogle.js

141 ms

Hearthstone-Legacy-Logo.jpg

133 ms

home_cmp_Radial100_hbtn_p.gif

49 ms

search.htm_cmp_Radial100_hbtn.gif

58 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 90% of them (36 requests) were addressed to the original Hearthstonelegacy.com, 5% (2 requests) were made to Pagead2.googlesyndication.com and 5% (2 requests) were made to Count.carrierzone.com. The less responsive or slowest element that took the longest time to load (298 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.8 kB (23%)

Content Size

371.3 kB

After Optimization

287.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hearthstonelegacy.com main page is 371.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 276.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 53.0 kB

  • Original 67.1 kB
  • After minification 66.2 kB
  • After compression 14.1 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 53.0 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 151 B

  • Original 27.3 kB
  • After minification 27.1 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. Hearthstone Legacy images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 30.7 kB

  • Original 276.9 kB
  • After minification 264.7 kB
  • After compression 246.3 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 30.7 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (87%)

Requests Now

39

After Optimization

5

  • Images
  • JavaScript

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

Network Requests Diagram

hearthstonelegacy.com

hearthstonelegacy.com

169 ms

adsbygoogle.js

adsbygoogle.js

141 ms

Hearthstone-Legacy-Logo.jpg

Hearthstone-Legacy-Logo.jpg

133 ms

home_cmp_Radial100_hbtn_p.gif

home_cmp_Radial100_hbtn_p.gif

49 ms

search.htm_cmp_Radial100_hbtn.gif

search.htm_cmp_Radial100_hbtn.gif

58 ms

multi-county_dvds.htm_cmp_radial100_hbtn.gif

multi-county_dvds.htm_cmp_radial100_hbtn.gif

56 ms

missouri_products.htm_cmp_Radial100_hbtn.gif

missouri_products.htm_cmp_Radial100_hbtn.gif

57 ms

southeast_missouri_region.htm_cmp_Radial100_hbtn.gif

southeast_missouri_region.htm_cmp_Radial100_hbtn.gif

57 ms

ozark_region1.htm_cmp_Radial100_hbtn.gif

ozark_region1.htm_cmp_Radial100_hbtn.gif

78 ms

arkansas_products.htm_cmp_Radial100_hbtn.gif

arkansas_products.htm_cmp_Radial100_hbtn.gif

85 ms

illinois-counties.htm_cmp_Radial100_hbtn.gif

illinois-counties.htm_cmp_Radial100_hbtn.gif

85 ms

indiana-counties-history-genealogy.htm_cmp_radial100_hbtn.gif

indiana-counties-history-genealogy.htm_cmp_radial100_hbtn.gif

86 ms

iowa-county-history-genealogy-maps.htm_cmp_radial100_hbtn.gif

iowa-county-history-genealogy-maps.htm_cmp_radial100_hbtn.gif

86 ms

kansas_counties.htm_cmp_Radial100_hbtn.gif

kansas_counties.htm_cmp_Radial100_hbtn.gif

105 ms

kentucky-history-genealogy-counties-county.htm_cmp_radial100_hbtn.gif

kentucky-history-genealogy-counties-county.htm_cmp_radial100_hbtn.gif

200 ms

louisiana_parishes.htm_cmp_Radial100_hbtn.gif

louisiana_parishes.htm_cmp_Radial100_hbtn.gif

200 ms

massachusetts-vital-records.htm_cmp_radial100_hbtn.gif

massachusetts-vital-records.htm_cmp_radial100_hbtn.gif

201 ms

north_carolina_counties.htm_cmp_radial100_hbtn.gif

north_carolina_counties.htm_cmp_radial100_hbtn.gif

200 ms

ohio-counties.htm_cmp_radial100_hbtn.gif

ohio-counties.htm_cmp_radial100_hbtn.gif

201 ms

pennsylvania-county-history-genealogy.htm_cmp_radial100_hbtn.gif

pennsylvania-county-history-genealogy.htm_cmp_radial100_hbtn.gif

206 ms

tennessee_counties.htm_cmp_Radial100_hbtn.gif

tennessee_counties.htm_cmp_Radial100_hbtn.gif

206 ms

texas_counties.htm_cmp_Radial100_hbtn.gif

texas_counties.htm_cmp_Radial100_hbtn.gif

206 ms

plat-map-books.htm_cmp_radial100_hbtn.gif

plat-map-books.htm_cmp_radial100_hbtn.gif

206 ms

census-records.htm_cmp_radial100_hbtn.gif

census-records.htm_cmp_radial100_hbtn.gif

206 ms

state_county_maps.htm_cmp_Radial100_hbtn.gif

state_county_maps.htm_cmp_Radial100_hbtn.gif

205 ms

new_titles.htm_cmp_Radial100_hbtn.gif

new_titles.htm_cmp_Radial100_hbtn.gif

233 ms

coming_soon.htm_cmp_Radial100_hbtn.gif

coming_soon.htm_cmp_Radial100_hbtn.gif

234 ms

questions_answers.htm_cmp_Radial100_hbtn.gif

questions_answers.htm_cmp_Radial100_hbtn.gif

234 ms

customer_comments.htm_cmp_Radial100_hbtn.gif

customer_comments.htm_cmp_Radial100_hbtn.gif

232 ms

wholesale.htm_cmp_Radial100_hbtn.gif

wholesale.htm_cmp_Radial100_hbtn.gif

233 ms

conferences.htm_cmp_Radial100_hbtn.gif

conferences.htm_cmp_Radial100_hbtn.gif

234 ms

missouri_journey.htm_cmp_Radial100_hbtn.gif

missouri_journey.htm_cmp_Radial100_hbtn.gif

262 ms

iris_median.htm_cmp_Radial100_hbtn.gif

iris_median.htm_cmp_Radial100_hbtn.gif

262 ms

contact_us1.htm_cmp_Radial100_hbtn.gif

contact_us1.htm_cmp_Radial100_hbtn.gif

261 ms

genealogy-and-history-in-the-news.htm_cmp_radial100_hbtn.gif

genealogy-and-history-in-the-news.htm_cmp_radial100_hbtn.gif

263 ms

special_offers.htm_cmp_Radial100_hbtn.gif

special_offers.htm_cmp_Radial100_hbtn.gif

263 ms

county-history-books.htm_cmp_radial100_hbtn.gif

county-history-books.htm_cmp_radial100_hbtn.gif

264 ms

count.js

count.js

291 ms

show_ads_impl.js

show_ads_impl.js

298 ms

ctin.php

ctin.php

98 ms

Accessibility Review

hearthstonelegacy.com accessibility score

78

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hearthstonelegacy.com SEO score

58

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hearthstonelegacy.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 Hearthstonelegacy.com main page’s claimed encoding is windows-1252. 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

hearthstonelegacy.com

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