Tools & Wizards About Us
lylemckeany.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lylemckeany.com

Just Enough to Get Me in Trouble | Lyle McKeany | Substack

Page Load Speed

652 ms in total

First Response

59 ms

Resources Loaded

592 ms

Page Rendered

1 ms

lylemckeany.com screenshot

About Website

Welcome to lylemckeany.com homepage info - get ready to check Lyle Mc Keany best content right away, or after learning these important things about lylemckeany.com

Personal, vulnerable, and sometimes funny essays from a husband, father, and disability advocate, delivered whatever days he wants at exactly 8:08 am PT. Click to read Just Enough to Get Me in Trouble...

Visit lylemckeany.com

Key Findings

We analyzed Lylemckeany.com page load time and found that the first response time was 59 ms and then it took 593 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

lylemckeany.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.622

10/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

www.lyle.blog

59 ms

entry-91397ed1.css

38 ms

responsive_img-51b02764.css

41 ms

FlexBox-129dc41d.css

43 ms

IntroPopup-a01e8e94.css

46 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lylemckeany.com, 14% (2 requests) were made to Static.cloudflareinsights.com and 7% (1 request) were made to Lyle.blog. The less responsive or slowest element that took the longest time to load (70 ms) relates to the external source Static.cloudflareinsights.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.8 kB (36%)

Content Size

189.8 kB

After Optimization

121.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lylemckeany.com main page is 189.8 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. 25% of websites need less resources to load. HTML takes 85.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 67.8 kB

  • Original 85.7 kB
  • After minification 83.6 kB
  • After compression 17.9 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 67.8 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 804 B

  • Original 19.8 kB
  • After minification 19.0 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. Lyle Mc Keany images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 33 B

  • Original 60.9 kB
  • After minification 60.9 kB
  • After compression 60.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

-1%

Potential reduce by 180 B

  • Original 23.5 kB
  • After minification 23.5 kB
  • After compression 23.3 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. Lylemckeany.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (77%)

Requests Now

13

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lyle.blog

www.lyle.blog

59 ms

entry-91397ed1.css

entry-91397ed1.css

38 ms

responsive_img-51b02764.css

responsive_img-51b02764.css

41 ms

FlexBox-129dc41d.css

FlexBox-129dc41d.css

43 ms

IntroPopup-a01e8e94.css

IntroPopup-a01e8e94.css

46 ms

free_email_form-a84f1e43.css

free_email_form-a84f1e43.css

47 ms

welcome.e22fe2e58bb9d95b578d.css

welcome.e22fe2e58bb9d95b578d.css

46 ms

6c2ff3e3828e4017b7faf7b63e24cdf8.min.js

6c2ff3e3828e4017b7faf7b63e24cdf8.min.js

32 ms

welcome-beb97556.js

welcome-beb97556.js

57 ms

beacon.min.js

beacon.min.js

59 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

70 ms

https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F333ea7d6-5c6c-44ef-ae1c-6d90f5671f81_1180x1180.png

https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F333ea7d6-5c6c-44ef-ae1c-6d90f5671f81_1180x1180.png

57 ms

bundle.es5.min.js

bundle.es5.min.js

25 ms

datadog-rum.js

datadog-rum.js

29 ms

Accessibility Review

lylemckeany.com accessibility score

60

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

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

lylemckeany.com SEO score

83

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

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lylemckeany.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 Lylemckeany.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

lylemckeany.com

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