45.3 sec in total
2.7 sec
41.4 sec
1.1 sec
Click here to check amazing 1688 Bm content. Otherwise, check out these important facts you probably never knew about 1688bm.com
域名是企业重要的资产,您所访问的域名已经过期,请尽快联络注册商续费
Visit 1688bm.comWe analyzed 1688bm.com page load time and found that the first response time was 2.7 sec and then it took 42.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 18 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
1688bm.com performance score
2725 ms
5095 ms
2684 ms
7775 ms
2463 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 49% of them (44 requests) were addressed to the original 1688bm.com, 16% (14 requests) were made to Bdimg.share.baidu.com and 7% (6 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain 1688bm.com.
Page size can be reduced by 547.8 kB (63%)
873.4 kB
325.6 kB
In fact, the total size of 1688bm.com main page is 873.4 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. 35% of websites need less resources to load. Javascripts take 630.5 kB which makes up the majority of the site volume.
Potential reduce by 35.7 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 35.7 kB or 75% of the original size.
Potential reduce by 15.8 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, 1688 Bm needs image optimization as it can save up to 15.8 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 388.9 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 388.9 kB or 62% of the original size.
Potential reduce by 107.4 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. 1688bm.com needs all CSS files to be minified and compressed as it can save up to 107.4 kB or 81% of the original size.
Number of requests can be reduced by 45 (67%)
67
22
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1688 Bm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
1688bm.com
2725 ms
www.1688bm.com
5095 ms
style.css
2684 ms
common.js
7775 ms
c_html_js_add.php
2463 ms
menu.css
3773 ms
default.css
1138 ms
nivo-slider.css
1713 ms
ie.html5.js
3502 ms
jquery.easing.1.3.js
3458 ms
jquery.nivo.slider.pack.js
3694 ms
menu.js
3361 ms
hover.js
3828 ms
buttons.js
3959 ms
jquery.cycle.js
11710 ms
c.js
1040 ms
z_stat.php
1322 ms
embed.js
243 ms
counts.jsonp
816 ms
uf.js
745 ms
shCore.pack.js
6863 ms
shCoreDefault.pack.css
476 ms
191454552897.jpg
4419 ms
background.png
516 ms
background-gray.png
4242 ms
logo.png
7385 ms
end-logo.png
1384 ms
201503121426091489675211.jpg
20123 ms
201412301419947402129383.jpg
20124 ms
201412301419952002104976.jpg
20123 ms
list-3.png
3375 ms
date.png
3932 ms
comments.png
4496 ms
201512091449662751680590.jpg
9979 ms
arrow.png
11089 ms
201512061449382313133282.jpg
20122 ms
201512041449216703714456.jpg
20123 ms
201512031449155469549386.jpg
20122 ms
201511301448849068591643.jpg
20123 ms
201511241448374159844929.jpg
20125 ms
201511191447937155695049.jpg
20126 ms
rss.png
20126 ms
f.png
20128 ms
f1.png
20128 ms
t.png
20128 ms
t1.png
20128 ms
g.png
20128 ms
g1.png
20127 ms
r.png
20128 ms
r1.png
20127 ms
jcem
1021 ms
share.js
1663 ms
stat.htm
252 ms
core.php
2208 ms
jcem
2197 ms
9.gif
2156 ms
ls.js
237 ms
ping.json
869 ms
share_api.js
239 ms
share_view.js
450 ms
select_api.js
496 ms
select_view.js
495 ms
image_api.js
456 ms
image_view.js
491 ms
ls_flowbar.js
239 ms
tangram.js
1624 ms
api_base.js
440 ms
pixel
58 ms
adx.php
729 ms
reduce_bd-logo1_oper.png
495 ms
pixel
51 ms
view_base.js
229 ms
home
850 ms
gpixel
533 ms
embed.default.css
81 ms
jquery_a4373ccd.js
487 ms
closefeedback.min.js
562 ms
arrow_left_60_e700a3bb.png
306 ms
arrow_left_50_1dfda915.png
453 ms
reduce_promotion_oper.png
475 ms
bd_logo.png
486 ms
bg_rb.png
537 ms
partners.js
236 ms
share_style0_24.css
311 ms
app.gif
874 ms
icons_0_24.png
951 ms
logger.js
227 ms
o.htm
774 ms
wh.js
830 ms
ac.js
550 ms
1688bm.com SEO score
N/A
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1688bm.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), while the claimed language is Chinese. Our system also found out that 1688bm.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.
1688bm.com
Open Graph description is not detected on the main page of 1688 Bm. 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: