Tools & Wizards About Us

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

ebookers.be

Reizen met Expedia: vakantiewoningen, hotels, autoverhuur, vluchten & meer

Page Load Speed

8.4 sec in total

First Response

3.5 sec

Resources Loaded

4.6 sec

Page Rendered

340 ms

About Website

Visit ebookers.be now to see the best up-to-date Ebookers content for Belgium and also check out these interesting facts you probably never knew about ebookers.be

Je alles-in-één reiswebsite voor jouw droomvakantie. Bundel je verblijf met een huurauto of vlucht zodat je nog meer geld kunt besparen. Doorzoek onze flexibele opties en vind een reis die aan al je w...

Visit ebookers.be

Key Findings

We analyzed Ebookers.be page load time and found that the first response time was 3.5 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ebookers.be performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value7,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value26.2 s

0/100

10%

Network Requests Diagram

www.expedia.be

3466 ms

sparkle_white.svg

88 ms

logo.svg

73 ms

nl_BE.7bd24ccfeca3e37ad256.js

97 ms

mobx.0e37a90d07e1ad4b6ea1.js

116 ms

Our browser made a total of 151 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ebookers.be, 8% (12 requests) were made to Forever.travel-assets.com and 4% (6 requests) were made to Expedia.be. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Expedia.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.4 MB (63%)

Content Size

8.6 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ebookers.be main page is 8.6 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. 80% 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. Javascripts take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 250.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. 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 1.4 MB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-68%

Potential reduce by 4.1 MB

  • Original 6.0 MB
  • After minification 6.0 MB
  • After compression 1.9 MB

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 4.1 MB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 128 (88%)

Requests Now

146

After Optimization

18

  • Images
  • JavaScript

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

Network Requests Diagram

Accessibility Review

ebookers.be accessibility score

100

Accessibility Issues

Best Practices

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

ebookers.be SEO score

99

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

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