36.8 sec in total
1 sec
35.1 sec
653 ms
Welcome to quyeba.com homepage info - get ready to check Quyeba best content for China right away, or after learning these important things about quyeba.com
北面
Visit quyeba.comWe analyzed Quyeba.com page load time and found that the first response time was 1 sec and then it took 35.8 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
quyeba.com performance score
1049 ms
2516 ms
3971 ms
4126 ms
6672 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Quyeba.com, 53% (86 requests) were made to S.qybimg.com and 7% (12 requests) were made to Ww2.sinaimg.cn. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source S.qybimg.com.
Page size can be reduced by 966.0 kB (21%)
4.6 MB
3.6 MB
In fact, the total size of Quyeba.com main page is 4.6 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. 60% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 93.8 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 26.8 kB, which is 24% 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 93.8 kB or 84% of the original size.
Potential reduce by 150.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. Quyeba images are well optimized though.
Potential reduce by 383.8 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 383.8 kB or 67% of the original size.
Potential reduce by 338.2 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. Quyeba.com needs all CSS files to be minified and compressed as it can save up to 338.2 kB or 83% of the original size.
Number of requests can be reduced by 51 (32%)
157
106
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Quyeba. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
quyeba.com
1049 ms
www.thenorthface.com.cn
2516 ms
css_97mFEvkiRfaVhKCyhsLN4ctlDeXs3e7hjyZnbYzKeCQ.css
3971 ms
css_GtADxgzpCgxdVoxFmfaqWc59x7lhedAG7CUBV3ZOpI0.css
4126 ms
css_RPNmY9EUUzccdbz1ND4KgYJeTsEXlLV3NExXQGxKx5o.css
6672 ms
css_6xM2HVN5cp7rOUuRjY6ZLxKCN6tw4NSRzsrXNOBrnFQ.css
4228 ms
jquery.min.js
6598 ms
jquery.once.js
4790 ms
drupal.js
4968 ms
jquery.ui.core.min.js
5287 ms
jquery.ui.widget.min.js
5218 ms
jquery.ui.position.min.js
5804 ms
jquery.ui.menu.min.js
6639 ms
jquery.ui.autocomplete.min.js
5748 ms
jquery.ui.button.min.js
5812 ms
jquery.ui.mouse.min.js
6271 ms
jquery.ui.draggable.min.js
6200 ms
jquery.ui.resizable.min.js
7147 ms
jquery.ui.dialog.min.js
6575 ms
jquery.validate.min.js
6760 ms
zh-hans_Zb_vqnsbHEH2uI6kjNGewCx73o9jW6Zj_LVxmEQUjnE.js
8907 ms
jquery.infinitescroll.min.js
8125 ms
jquery.lazyload.min.js
7055 ms
jquery.namecard.min.js
8429 ms
jquery.cookie.js
7279 ms
base.js
9949 ms
hack.js
7654 ms
jquery.vticker.min.js
7819 ms
jquery.slides.min.js
8143 ms
jquery.raty.js
8300 ms
tracking.js
7686 ms
tracking.event.www.js
7726 ms
os295x89tu8r10nz.jpg
1770 ms
14435103780777.jpg!middle.jpg
1760 ms
space.png
519 ms
l7kr1apdgv61sdox.jpg!320x200.jpg
1831 ms
14477418530794.jpg!205x0.jpg
1827 ms
a0iqi0jv7dc7bbf6.jpg!320x200.jpg
1835 ms
bwqtpfxent6e528b.jpg!320x200.jpg
1833 ms
pfa8mojm4eyvqzay.jpg!320x200.jpg
1830 ms
n-bg-bodyv2.jpg
19684 ms
home-left.png
2139 ms
space.png
526 ms
block-isystem-topbar-motto.jpg
1515 ms
quyeba1.jpg
3075 ms
quyeba2.jpg
1629 ms
quyeba3.jpg
3377 ms
quyeba4.jpg
3297 ms
quyeba6.png
3204 ms
yquxiaozu_03.jpg
2692 ms
exp1.jpg
3661 ms
exp2.jpg
4546 ms
exp3.jpg
4796 ms
about1.jpg
3795 ms
about2.jpg
5697 ms
about3.jpg
6086 ms
about4.jpg
5292 ms
close.png
4938 ms
white.gif
5331 ms
wechat.jpg
5749 ms
qrcode.jpg
7938 ms
weibo.jpg
6543 ms
tnf-new-homepage-man.png
10385 ms
tnf-new-homepage-arrow.png
6188 ms
tnf-new-homepage-close.png
6484 ms
tnf-new-homepage-text.png
8090 ms
4q8d708ytnvsstys.jpg
1785 ms
5axljgk2tz6bzej1.jpg
1716 ms
eb4psta54w67j8hl.jpg
1763 ms
bh4kgaqteis5rzao.jpg
1747 ms
435b5taiz3rkflhe.jpg
1743 ms
de4j0qsukoeqp9qg.jpg
1746 ms
hnw1jaa7r1qc405c.jpg
1754 ms
txdxqaw8zcuawriz.jpg
1779 ms
8iupph49gulxw07j.jpg
1756 ms
ubfpplklt6fqfbh2.jpg
1772 ms
ghs.png
4409 ms
y6zvznol9789yvbn.jpg!205x0.jpg
1815 ms
14574193990863.jpeg!454x300.jpg
1819 ms
enqwdul27m5g7h9g.JPG!205x0.jpg
1814 ms
14508411850012.jpg!205x0.jpg
1815 ms
logo.png
6906 ms
i-search.png
7035 ms
china.jpg
7742 ms
search-shop.jpg
7543 ms
nav-bg.jpg
8028 ms
nav-bg-hover.png
8569 ms
nav-bg.png
9341 ms
i-ads.png
8621 ms
fontawesome-webfont.woff
9774 ms
mask.png
8943 ms
index.php
1886 ms
piwik.js
5908 ms
dc.js
47 ms
analytics.js
9 ms
h.js
19565 ms
collect
50 ms
collect
11 ms
__utm.gif
13 ms
collect
63 ms
HelveticaNeueLTStd-BdCn.otf
10157 ms
weiboShow.css
27 ms
skin10.css
41 ms
gaea_1_19.js
39 ms
bg.png
7908 ms
1
68 ms
64196aa7gw1f2pbxjj1paj21kw11x7kp.jpg
76 ms
64196aa7gw1f2p7fb05r4j21kw11z7i2.jpg
68 ms
64196aa7gw1f2o59ohvc1j20ly0b10tn.jpg
65 ms
64196aa7gw1f2n6gl3542j20zk0qojtw.jpg
68 ms
icon_user.png
58 ms
btns_bg.png
59 ms
icon_follow.png
59 ms
64196aa7gw1f2p74ejo4bj21kw11v7m7.jpg
64 ms
64196aa7gw1f2p4kstqktj20k70aoq3k.jpg
64 ms
64196aa7gw1f2n9jzdscgj20qo0zk76v.jpg
88 ms
64196aa7gw1f2n3x6ba9kj21560ooq8h.jpg
87 ms
64196aa7gw1f2m654g38pj20hs0buaay.jpg
61 ms
i-arrow.png
8770 ms
64196aa7jw1f2iq7lj0p9j20zk0qo11x.jpg
39 ms
64196aa7jw1f2ibi2fpcij20m80ci0v7.jpg
48 ms
4d4f2680gw1f2i7gs3nbyj21w01w0kjr.jpg
34 ms
love.gif
14 ms
suda.js
12 ms
64196aa7gw1f2hb27hkp7j20ku0fmwhs.jpg
33 ms
64196aa7jw1f2iaak9rk0j20m80gotay.jpg
76 ms
723de71bjw1f2hf3y6ciwj20m80cimzm.jpg
38 ms
64196aa7gw1f2hfccioh0j20zk0qogqn.jpg
74 ms
64196aa7gw1f2h9vk47aej20rs0kudka.jpg
21 ms
64196aa7gw1f2h8ltawywj20jz0zkgqx.jpg
22 ms
show.js
3 ms
bg_trans.png
13 ms
icon_tips.png
14 ms
a.gif
864 ms
tmp.gif
4852 ms
hot-act.png
7670 ms
home-act-bg.png
7641 ms
home-story-bgx.png
7125 ms
home-story-bgd.png
7898 ms
i-fsh.png
7525 ms
n-quick.png
8059 ms
n-quick-v1-index.png
7208 ms
n-quick-v1.png
7470 ms
backtotop.png
6675 ms
piwik.php
2401 ms
layer_bg.png
863 ms
home_store
2010 ms
14568251920100.jpg!middle.jpg
12 ms
loading.gif
812 ms
arrow.png
2385 ms
i-slide-pvr.png
960 ms
i-slide-pv.png
1029 ms
14568257460614.jpg!middle.jpg
20 ms
14590657120700.jpg!middle.jpg
9 ms
14570856790884.jpg!middle.jpg
10 ms
14594058500647.jpg!middle.jpg
22 ms
14594061140991.jpg!middle.jpg
12 ms
14537080440744.jpg!middle.jpg
10 ms
14568165230111.jpg!middle.jpg
18 ms
view-star-on.png
1024 ms
map-tnf.jpg
826 ms
icon-tnf.jpg
484 ms
icon-addr.png
417 ms
quyeba.com SEO score
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quyeba.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Quyeba.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.
quyeba.com
Open Graph description is not detected on the main page of Quyeba. 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: