12.9 sec in total
946 ms
11.8 sec
155 ms
Click here to check amazing MySMS Gov content. Otherwise, check out these important facts you probably never knew about mysms.gov.my
Portal Rasmi Perkhidmatan Mobile Kerajaan Malaysia
Visit mysms.gov.myWe analyzed Mysms.gov.my page load time and found that the first response time was 946 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
mysms.gov.my performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value7.0 s
6/100
25%
Value7.0 s
32/100
10%
Value320 ms
76/100
30%
Value0.371
28/100
15%
Value6.7 s
56/100
10%
946 ms
1940 ms
237 ms
2943 ms
469 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mysms.gov.my, 96% (48 requests) were made to Mygovmobile.malaysia.gov.my and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Mygovmobile.malaysia.gov.my.
Page size can be reduced by 562.9 kB (12%)
4.9 MB
4.3 MB
In fact, the total size of Mysms.gov.my main page is 4.9 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. 20% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 29.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. 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 29.1 kB or 82% of the original size.
Potential reduce by 208.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. MySMS Gov images are well optimized though.
Potential reduce by 295.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 295.1 kB or 62% of the original size.
Potential reduce by 29.9 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. Mysms.gov.my needs all CSS files to be minified and compressed as it can save up to 29.9 kB or 83% of the original size.
Number of requests can be reduced by 15 (33%)
45
30
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MySMS 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 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
mysms.gov.my
946 ms
www.mygovmobile.malaysia.gov.my
1940 ms
web
237 ms
2943 ms
mod_vvisit_counter.css
469 ms
scrollable.css
476 ms
menu.min.css
481 ms
menu.fix.css
481 ms
jquery.min.js
7 ms
mootools.js
1262 ms
caption.js
505 ms
mt-1.1.js
707 ms
bar.js
723 ms
ext-core.js
1443 ms
menu.min.js
979 ms
system.css
533 ms
general.css
716 ms
template.css
759 ms
jquery-1.7.2.min.js
1716 ms
scrollable.min.js
953 ms
scrollable.autoscroll.min.js
993 ms
lake.jpg
1376 ms
panelbg.png
238 ms
shadow-l.png
254 ms
header-bg-en.jpg
567 ms
nav_bg.png
251 ms
menu-arrow-down.png
476 ms
menu-arrow-right.png
503 ms
mysms.png
536 ms
myussd.png
719 ms
mymms.png
742 ms
mypay.png
732 ms
4.jpg
1515 ms
DTSA_2016.png
1543 ms
SPR-banner.jpg
2100 ms
DBKL.png
1275 ms
myNiosh.png
3832 ms
myPTPTN.png
3981 ms
myZakat.png
4464 ms
alwaysconected.PNG
1978 ms
searchbg.png
1471 ms
list_member3_en.php
1998 ms
search-value-bg.png
1742 ms
search-btn-bg.png
1841 ms
mbg.png
1998 ms
icon-annoucement.png
2084 ms
icon-video.png
2240 ms
icon-members.png
2234 ms
shadow-r.png
2318 ms
mof.png
2447 ms
mysms.gov.my accessibility score
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
mysms.gov.my 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
Page has valid source maps
mysms.gov.my SEO score
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
MS
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mysms.gov.my can be misinterpreted by Google and other search engines. Our service has detected that Malay is used on the page, and it does not match the claimed English language. Our system also found out that Mysms.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.
mysms.gov.my
Open Graph description is not detected on the main page of MySMS 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: