47.1 sec in total
993 ms
45.7 sec
345 ms
Visit 500.com now to see the best up-to-date 500 content for China and also check out these interesting facts you probably never knew about 500.com
Visit 500.comWe analyzed 500.com page load time and found that the first response time was 993 ms and then it took 46.1 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.
500.com performance score
993 ms
8801 ms
5417 ms
4165 ms
10358 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 9% of them (7 requests) were addressed to the original 500.com, 43% (33 requests) were made to 500cache.com and 13% (10 requests) were made to Img.500.com. The less responsive or slowest element that took the longest time to load (18.5 sec) relates to the external source Ckmap.mediav.com.
Page size can be reduced by 442.8 kB (42%)
1.0 MB
600.9 kB
In fact, the total size of 500.com main page is 1.0 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. 30% of websites need less resources to load. Images take 470.1 kB which makes up the majority of the site volume.
Potential reduce by 98.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. This page needs HTML code to be minified as it can gain 13.3 kB, which is 11% 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 98.5 kB or 79% of the original size.
Potential reduce by 13.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. 500 images are well optimized though.
Potential reduce by 246.0 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 246.0 kB or 72% of the original size.
Potential reduce by 85.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. 500.com needs all CSS files to be minified and compressed as it can save up to 85.0 kB or 80% of the original size.
Number of requests can be reduced by 30 (41%)
73
43
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 500. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
500.com
993 ms
www.500.com
8801 ms
index_v2.css
5417 ms
core_jq.js
4165 ms
yclass.js
10358 ms
home_v2.js
6430 ms
stats.js
4584 ms
20151221160025_4772.png
7828 ms
ghs.png
10382 ms
song.gif
436 ms
m_logo.png
1920 ms
new.gif
1552 ms
kftel.png
2868 ms
loading.gif
1381 ms
ad_mobile_code.png
5088 ms
cert.jpg
3943 ms
20160127144131782.png
6261 ms
20140910172656776.png
5129 ms
20151221160025_1974.png
12326 ms
index_yh01.png
3703 ms
top_ad_btn2.png
3080 ms
liansai_close.png
3425 ms
gradual_bg.png
3441 ms
selfservice.png
3804 ms
l_cp_ico2.png
4714 ms
index_yh02.png
7086 ms
n_speed_buy.png
6131 ms
login_up.png
6043 ms
tz-fkcq.png
6655 ms
index_yh02.png
6640 ms
20150910150604_5677.png
5488 ms
shell_v2.js
1172 ms
bds_s_v2.js
7455 ms
top_v2.js
2186 ms
500_log.js
1082 ms
hm.js
2501 ms
mvl.js
797 ms
rt.js
1058 ms
push.js
700 ms
float_right.png
2833 ms
mobile_prize.php
1011 ms
gettime.php
1465 ms
gettime.php
1465 ms
logger.js
10215 ms
tabs.js
1644 ms
mask.js
2617 ms
dataInput.js
1221 ms
hmcase_yh.js
3440 ms
ajaxbuy.js
1644 ms
focus.png
2802 ms
20160405111540_8621.jpg
7835 ms
20160202173733_7285.jpg
1871 ms
20160408163925_2899.jpg
3331 ms
20160406161744_2137.jpg
2941 ms
20160330163017_4124.jpg
2526 ms
mba.js
280 ms
mv.js
723 ms
dcs.gif
1212 ms
t
1471 ms
b
18482 ms
t
2195 ms
mask.php
5995 ms
bdsstyle.css
401 ms
hm.gif
399 ms
config_index_hm.xml
496 ms
loading.gif
487 ms
jjmy.xml
539 ms
ckmap.htm
2202 ms
cm.gif
1384 ms
m
1952 ms
m
2117 ms
m
2162 ms
m
1675 ms
m
894 ms
m
1990 ms
m
449 ms
500.com SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 500.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 500.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.
500.com
Open Graph description is not detected on the main page of 500. 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: