2.4 sec in total
65 ms
2.2 sec
206 ms
Visit thecharlottepost.com now to see the best up-to-date The Charlotte Post content for United States and also check out these interesting facts you probably never knew about thecharlottepost.com
Leading source of News affecting African American community in Charlotte North Carolina.
Visit thecharlottepost.comWe analyzed Thecharlottepost.com page load time and found that the first response time was 65 ms and then it took 2.4 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.
thecharlottepost.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value10.0 s
0/100
25%
Value9.2 s
13/100
10%
Value3,160 ms
2/100
30%
Value0.028
100/100
15%
Value16.9 s
5/100
10%
65 ms
595 ms
37 ms
36 ms
60 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 31% of them (46 requests) were addressed to the original Thecharlottepost.com, 7% (10 requests) were made to Pbs.twimg.com and 6% (9 requests) were made to D234qeqk649blg.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Thecharlottepost.com.
Page size can be reduced by 2.1 MB (54%)
4.0 MB
1.8 MB
In fact, the total size of Thecharlottepost.com main page is 4.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 137.9 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 137.9 kB or 77% of the original size.
Potential reduce by 633.6 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. Obviously, The Charlotte Post needs image optimization as it can save up to 633.6 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 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.1 MB or 68% of the original size.
Potential reduce by 287.5 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. Thecharlottepost.com needs all CSS files to be minified and compressed as it can save up to 287.5 kB or 84% of the original size.
Number of requests can be reduced by 67 (47%)
142
75
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of The Charlotte Post. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
thecharlottepost.com
65 ms
www.thecharlottepost.com
595 ms
css
37 ms
style_revised.css
36 ms
font_awesome.css
60 ms
jquery.min.js
42 ms
jquery-ui.min.js
46 ms
jquery.loader.php
178 ms
addthis_widget.js
26 ms
jquery.youtubeplaylist.js
65 ms
adsbygoogle.js
29 ms
in.js
28 ms
screen-mobile.css
29 ms
screen-tablet.css
29 ms
www.liqwid.net
275 ms
analytics.js
44 ms
80_black.png
46 ms
logo.png
105 ms
headbar_mobile.png
89 ms
fs_535.jpg
90 ms
300x300_service.gif
49 ms
mm_tablet.png
49 ms
slide1.gif
230 ms
slide2.gif
288 ms
slide3.gif
289 ms
slide4.gif
344 ms
wb_Ashley-Mahoney.gif
120 ms
calendar.png
228 ms
broadcast.png
287 ms
fs_582.png
377 ms
fs_520.png
395 ms
fs_647.png
398 ms
fs_656.png
397 ms
fs_534.jpg
344 ms
ca-pub-8257785834822353.js
99 ms
zrt_lookup.html
167 ms
show_ads_impl.js
120 ms
collect
76 ms
section_bg.jpg
350 ms
slide_selected.png
352 ms
index.php
795 ms
all.js
68 ms
widgets.js
233 ms
zsM3eHRiueA
233 ms
secureAnonymousFramework
174 ms
footer_bg.png
342 ms
scroller.png
358 ms
index.php
855 ms
index.php
805 ms
index.php
926 ms
index.php
1080 ms
index.php
927 ms
index.php
994 ms
index.php
993 ms
300lo.json
131 ms
fontawesome-webfont.woff
877 ms
sh.8e5f85691f9aaa082472a194.html
88 ms
ads
219 ms
113 ms
osd.js
29 ms
xd_arbiter.php
235 ms
xd_arbiter.php
455 ms
ads
197 ms
search.jpg
774 ms
lightbox-close.jpg
726 ms
headbar_corner.png
732 ms
headbar_corner2.png
752 ms
feed_icon_fb.png
781 ms
feed_icon_tw.png
774 ms
feed_icon_yt.png
805 ms
feed_icon_in.png
785 ms
layers.e5ea973510bf60b3db41.js
27 ms
www-embed-player-vflfNyN_r.css
59 ms
www-embed-player.js
70 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
169 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
87 ms
ad_status.js
73 ms
71 ms
afr.php
117 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
65 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
98 ms
4844606755803035677
94 ms
abg.js
95 ms
m_js_controller.js
102 ms
googlelogo_color_112x36dp.png
93 ms
ajs.php
90 ms
syndication
122 ms
369455599450193920
172 ms
ajs.php
72 ms
maserati_dealershipbrand_02_728x90.html
44 ms
s
21 ms
x_button_blue2.png
22 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
2 ms
adUtils_v1.js
16 ms
edge.6.0.0.min.js
36 ms
jstag
83 ms
lg.php
20 ms
lg.php
36 ms
maserati_dealershipbrand_02_728x90_edge.js
10 ms
match.aspx
33 ms
maserati_dealershipbrand_02_728x90_edge.js
5 ms
TweenMax.min.js
51 ms
TweenMax.min.js
51 ms
vuTBEhQRUOQGE0wu.jpg
182 ms
proxy.jpg
186 ms
Cd9Qy86WAAAyTOW.jpg
186 ms
_GudWkWfypVCK6Md.jpg
244 ms
carImage.jpg
21 ms
mazText.svg
34 ms
mazLogo.svg
36 ms
mazShield.png
39 ms
acj
72 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
51 ms
Frutiger-Roman.woff
20 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
116 ms
acj
114 ms
x-xuGpY__normal.jpg
99 ms
-cdvGEqG_normal.jpg
113 ms
SI7ZLPY3_normal.jpg
132 ms
afrosplash_normal.jpg
131 ms
Cd9Iha2UMAA7bN1.jpg:small
131 ms
Cd8yazjWAAA9VSQ.jpg:small
129 ms
Cd8nxB7UsAEJAAV.jpg:small
142 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
24 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
71 ms
ajs.php
85 ms
468x60_01.jpg
14 ms
ajs.php
36 ms
lg.php
15 ms
match.aspx
13 ms
acj
67 ms
lg.php
13 ms
match.aspx
11 ms
acj
63 ms
proxy.jpg
104 ms
pd
27 ms
rr
33 ms
ri
40 ms
rr
33 ms
ri
35 ms
c0e256e2-8f26-dbe4-3b06-acda5671566c
39 ms
openx
11 ms
pixel
19 ms
openx
7 ms
sd
24 ms
sd
56 ms
sd
58 ms
sd
46 ms
sd
23 ms
jot.html
59 ms
thecharlottepost.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-hidden="true"] elements contain focusable descendents
[role]s are not contained by their required parent element
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
thecharlottepost.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
Page has valid source maps
thecharlottepost.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thecharlottepost.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Thecharlottepost.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
thecharlottepost.com
Open Graph description is not detected on the main page of The Charlotte Post. 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: