1.1 sec in total
14 ms
688 ms
443 ms
Visit worldbank.org now to see the best up-to-date World Bank content for India and also check out these interesting facts you probably never knew about worldbank.org
With 189 member countries, the World Bank Group is a unique global partnership fighting poverty worldwide through sustainable solutions.
Visit worldbank.orgWe analyzed Worldbank.org page load time and found that the first response time was 14 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
worldbank.org performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value7.1 s
6/100
25%
Value6.0 s
47/100
10%
Value3,700 ms
1/100
30%
Value0.045
99/100
15%
Value15.4 s
7/100
10%
14 ms
60 ms
15 ms
10 ms
87 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 70% of them (26 requests) were addressed to the original Worldbank.org, 11% (4 requests) were made to Worldbank.scene7.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (574 ms) relates to the external source Worldbank.scene7.com.
Page size can be reduced by 177.0 kB (31%)
577.3 kB
400.3 kB
In fact, the total size of Worldbank.org main page is 577.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 247.1 kB which makes up the majority of the site volume.
Potential reduce by 176.8 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. This page needs HTML code to be minified as it can gain 48.2 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 176.8 kB or 89% 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. World Bank images are well optimized though.
Potential reduce by 203 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.
Number of requests can be reduced by 13 (42%)
31
18
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of World Bank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
worldbank.org
14 ms
www.worldbank.org
60 ms
home
15 ms
jquery.js
10 ms
launch-7bc0cdc67098.min.js
87 ms
clientlib-l1-template.css
58 ms
site.css
58 ms
site.css
71 ms
embed.js
108 ms
wbgajax.js
66 ms
clientlib-l1-template.js
68 ms
site.js
67 ms
polyfill.min.js
208 ms
cookie-consent.js
66 ms
WebStatsUtil.js
79 ms
who-we-are
185 ms
what-we-do
186 ms
megamenu-photo-pakistan
574 ms
logo-wb-header-en.svg
53 ms
wblive-logo-ENG-short_white2.png
65 ms
search-orange.svg
65 ms
css2
63 ms
css2
80 ms
fb.svg
129 ms
ida-africa-summit-05-1440x600
98 ms
twitter.svg
89 ms
linkedln.svg
90 ms
instagram.svg
88 ms
youtube.svg
89 ms
flickr.svg
85 ms
logo-wbg-footer-en.svg
90 ms
font
111 ms
ai.0.js
87 ms
ampopup
64 ms
loopicon.ttf
19 ms
304244_1_0.woff
20 ms
font.woff
20 ms
worldbank.org accessibility score
worldbank.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
worldbank.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Worldbank.org 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 Worldbank.org 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.
worldbank.org
Open Graph data is detected on the main page of World Bank. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: