5.1 sec in total
20 ms
793 ms
4.3 sec
Click here to check amazing Economist content for United States. Otherwise, check out these important facts you probably never knew about economist.com
Get in-depth global news and analysis. Our coverage spans world politics, business, tech, culture and more. Subscribe for free trial.
Visit economist.comWe analyzed Economist.com page load time and found that the first response time was 20 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
economist.com performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value2.2 s
94/100
25%
Value11.8 s
4/100
10%
Value16,760 ms
0/100
30%
Value0.213
58/100
15%
Value39.6 s
0/100
10%
20 ms
254 ms
61 ms
67 ms
93 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 92% of them (69 requests) were addressed to the original Economist.com, 3% (2 requests) were made to Cdn.tinypass.com and 3% (2 requests) were made to Cmp-cdn.p.aws.economist.com. The less responsive or slowest element that took the longest time to load (361 ms) belongs to the original domain Economist.com.
Page size can be reduced by 483.3 kB (6%)
7.8 MB
7.3 MB
In fact, the total size of Economist.com main page is 7.8 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. 85% 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 6.2 MB which makes up the majority of the site volume.
Potential reduce by 482.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 482.9 kB or 85% of the original size.
Potential reduce by 0 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. Economist images are well optimized though.
Potential reduce by 329 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 58 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.com has all CSS files already compressed.
Number of requests can be reduced by 28 (38%)
73
45
The browser has sent 73 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 29 to 1 for JavaScripts and as a result speed up the page load time.
economist.com
20 ms
www.economist.com
254 ms
a80ec2eae7adc264.css
61 ms
30605e73dd3f3fe5.css
67 ms
polyfills-c67a75d1b6f99dc8.js
93 ms
tinypass.min.js
126 ms
economist.config.js
145 ms
cmp.min.js
144 ms
19440972562.js
122 ms
webpack-3253630fbc951c4a.js
64 ms
framework-10fac88913917d91.js
215 ms
main-4a5f0ca05551bf15.js
121 ms
_app-258542d6e59ba143.js
116 ms
109fbaa8-d71be12360a01938.js
225 ms
d6e1aeb5-bba70d05db3f9346.js
236 ms
423ae6dd-60dbca899e0d8ae7.js
231 ms
153-81cd04d38be18b05.js
237 ms
956-963533113c6e4da2.js
233 ms
626-ff821e29b1b0c1fa.js
234 ms
829-6387859aeeae655d.js
232 ms
696-fa9b91f1b050e183.js
243 ms
338-c51227e3eb7e0c03.js
246 ms
726-bb64096d99177cf3.js
242 ms
472-0e83d4c7db252da8.js
252 ms
224-4bba9acbb7c0fe3a.js
252 ms
413-06ba9c33c36541d8.js
254 ms
610-b2a048d7783dadef.js
255 ms
index-162f2e2387416b5d.js
255 ms
_buildManifest.js
255 ms
_ssgManifest.js
257 ms
20240504_LDD020.jpg
247 ms
20240504_LDD001.jpg
248 ms
1843_20240503_1843_STUDPROT-Teas.jpg
249 ms
20240504_WBP502.jpg
247 ms
20240504_CND000.jpg
250 ms
20240427_BLP504.jpg
361 ms
20240302_WOT929.png
358 ms
20240504_EUP001.jpg
354 ms
20240504_OPD002.jpg
355 ms
20240504_CNP001.jpg
358 ms
vedd3670a3b1c4e178fdfb0cc912d969e1713874337387
217 ms
20240405_LDD004.jpg
348 ms
20240504_FND000.jpg
316 ms
20240504_WBP001.jpg
319 ms
20240504_FNP001.jpg
298 ms
20240427_WOT010.png
265 ms
20240504_EUP502.jpg
265 ms
20240504_ASP001.jpg
285 ms
20240427_LDD001.jpg
280 ms
piano.es5.js
113 ms
a19205964212.html
201 ms
20240420_OPD010.jpg
183 ms
20240504_MAP503.jpg
175 ms
20240427_MAP002.jpg
172 ms
20240427_MAP001.jpg
171 ms
20240504_USD000.jpg
183 ms
20240504_USP508.jpg
188 ms
20240413_WOT994.png
176 ms
20240504_CUP503.jpg
193 ms
20240504_OBP001.jpg
177 ms
20240427_STD002.jpg
172 ms
20240504_CNP502.jpg
191 ms
20240504_ASP004.jpg
193 ms
20240504_USP002.jpg
195 ms
20240504_AMD001.jpg
198 ms
20240504_DE_US.jpg
195 ms
20240511_SRR.jpg
218 ms
20240504_FBD001.jpg
226 ms
20240427_AMP001.jpg
232 ms
20240504_PDP509.jpg
229 ms
20231209_BID001.jpg
223 ms
20240504_WOF958.png
218 ms
20240504_OPD003.jpg
145 ms
20240504_BLP512.jpg
168 ms
main.js
45 ms
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
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
Image elements do not have [alt] attributes
economist.com 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
Page has valid source maps
economist.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.
economist.com
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: