Access openclover.org. OpenClover - Java, Groovy and AspectJ code coverage tool

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

openclover.org

403 ms

openclover.org

525 ms

bootstrap-5.3.2.min.css

237 ms

style.css

347 ms

openclover_logo_white_40pt_alpha_with_icon.png

369 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that all of those requests were addressed to Openclover.org and no external sources were called. The less responsive or slowest element that took the longest time to load (806 ms) belongs to the original domain Openclover.org.

Content Size

471.0 kB

After Optimization

379.0 kB

In fact, the total size of Openclover.org main page is 471.0 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. 20% of websites need less resources to load. Images take 361.0 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.0 kB

Original 9.8 kB
After minification 8.3 kB
After compression 2.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 1.5 kB, which is 16% 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 7.0 kB or 71% of the original size.

Image Optimization

-20%

Potential reduce by 71.8 kB

Original 361.0 kB
After minification 289.1 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. Obviously, Open Clover needs image optimization as it can save up to 71.8 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-9%

Potential reduce by 5.6 kB

Original 61.1 kB
After minification 61.1 kB
After compression 55.6 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

-20%

Potential reduce by 7.7 kB

Original 39.1 kB
After minification 39.1 kB
After compression 31.4 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. Openclover.org needs all CSS files to be minified and compressed as it can save up to 7.7 kB or 20% of the original size.

Requests Now

After Optimization

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Clover. 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 as a result speed up the page load time.