Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

robinbotie.com

Robin Botie - About Me and Loss of a Child Marika Warden

Page Load Speed

307 ms in total

First Response

33 ms

Resources Loaded

274 ms

Page Rendered

0 ms

About Website

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

Writings of Robin Botie about loss of a child Marika, Bereaved Mother Designs Life After Death and a mother's road to healing

Visit robinbotie.com

Key Findings

We analyzed Robinbotie.com page load time and found that the first response time was 33 ms and then it took 274 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

robinbotie.com performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

robinbotie.com

33 ms

robinbotie.com

94 ms

bootstrap.min.css

18 ms

font-awesome.min.css

25 ms

css

43 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 63% of them (10 requests) were addressed to the original Robinbotie.com, 25% (4 requests) were made to Unpkg.com and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (103 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.3 kB (15%)

Content Size

133.1 kB

After Optimization

113.8 kB

In fact, the total size of Robinbotie.com main page is 133.1 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. 15% of websites need less resources to load. Javascripts take 53.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 11.7 kB

  • Original 16.5 kB
  • After minification 14.1 kB
  • After compression 4.8 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 2.4 kB, which is 14% 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 11.7 kB or 71% of the original size.

Image Optimization

-4%

Potential reduce by 985 B

  • Original 25.4 kB
  • After minification 24.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. Robin Botie images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 599 B

  • Original 53.4 kB
  • After minification 53.4 kB
  • After compression 52.8 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

-16%

Potential reduce by 6.1 kB

  • Original 37.8 kB
  • After minification 36.6 kB
  • After compression 31.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. Robinbotie.com needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 16% of the original size.

Requests Breakdown

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

Requests Now

12

After Optimization

4

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

Accessibility Review

robinbotie.com accessibility score

83

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

robinbotie.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

robinbotie.com SEO score

91

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

Image elements do not have [alt] attributes

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Robinbotie.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 Robinbotie.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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