1.8 sec in total
529 ms
1.1 sec
182 ms
Visit thecharlotteweekly.com now to see the best up-to-date Thecharlotteweekly content for United States and also check out these interesting facts you probably never knew about thecharlotteweekly.com
About the community, for the community
Visit thecharlotteweekly.comWe analyzed Thecharlotteweekly.com page load time and found that the first response time was 529 ms and then it took 1.3 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.
thecharlotteweekly.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value10.1 s
0/100
25%
Value16.2 s
0/100
10%
Value21,840 ms
0/100
30%
Value0.562
12/100
15%
Value30.4 s
0/100
10%
529 ms
23 ms
13 ms
27 ms
38 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 67% of them (30 requests) were addressed to the original Thecharlotteweekly.com, 7% (3 requests) were made to S.gravatar.com and 4% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (529 ms) belongs to the original domain Thecharlotteweekly.com.
Page size can be reduced by 295.6 kB (36%)
819.7 kB
524.1 kB
In fact, the total size of Thecharlotteweekly.com main page is 819.7 kB. 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 438.3 kB which makes up the majority of the site volume.
Potential reduce by 43.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 43.7 kB or 79% of the original size.
Potential reduce by 30.7 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. Thecharlotteweekly images are well optimized though.
Potential reduce by 115.1 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 115.1 kB or 58% of the original size.
Potential reduce by 106.2 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. Thecharlotteweekly.com needs all CSS files to be minified and compressed as it can save up to 106.2 kB or 83% of the original size.
Number of requests can be reduced by 17 (40%)
42
25
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thecharlotteweekly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
thecharlotteweekly.com
529 ms
wp-emoji-release.min.js
23 ms
style.css
13 ms
jetpack.css
27 ms
jquery.js
38 ms
jquery-migrate.min.js
18 ms
style_customizd.css
36 ms
MyFontsWebfontsKit.css
33 ms
soliloquy.css
107 ms
devicepx-jetpack.js
4 ms
gprofiles.js
110 ms
wpgroho.js
32 ms
wp-embed.min.js
32 ms
soliloquy-min.js
107 ms
e-201611.js
5 ms
ga.js
34 ms
2bf831
52 ms
slot_char.jpg
160 ms
SouthCharlotte-logo.jpg
159 ms
trans-1x1.png
157 ms
IMG_6488-420x400.jpg
154 ms
holder.gif
47 ms
IMG_1854-332x190.jpg
154 ms
slice.jpg
157 ms
CatholicWinsStates-332x190.jpg
155 ms
realwifes2-332x190.jpg
156 ms
Courtney-Schultz-mug-for-web-150x150.jpg
157 ms
__utm.gif
158 ms
lines.png
135 ms
search.png
135 ms
all.js
112 ms
hovercard.css
69 ms
services.css
117 ms
preloader.gif
46 ms
calendar2-420x400.jpg
52 ms
sedgefield-420x400.jpg
68 ms
IMG_6869-2-420x400.jpg
91 ms
DSCN0106-420x400.jpg
90 ms
donate-gold.gif
66 ms
2BF831_0_0.woff
159 ms
g.gif
23 ms
250 ms
xd_arbiter.php
36 ms
xd_arbiter.php
64 ms
2BF831_0_0.ttf
149 ms
thecharlotteweekly.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
thecharlotteweekly.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
thecharlotteweekly.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Thecharlotteweekly.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 Thecharlotteweekly.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.
thecharlotteweekly.com
Open Graph data is detected on the main page of Thecharlotteweekly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: