Tools & Wizards About Us
digitalehuis.nl screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

digitalehuis.nl

BouwConnect - Maak kennis met onze bouwsoftware en BIM-webapplicaties! - BouwConnect

Page Load Speed

5.8 sec in total

First Response

439 ms

Resources Loaded

3.9 sec

Page Rendered

1.5 sec

digitalehuis.nl screenshot

About Website

Visit digitalehuis.nl now to see the best up-to-date Digitalehuis content and also check out these interesting facts you probably never knew about digitalehuis.nl

Architecten, ontwerpers, aannemers, tekenbureaus, BIM-modelleurs en ingenieurs modelleren, detailleren, calculeren, toetsen en communiceren met onze samenwerkende software voor de bouw.

Visit digitalehuis.nl

Key Findings

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

Performance Metrics

digitalehuis.nl performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

digitalehuis.nl

439 ms

digitalehuis.nl

897 ms

gtm.js

175 ms

css

171 ms

css

292 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 63% of them (40 requests) were addressed to the original Digitalehuis.nl, 10% (6 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.8 kB (41%)

Content Size

748.2 kB

After Optimization

439.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digitalehuis.nl main page is 748.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 371.7 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 82.1 kB

  • Original 91.4 kB
  • After minification 75.9 kB
  • After compression 9.4 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 15.5 kB, which is 17% 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 82.1 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 7.8 kB

  • Original 242.9 kB
  • After minification 235.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. Digitalehuis images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 217.8 kB

  • Original 371.7 kB
  • After minification 364.2 kB
  • After compression 153.9 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 217.8 kB or 59% of the original size.

CSS Optimization

-3%

Potential reduce by 1.2 kB

  • Original 42.1 kB
  • After minification 41.9 kB
  • After compression 40.9 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. Digitalehuis.nl has all CSS files already compressed.

Requests Breakdown

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

Requests Now

54

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digitalehuis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

digitalehuis.nl

digitalehuis.nl

439 ms

digitalehuis.nl

digitalehuis.nl

897 ms

gtm.js

gtm.js

175 ms

css

css

171 ms

css

css

292 ms

formsOverrides.css

formsOverrides.css

297 ms

api.js

api.js

138 ms

eceb6d3c70.js

eceb6d3c70.js

206 ms

bootstrap.min.css

bootstrap.min.css

717 ms

font-awesome.min.css

font-awesome.min.css

841 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

776 ms

animate.min.css

animate.min.css

777 ms

owl.carousel.min.css

owl.carousel.min.css

646 ms

owl.theme.default.min.css

owl.theme.default.min.css

651 ms

StyleSheet.min.css

StyleSheet.min.css

839 ms

sharethis.js

sharethis.js

124 ms

jquery-3.0.0.min.js

jquery-3.0.0.min.js

115 ms

jquery.validate.min.js

jquery.validate.min.js

116 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

114 ms

recaptcha__en.js

recaptcha__en.js

204 ms

js.cookie.min.js

js.cookie.min.js

374 ms

jquery.min.js

jquery.min.js

1139 ms

popper.min.js

popper.min.js

625 ms

bootstrap.min.js

bootstrap.min.js

1132 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

1134 ms

jquery.lazy.min.js

jquery.lazy.min.js

1133 ms

wow.min.js

wow.min.js

1137 ms

jquery.slidereveal.min.js

jquery.slidereveal.min.js

1134 ms

owl.carousel.min.js

owl.carousel.min.js

1137 ms

scrollPosStyler.min.js

scrollPosStyler.min.js

1138 ms

bootstrap-fileselect.min.js

bootstrap-fileselect.min.js

1139 ms

general.js

general.js

1139 ms

uc.js

uc.js

495 ms

analytics.js

analytics.js

276 ms

cc.js

cc.js

575 ms

bouwconnect.svg

bouwconnect.svg

256 ms

bouwconnect-only-icon.svg

bouwconnect-only-icon.svg

251 ms

fabrikant-leverancier.jpg

fabrikant-leverancier.jpg

305 ms

architect-bimer-bouwkundige.jpg

architect-bimer-bouwkundige.jpg

1036 ms

bouwconnect-cad-company.jpg

bouwconnect-cad-company.jpg

260 ms

headerb-9900000000079e3c.png

headerb-9900000000079e3c.png

259 ms

tegel-online-cursus-on-demand-v2.png

tegel-online-cursus-on-demand-v2.png

260 ms

grid-orange.gif

grid-orange.gif

258 ms

bouwconnect-cad-company.jpg

bouwconnect-cad-company.jpg

261 ms

tweesnoeken.svg

tweesnoeken.svg

259 ms

woonconnect.svg

woonconnect.svg

1033 ms

architectuur.svg

architectuur.svg

1014 ms

bc-v4.min.html

bc-v4.min.html

1034 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

912 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

913 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

1234 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

1238 ms

rnCm-x5V0g7ipiTAT8M.ttf

rnCm-x5V0g7ipiTAT8M.ttf

1308 ms

rnCr-x5V0g7ipix7atM5kn0.ttf

rnCr-x5V0g7ipix7atM5kn0.ttf

1307 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1231 ms

ping.js

ping.js

1181 ms

home_banner-blauw.jpg

home_banner-blauw.jpg

537 ms

logo-vebo.jpg

logo-vebo.jpg

470 ms

logo-jpm-kok.jpg

logo-jpm-kok.jpg

470 ms

logo-plastica.jpg

logo-plastica.jpg

470 ms

logo-hoppe.jpg

logo-hoppe.jpg

469 ms

logo-dejo.jpg

logo-dejo.jpg

543 ms

collect

collect

162 ms

Accessibility Review

digitalehuis.nl accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

digitalehuis.nl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

digitalehuis.nl SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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 Digitalehuis.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 Digitalehuis.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

digitalehuis.nl

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