4 sec in total
770 ms
2.9 sec
295 ms
Visit weleda.be now to see the best up-to-date Weleda content for Belgium and also check out these interesting facts you probably never knew about weleda.be
Heb je vragen over Weleda of over onze producten? Zoek je een verkooppunt, een schoonheidsspecialiste of een arts?
Visit weleda.beWe analyzed Weleda.be page load time and found that the first response time was 770 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
weleda.be performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value7.6 s
4/100
25%
Value8.5 s
18/100
10%
Value3,130 ms
2/100
30%
Value0.002
100/100
15%
Value12.9 s
13/100
10%
770 ms
94 ms
214 ms
298 ms
399 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 65% of them (31 requests) were addressed to the original Weleda.be, 25% (12 requests) were made to Weleda.global.ssl.fastly.net and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Weleda.global.ssl.fastly.net.
Page size can be reduced by 63.6 kB (58%)
108.7 kB
45.1 kB
In fact, the total size of Weleda.be main page is 108.7 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. 55% of websites need less resources to load. Javascripts take 70.1 kB which makes up the majority of the site volume.
Potential reduce by 31.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. This page needs HTML code to be minified as it can gain 5.6 kB, which is 14% 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 31.6 kB or 82% of the original size.
Potential reduce by 32.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.0 kB or 46% of the original size.
Number of requests can be reduced by 20 (50%)
40
20
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weleda. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
www.weleda.be
770 ms
flexslider.css
94 ms
questionnaire.css
214 ms
weleda_imop.css
298 ms
jquery-2.1.1.min.js
399 ms
jquery.flexslider-min.js
319 ms
dropkick.min.js
317 ms
dropkick.jquery.js
316 ms
form-widget.js
315 ms
jquery-mobile-1.4.4.min.js
486 ms
touch-menu.js
390 ms
menu-positionning.js
417 ms
contextBlender.js
417 ms
multiply.js
418 ms
header-watercolor-module.js
529 ms
teaser-module.js
529 ms
weleda-google-analytics.js
530 ms
weleda-cookies.js
538 ms
language.js
539 ms
search.js
588 ms
scroll-to-anchor-id.js
594 ms
popup.js
612 ms
ga.js
11 ms
birch_watercolors_frame_.png
85 ms
birch_seal_tone_en_rgb.png
49 ms
2groepsbeeld-homepage.png
1095 ms
weleda%3Aimopmini
45 ms
weleda%3Aimopmini
46 ms
weleda%3Aimopmini
59 ms
weleda%3Aimopmini
46 ms
weleda%3Aimopsmall
202 ms
weleda%3Aimopsmall
52 ms
weleda%3Aimopsmall
49 ms
gtm.js
57 ms
f4f5a4ed-4698-470b-ae5e-e4bbe1f0b130.woff
183 ms
NeoSansWeleda-Rg.woff
547 ms
WeledaWebIcons2.svg
276 ms
WeledaWebIcons2.woff
87 ms
newweled-webfont.woff
90 ms
newweleda.eot
174 ms
WeledaWebIcons.woff
267 ms
analytics.js
18 ms
plantbeeld-homepage.jpg
530 ms
weleda_sprites.png
252 ms
stage_chlorophyll.png
210 ms
collect
16 ms
collect
66 ms
birch_web_stages.png
9 ms
weleda.be accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
weleda.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
weleda.be SEO score
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
Tap targets are not sized appropriately
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weleda.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Weleda.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.
weleda.be
Open Graph description is not detected on the main page of Weleda. 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: