Access gracecathedral.com. Grace Cathedral

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

gracecathedral.com

125 ms

gracecathedral.org

651 ms

css2

37 ms

tribe-events-pro-mini-calendar-block.min.css

17 ms

style.min.css

42 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gracecathedral.com, 86% (86 requests) were made to Gracecathedral.org and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (709 ms) relates to the external source Fonts.gstatic.com.

Content Size

8.8 MB

After Optimization

8.7 MB

In fact, the total size of Gracecathedral.com main page is 8.8 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. 65% of websites need less resources to load. Images take 8.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 91.1 kB

Original 120.2 kB
After minification 104.9 kB
After compression 29.1 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 15.2 kB, which is 13% 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 91.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 8.4 MB
After minification 8.4 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. Grace Cathedral images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

Original 155.5 kB
After minification 155.5 kB
After compression 154.4 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

-12%

Potential reduce by 7.1 kB

Original 60.7 kB
After minification 60.4 kB
After compression 53.5 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. Gracecathedral.com needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 12% of the original size.

Requests Now

After Optimization

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