43.3 sec in total
184 ms
20.5 sec
22.7 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 184 ms and then it took 43.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
economist.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value3.5 s
63/100
25%
Value14.2 s
1/100
10%
Value10,370 ms
0/100
30%
Value0.34
33/100
15%
Value32.4 s
0/100
10%
184 ms
264 ms
8003 ms
7689 ms
4215 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that 25% of them (5 requests) were addressed to the original Economist.com, 50% (10 requests) were made to Cdn.static-economist.com and 10% (2 requests) were made to Service.maxymiser.net. The less responsive or slowest element that took the longest time to load (8 sec) belongs to the original domain Economist.com.
Page size can be reduced by 3.7 MB (57%)
6.4 MB
2.7 MB
In fact, the total size of Economist.com main page is 6.4 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. 75% 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. Javascripts take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 436.2 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 436.2 kB or 78% of the original size.
Potential reduce by 97.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. Economist images are well optimized though.
Potential reduce by 2.3 MB
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 2.3 MB or 71% of the original size.
Potential reduce by 877.9 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. Economist.com needs all CSS files to be minified and compressed as it can save up to 877.9 kB or 74% of the original size.
Number of requests can be reduced by 5 (63%)
8
3
The browser has sent 8 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 6 to 1 for JavaScripts and as a result speed up the page load time.
economist.com
184 ms
www.economist.com
264 ms
www.economist.com
8003 ms
184475-137819213763014.js
7689 ms
icons--33fb586b88d14cf55598686375498cac05d9f8cc--.svg
4215 ms
app--84e2cd99ec1c2e1198cfd59444bb05f297041088--.js
3169 ms
econsans-lt--1ddd2fff3669e4ef671155ce7dcc2af279469916--.woff
6110 ms
econsans-rg--4409a58a388fe0e69419777646d533a943a0f65e--.woff
6885 ms
econsans-md--1c71277e112c5a8fdb98ae9c15e39cd5439f76b6--.woff
6109 ms
econsans-bd--6c6bb05807b0b961b59eb4d0c3af15b7a1b31f26--.woff
6811 ms
econsans-it--0a5a734309bf65d3f21b5c8b5777702b72dc02c2--.woff
6811 ms
milo-md--0f178a33a1b65af53d8d6023602c0b9385c18a4e--.woff
6883 ms
milo-rg--3db27d3af4b262cce911d2a92d2ed75c00e95b9f--.woff
6809 ms
milo-bd--06880a5829c21e7ad7454aa01fed6e5c27a89550--.woff
6809 ms
milo-it--479e4b4baee3442c6252258af2dcd7d5229aaf2f--.woff
7111 ms
11914.js
6351 ms
mmcore.js
4715 ms
312 ms
print-bundle--e800782b73ea4df94d1a223c42fb36cc35b176da--.css
264 ms
sync
343 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: