5.5 sec in total
32 ms
907 ms
4.6 sec
Click here to check amazing Economist content. Otherwise, check out these important facts you probably never knew about economist.co.uk
Get in-depth global news and analysis. Our coverage spans world politics, business, tech, culture and more. Subscribe for free trial.
Visit economist.co.ukWe analyzed Economist.co.uk page load time and found that the first response time was 32 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
economist.co.uk performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value2.7 s
85/100
25%
Value8.0 s
21/100
10%
Value15,750 ms
0/100
30%
Value0.163
72/100
15%
Value40.2 s
0/100
10%
32 ms
408 ms
60 ms
56 ms
100 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Economist.co.uk, 2% (2 requests) were made to Cmp-cdn.p.aws.economist.com and 1% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (408 ms) relates to the external source Economist.com.
Page size can be reduced by 520.2 kB (6%)
8.7 MB
8.2 MB
In fact, the total size of Economist.co.uk main page is 8.7 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. Only a small number of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.
Potential reduce by 516.4 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 516.4 kB or 85% of the original size.
Potential reduce by 3.1 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. Economist images are well optimized though.
Potential reduce by 403 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 192 B
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. Economist.co.uk has all CSS files already compressed.
Number of requests can be reduced by 25 (32%)
79
54
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 26 to 1 for JavaScripts and as a result speed up the page load time.
www.economist.com
32 ms
www.economist.com
408 ms
2f2737c89f93e9b6.css
60 ms
30605e73dd3f3fe5.css
56 ms
polyfills-c67a75d1b6f99dc8.js
100 ms
economist.config.js
54 ms
cmp.min.js
55 ms
19440972562.js
126 ms
webpack-7d8902e9d31a09a9.js
99 ms
framework-314c182fa7e2bf37.js
52 ms
main-62e698d1a440924b.js
120 ms
_app-f7765463fc30bbd3.js
122 ms
109fbaa8-72c897bb4087382f.js
123 ms
d6e1aeb5-8ae8dd40035ccd02.js
146 ms
423ae6dd-f3494bfb40db0360.js
123 ms
2153-c05314930d8723fc.js
144 ms
9777-fd7ece7031364850.js
144 ms
7192-c69306f0cd7a2c88.js
150 ms
2829-0f67ef6013ffd622.js
153 ms
8696-000c67c496b6abe0.js
152 ms
4338-b5d93b43962a4819.js
151 ms
7666-2786981b01e7b09e.js
160 ms
6822-46a4e203e4883803.js
164 ms
9375-b7356b686e79987f.js
160 ms
9610-b47fb4a50974af47.js
160 ms
index-39168d5922473482.js
161 ms
_buildManifest.js
164 ms
_ssgManifest.js
161 ms
20240701_drp018.png
146 ms
20240608_drp001.png
150 ms
20240608_drp008.png
147 ms
20240824_STP002.jpg
157 ms
20240824_LDP001.jpg
157 ms
1843_20240819_1843_PARA_TEAS.jpg
173 ms
20240824_FND004.jpg
177 ms
20240824_BRD002.jpg
236 ms
20240824_FNP506.jpg
179 ms
20240824_LDD001.jpg
188 ms
20240824_USP512.jpg
189 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
87 ms
20240723_OPD002.jpg
197 ms
20240824_EUP506.jpg
211 ms
20230624_WOT919.png
229 ms
20240818_EUP599.jpg
164 ms
20240824_ASP002.jpg
142 ms
20240824_USP505.jpg
144 ms
20240824_MAP001.jpg
159 ms
20240824_BRP003.jpg
153 ms
20240819_BID001.jpg
151 ms
20240824_EUP002.jpg
144 ms
20240824_LDD002.jpg
145 ms
20240824_FND002.jpg
167 ms
20240810_LDD002.jpg
150 ms
20240824_MAD001.jpg
158 ms
20240817_FNP502.jpg
159 ms
20240817_MAD001.jpg
160 ms
20240824_EUP503.jpg
184 ms
20230805_CUP502.jpg
169 ms
20220820_CUP005.jpg
175 ms
20240824_IRP001.jpg
182 ms
20240817_WBP002.jpg
180 ms
20240817_STP501.jpg
180 ms
20240817_BLP508.jpg
193 ms
20240810_STP502.jpg
199 ms
20240810_CUP001.jpg
193 ms
1843_20240722_1843_Taylor-TEAS.jpg
202 ms
1843_20240722_1843_2024-PB-TEAS.jpg
213 ms
1843_20240719_1843_BARGHOUTI_TEASER.jpg
189 ms
20240824_BRP501.jpg
203 ms
20240810_AMP504.jpg
190 ms
20240817_BLP506.jpg
202 ms
20240720_ABD001.jpg
191 ms
20240727_ABD001.jpg
192 ms
20240810_ABD001.jpg
192 ms
20240824_DE_US.jpg
182 ms
20240817_STP503.jpg
161 ms
20240824_PDP515.jpg
166 ms
20240824_WOT813.png
174 ms
20240824_BLP506.jpg
174 ms
20240817_BLP512.jpg
173 ms
main.js
76 ms
economist.co.uk accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
economist.co.uk 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
economist.co.uk 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 Economist.co.uk 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 Economist.co.uk 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.
economist.co.uk
Open Graph data is detected on the main page of Economist. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: