1.3 sec in total
114 ms
1.1 sec
143 ms
Welcome to carolinastory.com homepage info - get ready to check Carolina Story best content right away, or after learning these important things about carolinastory.com
Visit carolinastory.comWe analyzed Carolinastory.com page load time and found that the first response time was 114 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
carolinastory.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value40.6 s
0/100
25%
Value15.0 s
1/100
10%
Value2,630 ms
4/100
30%
Value0
100/100
15%
Value27.4 s
0/100
10%
114 ms
112 ms
106 ms
102 ms
119 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 (678 ms) relates to the external source Images.squarespace-cdn.com.
Page size can be reduced by 381.8 kB (4%)
9.9 MB
9.6 MB
In fact, the total size of Carolinastory.com main page is 9.9 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. 50% of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.
Potential reduce by 314.3 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 314.3 kB or 91% of the original size.
Potential reduce by 60.0 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. Carolina Story images are well optimized though.
Potential reduce by 7.3 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.
Potential reduce by 166 B
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 has all CSS files already compressed.
Number of requests can be reduced by 15 (63%)
24
9
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.
www.carolinastory.com
114 ms
64N4Pri4dtDoOmKZrA2QCVIcYyRYtAMA5b_RHqNGk33fezq2fFHN4UJLFRbh52jhWDjDZ2MXFhFqZQmyFesKw2Su5QMt52iRZg7AMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0jhBkdhUTdcBDieNkpPuRdhulO1FUiABkZWF3jAF8OcFzdP37O1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CjhBkdhUTdcBDieNkpPuRdhulO1FUiABkZWF3jAF8OcFzdPURjW4zde80jWFXda4oOcFzdPUCdhFydeyzSabCSaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0dcmXOYiaikoySkolZPUaiaS0jhBkdhUTdcBDieNkpPuRdhulO1FUiABkZWF3jAF8OcFzdPUaiaS0jhBkdhUTdcBDieNkpPoRdhXCiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXK2csyp1TCZPuudc8RjWF8H6GJRHjfIMMjMKMfH6GJK7jfIMMjMkMfH6GJKHjfIMMjgkMfqMYNcVPpg6.js
112 ms
css2
106 ms
legacy.js
102 ms
modern.js
119 ms
extract-css-runtime-2ab13720cc67772770c0-min.en-US.js
103 ms
extract-css-moment-js-vendor-f36b6dc9867ad0b8d0a8-min.en-US.js
231 ms
cldr-resource-pack-a682f7ad337741eb05d6-min.en-US.js
107 ms
common-vendors-stable-f9df4447a2af25df5875-min.en-US.js
248 ms
common-vendors-3d0896f3bf52a6ab42d9-min.en-US.js
248 ms
common-f4a4668e04903989544d-min.en-US.js
272 ms
commerce-cd4367ac539d1179c6df-min.en-US.js
247 ms
commerce-af8809f2481c48376f6a-min.en-US.css
118 ms
performance-5c471d9ec4c3660675d5-min.en-US.js
123 ms
site.css
127 ms
static.css
98 ms
site-bundle.461357a181df7ddcd970264c877fd49f.js
110 ms
fbevents.js
253 ms
CS-COMM-Logo.png
275 ms
7D94CB82-506B-41BA-AF08-5B65306F0377.png
678 ms
colors+of+my+mind.png
524 ms
CS-COMM-Cover-3000x3000.jpeg
505 ms
CS-COMM-Mockup-Vinyl-v2-3x2.png
655 ms
CS-COMM-Logo.png
552 ms
d
43 ms
d
89 ms
d
151 ms
p.gif
21 ms
carolinastory.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
carolinastory.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
carolinastory.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carolinastory.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Carolinastory.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
carolinastory.com
Open Graph description is not detected on the main page of Carolina Story. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: