Tools & Wizards About Us
eeckhout.be screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

eeckhout.be

Agence Eeckhout - Vind hier uw huis, appartement te huur of te koop in Oostende

Page Load Speed

13.2 sec in total

First Response

429 ms

Resources Loaded

6.4 sec

Page Rendered

6.4 sec

eeckhout.be screenshot

About Website

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

Agence Eeckhout : vastgoed - Immo - verkoop - verhuur. U zoekt een betrouwbare sleutelfiguur voor al uw vastgoed en immo in de regio Oostende en de kuststreek.

Visit eeckhout.be

Key Findings

We analyzed Eeckhout.be page load time and found that the first response time was 429 ms and then it took 12.8 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

eeckhout.be performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value5,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

eeckhout.be

429 ms

www.eeckhout.be

1180 ms

css

62 ms

eeckhout.css

102 ms

styles.min.css

1898 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 21% of them (5 requests) were addressed to the original Eeckhout.be, 42% (10 requests) were made to Skarabeestatic.b-cdn.net and 17% (4 requests) were made to Skarabeecmsfilestore.b-cdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Skarabeestatic.b-cdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.1 kB (1%)

Content Size

2.4 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eeckhout.be main page is 2.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. 45% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 11.4 kB

  • Original 15.3 kB
  • After minification 12.2 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 3.1 kB, which is 20% 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 11.4 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 3.9 kB

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

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-60%

Potential reduce by 756 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 496 B

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. Eeckhout.be needs all CSS files to be minified and compressed as it can save up to 756 B or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (67%)

Requests Now

21

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eeckhout.be

eeckhout.be

429 ms

www.eeckhout.be

www.eeckhout.be

1180 ms

css

css

62 ms

eeckhout.css

eeckhout.css

102 ms

styles.min.css

styles.min.css

1898 ms

bootstrap-select.min.css

bootstrap-select.min.css

1874 ms

FileStore.ashx

FileStore.ashx

1864 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

3155 ms

jquery.validate.min.js

jquery.validate.min.js

1873 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

2996 ms

Skarabee.min.js

Skarabee.min.js

1870 ms

jquery.lazy-load-google-maps.min.js

jquery.lazy-load-google-maps.min.js

3149 ms

modernizr.custom.68468.js

modernizr.custom.68468.js

2988 ms

bootstrap.min.js

bootstrap.min.js

2989 ms

bootstrap-select.min.js

bootstrap-select.min.js

3093 ms

functions.js

functions.js

2988 ms

FileStore.ashx

FileStore.ashx

1880 ms

FileStore.ashx

FileStore.ashx

2984 ms

FileStore.ashx

FileStore.ashx

2984 ms

Agence-Eeckhout-Oostende.jpg

Agence-Eeckhout-Oostende.jpg

2681 ms

sdk.js

sdk.js

1769 ms

eeckhout.woff

eeckhout.woff

1434 ms

ga.js

ga.js

970 ms

sdk.js

sdk.js

116 ms

Accessibility Review

eeckhout.be accessibility score

74

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

eeckhout.be 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

eeckhout.be 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

    BE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eeckhout.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed Byelorussian language. Our system also found out that Eeckhout.be 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

eeckhout.be

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