6.1 sec in total
670 ms
4.9 sec
441 ms
Click here to check amazing Eeff content for China. Otherwise, check out these important facts you probably never knew about eeff.net
穿针引线网站自2001年开始定位为服装设计、服装行业用户学习交流论坛。用户以男装设计、女装设计、童装设计、时装设计师、服装制版、服装打版、服饰搭配、立体裁剪、时尚买手、婚纱设计师、服装陈列、服装设计大赛参与者等服装从业人员为主。
Visit eeff.netWe analyzed Eeff.net page load time and found that the first response time was 670 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eeff.net performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value10.7 s
0/100
25%
Value21.0 s
0/100
10%
Value110 ms
98/100
30%
Value0.137
79/100
15%
Value9.4 s
31/100
10%
670 ms
1369 ms
222 ms
440 ms
863 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 34% of them (22 requests) were addressed to the original Eeff.net, 39% (25 requests) were made to Pic.eeff.net and 16% (10 requests) were made to Vip.eeff.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Image.eeff.net.
Page size can be reduced by 120.5 kB (16%)
774.1 kB
653.6 kB
In fact, the total size of Eeff.net main page is 774.1 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. 50% of websites need less resources to load. Images take 590.7 kB which makes up the majority of the site volume.
Potential reduce by 71.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 18.7 kB, which is 22% 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 71.8 kB or 83% of the original size.
Potential reduce by 45.0 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. Eeff images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.1 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. Eeff.net has all CSS files already compressed.
Number of requests can be reduced by 14 (23%)
61
47
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eeff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eeff.net
670 ms
www.eeff.net
1369 ms
style_9_common.css
222 ms
common.js
440 ms
jquery.min.js
863 ms
portal.js
655 ms
common.js
659 ms
style.css
655 ms
calendar.js
663 ms
swiper.min.css
275 ms
portal_index.css
664 ms
swiper.min.js
283 ms
portal_index.js
894 ms
jquery.lazyload.min.js
290 ms
footer.js
893 ms
ajax.js
456 ms
50x50
980 ms
79_avatar_small.jpg
679 ms
side_wxkf.png
1721 ms
style_9_common.css
223 ms
logo_white.svg
220 ms
hot.gif
225 ms
lazyload.png
224 ms
logo.png
223 ms
beian.png
456 ms
code01.jpg
440 ms
qi_niu_1598955615061_37_438_44.png
2029 ms
89_avatar_small.jpg
676 ms
74_avatar_small.jpg
677 ms
49_avatar_small.jpg
679 ms
76_avatar_small.jpg
682 ms
32_avatar_small.jpg
684 ms
17_avatar_middle.jpg
892 ms
38_avatar_middle.jpg
892 ms
75_avatar_middle.jpg
892 ms
30_avatar_middle.jpg
896 ms
359269_115903uql95es588.jpg
1160 ms
50x50
1171 ms
359269_103516y197zs971o.jpg
1374 ms
50x50
1610 ms
359269_151916aofkkp5s5o.png
1458 ms
359269_130145mv7fqmmqf0.jpg
1301 ms
359269_174526elt2lum16e.jpg
984 ms
11259_112049v8ydm14dir.jpg
1228 ms
11259_112936z43kmlz3e3.jpg
1302 ms
11259_172908qdv1fw2v58.jpg
1342 ms
2263175.jpg
1117 ms
2261014.jpg
1118 ms
2259051.jpg
1120 ms
2258661.jpg
1191 ms
2258621.jpg
1187 ms
2258488.jpg
1249 ms
2258422.jpg
1275 ms
2258240.jpg
1267 ms
11259_110437dkngjmkenl.png
1291 ms
11259_110501jczhbnvaja.png
1355 ms
359269_131401fvxst9t7rv.jpg
1304 ms
359269_132145bnnu7w99zp.jpg
1261 ms
359269_190255qn1ei28isv.jpg
1420 ms
app.png
1348 ms
iconfont.woff
306 ms
hm.js
954 ms
js_client_ol
260 ms
hm.gif
297 ms
eeff.net 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
eeff.net 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
eeff.net SEO score
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
Tap targets are not sized appropriately
ZH
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eeff.net 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 Eeff.net 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.
eeff.net
Open Graph description is not detected on the main page of Eeff. 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: