95.2 sec in total
4.9 sec
89.3 sec
990 ms
Click here to check amazing Jf content for China. Otherwise, check out these important facts you probably never knew about jf.cn
开什么加盟店好,免费加盟网店,家纺加盟店就到中国家纺官方商城JF.CN诚招家纺招商代理,家纺加盟.家居品牌购物家纺网,提供家纺品牌及家居用品,床上用品加盟,如四件套床品,全棉四件套,被子、被芯、床垫,枕芯及儿童用品。中国家纺官方商城,让好家纺走进千家万户。
Visit jf.cnWe analyzed Jf.cn page load time and found that the first response time was 4.9 sec and then it took 90.3 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 were 23 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
jf.cn performance score
4900 ms
8252 ms
6569 ms
7496 ms
8940 ms
Our browser made a total of 168 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Jf.cn, 74% (125 requests) were made to Static.zgjf168.com and 7% (11 requests) were made to Ckmap.mediav.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Static.zgjf168.com.
Page size can be reduced by 650.6 kB (46%)
1.4 MB
766.9 kB
In fact, the total size of Jf.cn main page is 1.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. 35% of websites need less resources to load. Images take 708.3 kB which makes up the majority of the site volume.
Potential reduce by 117.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. This page needs HTML code to be minified as it can gain 28.8 kB, which is 21% 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 117.7 kB or 85% of the original size.
Potential reduce by 113.5 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, Jf needs image optimization as it can save up to 113.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 350.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 350.1 kB or 72% of the original size.
Potential reduce by 69.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. Jf.cn needs all CSS files to be minified and compressed as it can save up to 69.3 kB or 79% of the original size.
Number of requests can be reduced by 40 (30%)
135
95
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
www.jf.cn
4900 ms
base.css
8252 ms
new_index.css
6569 ms
jquery-1.9.1.min.js
7496 ms
jquery.form.js
8940 ms
jquery.SuperSlide.2.1.1.js
6533 ms
jquery-ui.min.css
4545 ms
jquery-ui.min.js
19765 ms
jquery.lazyload.js
6973 ms
common.js
7468 ms
quick_links_v2.js
9467 ms
common_utils.js
7857 ms
jquery.nicescroll.js
10323 ms
lanrenzhijia.js
10485 ms
jquery.krakatoa.js
8675 ms
LoginDialog_v2.js
9098 ms
hm.js
2480 ms
ico1.jpg
394 ms
ico4.jpg
777 ms
gwctbbj.jpg
2678 ms
ico5.jpg
807 ms
canvas2.png
11723 ms
ico6.jpg
2395 ms
widget.do
3105 ms
ibar_sprites.png
1238 ms
no-img_mid.gif
3580 ms
wddd.jpg
3509 ms
yhq.jpg
3293 ms
weixin_code_145.png
6892 ms
201603291419561135.png
5560 ms
index_searchbg.jpg
3727 ms
201602221040027755.png
5377 ms
index_fl.png
4375 ms
201603212330520832.png
5596 ms
201603220902593610.png
5974 ms
201603221101574884.png
6154 ms
201603212326516752.png
6403 ms
201603212338498958.png
6943 ms
201603211917056771.png
6346 ms
201603221123226501.png
6540 ms
201603220002133365.png
7793 ms
201603212350113328.png
7217 ms
201603221129214281.jpg
7929 ms
201603212318271075.png
7976 ms
201603221130125023.jpg
11373 ms
201603221141451896.jpg
10017 ms
201603221143138137.jpg
8562 ms
201603221144143051.jpg
9172 ms
201603221150022239.png
8813 ms
201603221349363062.png
11892 ms
201603221350549881.png
9731 ms
201603221357052968.png
10486 ms
201603221402386735.png
10585 ms
201603180817089171.jpg
19574 ms
37bf193e3af3d6145d1394e98e765e6d
6111 ms
mvl.js
2250 ms
ag.js
2137 ms
z_stat.php
2175 ms
201602031638153801.jpg
20256 ms
201602221515114146.jpg
19864 ms
201603180818031285.jpg
19826 ms
201603180818301811.jpg
20381 ms
ag_track-0.1.10.js
975 ms
stat.htm
224 ms
core.php
811 ms
201604081107074213.jpg
20235 ms
mba.js
1429 ms
mv.js
6541 ms
hm.gif
326 ms
201604081106434390.jpg
19962 ms
hm.js
2215 ms
pixel
85 ms
t.gif
5115 ms
pv
1110 ms
201604081102210114.jpg
20327 ms
pixel
48 ms
cookieMapping
1044 ms
201603281332158974.jpg
20113 ms
201603311449490149.jpg
20053 ms
201603281831198700.jpg
19901 ms
t
1222 ms
BaiduCM
1925 ms
201604071117135082.jpg
20207 ms
hm.gif
325 ms
201604071117303610.jpg
19746 ms
201604071117545611.jpg
19264 ms
201604071129104302.jpg
19986 ms
201604071118109019.jpg
19608 ms
201604071118249112.jpg
20427 ms
201604071118405820.jpg
20234 ms
201604071119033322.jpg
20180 ms
201604071119183094.jpg
20049 ms
201604071119343773.jpg
19736 ms
index_one.png
19653 ms
1.bmp
20162 ms
sec_pr_bg.png
19594 ms
index_two.png
19449 ms
index_three.png
19602 ms
cm.gif
5337 ms
index_four.png
19227 ms
index_five.png
18983 ms
b
2204 ms
t
1707 ms
index_six.png
18696 ms
1f_2.png
18499 ms
1f_1.png
18220 ms
2f_2.png
17778 ms
2f_1.png
19987 ms
pixel
23 ms
t.gif
1944 ms
ckmap.htm
957 ms
cm.gif
726 ms
m
600 ms
3f_2.png
16974 ms
3f_1.png
16711 ms
m
5127 ms
m
571 ms
4f_2.png
16729 ms
m
5523 ms
m
957 ms
m
5076 ms
m
4858 ms
t.gif
933 ms
m
4627 ms
m
3785 ms
TanxCM
375 ms
m
605 ms
4f_1.png
9057 ms
5f_2.png
8101 ms
5f_1.png
8181 ms
6f_2.png
8198 ms
6f_1.png
7460 ms
shouji.jpg
7321 ms
weixin.jpg
9199 ms
morelogo1.png
5662 ms
morelogo2.png
9588 ms
morelogo5.png
5859 ms
dot1.png
7529 ms
dot2.png
5313 ms
ad_ctr.png
5472 ms
1f_3.png
5185 ms
2f_3.png
5132 ms
3f_3.png
7655 ms
4f_3.png
4507 ms
5f_3.png
6808 ms
6f_3.png
4924 ms
201603301419171923.gif
7945 ms
201603271736183607.png
5276 ms
201604071111409164.jpg
17039 ms
201604080822568061.jpg
17033 ms
201604071111595437.jpg
7437 ms
201604071112170034.jpg
7339 ms
201604071112314879.jpg
7742 ms
201604071112517659.jpg
10275 ms
201604070959458273.jpg
16988 ms
201604071114061016.jpg
9772 ms
201604071116386447.png
8520 ms
201604071117135082.jpg
6774 ms
201604071129104302.jpg
3391 ms
201604071118109019.jpg
19728 ms
201604071118249112.jpg
4692 ms
201604071118405820.jpg
5888 ms
201604071119033322.jpg
18511 ms
201604071119183094.jpg
10520 ms
201604071119343773.jpg
15272 ms
pagination.png
6268 ms
hm.gif
860 ms
hm.gif
1183 ms
jf.cn SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jf.cn 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 Jf.cn 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.
jf.cn
Open Graph description is not detected on the main page of Jf. 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: