Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

fevte.com

飞特网-设计超市-专业设计师接单平台 - 飞特(FEVTE)

Page Load Speed

53.2 sec in total

First Response

1.6 sec

Resources Loaded

51.1 sec

Page Rendered

410 ms

fevte.com screenshot

About Website

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

Key Findings

We 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 a poor result, as 95% 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.

Performance Metrics

fevte.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.109

87/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

fevte.com

1635 ms

www.fevte.com

11749 ms

style_1_common.css

10960 ms

common.js

5947 ms

portal.js

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

Page size can be reduced by 340.0 kB (36%)

Content Size

937.2 kB

After Optimization

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.

HTML Optimization

-78%

Potential reduce by 72.7 kB

  • Original 93.3 kB
  • After minification 92.4 kB
  • After compression 20.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.

Image Optimization

-11%

Potential reduce by 48.6 kB

  • Original 462.1 kB
  • After minification 413.5 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.

JavaScript Optimization

-57%

Potential reduce by 214.3 kB

  • Original 374.9 kB
  • After minification 349.1 kB
  • After compression 160.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 214.3 kB or 57% of the original size.

CSS Optimization

-65%

Potential reduce by 4.4 kB

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 2.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.

Requests Breakdown

Number of requests can be reduced by 36 (36%)

Requests Now

101

After Optimization

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.

Accessibility Review

fevte.com accessibility score

56

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[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

High

<html> element does not have a [lang] attribute

Best Practices

fevte.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fevte.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: