3.6 sec in total
389 ms
3.1 sec
124 ms
Click here to check amazing Weelife content for Germany. Otherwise, check out these important facts you probably never knew about weelife.de
This website is for sale! weelife.de is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, weelife.de has it a...
Visit weelife.deWe analyzed Weelife.de page load time and found that the first response time was 389 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.
weelife.de performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value10.7 s
0/100
25%
Value31.6 s
0/100
10%
Value46,010 ms
0/100
30%
Value0.002
100/100
15%
Value68.0 s
0/100
10%
389 ms
289 ms
268 ms
70 ms
359 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 79% of them (88 requests) were addressed to the original Weelife.de, 8% (9 requests) were made to Scontent.xx.fbcdn.net and 7% (8 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (856 ms) belongs to the original domain Weelife.de.
Page size can be reduced by 953.1 kB (49%)
2.0 MB
1.0 MB
In fact, the total size of Weelife.de main page is 2.0 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 800.6 kB which makes up the majority of the site volume.
Potential reduce by 23.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. 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 23.3 kB or 81% of the original size.
Potential reduce by 25.2 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. Weelife images are well optimized though.
Potential reduce by 240.7 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 240.7 kB or 69% of the original size.
Potential reduce by 663.9 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. Weelife.de needs all CSS files to be minified and compressed as it can save up to 663.9 kB or 85% of the original size.
Number of requests can be reduced by 62 (60%)
104
42
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weelife. 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 from 43 to 1 for CSS and as a result speed up the page load time.
www.weelife.de
389 ms
style.css
289 ms
jquery.fancybox.css
268 ms
all.js
70 ms
jquery.min.js
359 ms
bootstrap.min.js
277 ms
less.min.js
358 ms
jquery.sidr.js
264 ms
jquery.gritter.min.js
385 ms
bootstrap-datepicker.js
391 ms
bootstrap-timepicker.js
397 ms
jquery.tipsy.js
403 ms
modernizr.js
474 ms
jquery.hashchange.js
479 ms
system.js
496 ms
custom.js
502 ms
jquery.gridalicious.min.js
507 ms
adscript.php
413 ms
bootstrap-wysihtml5-0.0.2.css
232 ms
bootstrap-datepicker.css
300 ms
bootstrap-select.css
298 ms
bootstrap-switch.css
315 ms
bootstrap-timepicker.css
321 ms
farbtastic.css
328 ms
fileupload.css
335 ms
multi-select.css
400 ms
select2.css
403 ms
dropzone.css
418 ms
jquery.plupload.queue.css
451 ms
blueimp-gallery.min.css
490 ms
jquery.Jcrop.css
494 ms
prettyPhoto.css
508 ms
iThing.css
506 ms
ColReorder.css
535 ms
ColVis.css
557 ms
TableTools.css
593 ms
footable.core.min.css
599 ms
bootstrap.min.css
620 ms
font-awesome.min.css
628 ms
glyphicons_filetypes.css
639 ms
glyphicons_regular.css
661 ms
glyphicons_social.css
711 ms
picto.css
714 ms
jquery-ui.min.css
664 ms
fullcalendar.css
669 ms
jquery.easy-pie-chart.css
652 ms
elements.css
668 ms
jquery-jvectormap-1.1.1.css
714 ms
jquery-jvectormap-1.2.2.css
722 ms
jquery.gritter.css
656 ms
jquery.notyfy.css
653 ms
notyfy.theme.default.css
644 ms
pageguide.css
661 ms
owl.carousel.css
707 ms
owl.theme.css
712 ms
prettify.css
664 ms
animate.min.css
652 ms
logo_3.png
125 ms
nopic_50x50.png
119 ms
bilder5049_50x50.jpg
123 ms
bilder5138_50x50.jpg
125 ms
bilder5170_50x50.jpg
129 ms
bilder2973_50x50.jpg
138 ms
team.png
213 ms
bilder4591_50x50.jpg
222 ms
bilder2565_50x50.jpg
233 ms
bilder3374_50x50.jpg
237 ms
load.gif
259 ms
nopic.png
351 ms
bilder161059_500x375.jpg
426 ms
bilder161006_500x375.jpg
532 ms
bilder160993_500x375.jpg
442 ms
bilder160985_500x375.jpg
556 ms
bilder160967_500x375.jpg
570 ms
bilder160876_500x375.jpg
630 ms
bilder160834_500x375.jpg
555 ms
bilder160745_500x375.jpg
672 ms
bilder160638_500x375.jpg
856 ms
bilder160355_500x375.jpg
651 ms
bilder160339_500x375.jpg
756 ms
bilder160272_500x375.jpg
782 ms
nopic_120x120.png
691 ms
nopic_35x35.png
764 ms
likebox.php
389 ms
adscript.php
212 ms
fontawesome-webfont.woff
742 ms
picto-foundry-general.woff
762 ms
picto-foundry-multimedia.woff
802 ms
picto-foundry-arrows.woff
847 ms
picto-foundry-household.woff
847 ms
picto-foundry-vehicle-navigation.woff
848 ms
ga.js
27 ms
update.php
665 ms
__utm.gif
13 ms
410ucuAGgaJ.css
81 ms
tSbl8xBI27R.css
101 ms
q68gy-v_YMF.js
138 ms
FJmpeSpHpjS.js
171 ms
0wM5s1Khldu.js
135 ms
1bNoFZUdlYZ.js
136 ms
1919101_1095529750458356_7393389242826293886_n.jpg
126 ms
427514_378249225519749_692031160_n.jpg
108 ms
12642854_1015799161817492_8371799333204992239_n.jpg
138 ms
1918563_922432791186360_5725349672395376990_n.jpg
84 ms
12642469_1049937815072505_2709200591474320314_n.jpg
110 ms
12642904_1514257222213032_3828696306105799737_n.jpg
112 ms
12299327_10153867486407249_5600333133767205404_n.jpg
262 ms
1044219_1657495497850513_2533562123634470230_n.jpg
126 ms
11227385_901401863279076_830713809556704985_n.jpg
155 ms
wL6VQj7Ab77.png
23 ms
s7jcwEQH7Sx.png
24 ms
weelife.de 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
weelife.de 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
Browser errors were logged to the console
weelife.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weelife.de can be misinterpreted by Google and other search engines. Our service has detected that English 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 Weelife.de 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.
weelife.de
Open Graph data is detected on the main page of Weelife. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: