Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

brotherroy.blog

Chasing Jesus – This blog is about my experience among the Indigenous people in north central Saskatchewan as a Catholic Missionary, how I got there, ...

Page Load Speed

1.3 sec in total

First Response

25 ms

Resources Loaded

799 ms

Page Rendered

521 ms

About Website

Click here to check amazing Brotherroy content. Otherwise, check out these important facts you probably never knew about brotherroy.blog

This blog is about my experience among the Indigenous people in north central Saskatchewan as a Catholic Missionary, how I got there, and how the experience has changed my life in Christ.

Visit brotherroy.blog

Key Findings

We analyzed Brotherroy.blog page load time and found that the first response time was 25 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 30% of websites can load faster.

Performance Metrics

brotherroy.blog performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

brotherroy.blog

25 ms

brotherroy.blog

292 ms

infinity.css

117 ms

style.css

104 ms

109 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Brotherroy.blog, 28% (10 requests) were made to S2.wp.com and 25% (9 requests) were made to Fonts.wp.com. The less responsive or slowest element that took the longest time to load (292 ms) belongs to the original domain Brotherroy.blog.

Page Optimization Overview & Recommendations

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

Content Size

213.3 kB

After Optimization

150.2 kB

In fact, the total size of Brotherroy.blog main page is 213.3 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. 45% of websites need less resources to load. HTML takes 81.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 61.4 kB

  • Original 81.0 kB
  • After minification 76.3 kB
  • After compression 19.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. 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 61.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 688 B

  • Original 40.1 kB
  • After minification 39.4 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. Brotherroy images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 723 B

  • Original 70.7 kB
  • After minification 70.7 kB
  • After compression 69.9 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

-1%

Potential reduce by 290 B

  • Original 21.5 kB
  • After minification 21.5 kB
  • After compression 21.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. Brotherroy.blog has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (67%)

Requests Now

24

After Optimization

8

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brotherroy. 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 12 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

brotherroy.blog accessibility score

90

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

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

brotherroy.blog 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

brotherroy.blog SEO score

89

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

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 Brotherroy.blog 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 Brotherroy.blog 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 data is detected on the main page of Brotherroy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: