2.5 sec in total
172 ms
2.3 sec
59 ms
Visit charlestonmercury.com now to see the best up-to-date Charleston Mercury content for United States and also check out these interesting facts you probably never knew about charlestonmercury.com
Homepage for the Charleston Mercury — news, arts, culture, history and more in the South Carolina Lowcountry
Visit charlestonmercury.comWe analyzed Charlestonmercury.com page load time and found that the first response time was 172 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
charlestonmercury.com performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value6.4 s
10/100
25%
Value8.6 s
17/100
10%
Value1,510 ms
14/100
30%
Value0
100/100
15%
Value16.8 s
5/100
10%
172 ms
113 ms
171 ms
1227 ms
163 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Charlestonmercury.com, 33% (16 requests) were made to Static.parastorage.com and 33% (16 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Polyfill-fastly.io.
Page size can be reduced by 1.0 MB (57%)
1.8 MB
785.1 kB
In fact, the total size of Charlestonmercury.com main page is 1.8 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. 35% of websites need less resources to load. HTML takes 999.4 kB which makes up the majority of the site volume.
Potential reduce by 813.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. 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 813.0 kB or 81% of the original size.
Potential reduce by 16.9 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. Charleston Mercury images are well optimized though.
Potential reduce by 193.0 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 193.0 kB or 37% of the original size.
Number of requests can be reduced by 14 (40%)
35
21
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Charleston Mercury. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
www.charlestonmercury.com
172 ms
minified.js
113 ms
focus-within-polyfill.js
171 ms
polyfill.min.js
1227 ms
7324.chunk.min.js
163 ms
3013.chunk.min.js
164 ms
post-list-pro-gallery.chunk.min.js
163 ms
thunderbolt-commons.f07ad842.bundle.min.js
105 ms
main.aba140a9.bundle.min.js
105 ms
main.renderer.1d21f023.bundle.min.js
106 ms
lodash.min.js
110 ms
react.production.min.js
107 ms
react-dom.production.min.js
110 ms
siteTags.bundle.min.js
108 ms
wix-perf-measure.umd.min.js
108 ms
35e8c7_dba0a2bc437f481daa741f44669f24c8.png
210 ms
35e8c7_3b168297cbf7447da990857e582b3227~mv2.png
558 ms
ce1750_f28ef5de7f6f4854b7859fc7bcee19dc~mv2.jpeg
315 ms
ce1750_f28ef5de7f6f4854b7859fc7bcee19dc~mv2.jpeg
350 ms
ce1750_4eab58f78e964367b06dbf3fe0a5325f~mv2.jpg
398 ms
ce1750_4eab58f78e964367b06dbf3fe0a5325f~mv2.jpg
599 ms
ce1750_1923390d4b4b4b748fea67439e27ebd5~mv2.png
407 ms
ce1750_39d81b09c29b4a5cb7d4a7a396ea933d~mv2.jpg
494 ms
ce1750_39d81b09c29b4a5cb7d4a7a396ea933d~mv2.jpg
485 ms
ce1750_08e1b958f7b841319c97e405c629db66~mv2.jpg
595 ms
ce1750_08e1b958f7b841319c97e405c629db66~mv2.jpg
608 ms
ce1750_2fc0247dd3ba457484854a79dd91f006~mv2.jpg
688 ms
ce1750_2fc0247dd3ba457484854a79dd91f006~mv2.jpg
638 ms
ce1750_364aae04c8b441c1a07367d996a68266~mv2.jpg
719 ms
ce1750_364aae04c8b441c1a07367d996a68266~mv2.jpg
787 ms
35e8c7_576064fdc9cd412d822ee69ab5b060e8.png
755 ms
bundle.min.js
104 ms
114 ms
117 ms
109 ms
108 ms
108 ms
106 ms
148 ms
142 ms
143 ms
141 ms
143 ms
147 ms
deprecation-en.v5.html
9 ms
bolt-performance
26 ms
deprecation-style.v5.css
11 ms
right-arrow.svg
11 ms
charlestonmercury.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
charlestonmercury.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
Browser errors were logged to the console
Page has valid source maps
charlestonmercury.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Charlestonmercury.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 Charlestonmercury.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.
charlestonmercury.com
Open Graph data is detected on the main page of Charleston Mercury. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: