Tools & Wizards About Us
tuinhuis.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

tuinhuis.com

HOME | Blokhutwereld

Page Load Speed

3.3 sec in total

First Response

300 ms

Resources Loaded

2.8 sec

Page Rendered

188 ms

tuinhuis.com screenshot

About Website

Click here to check amazing Tuinhuis content. Otherwise, check out these important facts you probably never knew about tuinhuis.com

Van tuinhuizen tot chalets, wij creëren uw perfecte buitenverblijf met eerlijk advies en scherpe prijzen

Visit tuinhuis.com

Key Findings

We analyzed Tuinhuis.com page load time and found that the first response time was 300 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

tuinhuis.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.86

4/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

tuinhuis.com

300 ms

www.tuinhuis.com

476 ms

style.css

167 ms

css

25 ms

css

38 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 61% of them (56 requests) were addressed to the original Tuinhuis.com, 11% (10 requests) were made to Static.xx.fbcdn.net and 5% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (685 ms) belongs to the original domain Tuinhuis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (57%)

Content Size

1.8 MB

After Optimization

766.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tuinhuis.com main page is 1.8 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. 55% of websites need less resources to load. Javascripts take 894.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 49.5 kB

  • Original 69.9 kB
  • After minification 65.8 kB
  • After compression 20.3 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 49.5 kB or 71% of the original size.

Image Optimization

-10%

Potential reduce by 44.6 kB

  • Original 431.9 kB
  • After minification 387.3 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. Tuinhuis images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 595.0 kB

  • Original 894.3 kB
  • After minification 878.0 kB
  • After compression 299.2 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 595.0 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 324.2 kB

  • Original 383.3 kB
  • After minification 351.2 kB
  • After compression 59.1 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. Tuinhuis.com needs all CSS files to be minified and compressed as it can save up to 324.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (40%)

Requests Now

86

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tuinhuis.com

tuinhuis.com

300 ms

www.tuinhuis.com

www.tuinhuis.com

476 ms

style.css

style.css

167 ms

css

css

25 ms

css

css

38 ms

colorbox.css

colorbox.css

176 ms

jquery-ui-1.8.11.custom.css

jquery-ui-1.8.11.custom.css

177 ms

ui.selectmenu.css

ui.selectmenu.css

175 ms

jquery.js

jquery.js

262 ms

jquery-ui-1.8.10.min.js

jquery-ui-1.8.10.min.js

356 ms

base.js

base.js

246 ms

ui.selectmenu.js

ui.selectmenu.js

254 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

257 ms

jquery.cookie.js

jquery.cookie.js

257 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

326 ms

jquery.viewport.js

jquery.viewport.js

337 ms

addthis_widget.js

addthis_widget.js

13 ms

showroom-tuinhuis.png

showroom-tuinhuis.png

218 ms

maatwerk-specialisten.png

maatwerk-specialisten.png

224 ms

new_maatwerk-banner-home.png

new_maatwerk-banner-home.png

434 ms

new_icon-check-yellow.png

new_icon-check-yellow.png

143 ms

new_maatwerk-button-orange.png

new_maatwerk-button-orange.png

145 ms

new_maatwerk-button-black.png

new_maatwerk-button-black.png

144 ms

new_product-bg-big.png

new_product-bg-big.png

249 ms

image-chalets.jpg

image-chalets.jpg

336 ms

image-blokhutten.jpg

image-blokhutten.jpg

281 ms

264x214-mode[3]-cropFrom[Center]-bg[ffffff]-brabant11.jpg

264x214-mode[3]-cropFrom[Center]-bg[ffffff]-brabant11.jpg

309 ms

houten_garages.jpg

houten_garages.jpg

314 ms

124x101-mode[3]-cropFrom[Center]-bg[ffffff]-plaatje.jpg

124x101-mode[3]-cropFrom[Center]-bg[ffffff]-plaatje.jpg

336 ms

new_banner.png

new_banner.png

416 ms

sidebar-heading-bg.png

sidebar-heading-bg.png

392 ms

tevreden-klanten.jpg

tevreden-klanten.jpg

401 ms

icon-arrow-right.png

icon-arrow-right.png

418 ms

nav-bg1.jpg

nav-bg1.jpg

417 ms

logo-tuinhuiswereld.png

logo-tuinhuiswereld.png

472 ms

header-banner.png

header-banner.png

486 ms

icon-cart-new.png

icon-cart-new.png

504 ms

cart-hover-bg.png

cart-hover-bg.png

506 ms

icon-arrow-order.gif

icon-arrow-order.gif

507 ms

icon-phone-new.png

icon-phone-new.png

517 ms

foldout-shadow.png

foldout-shadow.png

553 ms

icon-clock-new.png

icon-clock-new.png

570 ms

icon-email-new.png

icon-email-new.png

586 ms

tuinhuis.com-email-g.png

tuinhuis.com-email-g.png

587 ms

search-input-bg.gif

search-input-bg.gif

589 ms

search-submit.gif

search-submit.gif

606 ms

nav-active.png

nav-active.png

635 ms

footer-bg-new.png

footer-bg-new.png

654 ms

footer-logo.png

footer-logo.png

671 ms

icon-arrow-mini.gif

icon-arrow-mini.gif

670 ms

icon-clock-white.png

icon-clock-white.png

674 ms

icon-phone-white.png

icon-phone-white.png

685 ms

ga.js

ga.js

42 ms

6qyLrE2wJK8

6qyLrE2wJK8

134 ms

likebox.php

likebox.php

179 ms

icon-email-white.png

icon-email-white.png

647 ms

s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff

s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff

70 ms

EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff

EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff

92 ms

all.js

all.js

293 ms

300lo.json

300lo.json

78 ms

__utm.gif

__utm.gif

41 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

39 ms

email-footer.png

email-footer.png

601 ms

overlay.png

overlay.png

628 ms

controls.png

controls.png

625 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

25 ms

www-embed-player.js

www-embed-player.js

47 ms

border.png

border.png

556 ms

loading_background.png

loading_background.png

552 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

295 ms

tSbl8xBI27R.css

tSbl8xBI27R.css

363 ms

1kPfZUdGrka.js

1kPfZUdGrka.js

500 ms

Yuj_Y8xNH2C.js

Yuj_Y8xNH2C.js

632 ms

Mpe38fuBVZ2.js

Mpe38fuBVZ2.js

521 ms

n8qIhCw3vMx.js

n8qIhCw3vMx.js

520 ms

loading.gif

loading.gif

551 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

52 ms

ad_status.js

ad_status.js

57 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

53 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

53 ms

32 ms

xd_arbiter.php

xd_arbiter.php

212 ms

xd_arbiter.php

xd_arbiter.php

422 ms

47557_435769963154556_1536090796_n.jpg

47557_435769963154556_1536090796_n.jpg

353 ms

10858426_854018704663011_8738033092460493416_n.jpg

10858426_854018704663011_8738033092460493416_n.jpg

420 ms

12219321_953801554710189_8108266244257136847_n.jpg

12219321_953801554710189_8108266244257136847_n.jpg

488 ms

12743623_965246886843887_8644177875868623608_n.jpg

12743623_965246886843887_8644177875868623608_n.jpg

555 ms

1743487_739883659430955_6001187190117738697_n.jpg

1743487_739883659430955_6001187190117738697_n.jpg

557 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

79 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

78 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

69 ms

AmlxWlqMvlv.js

AmlxWlqMvlv.js

137 ms

Accessibility Review

tuinhuis.com accessibility score

52

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

tuinhuis.com best practices score

67

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

tuinhuis.com SEO score

69

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tuinhuis.com 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 Tuinhuis.com 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

tuinhuis.com

Open Graph description is not detected on the main page of Tuinhuis. 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: