9.1 sec in total
1.8 sec
7 sec
279 ms
Visit data.gov.my now to see the best up-to-date Data Gov content and also check out these interesting facts you probably never knew about data.gov.my
Your one-stop interface to browse Malaysia's wealth of open data!
Visit data.gov.myWe analyzed Data.gov.my page load time and found that the first response time was 1.8 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
data.gov.my performance score
1769 ms
930 ms
467 ms
705 ms
468 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 80% of them (67 requests) were addressed to the original Data.gov.my, 19% (16 requests) were made to 1akses.malaysia.gov.my and 1% (1 request) were made to C.statcounter.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Data.gov.my.
Page size can be reduced by 535.2 kB (56%)
961.0 kB
425.8 kB
In fact, the total size of Data.gov.my main page is 961.0 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. 70% of websites need less resources to load. Javascripts take 548.4 kB which makes up the majority of the site volume.
Potential reduce by 40.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 10.8 kB, which is 24% 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 40.5 kB or 89% of the original size.
Potential reduce by 48.7 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, Data Gov needs image optimization as it can save up to 48.7 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 415.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 415.8 kB or 76% of the original size.
Potential reduce by 30.2 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. Data.gov.my needs all CSS files to be minified and compressed as it can save up to 30.2 kB or 77% of the original size.
Number of requests can be reduced by 19 (24%)
79
60
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data Gov. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
data.gov.my
1769 ms
style.css
930 ms
tabs.css
467 ms
contact.css
705 ms
functions.js
468 ms
jquery.min.js
1630 ms
jquery-1.3.2.min.js
1432 ms
jquery-ui-1.7.custom.min.js
1161 ms
tabs.js
937 ms
contacts.js
1160 ms
jquery.vticker.js
1173 ms
jssor.js
2098 ms
jssor.slider.js
2322 ms
gallery.js
1392 ms
main_display.css
944 ms
search.html
770 ms
65 ms
body.png
243 ms
cloud.jpg
475 ms
logo.png
237 ms
bgs.png
236 ms
nav.png
240 ms
main.png
239 ms
section-shadow2.png
469 ms
img5.png
471 ms
arrow2.png
470 ms
img7.png
472 ms
bgs2.png
475 ms
hackathonlogo.png
937 ms
img6.png
705 ms
img.png
701 ms
cols-shadow2.png
703 ms
perasmian1.JPG
939 ms
perasmian2.JPG
1420 ms
event1.JPG
1400 ms
event2.JPG
1169 ms
event3.JPG
1170 ms
event4.JPG
1402 ms
event5.JPG
1638 ms
event6.JPG
1637 ms
event7.JPG
1639 ms
event8.JPG
1898 ms
event9.JPG
1897 ms
event10.JPG
1898 ms
event11.JPG
2106 ms
event12.JPG
2107 ms
event13.JPG
2108 ms
event14.JPG
2334 ms
penilai.JPG
2570 ms
penilai2.JPG
2366 ms
penilaian.JPG
2572 ms
penilaian2.JPG
2574 ms
penilaian3.JPG
2575 ms
penilaian4.JPG
2570 ms
sijil1.JPG
2608 ms
sijil2.JPG
2820 ms
sijil3.JPG
2819 ms
sijil4.JPG
2819 ms
sijil5.JPG
2590 ms
sijil6.JPG
2802 ms
penutup.JPG
3084 ms
penutup2.JPG
3038 ms
penutup3.JPG
3038 ms
a02.png
2804 ms
jquery1.11.1.js
1172 ms
base64.js
498 ms
land.css
482 ms
font-awesome.min.css
954 ms
stylesheet.css
482 ms
garispanduan2.png
2578 ms
terma2.png
2802 ms
navbg.png
2808 ms
socials-inner.png
2576 ms
footer-cols.png
2798 ms
Widget
647 ms
6d9779f5-7539-4cc9-9c3c-43ce5875c1ea
652 ms
fontawesome-webfont.woff
652 ms
ubuntu-c-webfont.woff
652 ms
widgetUI.html
247 ms
osList.js
238 ms
widget.css
251 ms
6d9779f5-7539-4cc9-9c3c-43ce5875c1ea
941 ms
ubuntu-c-webfont.woff
237 ms
fontawesome-webfont.woff
713 ms
data.gov.my SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Data.gov.my 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 Data.gov.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.
data.gov.my
Open Graph description is not detected on the main page of Data Gov. 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: