4.7 sec in total
365 ms
3.8 sec
555 ms
Visit cm.com now to see the best up-to-date CM content for India and also check out these interesting facts you probably never knew about cm.com
Boost performance & surpass expectations by crafting hyper-personalized experiences, leading the way in AI-driven conversational commerce. Read more »
Visit cm.comWe analyzed Cm.com page load time and found that the first response time was 365 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cm.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value3.5 s
64/100
25%
Value7.0 s
32/100
10%
Value1,360 ms
16/100
30%
Value0.654
8/100
15%
Value11.8 s
17/100
10%
365 ms
742 ms
120 ms
128 ms
49 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 14% of them (8 requests) were addressed to the original Cm.com, 30% (17 requests) were made to Cdn.cm.com and 9% (5 requests) were made to Platform.cmtelecom.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cdn.cm.com.
Page size can be reduced by 1.6 MB (58%)
2.8 MB
1.2 MB
In fact, the total size of Cm.com 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. 50% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 52.9 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 52.9 kB or 80% of the original size.
Potential reduce by 63 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. CM images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 71% of the original size.
Potential reduce by 501.8 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. Cm.com needs all CSS files to be minified and compressed as it can save up to 501.8 kB or 86% of the original size.
Number of requests can be reduced by 15 (35%)
43
28
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
cm.com
365 ms
www.cm.com
742 ms
gtm.js
120 ms
gtm.js
128 ms
j.php
49 ms
platform.min.css
786 ms
app-37f80afdd2.css
910 ms
OneSignalSDK.js
70 ms
platform.min.js
1001 ms
angular-hash-eb3320a96c.js
677 ms
branding-50ff062d69.js
1070 ms
app-904193dbe8.js
773 ms
v.gif
5 ms
analytics.js
36 ms
hotjar-546992.js
201 ms
collect
14 ms
collect
48 ms
modules-f524bccd859bfc7e394e1123f7f90405.js
76 ms
old-way.png
373 ms
cm-member-GSMA.png
98 ms
new-way.png
548 ms
piwik.js
980 ms
banner-frontpage-lg.jpg
468 ms
dentadmin-interview-sm.jpg
348 ms
play-icon.png
342 ms
care-rate-interview-sm.jpg
348 ms
constamed-interview-lg.jpg
467 ms
hyve-interview-lg.jpg
668 ms
Open-Sans-Regular.woff
624 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
29 ms
Open-Sans-SemiBold.woff
487 ms
DINWebPro.woff
392 ms
Foro-Regular.woff
496 ms
Foro-Medium.woff
568 ms
fontawesome-webfont.woff
581 ms
fontawesome-webfont.woff
280 ms
cm-icons.woff
588 ms
cm-icons.woff
354 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
203 ms
gtm.js
163 ms
ns.html
172 ms
EN
666 ms
account.config.json
164 ms
keys
672 ms
identity.config.json
173 ms
149 ms
cm-logo-3d31822a54.js
220 ms
load.sumome.com
591 ms
old-shattered-way-vs-all-in-one-platform-lg.png
535 ms
visit-data
324 ms
visit-data
198 ms
send-messages-via-cm-webinterface-lg-2.gif
176 ms
keys
117 ms
piwik.php
148 ms
configs.php
224 ms
configs.php
264 ms
cm.com 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-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
[aria-*] attributes do not have valid values
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cm.com 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
Page has valid source maps
cm.com 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cm.com 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 Cm.com 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.
cm.com
Open Graph data is detected on the main page of CM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: