38.8 sec in total
2.5 sec
30.9 sec
5.4 sec
Click here to check amazing M1 content for Singapore. Otherwise, check out these important facts you probably never knew about m1.com.sg
Your preferred telco in Singapore for mobile and broadband solutions ✔️Best network experience ✔️Nationwide 5G ✔️Made-to-measure plans
Visit m1.com.sgWe analyzed M1.com.sg page load time and found that the first response time was 2.5 sec and then it took 36.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
m1.com.sg performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value26.5 s
0/100
25%
Value24.6 s
0/100
10%
Value4,030 ms
1/100
30%
Value0.12
84/100
15%
Value26.5 s
0/100
10%
2462 ms
977 ms
3195 ms
2999 ms
2999 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 43% of them (34 requests) were addressed to the original M1.com.sg, 6% (5 requests) were made to Google-analytics.com and 5% (4 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain M1.com.sg.
Page size can be reduced by 843.8 kB (30%)
2.8 MB
1.9 MB
In fact, the total size of M1.com.sg main page is 2.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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 34.8 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 34.8 kB or 76% of the original size.
Potential reduce by 69.2 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. M1 images are well optimized though.
Potential reduce by 718.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 718.1 kB or 73% of the original size.
Potential reduce by 21.7 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. M1.com.sg needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 80% of the original size.
Number of requests can be reduced by 37 (53%)
70
33
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
www.m1.com.sg
2462 ms
global
977 ms
jquery
3195 ms
WebResource.axd
2999 ms
ScriptResource.axd
2999 ms
ScriptResource.axd
2965 ms
jheader
3136 ms
jquery-ui-1.10.3.custom.min.css
6443 ms
gtm.js
3825 ms
gtm.js
3825 ms
ajax-loader.gif
1665 ms
95x95.png
2203 ms
slide_note8_walk-in
4201 ms
slide_mysim3.ashx
4297 ms
slide_FBB-Switch.ashx
2891 ms
slide_online-exclusive.ashx
6095 ms
slide_mcard_2gb.ashx
2840 ms
slide-control-bg-shadow-20.png
2838 ms
tile_mcard-account
4225 ms
gift.ashx
4147 ms
facebook.png
4144 ms
close.png
4245 ms
search.png
2096 ms
bg-sun.png
2096 ms
cart.png
3829 ms
analytics.js
2536 ms
bat.js
3905 ms
fbds.js
3750 ms
hotjar-46730.js
3750 ms
fbevents.js
4794 ms
container_55b758fe1c51b1bf653630d0.js
3749 ms
insight.min.js
3746 ms
mobile.png
1896 ms
broadband.png
1896 ms
home.png
1897 ms
international.png
1895 ms
myaccount.png
3437 ms
mym1.png
3437 ms
services.png
3437 ms
arrow-right-14x14.png
2775 ms
museosans_500-webfont.woff
2617 ms
collect
806 ms
collect
1739 ms
arrow-right-11x11.png
1853 ms
collect
1644 ms
4154 ms
dc.js
5298 ms
6100 ms
conversion.js
5725 ms
modules-f524bccd859bfc7e394e1123f7f90405.js
4706 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
4383 ms
insight.min.js
3307 ms
ga-audiences
5212 ms
844602022297136
2298 ms
ga-audiences
4612 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
1346 ms
ec.js
1112 ms
1125 ms
3700 ms
collect
834 ms
863 ms
visit-data
2984 ms
1357955647588863
255 ms
1193 ms
pixel
2610 ms
894 ms
1451 ms
1457 ms
visit-data
377 ms
pixel
1586 ms
1001 ms
Pug
1099 ms
generic
1139 ms
tap.php
616 ms
211 ms
generic
314 ms
pixel
167 ms
receive
360 ms
1640
835 ms
l
250 ms
m1.com.sg 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.
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
m1.com.sg 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
m1.com.sg 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 M1.com.sg 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 M1.com.sg 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.
m1.com.sg
Open Graph description is not detected on the main page of M1. 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: