2.7 sec in total
189 ms
2.4 sec
140 ms
Click here to check amazing UNICEF content for Malaysia. Otherwise, check out these important facts you probably never knew about unicef.my
You can make a difference by making a voluntary monthly or one-time donation. Every amount counts. Donate now.
Visit unicef.myWe analyzed Unicef.my page load time and found that the first response time was 189 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
unicef.my performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.7 s
59/100
25%
Value8.1 s
21/100
10%
Value110 ms
97/100
30%
Value0
100/100
15%
Value4.2 s
86/100
10%
189 ms
136 ms
95 ms
104 ms
18 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Unicef.my, 6% (3 requests) were made to Google-analytics.com and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (590 ms) relates to the external source Unicef.org.
Page size can be reduced by 121.4 kB (23%)
520.7 kB
399.3 kB
In fact, the total size of Unicef.my main page is 520.7 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. 30% of websites need less resources to load. Images take 432.7 kB which makes up the majority of the site volume.
Potential reduce by 15.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 4.1 kB, which is 20% 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 15.5 kB or 76% of the original size.
Potential reduce by 66.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, UNICEF needs image optimization as it can save up to 66.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 21.2 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 21.2 kB or 47% of the original size.
Potential reduce by 18.3 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.my needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 81% of the original size.
Number of requests can be reduced by 23 (48%)
48
25
The browser has sent 48 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 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
malaysia
189 ms
136 ms
java.js
95 ms
17144.css
104 ms
__utm.js
18 ms
jquery.min.js
27 ms
UNICEF_DownloadTracker-1.1.js
24 ms
jquery.min.js
22 ms
featuredcontentglider.css
180 ms
featuredcontentglider.js
177 ms
17145.css
107 ms
import_vs.css
102 ms
gtm.js
77 ms
ga.js
59 ms
__utm.gif
13 ms
malaysia.gif
56 ms
unicef-logo.gif
56 ms
upinipin_bannermain.jpg
202 ms
stayinformed_rdax_152x24.jpg
100 ms
take_action_rdax_152x24.jpg
148 ms
donateonline_rdax_152x24.jpg
153 ms
vacancy_rdax_152x24_copy.jpg
278 ms
my_CRC2012_1a.jpg
276 ms
my_MDG2012_1b.jpg
303 ms
my_Feb2016-saferinternet.jpg
335 ms
my_Feb2016-saferinternetvideo.jpg
308 ms
my_Feb2016-reportedu2.jpg
362 ms
my_Feb2016-reportedu1.jpg
424 ms
hp_feat_bottom_greydot.gif
374 ms
SMfollow-c.png
397 ms
FB.png
401 ms
Twitter.png
425 ms
YouTube.png
455 ms
my_news2015.png
520 ms
button_more.gif
492 ms
my_childline.png
499 ms
Endviolencewebsite.png
565 ms
my_publications.png
519 ms
my_DCSreport.png
551 ms
number.jpg
590 ms
unite_en.gif
522 ms
home-search-button.gif
543 ms
__utm.gif
26 ms
conversion_async.js
21 ms
fbds.js
6 ms
__utm.gif
20 ms
__utm.gif
474 ms
20 ms
37 ms
67 ms
3 ms
unicef.my 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
unicef.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
unicef.my SEO score
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
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unicef.my 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.my 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.my
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: