6.7 sec in total
386 ms
5.6 sec
680 ms
Welcome to content.nl homepage info - get ready to check Content best content right away, or after learning these important things about content.nl
Wij kijken verder, verder dan het cv en kijken naar jouw talent. Vind samen met ons de baan die echt bij jou past.
Visit content.nlWe analyzed Content.nl page load time and found that the first response time was 386 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
content.nl performance score
name
value
score
weighting
Value2.7 s
62/100
10%
Value13.8 s
0/100
25%
Value7.5 s
27/100
10%
Value1,740 ms
11/100
30%
Value0.002
100/100
15%
Value14.0 s
10/100
10%
386 ms
1041 ms
408 ms
1357 ms
196 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Content.nl, 77% (61 requests) were made to Unique.nl and 6% (5 requests) were made to . The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Unique.nl.
Page size can be reduced by 446.8 kB (18%)
2.4 MB
2.0 MB
In fact, the total size of Content.nl main page is 2.4 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. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 141.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 59.2 kB, which is 37% 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 141.0 kB or 89% of the original size.
Potential reduce by 23.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. Content images are well optimized though.
Potential reduce by 277.7 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 277.7 kB or 68% of the original size.
Potential reduce by 4.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. Content.nl needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 76% of the original size.
Number of requests can be reduced by 23 (34%)
68
45
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Content. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
content.nl
386 ms
www.unique.nl
1041 ms
www.unique.nl
408 ms
unique.nl
1357 ms
jquery.loadmask.min.css
196 ms
main-css
647 ms
vtx4shx.js
228 ms
Unique-animaties.css
284 ms
Telerik.Web.UI.WebResource.axd
300 ms
WebResource.axd
374 ms
Telerik.Web.UI.WebResource.axd
584 ms
require.js
391 ms
init.js
369 ms
swipeSlider.js
393 ms
d
131 ms
gtm.js
117 ms
UniqueLogo.png
103 ms
menuUniqueLogo.svg
102 ms
sticky-shadow.png
100 ms
menuShadow.jpg
101 ms
mobile-logo.svg
96 ms
arrow-right.png
100 ms
arrow-left.png
176 ms
crew-foto_marketingwidget.jpg
278 ms
lissabon_kandidaat.jpg
493 ms
foto_marketingwidget_unique-nlc56d0633cf886eb09f1bff000000717f.jpg
283 ms
award_marketingfeed.jpg
195 ms
mentality-match-1.png
196 ms
mijn-unique-icon-1.png
277 ms
mijn-unique-icon-2.png
304 ms
mijn-unique-icon-3.png
304 ms
websiteoftheyear.png
378 ms
gus.png
375 ms
20150622_uzbvhj_logos_274d70333cf886eb09f1bff000000717f.png
380 ms
onv.png
418 ms
usgpeople.png
411 ms
VyCMFk0AAAA=
26 ms
9XIIwWTQAAAA==
25 ms
9XIIwWTQAAAA==
23 ms
1cgjBZNAAAA
21 ms
VyCMFk0AAAA=
19 ms
logo-shadow.png
407 ms
mobile-search-background.png
411 ms
jquery-1.11.1.min.js
398 ms
home-header2.jpg
765 ms
werkenbijkpn-gs.png
434 ms
transavia.png
469 ms
ziggo_gs.png
472 ms
abn-amro-over.png
497 ms
megagroup-logistics53c3f432cf886eb09f1bff000000717f.png
494 ms
gdf-suez-(mousover).png
545 ms
20141230_overheid-amp-onderwijs.jpg
764 ms
branche-shadow.png
556 ms
20141230_industrie-amp-techniek.jpg
1240 ms
20141230_zakelijke-amp-financiele_dienstverlening.jpg
833 ms
20141230_logistiek-amp-transport.jpg
987 ms
20141230_bouw-amp-techniek.jpg
984 ms
20150104_retail.jpg
1081 ms
icomoon.woff
930 ms
p.gif
135 ms
bg-knowledge.jpg
994 ms
werken-bij-unique.png
1416 ms
knowledge.jpg
1137 ms
conversion_async.js
65 ms
analytics.js
49 ms
collect
27 ms
collect
63 ms
collect
32 ms
collect
71 ms
43 ms
29 ms
jquery-migrate-1.2.1.min.js
681 ms
main-js
194 ms
jquery.placeholder.min.js
91 ms
slick.js
87 ms
slick-arrow-left.png
92 ms
slick-arrow-right.png
92 ms
ajax-loader.gif
86 ms
cross-icon-28px.png
89 ms
content.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
[role]s do not have all required [aria-*] attributes
[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
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
content.nl 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
Missing source maps for large first-party JavaScript
content.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Content.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 Content.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.
content.nl
Open Graph description is not detected on the main page of Content. 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: