Tools & Wizards About Us
brianharrington.org screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

brianharrington.org

Brian Harrington - YouTube

Page Load Speed

2.4 sec in total

First Response

44 ms

Resources Loaded

2.3 sec

Page Rendered

118 ms

brianharrington.org screenshot

About Website

Click here to check amazing Brian Harrington content. Otherwise, check out these important facts you probably never knew about brianharrington.org

Bitcoin Personal Finance. Real Estate Professional. Profitable Predictor.

Visit brianharrington.org

Key Findings

We analyzed Brianharrington.org page load time and found that the first response time was 44 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

brianharrington.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value10,140 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value30.2 s

0/100

10%

Network Requests Diagram

brianharrington.org

44 ms

www.brianharrington.org

82 ms

css2

70 ms

legacy.js

47 ms

modern.js

55 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Brianharrington.org, 32% (18 requests) were made to Fonts.gstatic.com and 25% (14 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.2 kB (5%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Brianharrington.org main page is 1.5 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. Only a small number of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 37.4 kB

  • Original 49.5 kB
  • After minification 48.2 kB
  • After compression 12.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 37.4 kB or 76% of the original size.

JavaScript Optimization

-3%

Potential reduce by 37.8 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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

-0%

Potential reduce by 0 B

  • Original 119.8 kB
  • After minification 119.8 kB
  • After compression 119.8 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. Brianharrington.org has all CSS files already compressed.

Requests Breakdown

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

Requests Now

37

After Optimization

16

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

brianharrington.org

brianharrington.org

44 ms

www.brianharrington.org

www.brianharrington.org

82 ms

css2

css2

70 ms

legacy.js

legacy.js

47 ms

modern.js

modern.js

55 ms

extract-css-runtime-2aa3d1ea14f6d9c97330-min.en-US.js

extract-css-runtime-2aa3d1ea14f6d9c97330-min.en-US.js

52 ms

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

71 ms

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

49 ms

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

58 ms

common-vendors-8db852056516153189c0-min.en-US.js

common-vendors-8db852056516153189c0-min.en-US.js

71 ms

common-39a590beac1611bc37d7-min.en-US.js

common-39a590beac1611bc37d7-min.en-US.js

77 ms

performance-74d24f5c2adcf3b8ee8a-min.en-US.js

performance-74d24f5c2adcf3b8ee8a-min.en-US.js

55 ms

site.css

site.css

60 ms

js

js

109 ms

52 ms

8XxtFO7nUsU

8XxtFO7nUsU

127 ms

9WxhDoySEPk

9WxhDoySEPk

543 ms

GlbNEKZJcBk

GlbNEKZJcBk

494 ms

O1muDph8Tg8

O1muDph8Tg8

491 ms

POz6EYQGIwA

POz6EYQGIwA

663 ms

IC4TE1FzUE8

IC4TE1FzUE8

594 ms

www-player.css

www-player.css

15 ms

www-embed-player.js

www-embed-player.js

52 ms

base.js

base.js

76 ms

ad_status.js

ad_status.js

602 ms

S6u8w4BMUTPHh30AXC-sNiXg7Q.woff

S6u8w4BMUTPHh30AXC-sNiXg7Q.woff

590 ms

S6u8w4BMUTPHh30AUi-sNiXg7eU0.woff

S6u8w4BMUTPHh30AUi-sNiXg7eU0.woff

635 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

1255 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

1257 ms

YpaxWjHVNNO6KZk05PsGAol2GFYfBj4WvF05Ro9VHVE.js

YpaxWjHVNNO6KZk05PsGAol2GFYfBj4WvF05Ro9VHVE.js

586 ms

embed.js

embed.js

359 ms

www-player.css

www-player.css

299 ms

www-embed-player.js

www-embed-player.js

315 ms

base.js

base.js

485 ms

id

id

167 ms

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

664 ms

KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff

665 ms

KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff

989 ms

KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff

749 ms

KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff

988 ms

KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff

986 ms

KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff

987 ms

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

987 ms

KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff

991 ms

KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff

1000 ms

KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff

1000 ms

KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff

999 ms

KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff

991 ms

KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff

1001 ms

Create

Create

817 ms

Create

Create

837 ms

Create

Create

931 ms

Create

Create

933 ms

Create

Create

937 ms

Create

Create

791 ms

embed.js

embed.js

588 ms

id

id

129 ms

Accessibility Review

brianharrington.org accessibility score

88

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

brianharrington.org 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

High

Page has valid source maps

SEO Factors

brianharrington.org SEO score

92

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

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 Brianharrington.org 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 Brianharrington.org 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

brianharrington.org

Open Graph data is detected on the main page of Brian Harrington. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: