10.3 sec in total
699 ms
8.2 sec
1.4 sec
Welcome to yxrd.com homepage info - get ready to check Yxrd best content right away, or after learning these important things about yxrd.com
Visit yxrd.comWe analyzed Yxrd.com page load time and found that the first response time was 699 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yxrd.com performance score
699 ms
3584 ms
8 ms
15 ms
4 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yxrd.com, 96% (129 requests) were made to 23.com and 1% (1 request) were made to S95.cnzz.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source 23.com.
Page size can be reduced by 713.6 kB (5%)
14.4 MB
13.7 MB
In fact, the total size of Yxrd.com main page is 14.4 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. 85% 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 14.3 MB which makes up the majority of the site volume.
Potential reduce by 176 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 176 B or 36% of the original size.
Potential reduce by 594.4 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. Yxrd images are well optimized though.
Potential reduce by 94.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 94.1 kB or 64% of the original size.
Potential reduce by 25.0 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. Yxrd.com needs all CSS files to be minified and compressed as it can save up to 25.0 kB or 79% of the original size.
Number of requests can be reduced by 11 (8%)
133
122
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yxrd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
yxrd.com
699 ms
www.23.com
3584 ms
style.css
8 ms
jquery-1.8.3.min.js
15 ms
top_toolbar.js
4 ms
zxf_userinfojs.php
857 ms
all_bg.jpg
10 ms
logo.gif
6 ms
39695994c753e52e126d00791dde6776.png
8 ms
6aebd2a56d2121fe961377fee2719810.png
9 ms
16001b0550256768b4b8ef07049333e9.png
8 ms
63210c32957f8d679d3671e863ea888e.png
9 ms
628defb9e0c5ef2cc0ed67002355bcc1.png
10 ms
a10c0afd49e0d92cc4bd714bdc4e1f12.png
10 ms
4d4fac0f7ceea620e77f7e7a15ca6cbf.png
11 ms
f55bf9af9f21e981ff209d98f8514f9a.png
13 ms
58167bd5dc86d66246fbfa80e05d381c.png
33 ms
thumb_100_100_20140328012745878.png
14 ms
5061660d48de952ba5a94039ea3b7dd1.png
23 ms
3b7f2a7a72b0293a34eda559c3178df8.png
16 ms
thumb_100_100_20131128092511707.png
15 ms
2b6f6172eec62ccc7f19cda0146698c5.jpg
19 ms
e700a677ffea57d1f8807f15d67e7719.png
19 ms
68364e8eb4c7d6f9e55772a0316ac1b1.png
22 ms
a16bd1f18971f6425c2921037fa5620d.jpg
21 ms
f5f40c17ac55ecb7153e4a0b1d5ad06c.png
32 ms
277e17350664cdedd556e475155331cc.png
26 ms
020216c16e793a64f744ebe7cbfc1012.png
34 ms
95b42e99cc65ab83c5aff26c116357e0.jpg
29 ms
6e06c910d1ff8578388fce80365480a5.jpg
34 ms
5540336889cc0ba913ac2936738eb049.jpg
35 ms
fb45808ec5ee579cdae3eb4eae38240d.png
5 ms
33ce44922bb932221ef59b5c2ba2a619.jpg
7 ms
de0264bcbaa1474cfa0dd94b36839a42.jpg
4 ms
6a7d2b151f5ec903c0f00d5df237c200.jpg
26 ms
c73f69b31e3e3ed77b1752a43a080eea.jpg
12 ms
8b4529593bd986ca274007a93629c102.jpg
12 ms
fa5ef4162c264313647915270fb92155.png
10 ms
34d9861b3fab18d61841ef7481fee573.jpg
32 ms
56256648f1bec1def57fcdccb6e1d1d1.png
12 ms
49728922268603ca2ca12dc47258bbcd.gif
14 ms
0a3cbccd31380b23dcd7b8ce0f7a17d3.jpg
21 ms
18a87070b087ef2dd4c7dd561db7d537.png
19 ms
icon.png
59 ms
andriod_icon1.png
62 ms
app_icon1.png
58 ms
top_addtitle_bg.png
61 ms
pngbg.png
63 ms
hgx.jpg
61 ms
t_icon.png
64 ms
pic_border_bg.png
62 ms
hot_area_bg.png
63 ms
bg1.jpg
64 ms
title_left_bf.png
66 ms
f7654bce2fb48365bd00d869b96e3533.png
11 ms
7721898adf5787e2ac3b60ec3cc04904.png
10 ms
8d548f514cdc7de21414ba1efa5b48d1.jpg
11 ms
2cdd146f520dfec02cff21db85058906.jpg
14 ms
9467e497138a2149f09eece9a8de7982.jpg
20 ms
c7a268d84d0df919370181dbbeb51cd3.png
25 ms
4150def46981d9c08f5b51a33c23e98d.png
11 ms
414ce4fa03af3430f0ea7f307e493bd2.jpg
12 ms
d19792c6c486c4072e10519cfc998676.png
13 ms
625a5cbe7324e64b7858014c3b2d63ae.jpg
19 ms
2aba21a918b04e1506198bf6acbd8704.png
58 ms
09c283ba86538084ce2176fc9d37836a.jpg
13 ms
thumb_100_100_20140808014953693.png
15 ms
8883556f12f003a44e18544f7eecf6de.png
18 ms
326f6da238553d08a31cce4972734b7d.jpg
21 ms
72f89e54374c0184913fcb46e9b92846.png
20 ms
c9c07a7a769c6fec6584ad5eca55e338.png
29 ms
small7ba05226a2421ffa65b81610df371c8d.jpg
23 ms
6b74c59f7b39018a32e949c3e944dd65.jpg
24 ms
thea4.js
24 ms
194db35da2c79a416c0c63b6a3ab439c.jpg
21 ms
7db4a67e5f13f1e53be41f40ee29305a.jpg
30 ms
5d05e8df903290e9f3420c6acaae4be9.png
26 ms
dea8b350ebd102f14d41e4428fe42fab.png
29 ms
1a6c610deb41d3574669a81930d735cf.jpg
27 ms
5579e79de5c9bc4dbb2a3df22fd99848.jpg
25 ms
372424d3cab86f5844d48ea4ea757542.jpg
30 ms
d28908d4aae77cbc0533d029096ec923.jpg
32 ms
thea6.js
24 ms
fa5ef4162c264313647915270fb92155.png
16 ms
159b72713e5d4db1fa236f189e7744be.png
18 ms
c9c07a7a769c6fec6584ad5eca55e338.png
17 ms
f39455fa6c0101c7fb1a34c41562088d.png
17 ms
0fa3e10341d8f2538a15edeffa71d3fa.png
17 ms
0bffcd4212ede09617f5f528802a6aa8.png
19 ms
81ae3bf28041838d5f710ab4002c7f8b.png
20 ms
5b5cd355d66eb1ac89a0787fcf0f7e0d.png
21 ms
c290d7fcdf8bb53c84ca0943a474ee93.png
21 ms
1729061bbc05ddff92165502e05ce8e4.jpg
21 ms
ac6d194094aa6322c38a21ac577cc668.png
22 ms
de6c2ada1075ad863148fb9b0e0c4a22.png
21 ms
47b502a5a4f95dbeeb6740bfbf7aaf7f.jpg
33 ms
b56cae037b4148a845b93234031aff0b.png
23 ms
6e63533ccd5792da0441f2b1e0ccb921.png
23 ms
tb.gif
26 ms
5fbfe9479789f60e98e8d91c75da9d3b.png
28 ms
20140528060009330.jpg
25 ms
57acf0392b194f5b013d4f0c7c879a74.png
28 ms
1be0aa957e5be23e4c7206f9ccc91a62.jpg
30 ms
7b70774e25b1f3ab6c8d16bac83a8c17.jpg
26 ms
9e8a4ec4c94c5ca0f27db92710d6a2f9.jpg
32 ms
2f7ea2276837f3f929c4600b7f126efa.jpg
33 ms
0ad4b69da0ff291ceb15c904b05c7aca.jpg
30 ms
8b9f6ce7558ec7ef4372466da14335e7.jpg
42 ms
3cab4535dc91be2a6429db14046aba11.png
69 ms
75c6511b4d29ea2b80493ccb78e7bd6a.png
71 ms
thea5.js
31 ms
7af2bf9ba10b54706c22f46f5544a644.png
65 ms
062aef98fda25fb4a0dcc27286f23c90.png
68 ms
19ead5de78c88d5def5b81db6338a59c.png
33 ms
pngbg_a.png
34 ms
0ef8fdd65b521153fb18ec7069c47f9d.jpg
24 ms
pic_border_bg2.png
23 ms
popup_1.png
19 ms
popup_2.png
13 ms
knejenonclb.jpg
6 ms
a1fl3dz05ew.jpg
11 ms
zgllqw5whf4.jpg
16 ms
pxsq4nef4cm.jpg
11 ms
r3fniirepz4.jpg
22 ms
lt1uqa0ta2l.jpg
16 ms
kheifozg4d3.jpg
11 ms
focusbox.js
12 ms
global.js
18 ms
jquery.SuperSlide.2.1.1.js
15 ms
top.bar.js
17 ms
z_stat.php
1773 ms
stat.htm
167 ms
core.php
780 ms
share.js
1308 ms
yxrd.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yxrd.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Yxrd.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.
yxrd.com
Open Graph description is not detected on the main page of Yxrd. 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: