5.2 sec in total
963 ms
3.2 sec
1 sec
Visit wellnest.be now to see the best up-to-date Wellnest content and also check out these interesting facts you probably never knew about wellnest.be
Wellnest is an agile, holistic, employee-centric solution that creates inclusive corporate cultures and allows employees to reach their full potential
Visit wellnest.beWe analyzed Wellnest.be page load time and found that the first response time was 963 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wellnest.be performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value5.1 s
26/100
25%
Value7.1 s
30/100
10%
Value3,260 ms
2/100
30%
Value0.352
31/100
15%
Value19.4 s
2/100
10%
963 ms
112 ms
164 ms
372 ms
30 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 56% of them (33 requests) were addressed to the original Wellnest.be, 34% (20 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Wellnest.be.
Page size can be reduced by 243.3 kB (5%)
4.6 MB
4.3 MB
In fact, the total size of Wellnest.be main page is 4.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. 65% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 85.1 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 85.1 kB or 84% of the original size.
Potential reduce by 151.7 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. Wellnest images are well optimized though.
Potential reduce by 6.3 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.
Potential reduce by 77 B
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. Wellnest.be has all CSS files already compressed.
Number of requests can be reduced by 15 (42%)
36
21
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wellnest. 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 4 to 1 for CSS and as a result speed up the page load time.
wellnest.be
963 ms
wp-emoji-release.min.js
112 ms
style.min.css
164 ms
style.css
372 ms
css
30 ms
dashicons.min.css
236 ms
jquery.js
256 ms
jquery-migrate.min.js
156 ms
typeform-elements.js
288 ms
7915154.js
63 ms
custom.min.js
483 ms
common.js
235 ms
wp-embed.min.js
309 ms
shell.js
37 ms
banner.js
283 ms
Wellnest-Logo-2.png
129 ms
iba-wellnest.png
555 ms
ic-logo.jpg
480 ms
iba-logo-hd.jpg
278 ms
Logo-D%C3%A9cathlon-1.jpg
377 ms
Baxter-logo-website-1.png
129 ms
inBW.jpg
258 ms
stanteclogocolour_.jpg
482 ms
CM_Logo-FR.png
334 ms
logo-ekivita-nieuw.png
334 ms
1200px-Yves_Rocher_logo.svg_.png
410 ms
carmeuse.jpg
409 ms
ACTIVITY-VIEW.png
1802 ms
phones-diagonal.png
563 ms
BAXTER-DASH-activities-half-view-new.png
636 ms
crameuse-NEW-computer-preview-copy.png
633 ms
section-bg-hero2.png
566 ms
Beta-badge.png
630 ms
close.png
639 ms
corner-logo.png
647 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3iqzbXWjQeQ.ttf
79 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3iqzbXWjQeQ.ttf
168 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTQ3iqzbXWjQeQ.ttf
208 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3iqzbXWjQeQ.ttf
168 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3iqzbXWjQeQ.ttf
170 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3iqzbXWjQeQ.ttf
169 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTQ3iqzbXWjQeQ.ttf
169 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5Xs1UgIfM0qi1e.ttf
206 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVi5Xs1UgIfM0qi1e.ttf
204 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4Gfy5Xs1UgIfM0qi1e.ttf
205 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5Xs1UgIfM0qi1e.ttf
206 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXs1UgIfM0qi1e.ttf
205 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClXs1UgIfM0qi1e.ttf
262 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVilXs1UgIfM0qi1e.ttf
289 ms
modules.ttf
657 ms
collectedforms.js
154 ms
7915154.js
181 ms
7915154.js
226 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
56 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
54 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
55 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
54 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
64 ms
KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf
65 ms
wellnest.be accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wellnest.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wellnest.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wellnest.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wellnest.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.
wellnest.be
Open Graph data is detected on the main page of Wellnest. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: