5.7 sec in total
323 ms
935 ms
4.5 sec
Click here to check amazing Amp Economist content for United States. Otherwise, check out these important facts you probably never knew about amp.economist.com
Authoritative global news and analysis. Offering fair-minded, fact-checked coverage of world politics, economics, business, science and tech, culture and more
Visit amp.economist.comWe analyzed Amp.economist.com page load time and found that the first response time was 323 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
amp.economist.com performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value2.6 s
87/100
25%
Value13.4 s
2/100
10%
Value11,220 ms
0/100
30%
Value0.578
12/100
15%
Value35.3 s
0/100
10%
323 ms
56 ms
49 ms
55 ms
100 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Amp.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 (442 ms) relates to the external source Economist.com.
Page size can be reduced by 436.2 kB (7%)
6.3 MB
5.8 MB
In fact, the total size of Amp.economist.com main page is 6.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. 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 5.0 MB which makes up the majority of the site volume.
Potential reduce by 435.6 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 435.6 kB or 84% of the original size.
Potential reduce by 44 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. Amp Economist images are well optimized though.
Potential reduce by 457 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 147 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. Amp.economist.com has all CSS files already compressed.
Number of requests can be reduced by 24 (33%)
73
49
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amp 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 25 to 1 for JavaScripts and as a result speed up the page load time.
www.economist.com
323 ms
825c4a68ff9a007a.css
56 ms
1d5cf309c73bd4bb.css
49 ms
polyfills-c67a75d1b6f99dc8.js
55 ms
tinypass.min.js
100 ms
economist.config.js
92 ms
cmp.min.js
55 ms
19440972562.js
221 ms
lux.js
46 ms
webpack-2355ad8b8c6e2a8e.js
46 ms
framework-73b8966a3c579ab0.js
46 ms
main-d8258f1444c7428a.js
95 ms
_app-f232b604d35f5fde.js
96 ms
109fbaa8-b000ae6d99bd29ad.js
98 ms
153-a6d823c781a12c05.js
118 ms
956-2c575ecef7010ac0.js
119 ms
813-a5d0e625ebe0d0ed.js
120 ms
696-1003bd73e50338da.js
122 ms
357-3d4d86a8c85526af.js
121 ms
236-f57041f25a2c9011.js
131 ms
400-e66ad66fb915ef72.js
129 ms
366-edeb0d1715508f08.js
132 ms
index-117fe64d72438def.js
136 ms
_buildManifest.js
137 ms
_ssgManifest.js
143 ms
720x720_essential-india.png
343 ms
namethe_intelligence.png
319 ms
usib_la_112x1124x_0.png
351 ms
20240203_FNP502.jpg
316 ms
20240203_EUP501.jpg
314 ms
20240127_BRD000.jpg
319 ms
20240203_BRP503.jpg
316 ms
20240203_ASP501.jpg
317 ms
20240203_CUP501.jpg
341 ms
20240203_MAP501.jpg
336 ms
20240127_MAP501.jpg
336 ms
20240127_MAP002.jpg
337 ms
20240203_BLP902.jpg
342 ms
20240127_USP004.jpg
338 ms
20240127_IRP001.jpg
337 ms
v84a3a4012de94ce1a686ba8c167c359c1696973893317
111 ms
20240127_LDD001.jpg
332 ms
20240127_USP002.jpg
310 ms
20240127_USP510.jpg
320 ms
20240120_LDD003.jpg
312 ms
20240120_STP003.jpg
304 ms
20240127_PDP505.jpg
270 ms
20240203_CNP501.jpg
268 ms
20240203_BRP501.jpg
271 ms
20240127_BLP904.jpg
266 ms
piano.es5.js
31 ms
20240113_WBD001.jpg
243 ms
20240203_AMP501.jpg
247 ms
20240203_FNP501.jpg
267 ms
20230114_OPD011.jpg
280 ms
20230429_WOP001.jpg
294 ms
20230701_WOP953.jpg
277 ms
20240127_LDD002.jpg
267 ms
20240127_WBD001.jpg
267 ms
20240127_MAP001.jpg
294 ms
twa_2024_cover_1.jpg
442 ms
20240127_LDP501.jpg
302 ms
a19205964212.html
72 ms
20240127_DE_US.jpg
114 ms
20240203_TQR.jpg
206 ms
20240203_PDP502.jpg
132 ms
20240125_FLP001.jpg
153 ms
1843_20240130_1843_Sherpas_T.jpg
143 ms
20240127_STP001.jpg
156 ms
20240127_BID001.jpg
256 ms
20240203_WOT960.png
144 ms
20240203_BLP517.jpg
158 ms
20240120_BLP517.jpg
180 ms
main.js
92 ms
amp.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
amp.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
amp.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 Amp.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 Amp.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.
amp.economist.com
Open Graph data is detected on the main page of Amp Economist. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: