Tools & Wizards About Us
boudewijnseapark.be screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

boudewijnseapark.be

Boudewijn Seapark - Dolfinarium | Pretpark | Waterpark in Brugge

Page Load Speed

2.5 sec in total

First Response

34 ms

Resources Loaded

1.7 sec

Page Rendered

790 ms

boudewijnseapark.be screenshot

About Website

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

Zin in een dolfijne dag vol avontuur? Kom dan naar Boudewijn Seapark! Geniet van de verschillende shows en ontdek alle attracties, zowel indoor als outdoor!

Visit boudewijnseapark.be

Key Findings

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

Performance Metrics

boudewijnseapark.be performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value3,560 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.406

24/100

15%

TTI (Time to Interactive)

Value24.3 s

0/100

10%

Network Requests Diagram

boudewijnseapark.be

34 ms

boudewijnseapark.be

263 ms

www.boudewijnseapark.be

44 ms

style.min.css

20 ms

styles.css

33 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 60% of them (33 requests) were addressed to the original Boudewijnseapark.be, 9% (5 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (639 ms) belongs to the original domain Boudewijnseapark.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 185.2 kB (7%)

Content Size

2.5 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Boudewijnseapark.be main page is 2.5 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. Only a small number of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 94.9 kB

  • Original 112.8 kB
  • After minification 89.7 kB
  • After compression 17.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 23.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 94.9 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 8 B

  • Original 1.2 MB
  • After minification 1.2 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. Boudewijn Seapark images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 90.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 1.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 15 B

  • Original 109.6 kB
  • After minification 109.6 kB
  • After compression 109.6 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. Boudewijnseapark.be has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (45%)

Requests Now

47

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

boudewijnseapark.be

boudewijnseapark.be

34 ms

boudewijnseapark.be

boudewijnseapark.be

263 ms

www.boudewijnseapark.be

www.boudewijnseapark.be

44 ms

style.min.css

style.min.css

20 ms

styles.css

styles.css

33 ms

css

css

30 ms

app.min.css

app.min.css

35 ms

email-decode.min.js

email-decode.min.js

22 ms

app.min.js

app.min.js

115 ms

gtm.js

gtm.js

333 ms

iframe_api

iframe_api

317 ms

bg-pattern-5.svg

bg-pattern-5.svg

409 ms

logo-boudewijn-seapark-solid-white-blue.svg

logo-boudewijn-seapark-solid-white-blue.svg

34 ms

bobo-masthead-top.png

bobo-masthead-top.png

31 ms

bobo-masthead-arm.png

bobo-masthead-arm.png

31 ms

bobo-masthead-bottom.png

bobo-masthead-bottom.png

304 ms

1920x1080-homepage3.jpg

1920x1080-homepage3.jpg

306 ms

400x400-piratenboot-400x400.jpg

400x400-piratenboot-400x400.jpg

569 ms

400x400-kalender-400x400.jpg

400x400-kalender-400x400.jpg

406 ms

bg-pattern-10.svg

bg-pattern-10.svg

448 ms

400x300-waterbaan-400x300.jpg

400x300-waterbaan-400x300.jpg

572 ms

400x300-IWD5.jpg

400x300-IWD5.jpg

307 ms

400x400-abonnement.jpg

400x400-abonnement.jpg

406 ms

400x400-verjaardag.jpg

400x400-verjaardag.jpg

484 ms

usp-tick.svg

usp-tick.svg

481 ms

plan-boudewijnseapark-1772x1080.jpg

plan-boudewijnseapark-1772x1080.jpg

484 ms

boudewijn-bobo-large.png

boudewijn-bobo-large.png

485 ms

curve-overlay.svg

curve-overlay.svg

485 ms

logo.png

logo.png

572 ms

footer-curve-top.svg

footer-curve-top.svg

570 ms

footer-curve-middle.svg

footer-curve-middle.svg

568 ms

footer-curve-bottom.svg

footer-curve-bottom.svg

568 ms

icon-weather-clear-day.svg

icon-weather-clear-day.svg

573 ms

bg-pattern-dark-3.svg

bg-pattern-dark-3.svg

639 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

304 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQVIT9d4cw.ttf

402 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQVIT9d4cw.ttf

567 ms

update.min.js

update.min.js

476 ms

get

get

333 ms

www-widgetapi.js

www-widgetapi.js

226 ms

js

js

131 ms

analytics.js

analytics.js

126 ms

uc.js

uc.js

244 ms

icon-weather-overcast.svg

icon-weather-overcast.svg

214 ms

7CFtVw3LyKQ

7CFtVw3LyKQ

163 ms

collect

collect

41 ms

collect

collect

88 ms

www-player.css

www-player.css

16 ms

www-embed-player.js

www-embed-player.js

45 ms

base.js

base.js

108 ms

ga-audiences

ga-audiences

353 ms

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

70 ms

embed.js

embed.js

13 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

31 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

31 ms

Accessibility Review

boudewijnseapark.be accessibility score

75

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

Image elements do not have [alt] attributes

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

boudewijnseapark.be best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

boudewijnseapark.be SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

boudewijnseapark.be

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