3.5 sec in total
316 ms
2.8 sec
356 ms
Click here to check amazing CM content for Belgium. Otherwise, check out these important facts you probably never knew about cm.be
Welkom bij CM, jouw gezondheidsfonds.
Visit cm.beWe analyzed Cm.be page load time and found that the first response time was 316 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cm.be performance score
name
value
score
weighting
Value13.9 s
0/100
10%
Value25.8 s
0/100
25%
Value15.1 s
1/100
10%
Value3,680 ms
1/100
30%
Value0.172
69/100
15%
Value32.6 s
0/100
10%
316 ms
474 ms
998 ms
278 ms
908 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 70% of them (38 requests) were addressed to the original Cm.be, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Cm.be.
Page size can be reduced by 801.9 kB (48%)
1.7 MB
864.1 kB
In fact, the total size of Cm.be main page is 1.7 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. 30% of websites need less resources to load. Images take 716.4 kB which makes up the majority of the site volume.
Potential reduce by 55.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 10.0 kB, which is 15% 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 55.0 kB or 82% of the original size.
Potential reduce by 51.4 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. CM images are well optimized though.
Potential reduce by 304.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 304.1 kB or 69% of the original size.
Potential reduce by 391.5 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.be needs all CSS files to be minified and compressed as it can save up to 391.5 kB or 88% of the original size.
Number of requests can be reduced by 24 (51%)
47
23
The browser has sent 47 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 10 to 1 for JavaScripts and as a result speed up the page load time.
cm.be
316 ms
www.cm.be
474 ms
style-responsive.css
998 ms
modernizr-responsive.js
278 ms
jquery-responsive.js
908 ms
app-responsive.js
339 ms
logo.png
183 ms
vrijwilligeroppas_tcm375-119150.jpg
282 ms
mediko-kinesist_tcm375-138363.jpg
461 ms
oppas_tcm375-119358.jpg
554 ms
lazyload.png
183 ms
dmw_tcm375-143972.jpg
461 ms
brillen%20cm-voordeel_tcm375-102640.jpg
461 ms
slaaptherapie_tcm375-146793.jpg
461 ms
gtm.js
89 ms
bgheader.png
448 ms
primair-home.png
448 ms
search-bkg.png
472 ms
searchsubmit-bkg.png
472 ms
drop-down-bkg.png
508 ms
drop-down-fill.png
513 ms
mouse.png
517 ms
dossier.gif
542 ms
folds3b-bkg.png
549 ms
figure-bkg.png
594 ms
folds1-bkg.png
598 ms
gray-top.png
604 ms
shadowlinks-bkg.png
636 ms
bullet-green.png
637 ms
folds2-side-bkg.png
642 ms
figure-big-bkg.png
682 ms
bekkenbodemspieren_width170_tcm375-102826.jpg
612 ms
Voedselbox_width170_tcm375-166027.jpg
622 ms
bottom-left-visual.png
646 ms
slideshow-bullet.png
651 ms
image-caption-bkg.png
664 ms
futurastd-heavy-webfont.woff
1007 ms
futurastd-medium-webfont.woff
1007 ms
fontello.woff
735 ms
analytics.js
28 ms
conversion_async.js
25 ms
fbds.js
25 ms
conversion.js
23 ms
glyphicons-halflings-regular.woff
22 ms
60 ms
51 ms
collect
25 ms
collect
59 ms
45 ms
ga-audiences
32 ms
widget_v2.132.js
10 ms
__$$__stringtable_lang_nl.js
22 ms
24 ms
aL63HcygAAVYuCCsAAA==
3 ms
cm.be 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
[role] values are not valid
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
cm.be 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
cm.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cm.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Cm.be 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.be
Open Graph description is not detected on the main page of CM. 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: