Tools & Wizards About Us
vandeweyerhoeve.be screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

vandeweyerhoeve.be

Google Search Console - Melding over Sitemaps ontvangen

Page Load Speed

3.8 sec in total

First Response

588 ms

Resources Loaded

3 sec

Page Rendered

230 ms

vandeweyerhoeve.be screenshot

About Website

Welcome to vandeweyerhoeve.be homepage info - get ready to check Vandeweyerhoeve best content right away, or after learning these important things about vandeweyerhoeve.be

Visit vandeweyerhoeve.be

Key Findings

We analyzed Vandeweyerhoeve.be page load time and found that the first response time was 588 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 55% of websites can load faster.

Performance Metrics

vandeweyerhoeve.be performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.455

20/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

vandeweyerhoeve.be

588 ms

highslide.css

566 ms

highslide.js

657 ms

xr_main.css

297 ms

xr_text.css

311 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that all of those requests were addressed to Vandeweyerhoeve.be and no external sources were called. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Vandeweyerhoeve.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.2 kB (36%)

Content Size

356.6 kB

After Optimization

227.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vandeweyerhoeve.be main page is 356.6 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. Only 10% of websites need less resources to load. Images take 208.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 19.2 kB

  • Original 22.8 kB
  • After minification 22.6 kB
  • After compression 3.6 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 19.2 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 14.4 kB

  • Original 208.4 kB
  • After minification 194.0 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. Vandeweyerhoeve images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 73.9 kB

  • Original 99.8 kB
  • After minification 93.4 kB
  • After compression 25.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 73.9 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 21.8 kB

  • Original 25.6 kB
  • After minification 19.2 kB
  • After compression 3.8 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. Vandeweyerhoeve.be needs all CSS files to be minified and compressed as it can save up to 21.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (28%)

Requests Now

43

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vandeweyerhoeve.be

vandeweyerhoeve.be

588 ms

highslide.css

highslide.css

566 ms

highslide.js

highslide.js

657 ms

xr_main.css

xr_main.css

297 ms

xr_text.css

xr_text.css

311 ms

custom_styles.css

custom_styles.css

304 ms

roe.js

roe.js

695 ms

5.jpg

5.jpg

406 ms

6.png

6.png

228 ms

805.jpg

805.jpg

400 ms

806.jpg

806.jpg

404 ms

807.jpg

807.jpg

400 ms

808.jpg

808.jpg

404 ms

12.png

12.png

430 ms

133.jpg

133.jpg

769 ms

887.png

887.png

593 ms

888.png

888.png

592 ms

889.png

889.png

599 ms

890.png

890.png

595 ms

891.png

891.png

630 ms

892.png

892.png

779 ms

893.png

893.png

784 ms

894.png

894.png

787 ms

895.png

895.png

786 ms

447.png

447.png

828 ms

341.png

341.png

956 ms

644.jpg

644.jpg

1148 ms

3102.png

3102.png

1076 ms

898.jpg

898.jpg

973 ms

899.jpg

899.jpg

974 ms

900.jpg

900.jpg

1017 ms

901.jpg

901.jpg

1143 ms

902.jpg

902.jpg

1161 ms

903.jpg

903.jpg

1162 ms

904.jpg

904.jpg

1204 ms

905.jpg

905.jpg

1265 ms

906.jpg

906.jpg

1331 ms

456.jpg

456.jpg

1334 ms

351.jpg

351.jpg

1349 ms

zoomin.cur

zoomin.cur

1334 ms

custom.png

custom.png

100 ms

zoomout.cur

zoomout.cur

189 ms

loader.white.gif

loader.white.gif

189 ms

708.jpg

708.jpg

470 ms

Accessibility Review

vandeweyerhoeve.be accessibility score

87

Accessibility Issues

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

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

vandeweyerhoeve.be best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

vandeweyerhoeve.be SEO score

85

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

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vandeweyerhoeve.be 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 Vandeweyerhoeve.be main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

vandeweyerhoeve.be

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