Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

read.lukeburgis.com

Luke Burgis Newsletter | Substack

Page Load Speed

573 ms in total

First Response

222 ms

Resources Loaded

351 ms

Page Rendered

0 ms

About Website

Visit read.lukeburgis.com now to see the best up-to-date Read Luke Burgis content for United States and also check out these interesting facts you probably never knew about read.lukeburgis.com

Pursuing the mysterium tremendum et fascinans and writing at the intersection of philosophy, culture, art, technology, and religious wisdom. Click to read Luke Burgis Newsletter, a Substack publicatio...

Visit read.lukeburgis.com

Key Findings

We analyzed Read.lukeburgis.com page load time and found that the first response time was 222 ms and then it took 351 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

read.lukeburgis.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value4,920 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.439

21/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

read.lukeburgis.com

222 ms

entry-03c607af.css

29 ms

LazyComponent-856acd57.css

31 ms

Button-e0897a13.css

32 ms

IntroPopup-3c09dac8.css

35 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Read.lukeburgis.com, 56% (9 requests) were made to Substackcdn.com and 13% (2 requests) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (222 ms) belongs to the original domain Read.lukeburgis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.5 kB (34%)

Content Size

281.3 kB

After Optimization

185.7 kB

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

HTML Optimization

-80%

Potential reduce by 90.9 kB

  • Original 114.3 kB
  • After minification 112.0 kB
  • After compression 23.4 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 90.9 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 4.5 kB

  • Original 80.2 kB
  • After minification 75.7 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. Read Luke Burgis images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 60.5 kB
  • After minification 60.5 kB
  • After compression 60.5 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 147 B

  • Original 26.3 kB
  • After minification 26.3 kB
  • After compression 26.1 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. Read.lukeburgis.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (80%)

Requests Now

15

After Optimization

3

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

Accessibility Review

read.lukeburgis.com accessibility score

70

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

read.lukeburgis.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

High

Missing source maps for large first-party JavaScript

SEO Factors

read.lukeburgis.com SEO score

84

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