Tools & Wizards About Us
matthewbarby.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    83% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

matthewbarby.com

Matthew Howells-Barby: Crypto Growth Leader & Investor

Page Load Speed

3.8 sec in total

First Response

872 ms

Resources Loaded

2.3 sec

Page Rendered

689 ms

matthewbarby.com screenshot

About Website

Visit matthewbarby.com now to see the best up-to-date Matthew Barby content for India and also check out these interesting facts you probably never knew about matthewbarby.com

I lead, advise, and grow high-performing growth teams that bring value to the people, products, and services shaping the future of finance.

Visit matthewbarby.com

Key Findings

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

matthewbarby.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.292

41/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

www.matthewbarby.com

872 ms

fbevents.js

46 ms

wp-emoji-release.min.js

84 ms

widget.css

153 ms

styles.css

153 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 69% of them (52 requests) were addressed to the original Matthewbarby.com, 4% (3 requests) were made to Netdna.bootstrapcdn.com and 3% (2 requests) were made to Linkedin.com. The less responsive or slowest element that took the longest time to load (872 ms) belongs to the original domain Matthewbarby.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.0 kB (23%)

Content Size

987.7 kB

After Optimization

757.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 43.6 kB

  • Original 54.1 kB
  • After minification 42.2 kB
  • After compression 10.5 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. This page needs HTML code to be minified as it can gain 11.9 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.6 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 39.6 kB

  • Original 735.2 kB
  • After minification 695.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. Matthew Barby images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 47.8 kB

  • Original 79.2 kB
  • After minification 79.1 kB
  • After compression 31.4 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 47.8 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 99.0 kB

  • Original 119.2 kB
  • After minification 115.3 kB
  • After compression 20.2 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. Matthewbarby.com needs all CSS files to be minified and compressed as it can save up to 99.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (50%)

Requests Now

70

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.matthewbarby.com

www.matthewbarby.com

872 ms

fbevents.js

fbevents.js

46 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

84 ms

widget.css

widget.css

153 ms

styles.css

styles.css

153 ms

hypotext.css

hypotext.css

154 ms

icons.css

icons.css

155 ms

front.css

front.css

165 ms

bootstrap.min.css

bootstrap.min.css

14 ms

font-awesome.css

font-awesome.css

10 ms

animate.css

animate.css

159 ms

jquery.sidr.light.css

jquery.sidr.light.css

227 ms

matt.css

matt.css

228 ms

style.css

style.css

238 ms

ytprefs.min.css

ytprefs.min.css

238 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

22 ms

q2w3-fixed-widget.min.js

q2w3-fixed-widget.min.js

239 ms

comment-reply.custom.js

comment-reply.custom.js

238 ms

hypotext.js

hypotext.js

297 ms

share-count.js

share-count.js

298 ms

api.min.js

api.min.js

18 ms

script.js

script.js

300 ms

ytprefs.min.js

ytprefs.min.js

304 ms

tldr.js

tldr.js

307 ms

related.css

related.css

329 ms

front.js

front.js

380 ms

fitvids.min.js

fitvids.min.js

380 ms

wp-embed.min.js

wp-embed.min.js

381 ms

ThemeContactForm.js

ThemeContactForm.js

380 ms

oct.js

oct.js

64 ms

27 ms

css

css

29 ms

iframe_api

iframe_api

74 ms

goal.min.js

goal.min.js

25 ms

mattLogo.png

mattLogo.png

339 ms

seperator.png

seperator.png

106 ms

client-moz-339x85.png

client-moz-339x85.png

337 ms

client-forbes-339x85.png

client-forbes-339x85.png

315 ms

client-sel-333x85.png

client-sel-333x85.png

339 ms

marketingland-339x85.jpg

marketingland-339x85.jpg

315 ms

searchenginejournal-logo-339x85.jpg

searchenginejournal-logo-339x85.jpg

338 ms

the-guardian-logo-339x85.jpg

the-guardian-logo-339x85.jpg

338 ms

techradar-339x85.jpg

techradar-339x85.jpg

337 ms

entrepreneur1-339x85.jpg

entrepreneur1-339x85.jpg

409 ms

socialmediatoday-339x85.jpg

socialmediatoday-339x85.jpg

414 ms

319556a.jpg

319556a.jpg

410 ms

nickeubanks.jpg

nickeubanks.jpg

486 ms

0127a84.jpg

0127a84.jpg

485 ms

justincroxton.jpg

justincroxton.jpg

487 ms

danielbox.jpg

danielbox.jpg

635 ms

icon-pencil.png

icon-pencil.png

489 ms

icon-video.png

icon-video.png

496 ms

icon-paper-swan.png

icon-paper-swan.png

560 ms

icon-phone.png

icon-phone.png

563 ms

gtm.js

gtm.js

67 ms

active-tab.png

active-tab.png

546 ms

topHeader1-1800x527.jpg

topHeader1-1800x527.jpg

776 ms

featuredOn-arrow.png

featuredOn-arrow.png

558 ms

mb-circle.png

mb-circle.png

620 ms

blog-arrow.png

blog-arrow.png

621 ms

quote-open.png

quote-open.png

630 ms

quote-close.png

quote-close.png

639 ms

champagne__limousines-webfont.woff

champagne__limousines-webfont.woff

641 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

8 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

8 ms

www-widgetapi.js

www-widgetapi.js

30 ms

analytics.js

analytics.js

11 ms

join

join

234 ms

jquery.min.js

jquery.min.js

21 ms

adsct

adsct

240 ms

adsct

adsct

200 ms

collect

collect

5 ms

collect

collect

215 ms

graph.facebook.com

graph.facebook.com

58 ms

share

share

9 ms

Accessibility Review

matthewbarby.com 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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

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

matthewbarby.com SEO score

93

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

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

matthewbarby.com

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