Tools & Wizards About Us

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

eeff.net

服装设计-服装行业学习交流平台 - 穿针引线网

Page Load Speed

6.1 sec in total

First Response

670 ms

Resources Loaded

4.9 sec

Page Rendered

441 ms

About Website

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.net

Key Findings

We 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.

Performance Metrics

eeff.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value21.0 s

0/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.137

79/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

eeff.net

670 ms

www.eeff.net

1369 ms

style_9_common.css

222 ms

common.js

440 ms

jquery.min.js

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 Optimization Overview & Recommendations

Page size can be reduced by 120.5 kB (16%)

Content Size

774.1 kB

After Optimization

653.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-83%

Potential reduce by 71.8 kB

  • Original 86.2 kB
  • After minification 67.4 kB
  • After compression 14.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 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.

Image Optimization

-8%

Potential reduce by 45.0 kB

  • Original 590.7 kB
  • After minification 545.7 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.

JavaScript Optimization

-4%

Potential reduce by 2.6 kB

  • Original 63.1 kB
  • After minification 63.1 kB
  • After compression 60.5 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.

CSS Optimization

-3%

Potential reduce by 1.1 kB

  • Original 34.1 kB
  • After minification 34.1 kB
  • After compression 33.0 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.

Requests Breakdown

Number of requests can be reduced by 14 (23%)

Requests Now

61

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

eeff.net accessibility score

58

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

eeff.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

eeff.net SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    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.

Social Sharing Optimization

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: