6.8 sec in total
353 ms
6.1 sec
268 ms
Welcome to intus.nl homepage info - get ready to check Intus best content right away, or after learning these important things about intus.nl
Intus maakt planning concreet. Personeelsplanning, zelfroosteren, projectmanagement, resourcemanagement en portfoliomanagement
Visit intus.nlWe analyzed Intus.nl page load time and found that the first response time was 353 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
intus.nl performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value4.9 s
28/100
25%
Value3.1 s
93/100
10%
Value270 ms
82/100
30%
Value0.064
97/100
15%
Value6.0 s
64/100
10%
353 ms
1319 ms
270 ms
279 ms
327 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 99% of them (69 requests) were addressed to the original Intus.nl, 1% (1 request) were made to Server1.opentracker.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Intus.nl.
Page size can be reduced by 374.0 kB (28%)
1.3 MB
946.8 kB
In fact, the total size of Intus.nl 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. 25% of websites need less resources to load. Images take 955.7 kB which makes up the majority of the site volume.
Potential reduce by 28.5 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 28.5 kB or 81% of the original size.
Potential reduce by 83.2 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. Intus images are well optimized though.
Potential reduce by 195.8 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 195.8 kB or 78% of the original size.
Potential reduce by 66.4 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. Intus.nl needs all CSS files to be minified and compressed as it can save up to 66.4 kB or 84% of the original size.
Number of requests can be reduced by 41 (61%)
67
26
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intus. 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 from 19 to 1 for CSS and as a result speed up the page load time.
intus.nl
353 ms
www.intus.nl
1319 ms
system.base.css
270 ms
system.menus.css
279 ms
system.messages.css
327 ms
system.theme.css
334 ms
views_slideshow.css
360 ms
comment.css
383 ms
date.css
579 ms
datepicker.1.7.css
591 ms
field.css
607 ms
node.css
672 ms
search.css
673 ms
user.css
710 ms
views.css
853 ms
ctools.css
889 ms
quicktabs.css
927 ms
views_slideshow_cycle.css
943 ms
garland.css
967 ms
style.css
1233 ms
print.css
1162 ms
jquery.js
1390 ms
jquery.once.js
1216 ms
drupal.js
1354 ms
views_slideshow.js
1374 ms
jquery.cookie.js
1433 ms
jquery.form.js
1508 ms
ajax.js
1661 ms
progress.js
1662 ms
nl_6zSUMlFqq6_tY2kupLHX4KHoeWZGz6bZAdFK9yk4sMA.js
1704 ms
base.js
1737 ms
jquery.cycle.all.js
1987 ms
views_slideshow_cycle.js
1896 ms
ajax_view.js
1977 ms
piwik.js
1990 ms
quicktabs.js
2010 ms
server1.opentracker.net
19 ms
bg_info.jpg
228 ms
logo.png
163 ms
bg_topmenu_links.gif
313 ms
menu-leaf.png
311 ms
bg-menu-streep.gif
335 ms
bg_topmenu_rechts.gif
369 ms
bg_zoek.gif
483 ms
btn-zoek.gif
495 ms
wolken.jpg
1311 ms
4_2.png
1170 ms
1_3.png
1450 ms
2_2.png
1130 ms
3_3.png
1180 ms
bg-content.png
868 ms
bg-content-inhoud.gif
1221 ms
bg_content-front-inhoud-top.png
1478 ms
bg-sldieshow-menu.png
1502 ms
menu-pijl.png
1485 ms
btn-home-tab-hover-rechts.gif
1515 ms
icon_capaciteitsplanning%20%28optie%29.png
1594 ms
icon_zelfroosteren.png
1769 ms
icon_dienstrooster_1.png
1809 ms
icon_takenplanning.png
1814 ms
icon_flexpool_50x60.png
1804 ms
12098_icoonOnline_ruilen_0.png
1835 ms
icon_urenverantwoording%20%28optie%29.png
1915 ms
icon_intusmobile.png
2096 ms
icon_dienstrooster.png
2089 ms
piwik.js
2256 ms
chevin-light-webfont.woff
2185 ms
chevin-demibold-webfont.woff
2211 ms
chevin-medium-webfont.woff
2292 ms
zineslabdis-regularromantf-webfont.woff
2433 ms
intus.nl accessibility score
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
intus.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
intus.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
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intus.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 Intus.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.
intus.nl
Open Graph description is not detected on the main page of Intus. 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: