Tools & Wizards About Us
vivabox.be screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

vivabox.be

vivabox BE | Geschenkdoos met originele geschenkideeën

Page Load Speed

2.9 sec in total

First Response

267 ms

Resources Loaded

2.5 sec

Page Rendered

172 ms

vivabox.be screenshot

About Website

Click here to check amazing Vivabox content for Belgium. Otherwise, check out these important facts you probably never knew about vivabox.be

Schenk aan uw naasten een geschenkdoos, een 2-in-1 box met een cadeau en een activiteit: verblijf, wellnessmoment of gastronomische pauze. Perfect als verjaardags-, huwelijks- of kerstgeschenk …

Visit vivabox.be

Key Findings

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

vivabox.be performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

nl

267 ms

libs.css

160 ms

ui.css

318 ms

style.css

401 ms

header.css

246 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 88% of them (37 requests) were addressed to the original Vivabox.be, 7% (3 requests) were made to Sdk.privacy-center.org and 2% (1 request) were made to Wonderbox.ugc.bazaarvoice.com. The less responsive or slowest element that took the longest time to load (645 ms) belongs to the original domain Vivabox.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.6 kB (8%)

Content Size

982.4 kB

After Optimization

904.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 68.0 kB

  • Original 85.5 kB
  • After minification 75.6 kB
  • After compression 17.5 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 10.0 kB, which is 12% 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 68.0 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 8.0 kB

  • Original 488.4 kB
  • After minification 480.3 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. Vivabox images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 293 B

  • Original 262.3 kB
  • After minification 262.3 kB
  • After compression 262.0 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 1.2 kB

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

Requests Breakdown

Number of requests can be reduced by 20 (51%)

Requests Now

39

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vivabox. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nl

nl

267 ms

libs.css

libs.css

160 ms

ui.css

ui.css

318 ms

style.css

style.css

401 ms

header.css

header.css

246 ms

box.css

box.css

240 ms

popin-checkout.css

popin-checkout.css

250 ms

footer.css

footer.css

243 ms

homepage.css

homepage.css

328 ms

style.css

style.css

328 ms

recaptchaaddon.css

recaptchaaddon.css

330 ms

analyticsmediator.js

analyticsmediator.js

330 ms

generatedVariables.js

generatedVariables.js

325 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

417 ms

swiper.min.js

swiper.min.js

426 ms

lazysizes.min.js

lazysizes.min.js

418 ms

bvapi.js

bvapi.js

136 ms

libs.min.js

libs.min.js

512 ms

wonder.min.js

wonder.min.js

573 ms

recaptcha.min.js

recaptcha.min.js

425 ms

gtm.js

gtm.js

133 ms

VIVA-Cartouche-blanc.png

VIVA-Cartouche-blanc.png

154 ms

BE_NL_VIVA_HP_IHAVEABOX_mobile.jpg

BE_NL_VIVA_HP_IHAVEABOX_mobile.jpg

208 ms

BE_NL_VIVA_HP_STAY_mobile.jpg

BE_NL_VIVA_HP_STAY_mobile.jpg

154 ms

BE_NL_VIVA_HP_GASTRO_mobile.jpg

BE_NL_VIVA_HP_GASTRO_mobile.jpg

153 ms

BE_NL_VIVA_HP_WELLNESS_mobile.jpg

BE_NL_VIVA_HP_WELLNESS_mobile.jpg

204 ms

BE_NL_VIVA_HP_SPORT_mobile.jpg

BE_NL_VIVA_HP_SPORT_mobile.jpg

209 ms

BE_NL_VIVA_HP_CINEMA_mobile.jpg

BE_NL_VIVA_HP_CINEMA_mobile.jpg

210 ms

BE_NL_VIVA_HP_BREAKFAST_mobile.jpg

BE_NL_VIVA_HP_BREAKFAST_mobile.jpg

213 ms

BE_NL_VIVA_HP_MULTI_mobile.jpg

BE_NL_VIVA_HP_MULTI_mobile.jpg

327 ms

vivabox-kv-desk.jpg

vivabox-kv-desk.jpg

329 ms

Clients_satisfaits.svg

Clients_satisfaits.svg

327 ms

icomoon.woff

icomoon.woff

290 ms

loader.js

loader.js

159 ms

BE_NL_VIVA_HP_IHAVEABOX_desktop.jpg

BE_NL_VIVA_HP_IHAVEABOX_desktop.jpg

258 ms

BE_FR_VIVA_HP_STAY_desktop.jpg

BE_FR_VIVA_HP_STAY_desktop.jpg

259 ms

BE_FR_VIVA_HP_GASTRO_desktop.jpg

BE_FR_VIVA_HP_GASTRO_desktop.jpg

350 ms

BE_FR_VIVA_HP_WELLNESS_desktop.jpg

BE_FR_VIVA_HP_WELLNESS_desktop.jpg

645 ms

BE_FR_VIVA_HP_SPORT_desktop.jpg

BE_FR_VIVA_HP_SPORT_desktop.jpg

352 ms

BE_NL_VIVA_HP_CINEMA_desktop.jpg

BE_NL_VIVA_HP_CINEMA_desktop.jpg

644 ms

sdk.2e71e718a23e7508c6fd8cc0f241e61f88b3b14b.js

sdk.2e71e718a23e7508c6fd8cc0f241e61f88b3b14b.js

7 ms

ui-gdpr-fr-web.2e71e718a23e7508c6fd8cc0f241e61f88b3b14b.js

ui-gdpr-fr-web.2e71e718a23e7508c6fd8cc0f241e61f88b3b14b.js

275 ms

Accessibility Review

vivabox.be accessibility score

73

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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 valid value for its [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

Image elements do not have [alt] attributes

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

vivabox.be best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

vivabox.be SEO score

75

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

High

robots.txt is not valid

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

vivabox.be

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