Tools & Wizards About Us
intus.nl screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

intus.nl

Intus | Samen Slimmer Plannen

Page Load Speed

4.9 sec in total

First Response

303 ms

Resources Loaded

3 sec

Page Rendered

1.6 sec

intus.nl screenshot

About Website

Welcome to intus.nl homepage info - get ready to check Intus best content right away, or after learning these important things about intus.nl

Visit intus.nl

Key Findings

We analyzed Intus.nl page load time and found that the first response time was 303 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

intus.nl performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

intus.nl

303 ms

www.intus.nl

623 ms

main.min.css

139 ms

rich-text.min.css

267 ms

module_65807401433_icon.min.css

372 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 84% of them (59 requests) were addressed to the original Intus.nl, 3% (2 requests) were made to Cdn2.hubspot.net and 1% (1 request) were made to Static.hsappstatic.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Intus.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.4 kB (4%)

Content Size

4.4 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intus.nl main page is 4.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. 35% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 127.9 kB

  • Original 150.6 kB
  • After minification 129.5 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 21.1 kB, which is 14% 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 127.9 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 35.1 kB

  • Original 4.2 MB
  • After minification 4.1 MB

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.

JavaScript Optimization

-12%

Potential reduce by 7.7 kB

  • Original 62.4 kB
  • After minification 62.4 kB
  • After compression 54.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 7.7 kB or 12% of the original size.

CSS Optimization

-44%

Potential reduce by 11.6 kB

  • Original 26.4 kB
  • After minification 16.3 kB
  • After compression 14.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. Intus.nl needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (59%)

Requests Now

64

After Optimization

26

  • Images
  • JavaScript
  • CSS

The browser has sent 64 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 17 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

intus.nl

intus.nl

303 ms

www.intus.nl

www.intus.nl

623 ms

main.min.css

main.min.css

139 ms

rich-text.min.css

rich-text.min.css

267 ms

module_65807401433_icon.min.css

module_65807401433_icon.min.css

372 ms

nav.min.css

nav.min.css

375 ms

lang-select.min.css

lang-select.min.css

400 ms

site-search.min.css

site-search.min.css

382 ms

mobile-nav.min.css

mobile-nav.min.css

384 ms

header-04.min.css

header-04.min.css

427 ms

splide.min.css

splide.min.css

600 ms

hero-slider.min.css

hero-slider.min.css

580 ms

properties.min.css

properties.min.css

611 ms

box-over-image.min.css

box-over-image.min.css

616 ms

section-extra-settings.min.css

section-extra-settings.min.css

512 ms

section-intro.min.css

section-intro.min.css

556 ms

feature-card.min.css

feature-card.min.css

636 ms

quick-action.min.css

quick-action.min.css

777 ms

module_-35056501883_Video.min.css

module_-35056501883_Video.min.css

79 ms

logos.min.css

logos.min.css

792 ms

compact-card.min.css

compact-card.min.css

819 ms

quote.min.css

quote.min.css

818 ms

blog-card.min.css

blog-card.min.css

828 ms

column-navigation.min.css

column-navigation.min.css

751 ms

footer-11.min.css

footer-11.min.css

864 ms

main.min.js

main.min.js

1029 ms

embed.js

embed.js

49 ms

lightbox.min.js

lightbox.min.js

1028 ms

project.js

project.js

1030 ms

nav.min.js

nav.min.js

1030 ms

lang-select.min.js

lang-select.min.js

1029 ms

site-search.min.js

site-search.min.js

1032 ms

mobile-nav.min.js

mobile-nav.min.js

1032 ms

splide.min.js

splide.min.js

1035 ms

module_-35056501883_Video.min.js

module_-35056501883_Video.min.js

70 ms

26315547.js

26315547.js

452 ms

index.js

index.js

1049 ms

cropped-Logo_Intus_liggend_rgb-e1626272664215.png

cropped-Logo_Intus_liggend_rgb-e1626272664215.png

152 ms

0003_Intus_Klantendag_00303_3639_websize%20%282%29.jpg

0003_Intus_Klantendag_00303_3639_websize%20%282%29.jpg

495 ms

061_Intus_0794_5053_HR.jpg

061_Intus_0794_5053_HR.jpg

266 ms

Logo_InPlanning_liggend_rgb.png

Logo_InPlanning_liggend_rgb.png

290 ms

logo.svg

logo.svg

418 ms

Antonius_Logo%2BPayoff2021_rgb_Magenta_pos.png

Antonius_Logo%2BPayoff2021_rgb_Magenta_pos.png

270 ms

Logo%20woordmerk%20Gelre%20ziekenhuizen%20rgb.png

Logo%20woordmerk%20Gelre%20ziekenhuizen%20rgb.png

365 ms

holland%20casino.png

holland%20casino.png

412 ms

Logo_HBUE_vorm_paars-oranje.png

Logo_HBUE_vorm_paars-oranje.png

387 ms

brandweer.png

brandweer.png

424 ms

Handhaving%20Den%20Haag.png

Handhaving%20Den%20Haag.png

587 ms

0107452c04cd9e1827e2660fe17dda5a.png

0107452c04cd9e1827e2660fe17dda5a.png

514 ms

Basalt-logo-met-payoff-RGB.png

Basalt-logo-met-payoff-RGB.png

656 ms

beeldmerk-ggz-breburg.png

beeldmerk-ggz-breburg.png

536 ms

cropped-ADHD-icon-transparant%20(1).png

cropped-ADHD-icon-transparant%20(1).png

565 ms

RSC-logo-1.png

RSC-logo-1.png

614 ms

logo_Accare_RGB.png

logo_Accare_RGB.png

632 ms

logo-archipel.png

logo-archipel.png

740 ms

logo-Rijnhoven.png

logo-Rijnhoven.png

730 ms

Mars-Olen-Geert-800x864%20(1).jpg

Mars-Olen-Geert-800x864%20(1).jpg

739 ms

Altrecht%20HappyNurse.jpg

Altrecht%20HappyNurse.jpg

789 ms

Happy%20Nurse.jpg

Happy%20Nurse.jpg

1007 ms

20240404%20LinkedIn-RoessinghxIntus.jpg

20240404%20LinkedIn-RoessinghxIntus.jpg

1121 ms

regular.woff

regular.woff

881 ms

600.woff

600.woff

834 ms

700.woff

700.woff

944 ms

insight.min.js

insight.min.js

35 ms

banner.js

banner.js

529 ms

26315547.js

26315547.js

521 ms

collectedforms.js

collectedforms.js

510 ms

fb.js

fb.js

471 ms

insight_tag_errors.gif

insight_tag_errors.gif

85 ms

li_sync

li_sync

20 ms

Accessibility Review

intus.nl accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

intus.nl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

intus.nl SEO score

93

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    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.

Social Sharing Optimization

intus.nl

Open Graph data is detected on the main page of Intus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: