17.7 sec in total
1.3 sec
15.4 sec
952 ms
Visit feng.com now to see the best up-to-date Feng content for China and also check out these interesting facts you probably never knew about feng.com
域名是企业重要的资产,您所访问的域名已经过期,请尽快联络注册商续费
Visit feng.comWe analyzed Feng.com page load time and found that the first response time was 1.3 sec and then it took 16.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
feng.com performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value12.8 s
0/100
25%
Value18.0 s
0/100
10%
Value460 ms
61/100
30%
Value0.032
100/100
15%
Value11.8 s
17/100
10%
1288 ms
1483 ms
33 ms
47 ms
24 ms
Our browser made a total of 182 requests to load all elements on the main page. We found that 22% of them (40 requests) were addressed to the original Feng.com, 16% (30 requests) were made to Face.weiphone.net and 16% (29 requests) were made to Game.feng.com. The less responsive or slowest element that took the longest time to load (12.6 sec) relates to the external source Img.weiphone.net.
Page size can be reduced by 603.1 kB (16%)
3.7 MB
3.1 MB
In fact, the total size of Feng.com main page is 3.7 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. 55% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 104.0 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 17.5 kB, which is 13% 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 104.0 kB or 77% of the original size.
Potential reduce by 292.1 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. Feng images are well optimized though.
Potential reduce by 114.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 114.1 kB or 68% of the original size.
Potential reduce by 92.8 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. Feng.com needs all CSS files to be minified and compressed as it can save up to 92.8 kB or 85% of the original size.
Number of requests can be reduced by 13 (8%)
156
143
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Feng. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
feng.com
1288 ms
www.feng.com
1483 ms
common.css
33 ms
jquery-1.7.min.js
47 ms
common.js
24 ms
feng_index.css
37 ms
index.js
18 ms
jquery.autocomplete.min.ajax.js
37 ms
jquery.marquee.min.js
37 ms
topBarNav.js
37 ms
c.php
992 ms
dataList.js
9 ms
x.js
3862 ms
topbar.js
448 ms
img201602271817590.jpg
5998 ms
30_avatar_small.jpg
1404 ms
tutuicon2015.png
3125 ms
b2c9a784img201602290940260_306__220.jpg
8260 ms
1381297.175x175-75.png
3842 ms
mzl.cover.175x175-75.jpg
1372 ms
234749oj6bhcfiicii7j7e.jpg
8420 ms
28_avatar_middle.jpg
1902 ms
global_topbar.png
31 ms
topbar_tel.png
30 ms
fengCode.jpg
31 ms
navIcon.png
267 ms
tutuicon.png
225 ms
place.png
495 ms
prev_btn.png
32 ms
next_btn.png
30 ms
feng_client.jpg
31 ms
er_code_img.png
257 ms
feng_client_qr.jpg
32 ms
fengbuy_client.jpg
41 ms
fengbuy_client_qr.jpg
847 ms
saomadang_client.jpg
465 ms
saomadang_client_qr.jpg
509 ms
wp_client.jpg
273 ms
wp_client_qr.jpg
761 ms
dot_icon.jpg
421 ms
index_ico.png
430 ms
img201602291738220_330__418.jpg
868 ms
small_start.png
1244 ms
li_style_icon.jpg
713 ms
goTopBtn.png
516 ms
footer.png
531 ms
weiwei.png
546 ms
picp_bg.png
555 ms
48_avatar_middle.jpg
1896 ms
71_avatar_middle.jpg
2171 ms
72_avatar_middle.jpg
1893 ms
51_avatar_middle.jpg
1893 ms
71_avatar_middle.jpg
1896 ms
72_avatar_middle.jpg
1897 ms
13_avatar_middle.jpg
1898 ms
51_avatar_middle.jpg
1899 ms
59_avatar_middle.jpg
2145 ms
04_avatar_middle.jpg
2149 ms
64_avatar_middle.jpg
1903 ms
mzl.cover.175x175-75.jpg
3525 ms
mzl.cover.175x175-75.jpg
3531 ms
mzl.cover.175x175-75.jpg
3538 ms
mzl.cover.175x175-75.jpg
3837 ms
mzl.upsoviow.175x175-75.png
3848 ms
mzl.cover.175x175-75.jpg
3819 ms
mzl.cover.175x175-75.jpg
3826 ms
mzl.cover.175x175-75.jpg
3839 ms
mzl.cover.175x175-75.jpg
4106 ms
mzl.cover.175x175-75.jpg
4114 ms
mzl.cover.175x175-75.jpg
4123 ms
mzl.cover.175x175-75.jpg
4139 ms
mzl.cover.175x175-75.jpg
4141 ms
mzl.cover.175x175-75.jpg
4151 ms
mzl.cover.175x175-75.jpg
4400 ms
mzl.cover.175x175-75.jpg
4406 ms
mzl.cover.175x175-75.jpg
4417 ms
mzl.cover.175x175-75.png
4741 ms
mzl.cover.175x175-75.jpg
4441 ms
mzl.cover.175x175-75.jpg
4754 ms
mzl.cover.175x175-75.jpg
4691 ms
mzl.cover.175x175-75.jpg
4699 ms
mzl.cover.175x175-75.png
4713 ms
article_93008_640x320.jpg
5643 ms
article_93007_640x320.jpg
6338 ms
article_93006_640x320.jpg
5285 ms
article_93005_640x320.jpg
5752 ms
article_93004_640x320.jpg
5943 ms
0d4402bcimg201602291134440_308__219.png
8959 ms
7d92bafeimg201602221022490_66__66.png
7115 ms
b3306514img201602221017300_66__66.jpeg
7476 ms
06d53e5fimg201602221013580_66__66.jpeg
7561 ms
91e2791aimg201602221010090_66__66.png
7588 ms
c3802471img201602221005080_66__66.jpeg
7883 ms
94d9fc7aimg201602220959080_66__66.png
7947 ms
5b25fc25img201601181533220_66__66.jpeg
8033 ms
dce5a4feimg201601111044520_66__66.png
8061 ms
74f57c32img201603011010160_499__246.png
8975 ms
1c21bc66img201603011050300_249__246.jpg
8417 ms
fa699c76img201603011043330_248__246.jpg
12554 ms
1977c262img201603010011280_248__246.jpg
9452 ms
fe97d7baimg201602292354370_249__246.jpg
10079 ms
5577fe19img201602292344520_499__246.jpg
9828 ms
mzl.cover.175x175-75.jpg
2633 ms
mzl.cover.175x175-75.jpg
1751 ms
1839443.175x175-75.jpg
4542 ms
1677883.175x175-75.jpg
5279 ms
mzl.cover.175x175-75.jpg
2034 ms
1229185.175x175-75.png
5925 ms
mzl.cover.175x175-75.jpg
2113 ms
1378450.175x175-75.jpg
2727 ms
mzl.cover.175x175-75.jpg
3818 ms
mzl.cover.175x175-75.jpg
6549 ms
1819054.175x175-75.png
7188 ms
104859xekno3u3nwowkew0.png
8429 ms
181806wls199b1lclv3bw3.jpg
8409 ms
110021yq84s70nh7nz8u8l.jpg
8379 ms
090901vwtw4zaawzww1evr.png
8419 ms
143507y11sumrk1sktaa4u.jpg
8418 ms
182052ugbxht44bf8ggtbt.png
8423 ms
141049narchpriauapfk1r.jpg
8407 ms
49_avatar_small.jpg
1436 ms
99_avatar_small.jpg
1470 ms
64_avatar_small.jpg
1345 ms
25_avatar_small.jpg
1822 ms
55_avatar_small.jpg
1926 ms
15_avatar_small.jpg
2006 ms
61_avatar_small.jpg
2076 ms
49_avatar_small.jpg
2338 ms
98_avatar_small.jpg
2295 ms
21_avatar_small.jpg
2430 ms
69_avatar_small.jpg
2495 ms
54_avatar_small.jpg
2571 ms
75_avatar_small.jpg
2668 ms
76_avatar_small.jpg
2741 ms
45_avatar_small.jpg
2879 ms
90_avatar_small.jpg
2963 ms
64_avatar_small.jpg
3024 ms
2616013813.png
3077 ms
img201602270916020.jpg
5863 ms
img201602282256400.jpg
5157 ms
img201602251127510.jpg
5400 ms
img201602200851380.jpg
6302 ms
img201602181936560.jpg
5611 ms
newsheader.php
6807 ms
stat.htm
245 ms
core.php
740 ms
push.js
609 ms
64_avatar_small.jpg
545 ms
30_avatar_small.jpg
874 ms
49_avatar_small.jpg
769 ms
99_avatar_small.jpg
429 ms
25_avatar_small.jpg
84 ms
55_avatar_small.jpg
10 ms
15_avatar_small.jpg
325 ms
61_avatar_small.jpg
63 ms
noavatar_middle.gif
3043 ms
noavatar_middle.gif
4672 ms
noavatar_middle.gif
1438 ms
noavatar_small.gif
1207 ms
noavatar_small.gif
1212 ms
98_avatar_small.jpg
10 ms
noavatar_small.gif
1524 ms
49_avatar_small.jpg
11 ms
21_avatar_small.jpg
9 ms
69_avatar_small.jpg
11 ms
54_avatar_small.jpg
10 ms
75_avatar_small.jpg
24 ms
76_avatar_small.jpg
11 ms
45_avatar_small.jpg
10 ms
90_avatar_small.jpg
10 ms
64_avatar_small.jpg
9 ms
js.php
482 ms
560a0b6b83143.png
615 ms
5689d04a56fe6.jpg
608 ms
5639665ae02c7.jpg
1227 ms
5689cc2db5671.jpg
1215 ms
56c5303d047a2.jpg
1600 ms
56d412eb47908.jpg
1017 ms
jquery.FadeList.js
261 ms
56d501bc44ade1456800188.jpg
2921 ms
log.php
555 ms
opticy_40.png
377 ms
feng.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
feng.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
feng.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feng.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 Feng.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.
feng.com
Open Graph description is not detected on the main page of Feng. 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: