Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

brendandawes.com

Brendan Dawes - Brendan Dawes

Page Load Speed

11 sec in total

First Response

3.4 sec

Resources Loaded

6.3 sec

Page Rendered

1.3 sec

About Website

Visit brendandawes.com now to see the best up-to-date Brendan Dawes content for United Kingdom and also check out these interesting facts you probably never knew about brendandawes.com

Interaction Design

Visit brendandawes.com

Key Findings

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

Performance Metrics

brendandawes.com performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

brendandawes.com

3389 ms

bat5pgs.js

345 ms

font-awesome.min.css

6 ms

jquery-1.7.2.min.js

208 ms

jquery.isotope.min.js

221 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 91% of them (107 requests) were addressed to the original Brendandawes.com, 5% (6 requests) were made to Use.typekit.net and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Brendandawes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 277.9 kB (11%)

Content Size

2.5 MB

After Optimization

2.3 MB

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

HTML Optimization

-84%

Potential reduce by 59.2 kB

  • Original 70.8 kB
  • After minification 62.7 kB
  • After compression 11.6 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 8.1 kB, which is 11% 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 59.2 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 101.7 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. Brendan Dawes images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 82.5 kB

  • Original 142.1 kB
  • After minification 136.7 kB
  • After compression 59.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 82.5 kB or 58% of the original size.

CSS Optimization

-80%

Potential reduce by 34.6 kB

  • Original 43.4 kB
  • After minification 36.7 kB
  • After compression 8.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. Brendandawes.com needs all CSS files to be minified and compressed as it can save up to 34.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (8%)

Requests Now

112

After Optimization

103

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

Accessibility Review

brendandawes.com accessibility score

94

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.

Best Practices

brendandawes.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

brendandawes.com SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

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