Tools & Wizards About Us
hartify.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

hartify.com

Franchise Consulting | Franchise GrowthLab | Homepage

Page Load Speed

5.2 sec in total

First Response

1.2 sec

Resources Loaded

2.4 sec

Page Rendered

1.6 sec

hartify.com screenshot

About Website

Click here to check amazing Hartify content. Otherwise, check out these important facts you probably never knew about hartify.com

Franchise consulting for faster scale and better systems delivered by one of the most influential franchisors in North America.

Visit hartify.com

Key Findings

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

Performance Metrics

hartify.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

franchisegrowthlab.com

1236 ms

css

34 ms

post-8.css

67 ms

post-11.css

188 ms

post-1957.css

108 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hartify.com, 21% (15 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Franchisegrowthlab.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (59%)

Content Size

1.7 MB

After Optimization

707.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hartify.com main page is 1.7 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. 60% of websites need less resources to load. Images take 766.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 297.3 kB

  • Original 354.5 kB
  • After minification 347.3 kB
  • After compression 57.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 297.3 kB or 84% of the original size.

Image Optimization

-36%

Potential reduce by 273.8 kB

  • Original 766.8 kB
  • After minification 493.0 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. Obviously, Hartify needs image optimization as it can save up to 273.8 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 328.9 kB

  • Original 472.0 kB
  • After minification 471.8 kB
  • After compression 143.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 328.9 kB or 70% of the original size.

CSS Optimization

-89%

Potential reduce by 119.1 kB

  • Original 133.2 kB
  • After minification 129.0 kB
  • After compression 14.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. Hartify.com needs all CSS files to be minified and compressed as it can save up to 119.1 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (57%)

Requests Now

54

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

franchisegrowthlab.com

franchisegrowthlab.com

1236 ms

css

css

34 ms

post-8.css

post-8.css

67 ms

post-11.css

post-11.css

188 ms

post-1957.css

post-1957.css

108 ms

post-235.css

post-235.css

138 ms

post-244.css

post-244.css

144 ms

css

css

32 ms

timeme.min.js

timeme.min.js

151 ms

hooks.min.js

hooks.min.js

145 ms

i18n.min.js

i18n.min.js

176 ms

url.min.js

url.min.js

185 ms

api-fetch.min.js

api-fetch.min.js

184 ms

burst.min.js

burst.min.js

180 ms

jquery.min.js

jquery.min.js

261 ms

v4-shims.min.js

v4-shims.min.js

223 ms

js

js

71 ms

animations.min.css

animations.min.css

202 ms

post-4113.css

post-4113.css

207 ms

frontend.min.js

frontend.min.js

212 ms

site_tracking.js

site_tracking.js

202 ms

astra-addon-669d69751aed83-91335770.js

astra-addon-669d69751aed83-91335770.js

439 ms

lazyload.min.js

lazyload.min.js

241 ms

pminstantpage.min.js

pminstantpage.min.js

438 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

439 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

443 ms

webpack.runtime.min.js

webpack.runtime.min.js

442 ms

frontend-modules.min.js

frontend-modules.min.js

446 ms

frontend.min.js

frontend.min.js

444 ms

waypoints.min.js

waypoints.min.js

444 ms

core.min.js

core.min.js

446 ms

frontend.min.js

frontend.min.js

447 ms

elements-handlers.min.js

elements-handlers.min.js

446 ms

gtm.js

gtm.js

190 ms

frk-1024x182-1.webp

frk-1024x182-1.webp

144 ms

contactphotobg1_1.jpg

contactphotobg1_1.jpg

146 ms

shape2.png

shape2.png

144 ms

shape3.png

shape3.png

143 ms

programsphotobg1_1.jpg

programsphotobg1_1.jpg

146 ms

shape4.png

shape4.png

144 ms

Copy-of-Franchise-Growth-Lab-Logo.png

Copy-of-Franchise-Growth-Lab-Logo.png

145 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

31 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

31 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

85 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

99 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

101 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

102 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

101 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

101 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

100 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

100 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

101 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

102 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

102 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf

103 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf

103 ms

astra.woff

astra.woff

98 ms

redverticalline2.png

redverticalline2.png

72 ms

Hartify_Icon_white.png

Hartify_Icon_white.png

70 ms

blueline1.png

blueline1.png

71 ms

illustration2.png

illustration2.png

73 ms

one.png

one.png

72 ms

two.png

two.png

69 ms

three.png

three.png

78 ms

four.png

four.png

77 ms

johncircle1.png

johncircle1.png

138 ms

illustration3.png

illustration3.png

117 ms

Hartify_Icon_red.png

Hartify_Icon_red.png

90 ms

johnheadshot2.jpg

johnheadshot2.jpg

116 ms

HartifyTabletMockup1-updated.png

HartifyTabletMockup1-updated.png

157 ms

Manual-Render-1.png

Manual-Render-1.png

159 ms

Accessibility Review

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

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Best Practices

hartify.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hartify.com SEO score

84

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

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

hartify.com

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