3.3 sec in total
327 ms
2.5 sec
416 ms
Visit lillydoo.com now to see the best up-to-date LILLYDOO content for Switzerland and also check out these interesting facts you probably never knew about lillydoo.com
Einfach nur Wickeln war gestern: Windeln, Feuchttücher und Pflegeprodukte – Hautfreundlich und frei von allem, was unsere Haut nicht mag. Jetzt entdecken!
Visit lillydoo.comWe analyzed Lillydoo.com page load time and found that the first response time was 327 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
lillydoo.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value2.9 s
81/100
25%
Value3.1 s
93/100
10%
Value380 ms
69/100
30%
Value0
100/100
15%
Value4.4 s
83/100
10%
327 ms
574 ms
242 ms
206 ms
498 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 73% of them (33 requests) were addressed to the original Lillydoo.com, 7% (3 requests) were made to Google-analytics.com and 4% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (695 ms) belongs to the original domain Lillydoo.com.
Page size can be reduced by 556.3 kB (48%)
1.2 MB
613.8 kB
In fact, the total size of Lillydoo.com main page is 1.2 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. 30% of websites need less resources to load. Javascripts take 467.0 kB which makes up the majority of the site volume.
Potential reduce by 22.3 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.0 kB, which is 21% 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 22.3 kB or 77% of the original size.
Potential reduce by 15.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. LILLYDOO images are well optimized though.
Potential reduce by 311.2 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 311.2 kB or 67% of the original size.
Potential reduce by 207.5 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. Lillydoo.com needs all CSS files to be minified and compressed as it can save up to 207.5 kB or 84% of the original size.
Number of requests can be reduced by 18 (49%)
37
19
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LILLYDOO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
lillydoo.com
327 ms
www.lillydoo.com
574 ms
242 ms
all.css
206 ms
vendorsMain.js
498 ms
validationMain.js
428 ms
lillydoo_frontend.js
270 ms
all.js
273 ms
shopping_cart_icon.png
103 ms
icon-windeln-nav-dark.png
104 ms
icon-feuchttuecher-nav-dark.png
105 ms
icon-testpaket-nav-dark.png
104 ms
icon-windeln-nav.png
102 ms
icon-feuchttuecher-nav.png
183 ms
icon-testpaket-nav.png
197 ms
lillydoo_siegel_premium_schwarz.png
195 ms
diapers_lineup_home_01.png
194 ms
wipes_lineup_home.png
291 ms
trialpack_home.png
459 ms
0-prozent.png
290 ms
peta_cruelty_free.png
289 ms
dermatest.png
289 ms
codecheck.png
289 ms
contact-mail.png
381 ms
contact-phone.png
381 ms
social-facebook.png
377 ms
social-instagram.png
380 ms
gtm.js
122 ms
brooklyn_samuels_five_light-webfont.woff
446 ms
arr-up-new01.png
374 ms
brooklyn_samuels_four_bold-webfont.woff
458 ms
latinotype_-_newslab-webfont.woff
372 ms
lillydoo-logo.png
353 ms
header-index.jpg
695 ms
conversion_async.js
60 ms
fbevents.js
293 ms
goal.min.js
77 ms
analytics.js
53 ms
45 ms
ec.js
16 ms
collect
3 ms
collect
74 ms
39 ms
ga-audiences
19 ms
96 ms
lillydoo.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lillydoo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
lillydoo.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lillydoo.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Lillydoo.com 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.
lillydoo.com
Open Graph data is detected on the main page of LILLYDOO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: