3.5 sec in total
450 ms
2.8 sec
267 ms
Welcome to ypso.com homepage info - get ready to check Ypso best content right away, or after learning these important things about ypso.com
The domain name ypso.com is available for rent.
Visit ypso.comWe analyzed Ypso.com page load time and found that the first response time was 450 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ypso.com performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value1.7 s
99/100
25%
Value1.2 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.8 s
100/100
10%
450 ms
391 ms
396 ms
394 ms
394 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ypso.com, 93% (63 requests) were made to Paidi.de and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Paidi.de.
Page size can be reduced by 804.1 kB (46%)
1.7 MB
935.4 kB
In fact, the total size of Ypso.com main page is 1.7 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 758.2 kB which makes up the majority of the site volume.
Potential reduce by 28.0 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 28.0 kB or 81% of the original size.
Potential reduce by 47.4 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. Ypso images are well optimized though.
Potential reduce by 553.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 553.7 kB or 73% of the original size.
Potential reduce by 175.0 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. Ypso.com needs all CSS files to be minified and compressed as it can save up to 175.0 kB or 84% of the original size.
Number of requests can be reduced by 32 (48%)
66
34
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ypso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
450 ms
royalslider.css
391 ms
rs-default.css
396 ms
stylesheet_6be2424ee9.css
394 ms
javascript_d6ea4370ef.js
394 ms
mootools_core.js
584 ms
mootools_more.js
921 ms
jquery-1.9.1.min.js
676 ms
jquery-ui-1.8.2.min.js
886 ms
jquery.scrollTo-min.js
494 ms
jquery.validator.min.js
493 ms
jquery.ImageSwitch.js
604 ms
jquery.smoothDivScroll.js
604 ms
jquery.simpleslider.js
680 ms
jquery.lightbox.min.js
695 ms
jquery.touchwipe.1.1.1.js
697 ms
paidi.js
774 ms
popup.js
782 ms
popup_my_script.js
797 ms
css
80 ms
paidi.css
990 ms
popup.css
872 ms
rebrush_paidi_mediaall_global.css
889 ms
rebrush_paidi_mediaall_startseite.css
891 ms
rebrush_paidi_mediaall_wpro.css
980 ms
jquery.royalslider.min.js
995 ms
jquery.datetimepicker.js
967 ms
parsley.min.js
1014 ms
tabs.js
970 ms
form.js
998 ms
csm_paidi-logo-print_41a66d5cdc.png
142 ms
pinterest.png
141 ms
facebook.png
142 ms
location-pin.png
141 ms
merkzettel.png
170 ms
btn_search.png
184 ms
btn_search.gif
213 ms
zukunft_03.jpg
234 ms
abenteuer_01.jpg
312 ms
geborgenheit.jpg
411 ms
liebe_01.jpg
279 ms
traeumen_01.jpg
383 ms
spielen.jpg
331 ms
teaser_Fiona_Spielbett_weiss.jpg
341 ms
arrow-teaser-startseite.png
379 ms
teaser_fridaundanton_neu.jpg
418 ms
Juniorstufe_Startseite-2015.jpg
442 ms
katalog-teaser-2015-home.jpg
453 ms
arrow_right_small.gif
479 ms
arrow-news-right.png
480 ms
arrow-product.png
508 ms
PAIDI-PAIDI_Soft_Close_System_HOCH.png
517 ms
PAIDI-PAIDI_Nachkauf_Garantie.png
542 ms
PAIDI-PAIDI_Produkt_Garantie_rgb.jpg
559 ms
weltkugel.png
578 ms
arrow-down.png
580 ms
csm_popup-oeko-test-2015-k2_4514274c1d.png
801 ms
ga.js
8 ms
DsLzC9scoPnrGiwYYMQXphdbPw3QSf9R-kE0EsQUn2A.woff
29 ms
__utm.gif
18 ms
jquery.datetimepicker.js
524 ms
parsley.min.js
547 ms
tabs.js
557 ms
form.js
569 ms
arrow-sider-big-right.png
549 ms
close.png
599 ms
grab.png
621 ms
arrow-sider-big-left.png
629 ms
ypso.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
ypso.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
ypso.com SEO score
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ypso.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Ypso.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.
ypso.com
Open Graph description is not detected on the main page of Ypso. 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: