43.7 sec in total
877 ms
41.2 sec
1.6 sec
Welcome to haofeng.tmall.com homepage info - get ready to check Haofeng Tmall best content for China right away, or after learning these important things about haofeng.tmall.com
淘宝, 店铺, 旺铺, 豪峰旗舰店
Visit haofeng.tmall.comWe analyzed Haofeng.tmall.com page load time and found that the first response time was 877 ms and then it took 42.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.
haofeng.tmall.com performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value11.4 s
0/100
25%
Value9.2 s
13/100
10%
Value110 ms
97/100
30%
Value0.002
100/100
15%
Value11.0 s
20/100
10%
877 ms
4226 ms
940 ms
1725 ms
10856 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Haofeng.tmall.com, 32% (34 requests) were made to G.alicdn.com and 29% (31 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (15.3 sec) relates to the external source Gskip.taobao.com.
Page size can be reduced by 444.8 kB (30%)
1.5 MB
1.0 MB
In fact, the total size of Haofeng.tmall.com main page is 1.5 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. 50% of websites need less resources to load. Images take 797.4 kB which makes up the majority of the site volume.
Potential reduce by 249.4 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 67.5 kB, which is 23% 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 249.4 kB or 84% of the original size.
Potential reduce by 4.3 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. Haofeng Tmall images are well optimized though.
Potential reduce by 113.6 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 113.6 kB or 40% of the original size.
Potential reduce by 77.5 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. Haofeng.tmall.com needs all CSS files to be minified and compressed as it can save up to 77.5 kB or 79% of the original size.
Number of requests can be reduced by 65 (73%)
89
24
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haofeng Tmall. 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 from 9 to 1 for CSS and as a result speed up the page load time.
haofeng.tmall.com
877 ms
haofeng.tmall.com
4226 ms
haofeng.world.tmall.com
940 ms
haofeng.world.tmall.com
1725 ms
jump
10856 ms
add
3468 ms
haofeng.world.tmall.com
443 ms
haofeng.world.tmall.com
433 ms
haofeng.world.tmall.com
430 ms
haofeng.world.tmall.com
1914 ms
global-min.css
173 ms
seed-min.js
220 ms
global-min.js
266 ms
g.alicdn.com
201 ms
g.alicdn.com
215 ms
brandbar-min.css
214 ms
copyright-min.css
257 ms
352 ms
g.alicdn.com
256 ms
index.js
255 ms
init-async-min.js
255 ms
TB2O.ThhXXXXXXUXXXXXXXXXXXX_!!755658911.jpg
722 ms
117 ms
49 ms
95 ms
s.gif
813 ms
aplus_v2.js
80 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
583 ms
getipinfo
834 ms
counter6
3283 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
723 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
610 ms
shopinfo-min.css
206 ms
xwj_heat.js
161 ms
agp_heat.min.js
187 ms
wp-beacon.js
866 ms
2.gif
6382 ms
146 ms
232 ms
230 ms
ahot.1.9
6719 ms
font_1451273740_187741.woff
861 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
425 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
418 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
682 ms
posttry.js
234 ms
246 ms
246 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
477 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
497 ms
blank
20 ms
191 ms
TB1nfYqKVXXXXbhXVXXSutbFXXX.jpg
445 ms
T1vEi4XnhyXXXm0Pva-454-340.png
188 ms
blank
57 ms
T1GjdOXA8XXXbHTkoN-122-235.png
373 ms
T156jcXXhfXXcMeXnl-22-160.gif
351 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
266 ms
223 ms
212 ms
220 ms
font_1433225452_0164654.woff
150 ms
processUserCookie.htm
15272 ms
webww.js
329 ms
index.js
329 ms
326 ms
TB1BPTnMXXXXXcSXFXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E7801723395ffc445ca1cb2d397bd7f93;lang%5Egbk;t%5E1460133444000
715 ms
TB2JtzahXXXXXaQXXXXXXXXXXXX_!!755658911.jpg
149 ms
vdata.htm
494 ms
TB2ap4ffVXXXXX7XpXXXXXXXXXX_!!755658911.gif
156 ms
TB257M8fFXXXXbOXpXXXXXXXXXX_!!755658911.gif
157 ms
TB2q_4afVXXXXaNXpXXXXXXXXXX_!!755658911.gif
282 ms
TB21YVufVXXXXazXXXXXXXXXXXX_!!755658911.gif
282 ms
TB2ixXBfVXXXXXbXXXXXXXXXXXX_!!755658911.gif
281 ms
TB2RfBjfVXXXXXfXpXXXXXXXXXX_!!755658911.gif
287 ms
TB2Q3FrfVXXXXa7XXXXXXXXXXXX_!!755658911.gif
284 ms
TB2nuE4fFXXXXcPXpXXXXXXXXXX_!!755658911.gif
284 ms
TB2ihw9fFXXXXbzXpXXXXXXXXXX_!!755658911.gif
283 ms
TB2yuBtfVXXXXaIXXXXXXXXXXXX_!!755658911.gif
285 ms
TB2Q9JbfVXXXXXNXpXXXXXXXXXX_!!755658911.gif
279 ms
TB24eZ6fFXXXXckXpXXXXXXXXXX_!!755658911.gif
314 ms
TB2QHpBfVXXXXXhXXXXXXXXXXXX_!!755658911.gif
316 ms
TB2w6dufVXXXXalXXXXXXXXXXXX_!!755658911.gif
314 ms
TB23xI_fFXXXXbpXpXXXXXXXXXX_!!755658911.gif
308 ms
TB2ButpfVXXXXbsXXXXXXXXXXXX_!!755658911.gif
307 ms
TB2c1A.fFXXXXa4XpXXXXXXXXXX_!!755658911.gif
323 ms
TB2yKNdfVXXXXabXpXXXXXXXXXX_!!755658911.gif
338 ms
TB2ItXAfVXXXXXuXXXXXXXXXXXX_!!755658911.gif
341 ms
TB2p7BufVXXXXarXXXXXXXXXXXX_!!755658911.gif
341 ms
TB20P8lfVXXXXcrXXXXXXXXXXXX_!!755658911.gif
338 ms
TB2lhFcfVXXXXamXpXXXXXXXXXX_!!755658911.gif
340 ms
TB2o_BjfVXXXXaOXpXXXXXXXXXX_!!755658911.gif
359 ms
TB2S3XcfVXXXXaMXpXXXXXXXXXX_!!755658911.jpg
483 ms
TB2uSJBfVXXXXXbXXXXXXXXXXXX_!!755658911.jpg
379 ms
localhost.wwbizsrv.alibaba.com
133 ms
muliuserstatus.aw
9730 ms
index.js
46 ms
index.js
41 ms
localhost.wwbizsrv.alibaba.com
3 ms
ww.69.2
462 ms
adapter.js
71 ms
ww.69.2
121 ms
app.gif
3307 ms
T1FXHXXahjXXXAK3zo-77-18.gif
30 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
30 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
355 ms
haofeng.tmall.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
haofeng.tmall.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
haofeng.tmall.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haofeng.tmall.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Haofeng.tmall.com main page’s claimed encoding is gbk. 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.
haofeng.tmall.com
Open Graph description is not detected on the main page of Haofeng Tmall. 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: