Tools & Wizards About Us
engelenburg.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

engelenburg.com

Onvergetelijke herinneringen - Kasteel Engelenburg

Page Load Speed

4.8 sec in total

First Response

200 ms

Resources Loaded

4 sec

Page Rendered

674 ms

engelenburg.com screenshot

About Website

Visit engelenburg.com now to see the best up-to-date Engelenburg content and also check out these interesting facts you probably never knew about engelenburg.com

Welkom op het betoverende landgoed van Kasteel Engelenburg. Altijd al willen overnachten in een kasteel? Ontdek onze prachtige kamers en suites, elk uniek en voorzien van hedendaags comfort. Geniet va...

Visit engelenburg.com

Key Findings

We analyzed Engelenburg.com page load time and found that the first response time was 200 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

engelenburg.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value26.0 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value4,240 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value45.4 s

0/100

10%

Network Requests Diagram

engelenburg.com

200 ms

engelenburg.com

1622 ms

nit2yuq.css

154 ms

theme.min.css

93 ms

style.css

185 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 74% of them (75 requests) were addressed to the original Engelenburg.com, 6% (6 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Api.taggrs.io. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Engelenburg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 159.8 kB (2%)

Content Size

8.7 MB

After Optimization

8.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Engelenburg.com main page is 8.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 154.9 kB

  • Original 186.8 kB
  • After minification 180.1 kB
  • After compression 31.9 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 154.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 7.9 MB
  • After minification 7.9 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. Engelenburg images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.0 kB

  • Original 432.9 kB
  • After minification 432.9 kB
  • After compression 430.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 3.0 kB

  • Original 113.7 kB
  • After minification 113.3 kB
  • After compression 110.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. Engelenburg.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 70 (79%)

Requests Now

89

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

engelenburg.com

engelenburg.com

200 ms

engelenburg.com

engelenburg.com

1622 ms

nit2yuq.css

nit2yuq.css

154 ms

theme.min.css

theme.min.css

93 ms

style.css

style.css

185 ms

frontend.css

frontend.css

275 ms

styles.css

styles.css

277 ms

gclid-field-type-style.css

gclid-field-type-style.css

277 ms

style.min.css

style.min.css

286 ms

cookieblocker.min.css

cookieblocker.min.css

287 ms

style.min.css

style.min.css

287 ms

header-footer.min.css

header-footer.min.css

367 ms

public.css

public.css

370 ms

golf-status-widget.css

golf-status-widget.css

373 ms

jet-elements.css

jet-elements.css

481 ms

jet-elements-skin.css

jet-elements-skin.css

382 ms

frontend-lite.min.css

frontend-lite.min.css

473 ms

swiper.min.css

swiper.min.css

457 ms

post-7.css

post-7.css

461 ms

frontend-lite.min.css

frontend-lite.min.css

463 ms

jet-tabs-frontend.css

jet-tabs-frontend.css

494 ms

all.min.css

all.min.css

550 ms

v4-shims.min.css

v4-shims.min.css

553 ms

post-8.css

post-8.css

555 ms

post-563.css

post-563.css

566 ms

post-570.css

post-570.css

568 ms

style.css

style.css

572 ms

language-cookie.js

language-cookie.js

640 ms

jquery.min.js

jquery.min.js

647 ms

jquery-migrate.min.js

jquery-migrate.min.js

657 ms

gclid-handler.js

gclid-handler.js

661 ms

v4-shims.min.js

v4-shims.min.js

662 ms

tag.js

tag.js

113 ms

angular.min.js

angular.min.js

69 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

36 ms

jquery-ui.min.js

jquery-ui.min.js

91 ms

bootstrap.min.css

bootstrap.min.css

48 ms

jquery-ui.css

jquery-ui.css

94 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

687 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

783 ms

widget-icon-list.min.css

widget-icon-list.min.css

782 ms

widget-icon-box.min.css

widget-icon-box.min.css

783 ms

post-2121.css

post-2121.css

783 ms

post-1169.css

post-1169.css

783 ms

css

css

49 ms

api.js

api.js

54 ms

post-9566.css

post-9566.css

782 ms

custom-elementor-form.js

custom-elementor-form.js

796 ms

p.css

p.css

29 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

707 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

615 ms

wp-polyfill.min.js

wp-polyfill.min.js

612 ms

hooks.min.js

hooks.min.js

613 ms

vue.min.js

vue.min.js

706 ms

jet-menu-public-scripts.js

jet-menu-public-scripts.js

680 ms

complianz.min.js

complianz.min.js

681 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

602 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

619 ms

webpack.runtime.min.js

webpack.runtime.min.js

618 ms

frontend-modules.min.js

frontend-modules.min.js

646 ms

i18n.min.js

i18n.min.js

570 ms

frontend.min.js

frontend.min.js

568 ms

waypoints.min.js

waypoints.min.js

608 ms

core.min.js

core.min.js

593 ms

frontend.min.js

frontend.min.js

575 ms

elements-handlers.min.js

elements-handlers.min.js

648 ms

jet-elements.min.js

jet-elements.min.js

593 ms

widgets-scripts.js

widgets-scripts.js

590 ms

jet-tabs-frontend.min.js

jet-tabs-frontend.min.js

603 ms

gtm.js

gtm.js

715 ms

widget.js

widget.js

38 ms

kasteel_engelenburg_favicon.svg

kasteel_engelenburg_favicon.svg

504 ms

calender_icon.svg

calender_icon.svg

506 ms

guests_icon.svg

guests_icon.svg

525 ms

promo_icon.svg

promo_icon.svg

532 ms

BEWLogo_hotel_footer-website_Kasteel_Engelenburg.aiBEW-RECHTE-TEKST-981x1024.png

BEWLogo_hotel_footer-website_Kasteel_Engelenburg.aiBEW-RECHTE-TEKST-981x1024.png

737 ms

104-Marja-Peter-YourWeddingPhotos-Peter-Lammers-scaled.jpg

104-Marja-Peter-YourWeddingPhotos-Peter-Lammers-scaled.jpg

1042 ms

main.js

main.js

19 ms

OILI601-1.svg

OILI601-1.svg

565 ms

OILI601-3.svg

OILI601-3.svg

575 ms

KasteelEngelenburg_CTWC_021122-28-768x1152.jpg

KasteelEngelenburg_CTWC_021122-28-768x1152.jpg

495 ms

KasteelEngelenburg_CTWC_021122-37-1-768x1152.jpg

KasteelEngelenburg_CTWC_021122-37-1-768x1152.jpg

682 ms

KasteelEngelenburg_CTWC_feb2022-74-768x1152.jpg

KasteelEngelenburg_CTWC_feb2022-74-768x1152.jpg

769 ms

Still-Algemeen-6-768x430.png

Still-Algemeen-6-768x430.png

793 ms

IMG_4256-scaled.jpg

IMG_4256-scaled.jpg

942 ms

OILI601-2.svg

OILI601-2.svg

768 ms

IMG_4125-1-scaled.jpg

IMG_4125-1-scaled.jpg

959 ms

Schermafbeelding-2023-10-04-om-13.06.12-e1696425686452.png

Schermafbeelding-2023-10-04-om-13.06.12-e1696425686452.png

1176 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

44 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

46 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

84 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

87 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

87 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

88 ms

recaptcha__en.js

recaptcha__en.js

95 ms

js

js

256 ms

client

client

182 ms

client

client

164 ms

client

client

165 ms

client

client

165 ms

landing

landing

78 ms

Accessibility Review

engelenburg.com accessibility score

92

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best Practices

engelenburg.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

engelenburg.com SEO score

100

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 Engelenburg.com 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 Engelenburg.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

engelenburg.com

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