29.9 sec in total
2.3 sec
26.9 sec
639 ms
Welcome to 533.com homepage info - get ready to check 533 best content for China right away, or after learning these important things about 533.com
域名视频交易开创领导者,域名界首创视频交易由航伟[微信68888]和张大官人[微信12313]联合发起,由美女主播乔[微信788788]主持!
Visit 533.comWe analyzed 533.com page load time and found that the first response time was 2.3 sec and then it took 27.5 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.
533.com performance score
2332 ms
2272 ms
2633 ms
636 ms
4851 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 533.com, 33% (47 requests) were made to Img1.533.com and 26% (36 requests) were made to Ubmcmm.baidustatic.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Img1.533.com.
Page size can be reduced by 515.8 kB (28%)
1.9 MB
1.4 MB
In fact, the total size of 533.com main page is 1.9 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 167.3 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 30.5 kB, which is 15% 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 167.3 kB or 85% of the original size.
Potential reduce by 84.6 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. 533 images are well optimized though.
Potential reduce by 252.4 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 252.4 kB or 62% of the original size.
Potential reduce by 11.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. 533.com needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 79% of the original size.
Number of requests can be reduced by 36 (26%)
139
103
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 533. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
533.com
2332 ms
533_reset_xin.css
2272 ms
533_index_xin.css
2633 ms
jquery-1.4.2.min.js
636 ms
MSClass.js
4851 ms
m.js
1054 ms
c.php
1973 ms
533_index_xin.js
3982 ms
533xin_02.jpg
1591 ms
1458094392_52368600.jpg
5241 ms
1436434183_67695000.jpg
2861 ms
1436434269_54133500.jpg
4029 ms
1396575855_25913600.jpg
3168 ms
1438928163_44846500.jpg
2631 ms
1377141677_98281500.jpg
2102 ms
1404196449_90773600.jpg
2666 ms
1396581071_04069600.jpg
4226 ms
1425093784_79419600.jpg
3220 ms
1425093616_14391800.jpg
3325 ms
1425093808_14184000.jpg
5704 ms
1409296167_57135800.jpg
19986 ms
1398407218_47589300.jpg
3784 ms
1410849598_29856200.jpg
4249 ms
1415332835_40929300.jpg
4451 ms
1422254530_31159100.jpg
6258 ms
1422254662_15403600.jpg
7136 ms
1427354583_45309300.jpg
4929 ms
1427272996_75385600.jpg
8455 ms
1409293667_03450500.gif
5621 ms
1377153005_68224800.jpg
6780 ms
1422257349_64783400.jpg
6249 ms
1422257187_66784100.jpg
6803 ms
1422254781_14222800.jpg
8379 ms
1422254909_18572500.jpg
7173 ms
1422260972_02795000.jpg
7355 ms
1422261064_08124300.jpg
7637 ms
1422320431_49056400.jpg
7564 ms
1422258276_55731600.jpg
8905 ms
1422254995_67929900.jpg
7957 ms
1422255142_06980300.jpg
8573 ms
1422261183_99329500.jpg
8349 ms
1422261323_75681000.jpg
8739 ms
1422258425_34220700.jpg
8923 ms
1422258699_40953500.jpg
9457 ms
1422255288_03290400.jpg
9958 ms
new533Logo.gif
1709 ms
lx_ico1.gif
2028 ms
lx_ico2.gif
1900 ms
wcpm
1111 ms
wcpm
1575 ms
1422255750_85799700.jpg
7026 ms
1422261451_74779200.jpg
6835 ms
1422261546_10605800.jpg
6809 ms
t_ppzq.gif
762 ms
0f00057T9_gQJU3QKCGP-0.jpg
519 ms
0f000DEpfcRzFLOsJj_REs.jpg
521 ms
0f0005yYILnBotmJfPudqs.jpg
536 ms
0f000rgmX0CDKxNXoyuAs6.jpg
767 ms
0f000QtU4gFO9IIJTOCD7s.jpg
525 ms
0f0002EWaNI-J486Ew2vK6.jpg
523 ms
0f000Q6WT-4t_YgiJSliyf.jpg
1454 ms
0f000Zt-OySzKjqFKBdlV0.jpg
1290 ms
0f0005yYILtBotmJfPudts.jpg
2001 ms
0f000j5UUwM4NNYccbnkVf.jpg
2342 ms
0f000Poxpx4P5hDIOn0Q0f.jpg
1544 ms
0f000AD9VRqx8YQjMic2O0.jpg
2949 ms
wcpm
599 ms
1422258847_76380200.jpg
7835 ms
1422259258_10094300.jpg
6737 ms
1422255875_33316400.jpg
9383 ms
1422255962_53106400.jpg
7186 ms
bana.html
2133 ms
banb.html
2269 ms
banc.html
2371 ms
11111.gif
716 ms
wcpm
608 ms
1422256274_25989200.jpg
7072 ms
0f000aUOm4PA-AwxM1wfsf.jpg
542 ms
0f0000u0QUgBwmTFY5w5S6.jpg
715 ms
0f000KXcACsvrtHbL64Fc0.jpg
797 ms
0f000KXcAC0vrtHbL64FQ0.jpg
1067 ms
0f000KXcACfvrtHbL64F20.jpg
1243 ms
0f000KXcAG6vrtHbL64F70.jpg
1248 ms
0f000KXcAGsvrtHbL64FD0.jpg
1335 ms
0f000QuuSunQStwjP0qids.jpg
1572 ms
0f000ZoULbV3wQRgredb70.jpg
1620 ms
0f0002xZEpSVaj7iUBISz0.jpg
1707 ms
0f000cSojxL_OSHtXMKgss.jpg
1774 ms
0f000QuuSm_QStwjP0qiLs.jpg
1811 ms
0f000cSojxM_OSHtXMKg1s.jpg
2397 ms
0f0000u0QTMBwmTFY5w5e6.jpg
2129 ms
0f000aUOm4VA-AwxM1wfzf.jpg
2204 ms
0f000KXcAJ6vrtHbL64FK0.jpg
2213 ms
index_02.gif
426 ms
index_01.jpg
1087 ms
lx_ico3.gif
359 ms
wcpm
615 ms
1422261681_73504100.jpg
6394 ms
1422261762_08391100.jpg
7546 ms
1421396694_56809000.jpg
8481 ms
wcpm
636 ms
0f000Q2Qx5MhB5J383po36.jpg
1482 ms
0f000Ki-jU_7UR53W_YOl6.jpg
1008 ms
0f0007ZMk4BgHfZ9qPG2n6.jpg
1317 ms
0f000D9ndiq3y-f3QlDgkf.gif
1383 ms
0f000jGy_5UBaLbkzPpHGs.jpg
1443 ms
wcpm
609 ms
o.js
997 ms
c.js
438 ms
ask
1919 ms
ask_service
2395 ms
lcgm
585 ms
ycbm
2658 ms
bcqm
1163 ms
0f000QNxZD9iz2fW4Qu4g0.jpg
717 ms
0f000DYeKymproAX3jyYss.jpg
765 ms
o.htm
610 ms
ct
9048 ms
lm.jpg
1037 ms
wh.js
820 ms
ac.js
565 ms
pe.js
218 ms
wcpm
618 ms
log_print
757 ms
0f000jlWjR7i5k7GPvRHHs.jpg
502 ms
fp.htm
592 ms
fp.htm
598 ms
wcpm
596 ms
fp.htm
433 ms
fp.htm
270 ms
fp.htm
271 ms
t.js
2323 ms
wcpm
631 ms
fp.htm
270 ms
stat.htm
286 ms
core.php
571 ms
px
21 ms
sogou_icon_wz_1.png
658 ms
fc.js
225 ms
co.js
216 ms
fp.htm
550 ms
533.com SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 533.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 533.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.
533.com
Open Graph description is not detected on the main page of 533. 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: