4.8 sec in total
173 ms
4.4 sec
270 ms
Visit finances.worldbank.org now to see the best up-to-date Finances Worldbank content for India and also check out these interesting facts you probably never knew about finances.worldbank.org
Visit finances.worldbank.orgWe analyzed Finances.worldbank.org page load time and found that the first response time was 173 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
finances.worldbank.org performance score
name
value
score
weighting
Value25.9 s
0/100
10%
Value44.2 s
0/100
25%
Value29.9 s
0/100
10%
Value10,690 ms
0/100
30%
Value0.875
3/100
15%
Value47.8 s
0/100
10%
173 ms
1825 ms
220 ms
246 ms
245 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 61% of them (50 requests) were addressed to the original Finances.worldbank.org, 6% (5 requests) were made to Google-analytics.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Finances.worldbank.org.
Page size can be reduced by 1.9 MB (73%)
2.6 MB
686.0 kB
In fact, the total size of Finances.worldbank.org main page is 2.6 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. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 320.7 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 320.7 kB or 83% of the original size.
Potential reduce by 25.4 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. Obviously, Finances Worldbank needs image optimization as it can save up to 25.4 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 959.0 kB
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 959.0 kB or 68% of the original size.
Potential reduce by 588.7 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. Finances.worldbank.org needs all CSS files to be minified and compressed as it can save up to 588.7 kB or 85% of the original size.
Number of requests can be reduced by 41 (59%)
69
28
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Finances Worldbank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
finances.worldbank.org
173 ms
finances.worldbank.org
1825 ms
base.css
220 ms
socrata-apps.css
246 ms
errors.js
245 ms
components.css
249 ms
current_site.css
335 ms
mixpanel-analytics.js
250 ms
C1AF1F9A-AEFD-40B7-93A1-DFE5820697DF
385 ms
base.js
718 ms
canvas.js
426 ms
2BD63176-583E-4800-8196-F5B4594CBDCD
222 ms
WebStatsUtil.js
68 ms
s_code_remote.js
55 ms
jquery.min.js
62 ms
analytics.js
71 ms
YvVrP2mdOt4
122 ms
1398B789-A45F-45CF-B969-8FECEA614351
81 ms
icons.png
84 ms
6412D4EC-10B4-499F-8F28-755BC490F038
167 ms
4633CD2E-72AA-4FA8-B79F-B6E4D32F77A1
81 ms
5CEB7C64-F0AE-49A1-99C5-DE9F6A58420D
167 ms
AFB27343-B34F-447E-A606-B933F45D2578
166 ms
dataset_toolbar_icons.png
167 ms
homepage_ticker_bg.png
235 ms
QeSCIrz2Iklumdu1_zAK0ivR9Z8MpkJoP6yg5CoBdy0
802 ms
Dq0opL2-kwt35ythhZNrkA5SvqA4C8QaMpZCu6KEsos
424 ms
onLM9bElUPyCdi_YTXS85yvZOAZ6bRowPiJsBQSB9UE
802 ms
E8Le9hI5e4BMc5OCBFxidDgM63M26_8G4HGXmzIOVwA
709 ms
audience-arrow.gif
375 ms
bullet.png
384 ms
134AA060-425C-49A1-98D7-6C7DFACA2685
550 ms
widgets.js
123 ms
menu_icons.png
528 ms
collect
12 ms
www-embed-player-vflQrT_sR.css
75 ms
www-embed-player.js
99 ms
base.js
168 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
21 ms
ad_status.js
150 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
176 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
175 ms
spinner_background.png
155 ms
collect
142 ms
mixpanel-2.2.min.js
148 ms
mm46-4qjs.json
311 ms
YvVrP2mdOt4
159 ms
snuffleupasnake.gif
147 ms
BrandedSpinner.gif
147 ms
embed
1060 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
38 ms
87065CC0-B6D0-4073-8A87-C9257E0E84B6
158 ms
sanitize-html.js
176 ms
autolink-html.js
171 ms
syndication
90 ms
349281624715837440
203 ms
rows.json
268 ms
chart-screen.css
130 ms
rich-render-bundle.css
101 ms
display-chart.css
100 ms
shared-chart.js
168 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
27 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
69 ms
avgp4Ack_normal.png
138 ms
4A8HcjA7_normal.jpeg
149 ms
3Pv7U7M4_normal.jpg
181 ms
-rz_cY5L_normal.png
208 ms
s32231981793884
100 ms
%7Bchart%7D.json
88 ms
jot
46 ms
browse-control.css
151 ms
strip-chrome.css
77 ms
css
60 ms
renderType_toggle_icons.png
77 ms
type_icons_50.png
80 ms
empty.gif
79 ms
collect
11 ms
browse-control.js
81 ms
s39328277520835
86 ms
collect
49 ms
uniform_sprite.png
227 ms
print.css
79 ms
finances.worldbank.org accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
finances.worldbank.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
finances.worldbank.org 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
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 Finances.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 Finances.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.
finances.worldbank.org
Open Graph description is not detected on the main page of Finances Worldbank. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: