4.4 sec in total
26 ms
946 ms
3.4 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
Get in-depth global news and analysis. Our coverage spans world politics, business, tech, culture and more. Subscribe for free trial.
Visit amp.economist.comWe analyzed Amp.economist.com page load time and found that the first response time was 26 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
amp.economist.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value2.3 s
93/100
25%
Value12.3 s
3/100
10%
Value5,090 ms
0/100
30%
Value0.155
74/100
15%
Value31.9 s
0/100
10%
26 ms
511 ms
44 ms
39 ms
67 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Amp.economist.com, 94% (74 requests) were made to Economist.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 (511 ms) relates to the external source Economist.com.
Page size can be reduced by 490.3 kB (6%)
7.7 MB
7.2 MB
In fact, the total size of Amp.economist.com main page is 7.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. 80% 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.4 MB which makes up the majority of the site volume.
Potential reduce by 486.1 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 486.1 kB or 84% of the original size.
Potential reduce by 3.6 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. Amp Economist images are well optimized though.
Potential reduce by 435 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 54 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 26 (34%)
77
51
The browser has sent 77 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 27 to 1 for JavaScripts and as a result speed up the page load time.
amp.economist.com
26 ms
www.economist.com
511 ms
f6e6ed8e7ebc7b79.css
44 ms
30605e73dd3f3fe5.css
39 ms
polyfills-c67a75d1b6f99dc8.js
67 ms
economist.config.js
66 ms
cmp.min.js
82 ms
19440972562.js
93 ms
wall-ui.js
79 ms
webpack-8b7577bff0ee9ca0.js
38 ms
framework-314c182fa7e2bf37.js
41 ms
main-62e698d1a440924b.js
88 ms
_app-eac91066f585d068.js
87 ms
109fbaa8-8372a1dc8cbca781.js
89 ms
d6e1aeb5-8ae8dd40035ccd02.js
91 ms
423ae6dd-f3494bfb40db0360.js
90 ms
7183-6db3e398ed8ead30.js
113 ms
6254-6863f9bc6827ab35.js
117 ms
7192-c69306f0cd7a2c88.js
116 ms
2829-0f67ef6013ffd622.js
115 ms
6399-ec2cc957777d0a8d.js
123 ms
8696-000c67c496b6abe0.js
122 ms
7666-f6e956eae5dbd578.js
129 ms
6822-54950a9ebd7cf36f.js
141 ms
9375-3e173e0e9380f583.js
129 ms
9610-b47fb4a50974af47.js
128 ms
index-07faea2b0460a1dc.js
142 ms
_buildManifest.js
129 ms
_ssgManifest.js
139 ms
20240925_drp034.png
251 ms
20240917_drp037.png
150 ms
20240701_drp018.png
163 ms
20240928_LDP002.jpg
165 ms
20240928_LDD002.jpg
161 ms
20240928_WBP506.jpg
168 ms
20240928_USD000.jpg
168 ms
20240928_WOT203.png
175 ms
20240928_EUP505.jpg
186 ms
20240928_WWP002.jpg
185 ms
20240928_WWP501.jpg
194 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
95 ms
20240928_WWD000.jpg
188 ms
20240928_MAP501.jpg
179 ms
20240921_MAP005.jpg
181 ms
20231021_BLP504.jpg
186 ms
20240928_USP001.jpg
174 ms
20240928_CUP001.jpg
188 ms
20240723_OPD002.jpg
168 ms
20240928_FNP001.jpg
169 ms
20240928_FND001.jpg
176 ms
20240928_EUP504.jpg
174 ms
20240928_CNP001.jpg
168 ms
20240928_ASP001.jpg
164 ms
20240921_LDD001.jpg
169 ms
20240921_TQD001.jpg
170 ms
20240921_STD003.jpg
177 ms
20240928_BRP501.jpg
176 ms
20240921_FBD001.jpg
169 ms
20240921_OPP501.jpg
171 ms
20240928_STP004.jpg
222 ms
20240921_LDD002.jpg
177 ms
20240921_FND004.jpg
198 ms
20240916_BID001.jpg
195 ms
20240914_EUP505.jpg
191 ms
20240907_EUP512.jpg
183 ms
20240909_BID001.jpg
183 ms
20240922_blp901.jpg
179 ms
20240907_LDP001.jpg
201 ms
20240907_EUP001.jpg
188 ms
20240928_DE_US.jpg
181 ms
20240921_TQR.jpg
224 ms
20240928_USP002.jpg
211 ms
20240921_AMP001.jpg
184 ms
1843_20240916_1843_SATANISM_Teas.jpg
206 ms
20240928_PDP507.jpg
180 ms
20240925_BID001.jpg
197 ms
20240919_BLD001.jpg
201 ms
20240928_BLP503.jpg
209 ms
main.js
90 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
Some elements have a [tabindex] value greater than 0
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
Browser errors were logged to the console
Page has valid source maps
amp.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 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: