2.7 sec in total
234 ms
846 ms
1.6 sec
Visit counternotions.com now to see the best up-to-date Counternotions content for United States and also check out these interesting facts you probably never knew about counternotions.com
(by Kontra)
Visit counternotions.comWe analyzed Counternotions.com page load time and found that the first response time was 234 ms and then it took 2.5 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.
counternotions.com performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value1.4 s
100/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0.026
100/100
15%
Value0.7 s
100/100
10%
234 ms
101 ms
118 ms
128 ms
142 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Counternotions.com, 59% (43 requests) were made to Counternotions.files.wordpress.com and 10% (7 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (322 ms) relates to the external source Counternotions.files.wordpress.com.
Page size can be reduced by 380.5 kB (17%)
2.3 MB
1.9 MB
In fact, the total size of Counternotions.com main page is 2.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. 70% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 44.2 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 44.2 kB or 71% of the original size.
Potential reduce by 2 B
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. Counternotions images are well optimized though.
Potential reduce by 304.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 304.3 kB or 77% of the original size.
Potential reduce by 32.1 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. Counternotions.com needs all CSS files to be minified and compressed as it can save up to 32.1 kB or 78% of the original size.
Number of requests can be reduced by 18 (35%)
52
34
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Counternotions. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
counternotions.com
234 ms
101 ms
css
118 ms
css
128 ms
css
142 ms
109 ms
global.css
97 ms
109 ms
s2.wp.com
110 ms
gprofiles.js
111 ms
wpgroho.js
107 ms
jetpack-carousel.css
107 ms
tiled-gallery.css
95 ms
106 ms
widgets.js
131 ms
94 ms
w.js
76 ms
merriweather.css
9 ms
global-print.css
3 ms
cnlogo3702x.png
122 ms
hovercard.css
57 ms
services.css
82 ms
itunes.jpg
68 ms
itunes2.jpg
60 ms
nav-icons-twitter2x.png
18 ms
realnetworks.jpg
19 ms
nokia.jpg
18 ms
paypal.jpg
18 ms
article1.jpg
37 ms
articleorad.jpg
47 ms
purpose.jpg
46 ms
cnnfortune.jpg
46 ms
nav-icons-rss2x.png
56 ms
nav-icons-twitter2x.png
57 ms
nav-icons-email2x.png
56 ms
nav-icons-home882x.png
56 ms
nav-icons-rss882x.png
56 ms
nav-icons-twitter882x.png
57 ms
nav-icons-email882x.png
59 ms
FrmKYbbiMrxVeJO6lA8KEvesZW2xOQ-xsNqO47m55DA.ttf
67 ms
Noticons.svg
28 ms
BaABdRAi2AAAA
4 ms
merriweather-bold-webfont.ttf
39 ms
merriweather-regular-webfont.ttf
54 ms
merriweather-light-webfont.ttf
45 ms
g.gif
26 ms
g.gif
24 ms
g.gif
24 ms
twitterbird.png
44 ms
nav-icons-twitter2x.png
46 ms
nokia.jpg
52 ms
realnetworks.jpg
52 ms
paypal.jpg
52 ms
dcohen.jpg
48 ms
app1.jpg
47 ms
comcastbanner.jpg
47 ms
app2.jpg
52 ms
pro.jpg
71 ms
cons2.jpg
54 ms
article1.jpg
46 ms
soros1.jpg
44 ms
disclaimer.jpg
41 ms
purpose.jpg
61 ms
cnnfortune.jpg
59 ms
articleorad.jpg
322 ms
nav-icons-home2x.png
56 ms
nav-icons-rss2x.png
49 ms
nav-icons-email2x.png
48 ms
nav-icons-home882x.png
49 ms
nav-icons-rss882x.png
49 ms
nav-icons-twitter2x.png
84 ms
nav-icons-twitter882x.png
46 ms
nav-icons-email882x.png
46 ms
counternotions.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
counternotions.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
counternotions.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Counternotions.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Counternotions.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.
counternotions.com
Open Graph description is not detected on the main page of Counternotions. 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: