Tools & Wizards About Us
kasteelwijenburg.nl screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

kasteelwijenburg.nl

Trouwlocatie Kasteel Wijenburg - Romantische trouwlocatie - Trouwen in ons Kasteel in Echteld

Page Load Speed

15 sec in total

First Response

1.7 sec

Resources Loaded

12.5 sec

Page Rendered

812 ms

kasteelwijenburg.nl screenshot

About Website

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

Trouwlocatie Kasteel Wijenburg in Gelderland - Ons Kasteel heeft een prachtige uitstraling en mooie zalen - binnen trouwen of buiten trouwen

Visit kasteelwijenburg.nl

Key Findings

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

Performance Metrics

kasteelwijenburg.nl performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.8 s

0/100

25%

SI (Speed Index)

Value22.2 s

0/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

www.kasteelwijenburg.nl

1739 ms

style.css

280 ms

css

48 ms

css

65 ms

css

71 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 75% of them (44 requests) were addressed to the original Kasteelwijenburg.nl, 8% (5 requests) were made to Fonts.googleapis.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Kasteelwijenburg.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (22%)

Content Size

5.4 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 57.7 kB

  • Original 74.7 kB
  • After minification 69.8 kB
  • After compression 17.1 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 57.7 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 304.6 kB

  • Original 4.3 MB
  • After minification 4.0 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. Kasteel Wijenburg images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 458.4 kB

  • Original 627.0 kB
  • After minification 608.1 kB
  • After compression 168.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 458.4 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 354.2 kB

  • Original 412.2 kB
  • After minification 392.5 kB
  • After compression 58.0 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. Kasteelwijenburg.nl needs all CSS files to be minified and compressed as it can save up to 354.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (62%)

Requests Now

53

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.kasteelwijenburg.nl

www.kasteelwijenburg.nl

1739 ms

style.css

style.css

280 ms

css

css

48 ms

css

css

65 ms

css

css

71 ms

font-awesome.min.css

font-awesome.min.css

40 ms

jquery.js

jquery.js

40 ms

bootstrap.min.css

bootstrap.min.css

630 ms

bootstrap.min.js

bootstrap.min.js

369 ms

animate.css

animate.css

541 ms

css

css

19 ms

global.css

global.css

370 ms

style.min.css

style.min.css

755 ms

fonts.css

fonts.css

456 ms

sumoselect.min.css

sumoselect.min.css

557 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

842 ms

css

css

19 ms

styles.min.css

styles.min.css

909 ms

cookieblocker.min.css

cookieblocker.min.css

728 ms

swfobject.js

swfobject.js

812 ms

jquery.min.js

jquery.min.js

1318 ms

jquery-migrate.min.js

jquery-migrate.min.js

1011 ms

circle-progress.js

circle-progress.js

1163 ms

global.js

global.js

1115 ms

jquery.sumoselect.min.js

jquery.sumoselect.min.js

1272 ms

tocca.min.js

tocca.min.js

1206 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

1466 ms

jquery.fullscreen.min.js

jquery.fullscreen.min.js

1380 ms

scripts.min.js

scripts.min.js

2162 ms

require-utils.js

require-utils.js

1386 ms

js

js

42 ms

classic-10_7.css

classic-10_7.css

29 ms

mc-validate.js

mc-validate.js

58 ms

qppr_frontend_script.min.js

qppr_frontend_script.min.js

1364 ms

complianz.min.js

complianz.min.js

1588 ms

logo-zs.png

logo-zs.png

186 ms

Home-page-en-contact.jpg

Home-page-en-contact.jpg

2620 ms

keurmerk_trouwen-2.png

keurmerk_trouwen-2.png

364 ms

dwa_2012.png

dwa_2012.png

371 ms

dwa_2013.png

dwa_2013.png

371 ms

kaw-logo-se.png

kaw-logo-se.png

857 ms

Kasteel-Wijenburg-trouwlocatie.jpg

Kasteel-Wijenburg-trouwlocatie.jpg

2211 ms

Trouwen-in-de-winter-Kasteel-Wijenburg.jpg

Trouwen-in-de-winter-Kasteel-Wijenburg.jpg

2151 ms

Kasteel-Wijenburg-vergaderlocatie.jpg

Kasteel-Wijenburg-vergaderlocatie.jpg

2617 ms

OTR-300x300.jpg

OTR-300x300.jpg

646 ms

Kasteel-Wijenburg-home-2-2-1024x671.jpg

Kasteel-Wijenburg-home-2-2-1024x671.jpg

1674 ms

Romantische-trouwlocatie-2-2-1024x682.jpg

Romantische-trouwlocatie-2-2-1024x682.jpg

1735 ms

Kasteel-Wijenburg-home-4-2-1024x682.jpg

Kasteel-Wijenburg-home-4-2-1024x682.jpg

3023 ms

Romantische-trouwlocatie-3-1.jpg

Romantische-trouwlocatie-3-1.jpg

2429 ms

zalen.jpg

zalen.jpg

2902 ms

Romantisch-trouwen.jpg

Romantisch-trouwen.jpg

3729 ms

logo-footer.png

logo-footer.png

2722 ms

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

65 ms

tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf

tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf

110 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

112 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

112 ms

li-item.png

li-item.png

2834 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

55 ms

whatsapp-button.js

whatsapp-button.js

2768 ms

Accessibility Review

kasteelwijenburg.nl accessibility score

87

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

kasteelwijenburg.nl best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

kasteelwijenburg.nl SEO score

96

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

High

Tap targets are not sized appropriately

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

kasteelwijenburg.nl

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