Tools & Wizards About Us
fletchbarney.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

fletchbarney.com

Fletch-Barney - Fletch-Barney

Page Load Speed

1.4 sec in total

First Response

102 ms

Resources Loaded

1 sec

Page Rendered

259 ms

fletchbarney.com screenshot

About Website

Visit fletchbarney.com now to see the best up-to-date Fletch Barney content and also check out these interesting facts you probably never knew about fletchbarney.com

Visit fletchbarney.com

Key Findings

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

fletchbarney.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value1.097

1/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

fletchbarney.com

102 ms

fletchbarney.com

123 ms

formreset.min.css

31 ms

formsmain.min.css

42 ms

readyclass.min.css

32 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 60% of them (61 requests) were addressed to the original Fletchbarney.com, 22% (22 requests) were made to Fonts.gstatic.com and 14% (14 requests) were made to Fletchbarney.wpenginepowered.com. The less responsive or slowest element that took the longest time to load (417 ms) relates to the external source Fletchbarney.wpenginepowered.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.9 kB (30%)

Content Size

787.9 kB

After Optimization

550.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fletchbarney.com main page is 787.9 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. 70% of websites need less resources to load. HTML takes 260.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 219.8 kB

  • Original 260.8 kB
  • After minification 257.0 kB
  • After compression 41.0 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 219.8 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 11.4 kB

  • Original 178.6 kB
  • After minification 167.2 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. Fletch Barney images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 239.3 kB
  • After minification 239.3 kB
  • After compression 237.7 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

-5%

Potential reduce by 5.0 kB

  • Original 109.1 kB
  • After minification 107.1 kB
  • After compression 104.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. Fletchbarney.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 55 (75%)

Requests Now

73

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fletchbarney.com

fletchbarney.com

102 ms

fletchbarney.com

fletchbarney.com

123 ms

formreset.min.css

formreset.min.css

31 ms

formsmain.min.css

formsmain.min.css

42 ms

readyclass.min.css

readyclass.min.css

32 ms

browsers.min.css

browsers.min.css

36 ms

basic.min.css

basic.min.css

46 ms

theme.min.css

theme.min.css

54 ms

column-numbers.min.css

column-numbers.min.css

49 ms

column-stacking.min.css

column-stacking.min.css

55 ms

divi-blog-module.min.css

divi-blog-module.min.css

61 ms

divi-portfolio-module.min.css

divi-portfolio-module.min.css

67 ms

divi-gallery-module.min.css

divi-gallery-module.min.css

59 ms

divi-shop-module.min.css

divi-shop-module.min.css

63 ms

misc.css

misc.css

65 ms

user-meta-shortcode.css

user-meta-shortcode.css

68 ms

mobile-menu.css

mobile-menu.css

71 ms

preloader.css

preloader.css

72 ms

docs_menu.css

docs_menu.css

74 ms

tooltips.css

tooltips.css

77 ms

lightbox.css

lightbox.css

80 ms

body-classes.css

body-classes.css

78 ms

custom-archives.css

custom-archives.css

82 ms

menu-animations.css

menu-animations.css

84 ms

helpful-links.css

helpful-links.css

83 ms

style.min.css

style.min.css

84 ms

style.min.css

style.min.css

104 ms

css

css

63 ms

magnific_popup.css

magnific_popup.css

89 ms

swiper.css

swiper.css

87 ms

popup.css

popup.css

92 ms

animate.css

animate.css

95 ms

readmore.css

readmore.css

124 ms

dsm-easy-tb.css

dsm-easy-tb.css

98 ms

magnific_popup.min.css

magnific_popup.min.css

126 ms

jquery.cookie.js

jquery.cookie.js

61 ms

et-core-unified-108867.min.css

et-core-unified-108867.min.css

102 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

123 ms

loader.js

loader.js

39 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

122 ms

jquery.min.js

jquery.min.js

149 ms

jquery-migrate.min.js

jquery-migrate.min.js

143 ms

widow-fixer.min.js

widow-fixer.min.js

140 ms

misc.min.js

misc.min.js

138 ms

dh_snippets.js

dh_snippets.js

199 ms

scripts.min.js

scripts.min.js

135 ms

jquery.fitvids.js

jquery.fitvids.js

132 ms

easypiechart.js

easypiechart.js

129 ms

frontend-bundle.min.js

frontend-bundle.min.js

128 ms

common.js

common.js

125 ms

dsm-easy-tb.js

dsm-easy-tb.js

123 ms

magnific_popup.min.js

magnific_popup.min.js

120 ms

admin_scripts.js

admin_scripts.js

294 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

117 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

118 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

114 ms

motion-effects.js

motion-effects.js

113 ms

FB_logo.png

FB_logo.png

221 ms

et-divi-dynamic-tb-50087-tb-50078-108867-late.css

et-divi-dynamic-tb-50087-tb-50078-108867-late.css

18 ms

preloader.gif

preloader.gif

66 ms

perma-liner-trailer.jpg.webp

perma-liner-trailer.jpg.webp

237 ms

camera.jpg

camera.jpg

353 ms

plumber-7-ccd-18.webp

plumber-7-ccd-18.webp

352 ms

plumber-7-ccd-23.webp

plumber-7-ccd-23.webp

351 ms

plumber-7-ccd-21.webp

plumber-7-ccd-21.webp

353 ms

sewer-cleaning.jpg

sewer-cleaning.jpg

355 ms

plumber-7-ccd-20.webp

plumber-7-ccd-20.webp

351 ms

descaling-1.jpg

descaling-1.jpg

402 ms

plumber-7-ccd-19.webp

plumber-7-ccd-19.webp

402 ms

plumber-5-ot-15.png

plumber-5-ot-15.png

384 ms

plumber-5-ot-17.png

plumber-5-ot-17.png

384 ms

plumber-5-ot-16.png

plumber-5-ot-16.png

384 ms

about.jpg

about.jpg

417 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KyK62EE9C0.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KyK62EE9C0.woff

176 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Ky462EE9C0.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Ky462EE9C0.woff

205 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kzm62EE9C0.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kzm62EE9C0.woff

215 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw462EE9C0.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw462EE9C0.woff

271 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxm7GEE9C0.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxm7GEE9C0.woff

264 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxf7GEE9C0.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxf7GEE9C0.woff

287 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw47GEE9C0.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw47GEE9C0.woff

344 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KwR7GEE9C0.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KwR7GEE9C0.woff

287 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYw.woff

220 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYw.woff

222 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYw.woff

236 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYw.woff

237 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYw.woff

237 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYw.woff

237 ms

modules.woff

modules.woff

126 ms

modules.woff

modules.woff

125 ms

fa-solid-900.woff

fa-solid-900.woff

171 ms

fa-brands-400.woff

fa-brands-400.woff

171 ms

fa-regular-400.woff

fa-regular-400.woff

168 ms

cIf4MaFatEE-VTaP_JWEdGgmmw.woff

cIf4MaFatEE-VTaP_JWEdGgmmw.woff

326 ms

cIf4MaFatEE-VTaP_ImHdGgmmw.woff

cIf4MaFatEE-VTaP_ImHdGgmmw.woff

268 ms

cIf4MaFatEE-VTaP_K2GdGgmmw.woff

cIf4MaFatEE-VTaP_K2GdGgmmw.woff

320 ms

cIf4MaFatEE-VTaP_PGFdGgmmw.woff

cIf4MaFatEE-VTaP_PGFdGgmmw.woff

325 ms

cIf9MaFatEE-VTaP9CChZw.woff

cIf9MaFatEE-VTaP9CChZw.woff

284 ms

cIf4MaFatEE-VTaP_IWDdGgmmw.woff

cIf4MaFatEE-VTaP_IWDdGgmmw.woff

285 ms

cIf4MaFatEE-VTaP_OGAdGgmmw.woff

cIf4MaFatEE-VTaP_OGAdGgmmw.woff

341 ms

cIf_MaFatEE-VTaP_E2RbUEF.woff

cIf_MaFatEE-VTaP_E2RbUEF.woff

286 ms

embed

embed

352 ms

js

js

37 ms

Accessibility Review

fletchbarney.com accessibility score

88

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

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

fletchbarney.com best practices score

83

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fletchbarney.com SEO score

77

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

High

Page is blocked from indexing

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fletchbarney.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 Fletchbarney.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

fletchbarney.com

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