Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

whoohoo.be

Projectsourcing voor technische professionals | Maandag® Belgium

Page Load Speed

4.1 sec in total

First Response

397 ms

Resources Loaded

2.8 sec

Page Rendered

859 ms

whoohoo.be screenshot

About Website

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

Technisch talent verbinden met vooruitdenkende organisaties. Voor werk dat ertoe doet. Dat is Maandag®. Waar ga jij aan de slag?

Visit whoohoo.be

Key Findings

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

Performance Metrics

whoohoo.be performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value4,050 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

whoohoo.be

397 ms

www.whoohoo.be

1249 ms

jquery-1.10.2.min.js

8 ms

addthis_widget.js

25 ms

maandag.less

282 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 77% of them (40 requests) were addressed to the original Whoohoo.be, 8% (4 requests) were made to S7.addthis.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Whoohoo.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 790.3 kB (27%)

Content Size

2.9 MB

After Optimization

2.2 MB

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

HTML Optimization

-81%

Potential reduce by 179.4 kB

  • Original 222.0 kB
  • After minification 221.8 kB
  • After compression 42.6 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 179.4 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 3.4 kB

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

JavaScript Optimization

-67%

Potential reduce by 607.4 kB

  • Original 912.5 kB
  • After minification 912.1 kB
  • After compression 305.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 607.4 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (46%)

Requests Now

48

After Optimization

26

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

Accessibility Review

whoohoo.be accessibility score

92

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoohoo.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 English language. Our system also found out that Whoohoo.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 description is not detected on the main page of Whoohoo. 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: