Tools & Wizards About Us
johnhenryguitarman.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

johnhenryguitarman.com

Page Load Speed

4.1 sec in total

First Response

610 ms

Resources Loaded

3.4 sec

Page Rendered

30 ms

johnhenryguitarman.com screenshot

About Website

Welcome to johnhenryguitarman.com homepage info - get ready to check Johnhenryguitarman best content right away, or after learning these important things about johnhenryguitarman.com

Visit johnhenryguitarman.com

Key Findings

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

Performance Metrics

johnhenryguitarman.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value4.1 s

78/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

www.johnhenryguitarman.com

610 ms

wp-emoji-release.min.js

45 ms

style.min.css

145 ms

style.css

112 ms

style.css

148 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 46% of them (16 requests) were addressed to the original Johnhenryguitarman.com, 17% (6 requests) were made to Youtube.com and 17% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (610 ms) belongs to the original domain Johnhenryguitarman.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 651.8 kB (79%)

Content Size

827.6 kB

After Optimization

175.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 20.6 kB

  • Original 27.7 kB
  • After minification 26.9 kB
  • After compression 7.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 20.6 kB or 74% of the original size.

Image Optimization

-7%

Potential reduce by 435 B

  • Original 6.0 kB
  • After minification 5.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. Johnhenryguitarman images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 172.2 kB

  • Original 255.8 kB
  • After minification 254.5 kB
  • After compression 83.6 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 172.2 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 458.5 kB

  • Original 538.1 kB
  • After minification 507.6 kB
  • After compression 79.6 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. Johnhenryguitarman.com needs all CSS files to be minified and compressed as it can save up to 458.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (82%)

Requests Now

28

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.johnhenryguitarman.com

www.johnhenryguitarman.com

610 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

45 ms

style.min.css

style.min.css

145 ms

style.css

style.css

112 ms

style.css

style.css

148 ms

themify-icons.css

themify-icons.css

108 ms

layout-styles.min.css

layout-styles.min.css

83 ms

css

css

48 ms

icon

icon

67 ms

animation-styles.min.css

animation-styles.min.css

99 ms

jquery.js

jquery.js

202 ms

ctct-plugin-recaptcha-v2.min.js

ctct-plugin-recaptcha-v2.min.js

153 ms

api.js

api.js

64 ms

ctct-plugin-frontend.min.js

ctct-plugin-frontend.min.js

154 ms

scripts.min.js

scripts.min.js

168 ms

ba-throttle-debounce.min.js

ba-throttle-debounce.min.js

168 ms

ripple.min.js

ripple.min.js

167 ms

wp-embed.min.js

wp-embed.min.js

306 ms

b6rgcJrkfrU

b6rgcJrkfrU

259 ms

td-11kv_hero-300x169.jpg

td-11kv_hero-300x169.jpg

132 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

138 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

156 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

156 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

211 ms

recaptcha__en.js

recaptcha__en.js

423 ms

www-player.css

www-player.css

79 ms

www-embed-player.js

www-embed-player.js

262 ms

base.js

base.js

390 ms

fetch-polyfill.js

fetch-polyfill.js

296 ms

ad_status.js

ad_status.js

392 ms

BtfhbKJ-Y5RfiteF0SJrgrcmJB2_8an7Z4FyTQpfLrM.js

BtfhbKJ-Y5RfiteF0SJrgrcmJB2_8an7Z4FyTQpfLrM.js

287 ms

embed.js

embed.js

87 ms

id

id

76 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

12 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

11 ms

Accessibility Review

johnhenryguitarman.com accessibility score

89

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

johnhenryguitarman.com best practices score

67

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

SEO Factors

johnhenryguitarman.com SEO score

92

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnhenryguitarman.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Johnhenryguitarman.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

johnhenryguitarman.com

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