53.2 sec in total
1.6 sec
51.1 sec
410 ms
Welcome to fevte.com homepage info - get ready to check FEVTE best content for China right away, or after learning these important things about fevte.com
飞特网成立于2007年,深耕设计/创意领域13年.全力助力设计师创意变现、知识变现。为设计师/创意人提供一个安全、便捷的设计师接单平台。为企业和创业者提供一个专业、高效、靠谱的设计业务外包平台暨网络设计超市。
Visit fevte.comWe analyzed Fevte.com page load time and found that the first response time was 1.6 sec and then it took 51.5 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 32 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fevte.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value16.0 s
0/100
25%
Value11.5 s
5/100
10%
Value10 ms
100/100
30%
Value0.109
87/100
15%
Value18.2 s
3/100
10%
1635 ms
11749 ms
10960 ms
5947 ms
2859 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 55% of them (75 requests) were addressed to the original Fevte.com, 22% (30 requests) were made to Uc.fevte.com and 7% (10 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Fevte.com.
Page size can be reduced by 340.0 kB (36%)
937.2 kB
597.2 kB
In fact, the total size of Fevte.com main page is 937.2 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. Images take 462.1 kB which makes up the majority of the site volume.
Potential reduce by 72.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 72.7 kB or 78% of the original size.
Potential reduce by 48.6 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, FEVTE needs image optimization as it can save up to 48.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 214.3 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 214.3 kB or 57% of the original size.
Potential reduce by 4.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. Fevte.com needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 65% of the original size.
Number of requests can be reduced by 36 (36%)
101
65
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEVTE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fevte.com
1635 ms
www.fevte.com
11749 ms
style_1_common.css
10960 ms
common.js
5947 ms
portal.js
2859 ms
logging.js
1462 ms
cmp.js
767 ms
ftty.css
18496 ms
siye.js
2173 ms
c.js
1031 ms
ping.js
681 ms
stat.php
958 ms
discuz_tips.js
661 ms
qq_login.gif
707 ms
wxm.gif
4042 ms
logo.png
1145 ms
wb.gif
584 ms
wx.gif
1137 ms
162704cr33p7fsss3m7f3e.png
19807 ms
old.jpg
16908 ms
4df948aaef1646396af1052fe9816b9a.jpg
14208 ms
0f764464a6fd4079391b44bb052554c5.jpg
17634 ms
22cc953eddd08c313ee0c41b10be1031.jpg
19807 ms
29c31f198fcae6db3ae7e27029062963.jpg
19808 ms
8ec927bd1a2bc6fb70aa815787d7010b.jpg
19808 ms
2bbd388938d22aad6b1158fafaa76f76.jpg
19810 ms
1841ef709f5b4cc750d042ba592569d0.jpg
19810 ms
f95fface0428cdfaaff86643a0ed39be.jpg
19811 ms
d5938d5ca9b8e3d05d65eb1d875871ea.jpg
19811 ms
f7e1e4438b8558895b519104c7f55704.jpg
19812 ms
bf8e63d1e3131003d888865284f7848f.jpg
19812 ms
d909ca1ce0e5b15748b1367b942e8093.jpg
19813 ms
a9136d206c9ad609684f7759ccf6406e.jpg
19814 ms
f2bb68407cb8ee03bb00d30d6a553f06.jpg
19815 ms
da86b422dcbb1f668ca10366d40855ae.jpg
19815 ms
18ccd1573349a77af6d84faace6a6466.jpg
19815 ms
ff0bdfb928927c8fe6e6f8b119d6aded.jpg
19816 ms
580c6c3d60bd44196edd499ffd73561b.jpg
19817 ms
04363c4b75731ffbe57f72485a0eaf3f.jpg
19817 ms
6c97537482435a65896febf0b996e43a.jpg
19818 ms
9383939dee261a54db7f7f444aaa3ec8.jpg
19819 ms
show.png
19819 ms
e3eb6d2f9a29556c7a6d5d7a4d34ed22.jpg
19819 ms
67b80f2e6e60fb8db89fd0522e5349af.jpg
19820 ms
185015t3qtu53cqagccdla.gif
19821 ms
c72c298b808bfd9e312a3cc6365c6ba4.jpg
19820 ms
4e9b5bcd36c1d75a5bc97c9a19de16af.jpg
19821 ms
avatar.php
19817 ms
2b23e2d0ef64a29a7497424cb195f897.jpg
19804 ms
followbutton.php
885 ms
135911fcefsu5frasf7xai.gif
20223 ms
125442o2hq8a6uqgi7ui6n.gif
20102 ms
followButton.css
17 ms
sso.js
15 ms
followButton.js
11 ms
suda.js
14 ms
b.gif
1114 ms
bg_flbtn.png
16 ms
335ee18ec5824b1ceb0438b9a09b694c.jpg
19671 ms
092858c0fy9xp8nxrke8mb.gif
19663 ms
62_avatar_small.jpg
10201 ms
75_avatar_small.jpg
10333 ms
95_avatar_small.jpg
14009 ms
09_avatar_small.jpg
10965 ms
84_avatar_small.jpg
11300 ms
97_avatar_small.jpg
14457 ms
61_avatar_small.jpg
10411 ms
8c2f0155d80118baa5d0273750b03021.jpg
19319 ms
05_avatar_small.jpg
8008 ms
27_avatar_small.jpg
8124 ms
08_avatar_small.jpg
7569 ms
88_avatar_small.jpg
7658 ms
noavatar_small.gif
7826 ms
21_avatar_small.jpg
8365 ms
95_avatar_small.jpg
7330 ms
08_avatar_small.jpg
10541 ms
12_avatar_small.jpg
10747 ms
noavatar_small.gif
8001 ms
24_avatar_small.jpg
11275 ms
17_avatar_small.jpg
7591 ms
noavatar_small.gif
7670 ms
33_avatar_small.jpg
11716 ms
213126caa2cc5qmmgf5g2p.png
17506 ms
87_avatar_small.jpg
11538 ms
ocsm
1132 ms
MTc4OTkxOA==.js
323 ms
stat.htm
651 ms
core.php
790 ms
ping_hotclick.js
325 ms
04_avatar_small.jpg
11966 ms
pic.gif
763 ms
share.js
844 ms
59_avatar_small.jpg
12775 ms
94_avatar_small.jpg
10067 ms
89_avatar_small.jpg
10736 ms
share_api.js
269 ms
share_view.js
540 ms
tangram.js
1360 ms
api_base.js
544 ms
noavatar_small.gif
9966 ms
view_base.js
276 ms
58_avatar_small.jpg
13220 ms
partners.js
274 ms
share_style1_24.css
267 ms
27_avatar_small.jpg
9083 ms
icons_1_24.png
1063 ms
logger.js
267 ms
7d12417a03bdf389915208717b903c1b.jpg
10797 ms
3662aa676815de52a8d6eb0f4e1b50ec.jpg
9469 ms
d7781c75fac3e98bc3d782d64f99df9f.jpg
15011 ms
eec5a930835897778bfe123ad90c9623.jpg
6706 ms
421deca6b58db790c221594fa96d24f4.jpg
8989 ms
057faf331d09e65a88f911644e19cbd9.jpg
9754 ms
new.gif
7254 ms
share_qq.png
7183 ms
share_sina.png
7411 ms
qun.png
9063 ms
my.png
10761 ms
hd.png
8097 ms
search.png
10867 ms
arrwd1.gif
9675 ms
ss.gif
11216 ms
cdbg.png
10338 ms
loading.gif
10418 ms
fttitle.png
11047 ms
fevtebg.png
14550 ms
btsx.png
11424 ms
1.gif
12191 ms
frame_bg.png
11709 ms
ftdbbg.gif
11685 ms
dbtm.png
13461 ms
scrollimg_tigger_on.png
12161 ms
o.htm
910 ms
wh.js
767 ms
ac.js
545 ms
fp.htm
527 ms
fevte.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
fevte.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fevte.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fevte.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 Fevte.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.
fevte.com
Open Graph description is not detected on the main page of FEVTE. 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: