9.1 sec in total
1.3 sec
7.6 sec
206 ms
Click here to check amazing UNICEF content for India. Otherwise, check out these important facts you probably never knew about unicef.in
UNICEF is the global leader promoting and protecting children’s rights in 190 countries, including India.
Visit unicef.inWe analyzed Unicef.in page load time and found that the first response time was 1.3 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
unicef.in performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value7.5 s
4/100
25%
Value4.8 s
66/100
10%
Value750 ms
40/100
30%
Value0.432
22/100
15%
Value13.5 s
11/100
10%
1340 ms
3523 ms
1046 ms
1829 ms
553 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 66% of them (75 requests) were addressed to the original Unicef.in, 11% (12 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Unicef.in.
Page size can be reduced by 1.0 MB (56%)
1.8 MB
813.7 kB
In fact, the total size of Unicef.in main page is 1.8 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. 55% of websites need less resources to load. CSS take 863.3 kB which makes up the majority of the site volume.
Potential reduce by 26.3 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 26.3 kB or 73% of the original size.
Potential reduce by 33.5 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. UNICEF images are well optimized though.
Potential reduce by 185.1 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 185.1 kB or 67% of the original size.
Potential reduce by 773.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. Unicef.in needs all CSS files to be minified and compressed as it can save up to 773.5 kB or 90% of the original size.
Number of requests can be reduced by 33 (29%)
112
79
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UNICEF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
unicef.in
1340 ms
Maincss.css
3523 ms
jquery.mCustomScrollbar.css
1046 ms
bootstrap2.css
1829 ms
elastislide.css
553 ms
jquery-1.7.2.min.js
1890 ms
jquery.mCustomScrollbar.concat.min.js
1082 ms
modernizr-2.6.2.min.js
208 ms
bootstrap.js
617 ms
bootstrap.min.js
963 ms
docs.js
740 ms
jquery.elastislide.js
827 ms
logo.jpg
206 ms
socila_icon1.jpg
208 ms
socila_icon2.jpg
315 ms
socila_icon3.jpg
316 ms
socila_icon4.jpg
315 ms
socila_icon5.jpg
327 ms
socila_icon6.jpg
411 ms
socila_icon7.jpg
418 ms
search.gif
535 ms
donate_icon.jpg
531 ms
get_icon.jpg
539 ms
meet_icon.jpg
545 ms
cam_img6.jpg
615 ms
cam_img4.jpg
621 ms
cam_img3.jpg
792 ms
aerow.jpg
800 ms
med_thu_img48.jpg
804 ms
video-play.png
819 ms
med_thu_img47.jpg
819 ms
med_thu_img46.jpg
826 ms
alb_img55.jpg
1083 ms
alb_img54.jpg
1083 ms
alb_img53.jpg
1083 ms
pub_img109.jpg
1100 ms
pub_img108.jpg
1079 ms
pub_img107.jpg
1080 ms
pub_img106.jpg
1250 ms
speak_icon.jpg
1248 ms
img_spk10.jpg
1327 ms
img_spk9.jpg
1326 ms
img_par1.png
1346 ms
img_par2.png
1373 ms
img_par4.png
1461 ms
img_par5.png
1464 ms
img_par6.png
1601 ms
likebox.php
260 ms
img_par7.png
1518 ms
analytics.js
64 ms
widgets.js
115 ms
collect
12 ms
GetLatestStories
1645 ms
GetWhatWeDo
1452 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
122 ms
GetBanners
1566 ms
img_par17.jpg
1372 ms
contacy_icon.png
1353 ms
career_icon.jpg
1548 ms
BdmCbeqDF1M.css
318 ms
34E4j2xurGO.css
420 ms
N925kd9Aw2G.css
519 ms
_rx8naC75Dy.js
652 ms
b94UUzHjapV.js
673 ms
0wM5s1Khldu.js
535 ms
TTCre3391I0.js
534 ms
feedback_icon.png
1519 ms
legal_icn.png
1483 ms
syndication
102 ms
404856567624781824
208 ms
unicfe_con.png
1369 ms
loading.gif
1587 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
29 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
80 ms
AyUo9W6Y_normal.jpeg
121 ms
7Bpo0qke_normal.png
155 ms
eXIfepWN_normal.jpg
178 ms
D1rv1nf3_normal.png
262 ms
0yeD4-WJ_normal.jpg
237 ms
cl5q9II9_normal.png
245 ms
sCr5m2lb_normal.jpg
247 ms
jot
72 ms
1235981_10151790921199123_1810152568_n.jpg
354 ms
1231219_10151790921559123_1957405097_n.jpg
419 ms
62540_171168263240924_8633800298550358320_n.jpg
489 ms
12196138_1680536315524848_7514802525864563041_n.jpg
552 ms
10417504_217457961920202_7363186551469444165_n.jpg
560 ms
12274311_10153273297144205_7923370228303634448_n.jpg
557 ms
12038565_153702544972833_3448817838636678289_n.jpg
557 ms
11025658_926312344079880_2690354049559729853_n.jpg
558 ms
12644799_954680144618849_6365087044992808411_n.jpg
560 ms
HEyyDkPknAC.png
80 ms
wL6VQj7Ab77.png
73 ms
s7jcwEQH7Sx.png
72 ms
I6-MnjEovm5.js
88 ms
f6T91Deal_q.js
135 ms
cat_wwd_img1.jpg
487 ms
cat_wwd_img2.jpg
484 ms
cat_wwd_img3.jpg
450 ms
cat_wwd_img4.jpg
450 ms
nav2.png
501 ms
img_str1178.jpg
493 ms
img_str1177.jpg
496 ms
img_str1174.jpg
560 ms
img_str1173.jpg
563 ms
img_str1175.jpg
561 ms
img_str1176.jpg
628 ms
bnr_img5.jpg
879 ms
bnr_img3.jpg
892 ms
bnr_img2.jpg
1334 ms
bnr_img1.jpg
1075 ms
aerow_left.png
798 ms
aerow_right.png
879 ms
unicef.in 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
button, link, and menuitem elements do not have accessible names.
[aria-hidden="true"] elements contain focusable descendents
[role]s do not have all required [aria-*] attributes
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
unicef.in 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
unicef.in 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
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unicef.in 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 Unicef.in 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.
unicef.in
Open Graph description is not detected on the main page of UNICEF. 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: