2 sec in total
26 ms
1.4 sec
551 ms
Visit yoyo.com now to see the best up-to-date Yo content for United States and also check out these interesting facts you probably never knew about yoyo.com
Online shopping for YoYo.com at Amazon.com
Visit yoyo.comWe analyzed Yoyo.com page load time and found that the first response time was 26 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
yoyo.com performance score
26 ms
51 ms
167 ms
39 ms
119 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 6% of them (8 requests) were addressed to the original Yoyo.com, 39% (55 requests) were made to Yoyo.q-assets.com and 16% (23 requests) were made to Images-na.ssl-images-amazon.com. The less responsive or slowest element that took the longest time to load (352 ms) belongs to the original domain Yoyo.com.
Page size can be reduced by 807.1 kB (39%)
2.1 MB
1.3 MB
In fact, the total size of Yoyo.com main page is 2.1 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. 70% of websites need less resources to load. Images take 963.6 kB which makes up the majority of the site volume.
Potential reduce by 98.4 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 18.8 kB, which is 15% 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 98.4 kB or 79% of the original size.
Potential reduce by 46.9 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. Yo images are well optimized though.
Potential reduce by 462.5 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 462.5 kB or 62% of the original size.
Potential reduce by 199.3 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. Yoyo.com needs all CSS files to be minified and compressed as it can save up to 199.3 kB or 83% of the original size.
Number of requests can be reduced by 47 (39%)
122
75
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
yoyo.com
26 ms
www.yoyo.com
51 ms
authorize
167 ms
resource
39 ms
www.yoyo.com
119 ms
homepagecss_combined.css
44 ms
QuidsiUIAsset-34396ad5b4a369fbe9c538aa3443b407af64a254._V2_.css
98 ms
QuidsiWebChromeAsset-6fe5352fd699253d018b2aab10fd0c73a7cc9beb._V2_.css
102 ms
QuidsiWebLegacyOverrideAsset-61f4dc7bfd12db4b405ad9f7da16a6f8b9659cdb._V2_.css
91 ms
webfont.css
61 ms
homepagejs_combined.js
63 ms
ubernavjs_combined.js
62 ms
core.js
62 ms
yoyo_logo._V331493600_.png
193 ms
CR-1957_yy_navbtn_starwars._V285874669_.png
193 ms
hp_nexo_herobanner2_022516.jpg
31 ms
cr-1702_122115_rvhp2.jpg
18 ms
cr-1702_122115_rvhp3.jpg
194 ms
hp_herobanner1_090815.jpg
27 ms
outageshops.gif
21 ms
nvhp_age_banner_0-12mo.png
21 ms
nvhp_age_0-12mo.png
24 ms
nvhp_age_banner_1.png
190 ms
nvhp_age_1.png
32 ms
nvhp_age_banner_2.png
189 ms
nvhp_age_2.png
190 ms
nvhp_age_banner_3-4.png
190 ms
nvhp_age_3-4.png
191 ms
nvhp_age_banner_5-6.png
204 ms
nvhp_age_5-6.png
219 ms
nvhp_age_banner_7-8.png
206 ms
nvhp_age_7-8.png
207 ms
nvhp_age_banner_9.png
201 ms
nvhp_age_9.png
207 ms
recommend.gif
204 ms
yy_hp_werec_promo1_010215.jpg
208 ms
yy_hp_werec_promo2_010215.jpg
205 ms
yy_hp_werec_promo3_010215.jpg
206 ms
yy_hp_werec_cat1_010215v2.png
208 ms
yy_werecco_boutique2014.png
207 ms
yy_werecco_50pctoff2014.png
208 ms
popularbrandsbanner.gif
209 ms
lego.jpg
210 ms
jellycat.gif
207 ms
littletikes.gif
208 ms
kidkraft.gif
209 ms
fisherprice.jpg
210 ms
melissa&doug.jpg
210 ms
crayola.jpg
210 ms
plantoys.jpg
209 ms
step2.gif
210 ms
vtech.gif
206 ms
barbie.jpg
201 ms
leapfrog.gif
203 ms
haba.jpg
196 ms
alex.gif
204 ms
radioflyer.jpg
193 ms
getadi
169 ms
getadi
167 ms
getadi
163 ms
119776_coe.gif
255 ms
QuidsiUIJS-4e9a539ec4b77d3a1f49e44189c90854850c218c._V2_.js
165 ms
QuidsiWebDesktopJS-230a2b6353f534414f7605ce0a8a812d8e65862b._V2_.js
153 ms
QuidsiWebLegacyOverrideAsset-7f2bd62462a77292308e1723b734424f8d246d28._V2_.js
151 ms
gtm.js
145 ms
dc.js
144 ms
tag.js
144 ms
119776_medal.gif
142 ms
263324_medal.gif
142 ms
ubernav-sprites_150709_1826.png
139 ms
wrap_bg_151113_1439.png
139 ms
sitenav_arrow.png
139 ms
footer_bg_151113_1414.png
138 ms
footer-sprite_151113_1436.png
135 ms
footerlogo_151113_1238.png
154 ms
logostring.png
136 ms
mainshadowbg.png
102 ms
toyFinderImages.png
133 ms
headerFooterImages.gif
131 ms
ageShopBlueAndRedGraphic.png
99 ms
arrow.gif
128 ms
ProximaNova-Reg-webfont.woff
145 ms
ProximaNova-Sbold-webfont.woff
146 ms
ProximaNova-Bold-webfont.woff
146 ms
ProximaNova-Xbold-webfont.woff
147 ms
ProximaNovaExCn-Reg-webfont.woff
146 ms
ProximaNovaExCn-Light-webfont.woff
145 ms
ProximaNovaExCn-Bold-webfont.woff
146 ms
ProximaNovaExCn-Light-webfont.woff
128 ms
fontawesome-webfont.woff
174 ms
Quidsi-iconfonts.woff
173 ms
mainshadowbtm.png
115 ms
__utm.gif
74 ms
analytics.js
89 ms
tag
48 ms
symphony
352 ms
Cart!GetTotalQtyAndAmount.qs
95 ms
DynamicAjax!GetDynamicUserData.qs
92 ms
tag
31 ms
collect
13 ms
heroBannerImages.png
31 ms
__qrum.min.js
31 ms
conversion.js
15 ms
64 ms
foundation-A58772-c4c4-4714-974e-f334109965bd1.js
40 ms
iu3
121 ms
live.js
21 ms
50000188.js
46 ms
ld.js
58 ms
__qrum
98 ms
hit
24 ms
foundation-tags-SD1207-3488-4518-abd9-2d00ba3b12841.js
18 ms
Desktop_UberStatic_2day._V285901425_.png
36 ms
Desktop_UberAnim_2day._V285901431_.gif
41 ms
graphic_hop-up._V301124159_.jpg
41 ms
68 ms
event
49 ms
onepixel.gif
31 ms
iu3
42 ms
mediasource-A58772-c4c4-4714-974e-f334109965bd1-c-2056.js
13 ms
366738.gif
12 ms
12 ms
apid
40 ms
pr
14 ms
14 ms
pixel
45 ms
usersync.html
166 ms
dis.aspx
47 ms
ecm3
14 ms
ecm3
17 ms
ecm3
20 ms
ecm3
17 ms
ecm3
15 ms
ecm3
15 ms
ecm3
11 ms
ecm3
10 ms
ecm3
12 ms
ecm3
10 ms
ecm3
11 ms
ecm3
10 ms
ecm3
10 ms
yoyo.com SEO score
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yoyo.com 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 Yoyo.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
yoyo.com
Open Graph description is not detected on the main page of Yo. 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: