3.6 sec in total
969 ms
2.1 sec
521 ms
Visit tm.com.my now to see the best up-to-date Tm content for Malaysia and also check out these interesting facts you probably never knew about tm.com.my
Connect to your future with Telekom Malaysia, Malaysia's communications solution provider
Visit tm.com.myWe analyzed Tm.com.my page load time and found that the first response time was 969 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
tm.com.my performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value6.4 s
10/100
25%
Value7.8 s
23/100
10%
Value1,560 ms
13/100
30%
Value0.01
100/100
15%
Value17.7 s
4/100
10%
969 ms
76 ms
18 ms
15 ms
17 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 82% of them (102 requests) were addressed to the original Tm.com.my, 4% (5 requests) were made to Googletagmanager.com and 4% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Tm.listedcompany.com.
Page size can be reduced by 52.4 kB (4%)
1.3 MB
1.3 MB
In fact, the total size of Tm.com.my main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 52.0 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 15.4 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 52.0 kB or 82% of the original size.
Potential reduce by 13 B
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. Tm images are well optimized though.
Potential reduce by 71 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 300 B
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. Tm.com.my has all CSS files already compressed.
Number of requests can be reduced by 68 (62%)
110
42
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
tm.com.my
969 ms
js
76 ms
google_tag.script.js
18 ms
css_3gR_EA621r098RLcDPavocnl_viTmGiRIW9ql68K7OE.css
15 ms
css_dFzFKUSVoKvJdkfRRKtwxidldNeaAESdma4OZdtGP8o.css
17 ms
css_VExiKPKHw0Fc7aQgk5GnZXiFQue65mdq1D2O9ZEM32w.css
17 ms
newsletter
295 ms
css_4vLarqEEtXUCqduGEM59qRCmSNO9AtxJFhBKHdPa2LQ.css
21 ms
css_ieA30Tjh9bdMuZ2CfCPJZ1ghrZ5bJ-LgLX3MGYiw2Gg.css
28 ms
TM_YNIN.webp
44 ms
element-desktop-navbar.png
30 ms
IAR2023_WebsiteBanner-mobile_BG.png.webp
31 ms
IAR2023_WebsiteBanner-desktop_BG.png.webp
46 ms
tm-your-next-is-now-banner-mobile_0.jpg.webp
44 ms
tm-your-next-is-now-banner_0.jpg.webp
48 ms
tm-global-next-level-growth-banner-mobile_0.jpg.webp
48 ms
tm-global-next-level-growth-banner_0.jpg.webp
82 ms
tm-one-smarter-smarts-now-banner-mobile_0.jpg.webp
48 ms
tm-one-smarter-smarts-now-banner_0.jpg.webp
110 ms
unifi-your-next-moment-banner-mobile_0.jpg.webp
82 ms
unifi-your-next-moment-banner_0.jpg.webp
48 ms
unifi-business-level-up-your-growth-banner-mobile_0.jpg.webp
80 ms
css2
83 ms
integration_external_stock_quotes_homepage.html
1143 ms
jquery.min.js
56 ms
nodelist.foreach.js
51 ms
element.matches.js
54 ms
object.assign.js
50 ms
css.escape.js
77 ms
es6-promise.auto.min.js
51 ms
once.min.js
53 ms
jquery.once.min.js
55 ms
drupalSettingsLoader.js
56 ms
drupal.js
76 ms
drupal.init.js
77 ms
index.umd.min.js
78 ms
progress.js
80 ms
jquery.once.bc.js
78 ms
loadjs.min.js
79 ms
ajax.js
80 ms
ajax-throbber.js
81 ms
faqs.js
95 ms
google_analytics.js
81 ms
supporting_documents.js
82 ms
bootstrap.min.js
85 ms
jquery.once.min.js
83 ms
jquery.waypoints.min.js
83 ms
slick.min.js
83 ms
swiper-bundle.min.js
84 ms
select2.min.js
83 ms
dropdown1.js
80 ms
affix.js
79 ms
daterangepicker.js
81 ms
iframeResizer.min.js
84 ms
tm_main.js
53 ms
main.js
49 ms
timeline.js
54 ms
tender_notice.js
52 ms
tender_notice_full.js
53 ms
tm_ldap.js
56 ms
tweets.js
49 ms
debounce.js
52 ms
form.js
52 ms
webform.behaviors.js
50 ms
states.js
51 ms
analytics.js
35 ms
webform.states.js
102 ms
webform.form.js
98 ms
webform.element.details.save.js
98 ms
announce.js
97 ms
webform.element.details.toggle.js
98 ms
webform.scroll.js
97 ms
webform.ajax.js
96 ms
webform.element.message.js
95 ms
jquery.form.min.js
98 ms
tm-v2.js
96 ms
_Incapsula_Resource
97 ms
unifi-business-level-up-your-growth-banner_0.jpg.webp
94 ms
element-logo-tm-global.svg
91 ms
element-logo-tm-global-mob.svg
94 ms
logo-tm-global_1.svg
94 ms
logo-tm-global-mob_1.svg
96 ms
element-logo-tm-one.svg
98 ms
element-logo-tm-one-mob.svg
102 ms
logo-tm-one.svg
95 ms
logo-tm-one-mob.svg
98 ms
element-logo-tm-unifi.svg
103 ms
element-logo-tm-unifi-mob.svg
103 ms
logo-tm-unifi.svg
111 ms
logo-tm-unifi-mob.svg
101 ms
element-logo-tm-unifi-business.svg
102 ms
element-logo-tm-unifi-business-mob.svg
105 ms
logo-tm-unifi-business.svg
101 ms
logo-tm-unifi-business-mob.svg
103 ms
TmNewsTemplate-06_0.jpg.webp
105 ms
Award%202.JPG.webp
105 ms
GBCL0273b.jpg.webp
103 ms
collect
52 ms
investor-relations-tile.webp
43 ms
redress-your-complaints.webp
42 ms
KFOmCnqEu92Fr1Me5Q.ttf
135 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
211 ms
KFOkCnqEu92Fr1MmgWxP.ttf
212 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
214 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
215 ms
HKGroteskWide-Black.woff
201 ms
HKGroteskWide-Bold.woff
132 ms
HKGroteskWide-Regular.woff
9 ms
tmicon.ttf
574 ms
arrow-right%E2%80%93lg.svg
210 ms
redress-your-complaints.webp
179 ms
gtm.js
133 ms
_Incapsula_Resource
13 ms
js
50 ms
collect
40 ms
destination
126 ms
destination
183 ms
fbevents.js
180 ms
events.js
287 ms
fs.js
286 ms
collect
279 ms
activityi;src=14077788;type=tmcor0;cat=tmcor0;ord=2554930783855;npa=0;auiddc=292960474.1714880752;u1=https%3A%2F%2Ftm.com.my%2F;pscdl=noapi;gtm=45fe4510z8843566757za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Ftm.com.my%2F
123 ms
main.MTIyYzc3NzllMQ.js
239 ms
ga-audiences
38 ms
src=14077788;type=tmcor0;cat=tmcor0;ord=2554930783855;npa=0;auiddc=*;u1=https%3A%2F%2Ftm.com.my%2F;pscdl=noapi;gtm=45fe4510z8843566757za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Ftm.com.my%2F
82 ms
tm.com.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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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
tm.com.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
Page has valid source maps
tm.com.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tm.com.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 Tm.com.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.
tm.com.my
Open Graph data is detected on the main page of Tm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: