35 sec in total
1 sec
29.1 sec
4.9 sec
Click here to check amazing Yunbeibi content. Otherwise, check out these important facts you probably never knew about yunbeibi.com
Visit yunbeibi.comWe analyzed Yunbeibi.com page load time and found that the first response time was 1 sec and then it took 34 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
yunbeibi.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.173
69/100
15%
Value0
0/100
10%
1032 ms
465 ms
215 ms
428 ms
1498 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Yunbeibi.com, 18% (16 requests) were made to Img01.whatfugui.com and 7% (6 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Js.users.51.la.
Page size can be reduced by 77.4 kB (9%)
889.9 kB
812.5 kB
In fact, the total size of Yunbeibi.com main page is 889.9 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. 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 822.9 kB which makes up the majority of the site volume.
Potential reduce by 808 B
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 808 B or 50% of the original size.
Potential reduce by 50.0 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. Yunbeibi images are well optimized though.
Potential reduce by 15.2 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 15.2 kB or 53% of the original size.
Potential reduce by 11.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. Yunbeibi.com needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 31% of the original size.
Number of requests can be reduced by 15 (25%)
61
46
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yunbeibi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
www.yunbeibi.com
1032 ms
push.js
465 ms
tj.js
215 ms
common.js
428 ms
hm.js
1498 ms
21329749.js
19864 ms
hm.gif
324 ms
yhys.html
450 ms
0.43174038268625736
449 ms
0.5331368839833885
451 ms
0.18738432391546667
451 ms
0.13498676079325378
451 ms
0.34327594470232725
451 ms
0.12651173258200288
449 ms
0.39361464022658765
449 ms
165.3.93.79
1 ms
165.3.91.13
262 ms
ate.css
234 ms
zui.css
1870 ms
tb.js
424 ms
qq1.js
429 ms
dht.js
437 ms
dh.js
442 ms
sp.js
443 ms
sp1.js
446 ms
gg.js
629 ms
dl.js
636 ms
tz.js
640 ms
z1.js
644 ms
qq2.js
650 ms
qq3.js
656 ms
B64F4AC63F119179.jpg
2220 ms
EFE760B314831FBF.jpg
2253 ms
6FBBEE97CE67DAD3.jpg
2214 ms
677FF9017A20FFB7.jpg
2214 ms
D041FC4EE3BB7B3F.jpg
2213 ms
FE9ABEB2E0F53126.jpg
2213 ms
0699671B57CCADAD.jpg
2458 ms
C7BD8869E1660014.jpg
3114 ms
E99BCE99A9FF3FE2.jpg
2833 ms
87A7C2C12ED9DB79.jpg
2451 ms
43054646684A793E.jpg
2436 ms
9D8983E33C9EE996.jpg
2440 ms
CF7F33296B8EE0AF.jpg
3124 ms
CCBCC00C40F4A823.jpg
3139 ms
D8B2B98BDBEF19B8.jpg
3123 ms
7160C2A03DF608A9.jpg
2889 ms
1.gif
478 ms
03964120009rs6jjg70FF.gif
576 ms
4d5d4fe194df40eb84c60809c96354f9.gif
2537 ms
443e2520a8f945c788135743c09332fc.gif
2098 ms
463b9cd8e3724286b503e9724583a8fd.gif
2424 ms
f75be49de3de4182bb4b058dd358ddb4.gif
2314 ms
0.png
2834 ms
video-play.png
273 ms
230-160.gif
1175 ms
0yFUidjGHhQ
2986 ms
0
3224 ms
0yFVWR9AM6k
3279 ms
0
3051 ms
786BE1E8-3122-17487-34-DA2F48B5C3F9.alpha
522 ms
1821B7A6-8C27-17986-33-CCBBFECACFF8.alpha
506 ms
iconfont.woff
227 ms
iconfont.woff
266 ms
iconfont.ttf
877 ms
iconfont.ttf
876 ms
hm.js
1578 ms
hm.js
1834 ms
6322becc136c30cff133c82c.gif
1337 ms
200200.gif
1353 ms
6322beed136c30cff133c82d.gif
1415 ms
xxww.gif
1363 ms
9cc7e85fly1h6maqvwzx9g203c03c798.gif
977 ms
008t7KXCgy1h5wvdrfz0qg303c03c75m.gif
1021 ms
aa17e173a4c65df1ec1b23879a2d31.gif
2683 ms
gif22.gif
1273 ms
0103d120009h1026r1BFC.gif
661 ms
006j3g7igy1h3qh5sh9ttg303c03c78m.gif
1055 ms
290299ed48d84c7b99d8fbd8a96a254c
1474 ms
9b68c13628d3eda27f139dbcab11f1e5.gif
977 ms
78b711a758da55c9f0a6f88d5ed54fc2.gif
966 ms
2d9e99d0532fbc12eded53b70c20d64d.gif
929 ms
008rpxqrgy1h385k3gbgwg302s02swf0.gif
1035 ms
iconfont.svg
276 ms
iconfont.svg
323 ms
hm.gif
330 ms
hm.gif
335 ms
yunbeibi.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yunbeibi.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
yunbeibi.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
N/A
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yunbeibi.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 Yunbeibi.com main page’s claimed encoding is gb2312. 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.
yunbeibi.com
Open Graph description is not detected on the main page of Yunbeibi. 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: