Access davidweekly.org.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

davidweekly.org

167 ms

davidweekly.org

1556 ms

css2

51 ms

legacy.js

34 ms

modern.js

36 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 17% of them (2 requests) were addressed to the original Davidweekly.org, 33% (4 requests) were made to Assets.squarespace.com and 25% (3 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Davidweekly.org.

Content Size

1.6 MB

After Optimization

1.4 MB

In fact, the total size of Davidweekly.org main page is 1.6 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. 25% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 93.8 kB

Original 112.2 kB
After minification 91.8 kB
After compression 18.5 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 20.4 kB, which is 18% 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 93.8 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 32.2 kB

Original 1.3 MB
After minification 1.3 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. Davidweekly images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 75.5 kB

Original 131.6 kB
After minification 131.6 kB
After compression 56.2 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 75.5 kB or 57% of the original size.

CSS Optimization

-12%

Potential reduce by 3.2 kB

Original 26.5 kB
After minification 26.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. Davidweekly.org needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 12% of the original size.

Requests Now

After Optimization

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