Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

voo.be

Opérateur Internet, TV, Mobile et Téléphone en Belgique - VOO

Page Load Speed

47.4 sec in total

First Response

486 ms

Resources Loaded

22.1 sec

Page Rendered

24.8 sec

voo.be screenshot

About Website

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

Découvrez sur le site de VOO nos offres et conditions incomparables pour l'Internet ultra rapide, la TV numérique, la téléphonie fixe et mobile.

Visit voo.be

Key Findings

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

Performance Metrics

voo.be performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value4,160 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.9 s

1/100

10%

Network Requests Diagram

voo.be

486 ms

1668 ms

common.css

471 ms

home2016.css

645 ms

jquery.min.js

995 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 71% of them (54 requests) were addressed to the original Voo.be, 12% (9 requests) were made to Mobile.voo.be and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (13.2 sec) relates to the external source Mobile.voo.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (26%)

Content Size

6.5 MB

After Optimization

4.8 MB

In fact, the total size of Voo.be main page is 6.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. 85% 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. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 43.5 kB

  • Original 55.3 kB
  • After minification 48.5 kB
  • After compression 11.8 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 6.9 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 43.5 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 537.0 kB

  • Original 5.0 MB
  • After minification 4.4 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. Obviously, VOO needs image optimization as it can save up to 537.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 645.4 kB

  • Original 944.8 kB
  • After minification 836.3 kB
  • After compression 299.4 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 645.4 kB or 68% of the original size.

CSS Optimization

-91%

Potential reduce by 500.5 kB

  • Original 547.9 kB
  • After minification 397.9 kB
  • After compression 47.4 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. Voo.be needs all CSS files to be minified and compressed as it can save up to 500.5 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (26%)

Requests Now

72

After Optimization

53

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

Accessibility Review

voo.be accessibility score

85

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

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

voo.be SEO score

84

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

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

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voo.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Voo.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 VOO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: