2 sec in total
442 ms
1.3 sec
170 ms
Visit ppi.worldbank.org now to see the best up-to-date PPI World Bank content for India and also check out these interesting facts you probably never knew about ppi.worldbank.org
The Private Participation in Infrastructure (PPI) Project Database has data on over 6,400 infrastructure projects in 139 low- and middle-income countries. The database is the leading source of PPI tre...
Visit ppi.worldbank.orgWe analyzed Ppi.worldbank.org page load time and found that the first response time was 442 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
ppi.worldbank.org performance score
name
value
score
weighting
Value11.6 s
0/100
10%
Value96.1 s
0/100
25%
Value24.6 s
0/100
10%
Value5,550 ms
0/100
30%
Value0.014
100/100
15%
Value49.3 s
0/100
10%
442 ms
212 ms
120 ms
86 ms
88 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 61% of them (46 requests) were addressed to the original Ppi.worldbank.org, 11% (8 requests) were made to Mts0.googleapis.com and 11% (8 requests) were made to Mts1.googleapis.com. The less responsive or slowest element that took the longest time to load (442 ms) belongs to the original domain Ppi.worldbank.org.
Page size can be reduced by 984.6 kB (43%)
2.3 MB
1.3 MB
In fact, the total size of Ppi.worldbank.org main page is 2.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. 50% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 31.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. This page needs HTML code to be minified as it can gain 8.5 kB, which is 22% 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 31.1 kB or 82% of the original size.
Potential reduce by 8.2 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. PPI World Bank images are well optimized though.
Potential reduce by 715.8 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 715.8 kB or 77% of the original size.
Potential reduce by 229.5 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. Ppi.worldbank.org needs all CSS files to be minified and compressed as it can save up to 229.5 kB or 84% of the original size.
Number of requests can be reduced by 32 (43%)
75
43
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PPI 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 22 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
ppi.worldbank.org
442 ms
bootstrap.min.css
212 ms
global.css
120 ms
GoogleAPI.css
86 ms
notonaskharabic.css
88 ms
WebStatsUtil.js
97 ms
normalize.css
112 ms
main.css
130 ms
style.css
210 ms
jquery-ui.css
239 ms
master.css
155 ms
rzslider.css
167 ms
responsive.css
176 ms
map.css
209 ms
modernizr-2.8.3.min.js
230 ms
jsapi.js
231 ms
jquery.min.js
301 ms
jquery-ui.js
389 ms
angular.js
418 ms
ppi-master.js
272 ms
angular-touch.min.js
274 ms
ngutilities.js
284 ms
main.js
318 ms
utils.js
318 ms
OmniturePPI.js
334 ms
jquery.cycle.all.js
342 ms
googlemap.js
348 ms
plugins.js
354 ms
map.js
413 ms
bootstrap.min.js
415 ms
wb.js
414 ms
s_code_remote.js
114 ms
logo-wb-header-en.svg
54 ms
construction.jpg
217 ms
vt
207 ms
vt
216 ms
google_white2.png
90 ms
vt
215 ms
vt
240 ms
vt
231 ms
vt
237 ms
vt
255 ms
vt
246 ms
vt
235 ms
vt
249 ms
vt
263 ms
vt
252 ms
vt
241 ms
vt
258 ms
vt
252 ms
vt
268 ms
mobile-menu-lines.png
45 ms
logo-wbg-footer-en.svg
45 ms
water
209 ms
wind-turbines
208 ms
port
226 ms
carousel_arrow_up.png
60 ms
mapcnt3.png
82 ms
cb_scout2.png
82 ms
imgs8.png
83 ms
main.js
60 ms
icon-search-black.png
112 ms
openhand_8_8.cur
110 ms
carousel_arrow_left.png
63 ms
carousel_arrow_right.png
62 ms
A8D8A6111C9A418A8D2676CB14D93781.ashx
53 ms
pdf_icon_small.gif
49 ms
333C28F0484745F5A175DD4450E38AB9.ashx
50 ms
B020E578CC6549A9A47E0489598FBC80.ashx
64 ms
sprite_icon_for_subsectors.png
90 ms
arrow_gray.png
90 ms
shape_tab.png
98 ms
arrow_white.png
105 ms
s08902054701466
82 ms
common.js
19 ms
map.js
18 ms
ppi.worldbank.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
ppi.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
ppi.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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ppi.worldbank.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ppi.worldbank.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ppi.worldbank.org
Open Graph description is not detected on the main page of PPI World Bank. 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: