1.2 sec in total
42 ms
684 ms
477 ms
Click here to check amazing Debates Economist content for United States. Otherwise, check out these important facts you probably never knew about debates.economist.com
Get in-depth global news and analysis. Our coverage spans world politics, business, tech, culture and more. Subscribe for free trial.
Visit debates.economist.comWe analyzed Debates.economist.com page load time and found that the first response time was 42 ms and then it took 1.2 sec 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.
debates.economist.com performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value9.3 s
1/100
25%
Value14.3 s
1/100
10%
Value5,090 ms
0/100
30%
Value0.181
67/100
15%
Value22.7 s
1/100
10%
42 ms
10 ms
13 ms
13 ms
18 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 48% of them (24 requests) were addressed to the original Debates.economist.com, 10% (5 requests) were made to Tags.bluekai.com and 6% (3 requests) were made to Consent.truste.com. The less responsive or slowest element that took the longest time to load (225 ms) relates to the external source Consent.truste.com.
Page size can be reduced by 470.7 kB (31%)
1.5 MB
1.0 MB
In fact, the total size of Debates.economist.com main page is 1.5 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. 60% of websites need less resources to load. Images take 711.8 kB which makes up the majority of the site volume.
Potential reduce by 30.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. This page needs HTML code to be minified as it can gain 6.1 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 30.0 kB or 76% of the original size.
Potential reduce by 4.3 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. Debates Economist images are well optimized though.
Potential reduce by 309.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 309.1 kB or 63% of the original size.
Potential reduce by 127.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. Debates.economist.com needs all CSS files to be minified and compressed as it can save up to 127.2 kB or 47% of the original size.
Number of requests can be reduced by 26 (57%)
46
20
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Debates Economist. 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 from 6 to 1 for CSS and as a result speed up the page load time.
debates.economist.com
42 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
10 ms
css_51jAj5gdi1UOs7R7fNpxnR1JS3IteL-BeqIYPGrvaXk.css
13 ms
css_zAcZ9UfMhroMTiwBY2Nc7Tg6OnooHZLdswoO4Z7iMEc.css
13 ms
slick.css
18 ms
css_yx12vsxhwhB_95L-I_UtpMCRtGby97wHQulFe_FqsYs.css
19 ms
jquery.min.js
33 ms
js_IkgOrrVZK1UTp2HktvFi5vo1g7b25Muyr5GoySikuic.js
15 ms
js_H7q2xORKmR9AN8Qx5spKEIBp7R_wG2apAswJoCUZY7I.js
27 ms
js_JY0PLUW3vHNpoXL11sEziWjjUyejOcP-_kArn_JZWMk.js
27 ms
slick.min.js
24 ms
js_R9LA7-dwbAiHpk7xk09Qxz5-q3z7V-0xIrPlDZSb8Oo.js
25 ms
notice
175 ms
omniture.js
26 ms
ec-custom-fonts.css
33 ms
logo.svg
5 ms
me%20aug%202014.jpg
7 ms
deborah%20sherry%20small.PNG
7 ms
Jonathan-Cooper.jpg
8 ms
Helen%20Joyce%20Headshot%20Spring2015.jpg
7 ms
Gallop_Y_headshot.jpg
8 ms
Jensen_N_headshot.jpg
8 ms
ludwigsiegele.jpg
8 ms
crosby2.jpg
9 ms
schneier.jpg
9 ms
get
225 ms
NEW-DEBATE-ARTWORK-%5B3%5D.jpg
125 ms
utag.js
129 ms
page.js
89 ms
bk-coretag.js
89 ms
debates.economist.com
84 ms
smartphone%20hall%20FINAL.jpg
77 ms
2000X243%5BQUALITY90%5D_1.jpg
80 ms
42EX7spdjAA
21 ms
jYRfuyl2MAA=
22 ms
utag.6.js
10 ms
get
109 ms
gpt.js
7 ms
18452
72 ms
r2
13 ms
pubads_impl_81.js
15 ms
container.html
32 ms
adsct
122 ms
65 ms
2222
27 ms
16365
76 ms
55 ms
2981
48 ms
2981
75 ms
3096
16 ms
debates.economist.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
debates.economist.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
debates.economist.com SEO score
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 Debates.economist.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 Debates.economist.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.
debates.economist.com
Open Graph description is not detected on the main page of Debates Economist. 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: