Access carolinastory.com. Carolina Story

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value18.5 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value3,690 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

www.carolinastory.com

83 ms

64N4Pri4dtDoOmKZrA2QCVIcYyRYtAMA5b_RHqNGk33fezq2fFHN4UJLFRbh52jhWDjDZ2MXFhFqZQmyFesKw2Su5QMt52iRZg7AMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0jhBkdhUTdcBDieNkpPuRdhulO1FUiABkZWF3jAF8OcFzdP37O1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CjhBkdhUTdcBDieNkpPuRdhulO1FUiABkZWF3jAF8OcFzdPURjW4zde80jWFXda4oOcFzdPUCdhFydeyzSabCSaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0dcmXOYiaikoySkolZPUaiaS0jhBkdhUTdcBDieNkpPuRdhulO1FUiABkZWF3jAF8OcFzdPUaiaS0jhBkdhUTdcBDieNkpPoRdhXCiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXK2csyp1TCZPuudc8RjWF8H6GJRHjfIMMjMKMfH6GJK7jfIMMjMkMfH6GJKHjfIMMjgkMfqMYNcVPpg6.js

67 ms

css2

84 ms

legacy.js

57 ms

modern.js

74 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Carolinastory.com, 39% (11 requests) were made to Assets.squarespace.com and 21% (6 requests) were made to Images.squarespace-cdn.com. The less responsive or slowest element that took the longest time to load (561 ms) relates to the external source Images.squarespace-cdn.com.

Content Size

11.3 MB

After Optimization

9.5 MB

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

HTML Optimization

-84%

Potential reduce by 119.4 kB

Original 141.8 kB
After minification 128.9 kB
After compression 22.4 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 119.4 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 60.0 kB

Original 8.3 MB
After minification 8.2 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. Carolina Story images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 1.5 MB

Original 2.8 MB
After minification 2.8 MB
After compression 1.3 MB

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 1.5 MB or 55% of the original size.

CSS Optimization

-12%

Potential reduce by 3.2 kB

Original 26.2 kB
After minification 26.2 kB
After compression 22.9 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. Carolinastory.com 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 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carolina Story. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.