Tools & Wizards About Us
carolinastory.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

carolinastory.com

Carolina Story

Page Load Speed

1 sec in total

First Response

83 ms

Resources Loaded

832 ms

Page Rendered

94 ms

carolinastory.com screenshot

About Website

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.com

Key Findings

We analyzed Carolinastory.com page load time and found that the first response time was 83 ms and then it took 926 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

carolinastory.com performance score

16

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (15%)

Content Size

11.3 MB

After Optimization

9.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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 Breakdown

Number of requests can be reduced by 15 (63%)

Requests Now

24

After Optimization

9

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

www.carolinastory.com

www.carolinastory.com

83 ms

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

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

67 ms

css2

css2

84 ms

legacy.js

legacy.js

57 ms

modern.js

modern.js

74 ms

extract-css-runtime-a3a2741fb711753f48de-min.en-US.js

extract-css-runtime-a3a2741fb711753f48de-min.en-US.js

57 ms

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

80 ms

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

71 ms

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

77 ms

common-vendors-8db852056516153189c0-min.en-US.js

common-vendors-8db852056516153189c0-min.en-US.js

81 ms

common-11e18ea65739225beb15-min.en-US.js

common-11e18ea65739225beb15-min.en-US.js

166 ms

commerce-c53d89ca07a1579bd8e7-min.en-US.js

commerce-c53d89ca07a1579bd8e7-min.en-US.js

169 ms

commerce-fb908395734262466dc9-min.en-US.css

commerce-fb908395734262466dc9-min.en-US.css

83 ms

performance-74d24f5c2adcf3b8ee8a-min.en-US.js

performance-74d24f5c2adcf3b8ee8a-min.en-US.js

165 ms

site.css

site.css

72 ms

static.css

static.css

61 ms

site-bundle.11fff701a22dbd232e9127391845b3e2.js

site-bundle.11fff701a22dbd232e9127391845b3e2.js

59 ms

fbevents.js

fbevents.js

155 ms

CS-COMM-Logo.png

CS-COMM-Logo.png

235 ms

7D94CB82-506B-41BA-AF08-5B65306F0377.png

7D94CB82-506B-41BA-AF08-5B65306F0377.png

561 ms

colors+of+my+mind.png

colors+of+my+mind.png

397 ms

CS-COMM-Cover-3000x3000.jpeg

CS-COMM-Cover-3000x3000.jpeg

340 ms

CS-COMM-Mockup-Vinyl-v2-3x2.png

CS-COMM-Mockup-Vinyl-v2-3x2.png

523 ms

CS-COMM-Logo.png

CS-COMM-Logo.png

317 ms

d

d

54 ms

d

d

58 ms

d

d

58 ms

p.gif

p.gif

28 ms

Accessibility Review

carolinastory.com accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

carolinastory.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

carolinastory.com SEO score

89

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: