46.1 sec in total
1.5 sec
44 sec
585 ms
Visit 2yinyue.com now to see the best up-to-date 2 Yinyue content and also check out these interesting facts you probably never knew about 2yinyue.com
白俊遥的php博客,个人技术博客,bjyblog,bjyadmin官方网站
Visit 2yinyue.comWe analyzed 2yinyue.com page load time and found that the first response time was 1.5 sec and then it took 44.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
2yinyue.com performance score
1541 ms
4071 ms
2188 ms
1073 ms
5332 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 74% of them (61 requests) were addressed to the original 2yinyue.com, 12% (10 requests) were made to Dbank.com and 4% (3 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Dbank.com.
Page size can be reduced by 364.5 kB (70%)
518.2 kB
153.7 kB
In fact, the total size of 2yinyue.com main page is 518.2 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. 20% of websites need less resources to load. Javascripts take 261.0 kB which makes up the majority of the site volume.
Potential reduce by 89.2 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 89.2 kB or 83% of the original size.
Potential reduce by 6.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. Obviously, 2 Yinyue needs image optimization as it can save up to 6.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 184.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 184.5 kB or 71% of the original size.
Potential reduce by 84.5 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. 2yinyue.com needs all CSS files to be minified and compressed as it can save up to 84.5 kB or 80% of the original size.
Number of requests can be reduced by 29 (39%)
74
45
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2 Yinyue. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
2yinyue.com
1541 ms
forum.php
4071 ms
style_14_common.css
2188 ms
style_14_forum_index.css
1073 ms
common.js
5332 ms
forum.js
2071 ms
elecnation.css
2568 ms
logging.js
3645 ms
md5.js
2302 ms
pc_proxy.php
986 ms
dbank_plugin.js
2449 ms
nge.css
3932 ms
common.js
1349 ms
f.js
2251 ms
ping.js
464 ms
discuz_tips.js
462 ms
elecnation_bg.jpg
12713 ms
unbg.png
6167 ms
noavatar_small.gif
1610 ms
him_fg.png
5339 ms
login_bt.gif
492 ms
login_qq.gif
503 ms
collapsed_no.gif
2244 ms
list10.gif
8755 ms
0.gif
2033 ms
1.gif
2729 ms
2.gif
3274 ms
forum.gif
8007 ms
ad_close.gif
7987 ms
security.png
8065 ms
nv_bot.png
8098 ms
bg_na.gif
8420 ms
bg_pw.gif
8469 ms
ccpm
19649 ms
ODc5OTk1MA==.js
347 ms
h.js
798 ms
common_extra.js
9699 ms
connect.php
8168 ms
21.gif
980 ms
hm.gif
426 ms
dlinknotexist.html
19529 ms
nv.png
7388 ms
dlinknotexist.html
1477 ms
dlinknotexist.html
20312 ms
nv_a.png
7024 ms
dlinknotexist.html
11126 ms
dlinknotexist.html
2801 ms
search.png
6826 ms
15_avatar_small.jpg
10191 ms
nv_sd.png
6736 ms
06_avatar_small.jpg
6691 ms
dlinknotexist.html
2267 ms
pt_item.png
6842 ms
30_avatar_small.jpg
6412 ms
noavatar_small.gif
6303 ms
noavatar_small.gif
6470 ms
12_avatar_small.jpg
6293 ms
noavatar_small.gif
6120 ms
noavatar_small.gif
5816 ms
09_avatar_small.jpg
6019 ms
chart.png
5596 ms
noavatar_small.gif
5237 ms
noavatar_small.gif
6384 ms
titlebg.png
5169 ms
noavatar_small.gif
5228 ms
noavatar_small.gif
6533 ms
noavatar_small.gif
4763 ms
noavatar_small.gif
4628 ms
noavatar_small.gif
4617 ms
noavatar_small.gif
6142 ms
noavatar_small.gif
9296 ms
noavatar_small.gif
5321 ms
style_switch.png
5147 ms
fav.gif
5107 ms
listbg.gif
5415 ms
line_bottom.png
6184 ms
scrolltop.png
5088 ms
dlinknotexist.html
20277 ms
dlinknotexist.html
439 ms
dlinknotexist.html
838 ms
o.htm
912 ms
hm.gif
714 ms
2yinyue.com SEO score
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2yinyue.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 2yinyue.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.
2yinyue.com
Open Graph description is not detected on the main page of 2 Yinyue. 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: