Tools & Wizards About Us
kasteelwijnen.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% 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

kasteelwijnen.com

Kasteelovernachtingen - wijnreizen en wijnproeven

Page Load Speed

3.9 sec in total

First Response

752 ms

Resources Loaded

2.7 sec

Page Rendered

457 ms

kasteelwijnen.com screenshot

About Website

Click here to check amazing Kasteelwijn En content. Otherwise, check out these important facts you probably never knew about kasteelwijnen.com

Kasteelovernachtingen, wijnvakanties, wijnreizen, wijnproeven, wijnveilingen, wijnexcursies en unieke kasteelwijnen ontdekken in Frankrijk en Italië!

Visit kasteelwijnen.com

Key Findings

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

Performance Metrics

kasteelwijnen.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value900 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

www.kasteelwijnen.com

752 ms

styles.72280dcdfb5686eb034b.css

94 ms

style.css

34 ms

js

71 ms

script.manual.js

26 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Kasteelwijnen.com, 44% (11 requests) were made to Primary.jwwb.nl and 24% (6 requests) were made to Assets.jwwb.nl. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Primary.jwwb.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.9 kB (6%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 97.4 kB

  • Original 112.4 kB
  • After minification 98.4 kB
  • After compression 15.0 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 14.1 kB, which is 13% 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 97.4 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 1.4 MB
  • After minification 1.4 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. Kasteelwijn En images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 4.0 kB

  • Original 133.4 kB
  • After minification 133.4 kB
  • After compression 129.4 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

-1%

Potential reduce by 360 B

  • Original 44.7 kB
  • After minification 44.7 kB
  • After compression 44.3 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. Kasteelwijnen.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (41%)

Requests Now

22

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.kasteelwijnen.com

www.kasteelwijnen.com

752 ms

styles.72280dcdfb5686eb034b.css

styles.72280dcdfb5686eb034b.css

94 ms

style.css

style.css

34 ms

js

js

71 ms

script.manual.js

script.manual.js

26 ms

js

js

137 ms

nl-NL.js

nl-NL.js

90 ms

runtime.360f4e70e672972a7df1.js

runtime.360f4e70e672972a7df1.js

68 ms

41.740c8f9b06086267a83f.js

41.740c8f9b06086267a83f.js

124 ms

main.f82f42d9e7aa0bf520cb.js

main.f82f42d9e7aa0bf520cb.js

123 ms

1774897

1774897

443 ms

logokasteelwijnen90x84.png

logokasteelwijnen90x84.png

253 ms

94861ad9-a76c-40fe-a356-c909322325b1.js

94861ad9-a76c-40fe-a356-c909322325b1.js

549 ms

39.png

39.png

1125 ms

71-psd-verduno-2-high.jpg

71-psd-verduno-2-high.jpg

539 ms

image-538.png

image-538.png

727 ms

centvmvitisfoto1.jpg

centvmvitisfoto1.jpg

458 ms

logo_castello_di_verduno_200_x_75-1.png

logo_castello_di_verduno_200_x_75-1.png

473 ms

logo_marchesi_alfieri_200_x_74-1.jpeg

logo_marchesi_alfieri_200_x_74-1.jpeg

593 ms

logo_chateau_du_rouet_225_x_74-1.gif

logo_chateau_du_rouet_225_x_74-1.gif

786 ms

logo_poderi_luigi_einaudi_225_x_91.jpeg

logo_poderi_luigi_einaudi_225_x_91.jpeg

890 ms

nix18.jpg

nix18.jpg

902 ms

website-rendering.woff

website-rendering.woff

2 ms

ppms.js

ppms.js

94 ms

ppms.php

ppms.php

357 ms

Accessibility Review

kasteelwijnen.com accessibility score

96

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

kasteelwijnen.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

kasteelwijnen.com

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