Access richcount.com. 리치카운트(RichCount)

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

richcount.com

315 ms

css

26 ms

bootstrap.min.css

108 ms

font-awesome.min.css

135 ms

misc.css

138 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 47% of them (47 requests) were addressed to the original Richcount.com, 18% (18 requests) were made to Maps.google.com and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (989 ms) belongs to the original domain Richcount.com.

Content Size

3.6 MB

After Optimization

2.7 MB

In fact, the total size of Richcount.com main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 25.0 kB

Original 29.9 kB
After minification 21.5 kB
After compression 5.0 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 8.4 kB, which is 28% 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 25.0 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 181.5 kB

Original 2.7 MB
After minification 2.5 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. Rich Count images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 478.1 kB

Original 689.3 kB
After minification 650.0 kB
After compression 211.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 478.1 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 137.6 kB

Original 165.9 kB
After minification 155.5 kB
After compression 28.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. Richcount.com needs all CSS files to be minified and compressed as it can save up to 137.6 kB or 83% of the original size.

Requests Now

After Optimization

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