5 sec in total
263 ms
4.4 sec
352 ms
Visit cm.nl now to see the best up-to-date CM content for Egypt and also check out these interesting facts you probably never knew about cm.nl
Maximaliseer resultaten en overtreft verwachtingen door AI-gedreven software, creër hyper-gepersonaliseerde ervaringen. Ontdek meer »
Visit cm.nlWe analyzed Cm.nl page load time and found that the first response time was 263 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cm.nl performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value4.9 s
29/100
25%
Value7.2 s
30/100
10%
Value1,090 ms
24/100
30%
Value0.478
18/100
15%
Value9.5 s
30/100
10%
263 ms
792 ms
2053 ms
179 ms
264 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 40% of them (24 requests) were addressed to the original Cm.nl, 12% (7 requests) were made to Fast.wistia.com and 10% (6 requests) were made to Cdn.cmtelecom.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Cdn.cmtelecom.com.
Page size can be reduced by 1.3 MB (49%)
2.7 MB
1.4 MB
In fact, the total size of Cm.nl main page is 2.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. 45% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 66.7 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 66.7 kB or 72% of the original size.
Potential reduce by 2.0 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 953.0 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 953.0 kB or 60% of the original size.
Potential reduce by 319.3 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.nl needs all CSS files to be minified and compressed as it can save up to 319.3 kB or 81% of the original size.
Number of requests can be reduced by 14 (30%)
46
32
The browser has sent 46 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 15 to 1 for JavaScripts and as a result speed up the page load time.
cm.nl
263 ms
www.cm.nl
792 ms
cm-branding.min.css
2053 ms
app-516a72a4b3.css
179 ms
print-9be1f69964.css
264 ms
js
88 ms
app-8b61f5058f.js
784 ms
addthis_widget.js
58 ms
count.js
68 ms
E-v1.js
98 ms
j.php
155 ms
randstad.png
233 ms
parkmobile.png
233 ms
tasis.png
233 ms
eurovision-song-contest.png
323 ms
bestmanagedcompanies.jpg
323 ms
greatplacetowork.jpg
334 ms
deloittefast50.jpg
458 ms
redherring.jpg
457 ms
global_connections.jpg
526 ms
cm_building_breda.jpg
457 ms
connect-20333_960_720.jpg
526 ms
hongkong-south-africa-expansion.png
750 ms
gtm.js
285 ms
cm-logo-invert.png
523 ms
caroussel-cm.jpg
848 ms
carousel-analytics.jpg
675 ms
carousel-events.jpg
928 ms
carousel-nac.jpg
972 ms
map.png
753 ms
cm-icons.woff
211 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
313 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
328 ms
DINWebPro.woff
357 ms
fontawesome-webfont.woff
610 ms
DINWebPro-Light.woff
537 ms
DINWebPro-Bold.woff
509 ms
get-csrf-token
683 ms
iframe_shim
102 ms
v.gif
59 ms
9rhgol2k47.json
74 ms
load.sumome.com
666 ms
hotjar-48680.js
235 ms
requireEmail-v1.js
12 ms
fd58b9ed374077c21321a5f43c7a2aec8516e529.jpg
165 ms
WistiaOpenSansLight.woff
19 ms
WistiaOpenSansSemiBold.woff
58 ms
WistiaOpenSansBold.woff
58 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
38 ms
visit-data
271 ms
analytics.js
55 ms
linkid.js
14 ms
collect
11 ms
mput
220 ms
collect
63 ms
collect
22 ms
ga-audiences
36 ms
ga-audiences
27 ms
300lo.json
86 ms
sh.7c7179124ea24ac6ba46caac.html
48 ms
cm.nl 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.nl 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
cm.nl 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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cm.nl 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.nl 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.nl
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: