4.1 sec in total
498 ms
3 sec
599 ms
Visit ilo.int now to see the best up-to-date Ilo content for India and also check out these interesting facts you probably never knew about ilo.int
Visit ilo.intWe analyzed Ilo.int page load time and found that the first response time was 498 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ilo.int performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value12.5 s
0/100
25%
Value18.7 s
0/100
10%
Value1,710 ms
11/100
30%
Value0.035
100/100
15%
Value23.2 s
1/100
10%
498 ms
671 ms
105 ms
287 ms
196 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ilo.int, 72% (49 requests) were made to Ilo.org and 9% (6 requests) were made to F.fontdeck.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Ilo.org.
Page size can be reduced by 860.2 kB (43%)
2.0 MB
1.1 MB
In fact, the total size of Ilo.int main page is 2.0 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. Images take 870.9 kB which makes up the majority of the site volume.
Potential reduce by 68.5 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 11.1 kB, which is 13% 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 68.5 kB or 83% of the original size.
Potential reduce by 17.3 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. Ilo images are well optimized though.
Potential reduce by 460.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 460.8 kB or 70% of the original size.
Potential reduce by 313.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. Ilo.int needs all CSS files to be minified and compressed as it can save up to 313.5 kB or 83% of the original size.
Number of requests can be reduced by 29 (50%)
58
29
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ilo. 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 4 to 1 for CSS and as a result speed up the page load time.
ilo.int
498 ms
index.htm
671 ms
sitenavigationfunctions.js
105 ms
sitenavigation.js
287 ms
wcm.toggle.js
196 ms
ssajax.js
195 ms
screen.css
383 ms
jquery.fancybox.css
196 ms
jquery.min.js
31 ms
plugins-ck.js
467 ms
jquery.fancybox.js
469 ms
jquery.fancybox-thumbs.js
465 ms
jquery.fancybox-media.js
465 ms
jMonthCalendar.js
516 ms
jquery.easydropdown.min.js
466 ms
tinynav.min.js
468 ms
onload-ck.js
467 ms
webfont.js
67 ms
ilo.png
482 ms
down-arrow-large.png
421 ms
ilo-map-large.png
484 ms
mag-low.png
420 ms
icon-twitter.png
418 ms
icon-youtube.png
480 ms
icon-facebook.png
484 ms
icon-flickr.png
483 ms
icon-linkedin.png
484 ms
icon-rss.png
486 ms
wcms_461271.jpg
679 ms
wcms_459558.jpg
493 ms
wcms_458661.jpg
652 ms
wcms_460962.jpg
495 ms
wcq1_180809.gif
488 ms
wcms_375697.jpg
1067 ms
wcms_458202.gif
654 ms
wcms_458876.jpg
677 ms
wcms_458881.gif
757 ms
wcq1_180812.jpg
818 ms
wcms_346722.gif
818 ms
wcms_447526.jpg
1243 ms
wcms_431726.jpg
811 ms
wcms_190521.jpg
1058 ms
wcms_456901.jpg
1060 ms
wcms_149444.jpg
1060 ms
wcms_222806.jpg
1059 ms
bullet-grey.png
1027 ms
right-arrow-large-dark.png
1023 ms
up-arrow-large.png
1021 ms
ga.js
329 ms
41991.js
390 ms
border-vert.png
898 ms
bg_direction_nav.png
964 ms
icons.ttf
719 ms
__utm.gif
51 ms
WFKboJTkl5Q
177 ms
www-embed-player-vflfNyN_r.css
110 ms
www-embed-player.js
165 ms
base.js
244 ms
uDTgjDrbAskur5bf4WmjK3z6RX2DQyDzQS4AzaTvPLfGZlKhCsjdudYKFDX5JPLg9QzIeDNDGgJqkN86pdByWHnO96uS1datQ.woff
214 ms
TBw.woff
403 ms
3rRkFaYQ50lFQrFkeg.woff
402 ms
u9OzsE2WghTvkON6A+hFJPGfZdAcxx7YSFfx+iDjE5x3BA.woff
402 ms
PQNHLZg2BFeP8Z5yZ0Yr63CUvhhWJb1anEiza22rwVWn4MxA.woff
402 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
153 ms
ad_status.js
103 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
110 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
111 ms
print.css
99 ms
ilo.int 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
ilo.int 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ilo.int SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Ilo.int 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 Ilo.int 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.
ilo.int
Open Graph description is not detected on the main page of Ilo. 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: