3.5 sec in total
532 ms
2.3 sec
636 ms
Click here to check amazing Yoyo content. Otherwise, check out these important facts you probably never knew about yoyo.ag
yoyo-AG
Visit yoyo.agWe analyzed Yoyo.ag page load time and found that the first response time was 532 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
yoyo.ag performance score
532 ms
465 ms
482 ms
197 ms
197 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 40% of them (48 requests) were addressed to the original Yoyo.ag, 23% (28 requests) were made to Google.com and 16% (19 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Yoyo.ag.
Page size can be reduced by 1.1 MB (24%)
4.5 MB
3.4 MB
In fact, the total size of Yoyo.ag main page is 4.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 48.8 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 17.8 kB, which is 30% 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 48.8 kB or 83% of the original size.
Potential reduce by 81.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. Yoyo images are well optimized though.
Potential reduce by 723.1 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 723.1 kB or 68% of the original size.
Potential reduce by 216.4 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.ag needs all CSS files to be minified and compressed as it can save up to 216.4 kB or 86% of the original size.
Number of requests can be reduced by 44 (40%)
109
65
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yoyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
yoyo.ag
532 ms
bootstrap.min.css
465 ms
animate.css
482 ms
nivo-lightbox.css
197 ms
default.css
197 ms
owl.carousel.css
205 ms
owl.theme.css
276 ms
style.css
290 ms
responsiveness.css
292 ms
font-awesome.min.css
306 ms
css
25 ms
modernizr.custom.js
368 ms
jquery-1.11.0.js
409 ms
jquery.min.js
32 ms
bootstrap.min.js
207 ms
isotope.pkgd.min.js
405 ms
owl.carousel.min.js
345 ms
nivo-lightbox.min.js
404 ms
jquery.easing.min.js
408 ms
SmoothScroll.js
407 ms
wow.min.js
407 ms
matchMedia.js
407 ms
jquery.backgroundvideo.js
444 ms
imagesloaded.js
502 ms
js
53 ms
jqBootstrapValidation.js
499 ms
main.js
499 ms
embed
217 ms
embed
311 ms
loading.gif
211 ms
yoyoLogo0.svg
466 ms
waves.png
277 ms
yoyo_logo_white.svg
278 ms
playerPhone.png
492 ms
playerPhoneGlow.png
391 ms
Stern.png
276 ms
3dWuerfel.png
492 ms
m4mLogo.png
392 ms
FANPOWER_Logo_3D_silber.png
392 ms
website_yoyo_fanpower_tablet.png
836 ms
aroundTheWorld.png
813 ms
profilChristianDaudert@2x.png
774 ms
profilJulianVonHassell@2x.png
776 ms
profilKarolinStechert@2x.png
871 ms
profilUlrikeKnauf@2x.png
872 ms
profilNicoleLange@2x.png
963 ms
profilIngoVolkmann@2x.png
1082 ms
profilSimonGoerdes@2x.png
908 ms
profilMartinSoltow@2x.png
924 ms
profilmarthewolbring.png
1286 ms
profilMarkoRehmer@2x.png
1283 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
38 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
38 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
39 ms
Jzo62I39jc0gQRrbndN6nXYhjbSpvc47ee6xR_80Hnw.ttf
38 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
37 ms
mnpfi9pxYH-Go5UiibESIiZ2oysoEQEeKwjgmXLRnTc.ttf
38 ms
fontawesome-webfont.woff
938 ms
js
26 ms
init_embed.js
78 ms
js
95 ms
common.js
63 ms
map.js
63 ms
google4.png
94 ms
overlay.js
24 ms
util.js
89 ms
onion.js
90 ms
search_impl.js
90 ms
stats.js
70 ms
openhand_8_8.cur
75 ms
ViewportInfoService.GetViewportInfo
125 ms
ViewportInfoService.GetViewportInfo
38 ms
kh
207 ms
transparent.png
85 ms
controls.js
78 ms
ViewportInfoService.GetViewportInfo
112 ms
ViewportInfoService.GetViewportInfo
105 ms
kh
205 ms
ViewportInfoService.GetViewportInfo
165 ms
kh
165 ms
vt
146 ms
vt
217 ms
vt
191 ms
vt
196 ms
vt
190 ms
vt
191 ms
vt
188 ms
vt
214 ms
vt
225 ms
vt
224 ms
vt
226 ms
vt
239 ms
vt
261 ms
css
135 ms
entity11.png
107 ms
mapcnt6.png
63 ms
tmapctrl.png
41 ms
vt
220 ms
vt
165 ms
vt
170 ms
vt
170 ms
vt
165 ms
vt
175 ms
vt
198 ms
vt
202 ms
vt
212 ms
vt
212 ms
vt
226 ms
vt
230 ms
vt
239 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
33 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
34 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
47 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
51 ms
AuthenticationService.Authenticate
16 ms
AuthenticationService.Authenticate
15 ms
marker.js
28 ms
google4.png
12 ms
sv5.png
12 ms
map-marker.png
97 ms
yoyo.ag SEO score
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yoyo.ag can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Yoyo.ag 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.
yoyo.ag
Open Graph description is not detected on the main page of Yoyo. 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: