Access cuantoyporquetanto.com. Cuanto y Porque Tanto

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value18.5 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.304

39/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

cuantoyporquetanto.com

954 ms

style.min.css

32 ms

wp-show-posts-min.css

35 ms

animate.min.css

38 ms

style.css

48 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 51% of them (51 requests) were addressed to the original Cuantoyporquetanto.com, 24% (24 requests) were made to Fonts.gstatic.com and 11% (11 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (954 ms) belongs to the original domain Cuantoyporquetanto.com.

Content Size

4.2 MB

After Optimization

3.9 MB

In fact, the total size of Cuantoyporquetanto.com main page is 4.2 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. Only a small number of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 98.6 kB

Original 117.3 kB
After minification 110.6 kB
After compression 18.7 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 98.6 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 24.3 kB

Original 3.0 MB
After minification 2.9 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. Cuanto Y Porque Tanto images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 34.1 kB

Original 905.9 kB
After minification 905.6 kB
After compression 871.8 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

-50%

Potential reduce by 105.0 kB

Original 209.5 kB
After minification 209.3 kB
After compression 104.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. Cuantoyporquetanto.com needs all CSS files to be minified and compressed as it can save up to 105.0 kB or 50% of the original size.

Requests Now

After Optimization

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