44.3 sec in total
2.5 sec
41.1 sec
674 ms
Visit yoyo61.com now to see the best up-to-date Yoyo 61 content and also check out these interesting facts you probably never knew about yoyo61.com
Visit yoyo61.comWe analyzed Yoyo61.com page load time and found that the first response time was 2.5 sec and then it took 41.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
yoyo61.com performance score
2460 ms
71 ms
1399 ms
1402 ms
1416 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 25% of them (20 requests) were addressed to the original Yoyo61.com, 26% (21 requests) were made to Imgcdn.mazaibang.com and 12% (10 requests) were made to J.humanding.com. The less responsive or slowest element that took the longest time to load (13.4 sec) relates to the external source Baidu.com.cyad456.com.
Page size can be reduced by 175.8 kB (43%)
409.1 kB
233.3 kB
In fact, the total size of Yoyo61.com main page is 409.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 212.3 kB which makes up the majority of the site volume.
Potential reduce by 36.5 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 36.5 kB or 76% of the original size.
Potential reduce by 38.5 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. Obviously, Yoyo 61 needs image optimization as it can save up to 38.5 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 72.3 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 72.3 kB or 64% of the original size.
Potential reduce by 28.6 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. Yoyo61.com needs all CSS files to be minified and compressed as it can save up to 28.6 kB or 79% of the original size.
Number of requests can be reduced by 18 (25%)
73
55
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yoyo 61. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
www.yoyo61.com
2460 ms
style.css
71 ms
960-3.js
1399 ms
960-4.js
1402 ms
960-5.js
1416 ms
960-6.js
136 ms
960-1.js
1419 ms
logo.png
1484 ms
960-2.js
204 ms
tongji.js
274 ms
foot.js
342 ms
meiwen_header_bg.jpg
334 ms
meiwen.com.cn_ico.png
403 ms
meiwen_head_ico.png
473 ms
new.gif
540 ms
s.php
1686 ms
v.php
999 ms
i7click.php
5020 ms
3.jpg
7555 ms
4.jpg
3615 ms
2.jpg
5613 ms
37.gif
3727 ms
38.gif
3231 ms
5.jpg
6055 ms
4.jpg
13409 ms
view_p7.php
3851 ms
i.php
945 ms
s.php
490 ms
i7click.php
5415 ms
jquery1.9.0.js
4416 ms
wholeclick.js
1406 ms
ha0000.php
2328 ms
21.jpg
1794 ms
logowz.png
408 ms
14.jpg
2138 ms
42.gif
803 ms
23.jpg
4326 ms
28.jpg
1636 ms
17.jpg
4694 ms
21.jpg
1870 ms
view_p7.php
491 ms
i.php
2038 ms
ha0000.php
445 ms
20.jpg
1235 ms
s.php
2863 ms
meiwen_container_repeat_list.png
2346 ms
meiwen_container_top_list.jpg
2352 ms
meiwen_toolbar.gif
2363 ms
meiwen_list.gif
2366 ms
meiwen_container_bottom.png
2366 ms
i.php
901 ms
wholeclick.js
909 ms
s.php
936 ms
view_p7.php
1811 ms
view_p7.php
2139 ms
stat.php
830 ms
stat.htm
268 ms
core.php
1007 ms
22.jpg
2235 ms
24.jpg
2166 ms
ha0000.php
442 ms
21.jpg
1325 ms
9.gif
992 ms
i7click.php
926 ms
i7click.php
473 ms
ha0000.php
551 ms
24.jpg
444 ms
view_p7.php
496 ms
close.gif
372 ms
logodl.png
375 ms
view_i.php
1511 ms
view_i.php
455 ms
app.gif
910 ms
couplet_close.jpg
376 ms
ha0000.php
443 ms
logopic.png
479 ms
26.gif
1834 ms
ha0000.php
421 ms
g12.gif
365 ms
ha0000.php
440 ms
1.gif
1749 ms
yoyo61.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yoyo61.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Yoyo61.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.
yoyo61.com
Open Graph description is not detected on the main page of Yoyo 61. 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: