Tools & Wizards About Us
heritagefirecompany.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

heritagefirecompany.com

Heritage Fire Company – A Family Heritage…your local family-run fireplace, wood stove, and chimney sweep business for over 35 years!

Page Load Speed

3.4 sec in total

First Response

886 ms

Resources Loaded

2.4 sec

Page Rendered

162 ms

heritagefirecompany.com screenshot

About Website

Visit heritagefirecompany.com now to see the best up-to-date Heritage Fire Company content and also check out these interesting facts you probably never knew about heritagefirecompany.com

Heritage Fire Company, your local family-run fireplace, wood stove, and chimney sweep business for over 35 years!

Visit heritagefirecompany.com

Key Findings

We analyzed Heritagefirecompany.com page load time and found that the first response time was 886 ms and then it took 2.5 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

heritagefirecompany.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

www.heritagefirecompany.com

886 ms

wp-emoji-release.min.js

55 ms

styles.css

108 ms

rs6.css

110 ms

style.css

107 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 87% of them (46 requests) were addressed to the original Heritagefirecompany.com, 11% (6 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (886 ms) belongs to the original domain Heritagefirecompany.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.5 kB (9%)

Content Size

1.1 MB

After Optimization

988.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 71.9 kB

  • Original 89.2 kB
  • After minification 88.7 kB
  • After compression 17.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. 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 71.9 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 9.0 kB

  • Original 529.6 kB
  • After minification 520.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. Heritage Fire Company images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.8 kB

  • Original 376.9 kB
  • After minification 376.9 kB
  • After compression 371.2 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

-12%

Potential reduce by 10.8 kB

  • Original 89.8 kB
  • After minification 89.6 kB
  • After compression 79.0 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. Heritagefirecompany.com needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (84%)

Requests Now

45

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.heritagefirecompany.com

www.heritagefirecompany.com

886 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

55 ms

styles.css

styles.css

108 ms

rs6.css

rs6.css

110 ms

style.css

style.css

107 ms

base.css

base.css

114 ms

layout.css

layout.css

131 ms

shortcodes.css

shortcodes.css

119 ms

animations.min.css

animations.min.css

161 ms

jquery.ui.all.css

jquery.ui.all.css

159 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

162 ms

responsive.css

responsive.css

163 ms

css

css

29 ms

jquery.min.js

jquery.min.js

166 ms

jquery-migrate.min.js

jquery-migrate.min.js

166 ms

rbtools.min.js

rbtools.min.js

213 ms

rs6.min.js

rs6.min.js

270 ms

wp-polyfill.min.js

wp-polyfill.min.js

238 ms

i18n.min.js

i18n.min.js

206 ms

lodash.min.js

lodash.min.js

237 ms

url.min.js

url.min.js

238 ms

hooks.min.js

hooks.min.js

258 ms

api-fetch.min.js

api-fetch.min.js

267 ms

index.js

index.js

264 ms

core.min.js

core.min.js

266 ms

mouse.min.js

mouse.min.js

277 ms

sortable.min.js

sortable.min.js

344 ms

tabs.min.js

tabs.min.js

345 ms

accordion.min.js

accordion.min.js

345 ms

plugins.js

plugins.js

385 ms

menu.js

menu.js

345 ms

animations.min.js

animations.min.js

345 ms

jplayer.min.js

jplayer.min.js

366 ms

translate3d.js

translate3d.js

371 ms

scripts.js

scripts.js

383 ms

wp-embed.min.js

wp-embed.min.js

377 ms

HeritageFireCo_LogoHoriz_S.png

HeritageFireCo_LogoHoriz_S.png

104 ms

Home1-1024x678.jpg

Home1-1024x678.jpg

333 ms

Home2-1024x678.jpg

Home2-1024x678.jpg

199 ms

Home3-1024x678.jpg

Home3-1024x678.jpg

150 ms

264835580_4592359484173944_6244830304835812736_n.jpeg

264835580_4592359484173944_6244830304835812736_n.jpeg

408 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

97 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

95 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

140 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

152 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

154 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

27 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

37 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

42 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

43 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

53 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

42 ms

mfn-icons.woff

mfn-icons.woff

281 ms

Accessibility Review

heritagefirecompany.com accessibility score

75

Accessibility Issues

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

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

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

heritagefirecompany.com SEO score

91

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

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

heritagefirecompany.com

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