Tools & Wizards About Us
fenby.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fenby.com

备案

Page Load Speed

26 sec in total

First Response

707 ms

Resources Loaded

25.2 sec

Page Rendered

142 ms

fenby.com screenshot

About Website

Click here to check amazing Fenby content for China. Otherwise, check out these important facts you probably never knew about fenby.com

腾讯云域名注册, 腾讯云旗下品牌。腾讯云域名注册是中国领先的域名注册服务提供商, 并提供云主机、网站建设等网络服务。

Visit fenby.com

Key Findings

We analyzed Fenby.com page load time and found that the first response time was 707 ms and then it took 25.3 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 8 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

fenby.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

fenby.com

707 ms

www.fenby.com

2790 ms

font-awesome.min.css

223 ms

codemirror.css

438 ms

blackboard.css

439 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 77% of them (51 requests) were addressed to the original Fenby.com, 12% (8 requests) were made to Media.fenby.com and 5% (3 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Media.fenby.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (65%)

Content Size

1.8 MB

After Optimization

614.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fenby.com main page is 1.8 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. 40% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 65.3 kB

  • Original 75.6 kB
  • After minification 55.7 kB
  • After compression 10.3 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 19.8 kB, which is 26% 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 65.3 kB or 86% of the original size.

Image Optimization

-41%

Potential reduce by 180.1 kB

  • Original 439.8 kB
  • After minification 259.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, Fenby needs image optimization as it can save up to 180.1 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 711.4 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 291.9 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 711.4 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 207.9 kB

  • Original 260.9 kB
  • After minification 254.2 kB
  • After compression 53.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. Fenby.com needs all CSS files to be minified and compressed as it can save up to 207.9 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

49

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fenby. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fenby.com

fenby.com

707 ms

www.fenby.com

www.fenby.com

2790 ms

font-awesome.min.css

font-awesome.min.css

223 ms

codemirror.css

codemirror.css

438 ms

blackboard.css

blackboard.css

439 ms

select.min.css

select.min.css

451 ms

angular-ui-tree.min.css

angular-ui-tree.min.css

452 ms

ng-img-crop.css

ng-img-crop.css

444 ms

xeditable.css

xeditable.css

484 ms

fenby3_base.css

fenby3_base.css

1347 ms

masterslider.css

masterslider.css

658 ms

style.css

style.css

667 ms

homeslider_style.css

homeslider_style.css

668 ms

fenby3.min.js

fenby3.min.js

4956 ms

stats

stats

285 ms

masterslider.min.js

masterslider.min.js

1435 ms

hm.js

hm.js

426 ms

logo.jpeg

logo.jpeg

20308 ms

fenby_logo_1.png

fenby_logo_1.png

212 ms

blank.gif

blank.gif

221 ms

The_Django_Book_8VptcGN.jpg

The_Django_Book_8VptcGN.jpg

20308 ms

logo.png

logo.png

20308 ms

logo_0TwMPgU.jpg

logo_0TwMPgU.jpg

20308 ms

logo_zKWV2J6.jpg

logo_zKWV2J6.jpg

20307 ms

logo.jpg

logo.jpg

20308 ms

default_avatar.jpeg

default_avatar.jpeg

20308 ms

UVHlm77niYcyMDIxMTEyNDA5MDgzOQ.jpg

UVHlm77niYcyMDIxMTEyNDA5MDgzOQ.jpg

20309 ms

js

js

1395 ms

hm.js

hm.js

1106 ms

220 ms

blank.gif

blank.gif

242 ms

magnifier-icon.png

magnifier-icon.png

269 ms

ping

ping

595 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

656 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

426 ms

hm.gif

hm.gif

292 ms

loading-2.gif

loading-2.gif

207 ms

217 ms

bg.jpg

bg.jpg

481 ms

ico-1.png

ico-1.png

220 ms

ico-6.png

ico-6.png

216 ms

ico-8.png

ico-8.png

206 ms

ico-14.png

ico-14.png

326 ms

ico-15.png

ico-15.png

377 ms

ico-16.png

ico-16.png

412 ms

ipad.png

ipad.png

658 ms

ipad-screen-bg.jpg

ipad-screen-bg.jpg

673 ms

logo-trans-stroke.png

logo-trans-stroke.png

539 ms

ico-2.png

ico-2.png

598 ms

ico-3.png

ico-3.png

629 ms

ico-5.png

ico-5.png

726 ms

ico-7.png

ico-7.png

752 ms

ico-9.png

ico-9.png

815 ms

ico-10.png

ico-10.png

835 ms

ico-11.png

ico-11.png

869 ms

ico-12.png

ico-12.png

886 ms

ico-13.png

ico-13.png

958 ms

logo-white-stroke.png

logo-white-stroke.png

956 ms

logo.gif

logo.gif

1019 ms

hand.png

hand.png

1248 ms

light-skin-1.png

light-skin-1.png

1071 ms

bg.jpg

bg.jpg

214 ms

paperPlane.png

paperPlane.png

415 ms

bg.jpg

bg.jpg

211 ms

video-shadow.png

video-shadow.png

205 ms

video-cover.jpg

video-cover.jpg

691 ms

Accessibility Review

fenby.com accessibility score

70

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fenby.com 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 Fenby.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

fenby.com

Open Graph description is not detected on the main page of Fenby. 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: