Tools & Wizards About Us
segmentfault.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

segmentfault.com

SegmentFault 思否

Page Load Speed

8 sec in total

First Response

1.5 sec

Resources Loaded

5.9 sec

Page Rendered

578 ms

segmentfault.com screenshot

About Website

Visit segmentfault.com now to see the best up-to-date Segment Fault content for China and also check out these interesting facts you probably never knew about segmentfault.com

SegmentFault 思否是中国专业的开发者技术社区。我们以技术问答、技术博客、技术课程、技术资讯为核心的产品形态，为开发者提供纯粹、高质的技术交流平台。

Visit segmentfault.com

Key Findings

We analyzed Segmentfault.com page load time and found that the first response time was 1.5 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

segmentfault.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

segmentfault.com

1527 ms

global.css

84 ms

qa_all.css

80 ms

responsive.css

78 ms

debug.js

75 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Segmentfault.com, 51% (19 requests) were made to Dfnjy7g2qaazm.cloudfront.net and 35% (13 requests) were made to Sfault-avatar.b0.upaiyun.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 556.7 kB (70%)

Content Size

794.3 kB

After Optimization

237.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Segmentfault.com main page is 794.3 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. 30% of websites need less resources to load. Javascripts take 322.9 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 139.5 kB

  • Original 156.6 kB
  • After minification 107.0 kB
  • After compression 17.0 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 49.6 kB, which is 32% 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 139.5 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 331 B

  • Original 56.3 kB
  • After minification 56.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. Segment Fault images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 206.4 kB

  • Original 322.9 kB
  • After minification 322.0 kB
  • After compression 116.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 206.4 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 210.4 kB

  • Original 258.6 kB
  • After minification 257.6 kB
  • After compression 48.2 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. Segmentfault.com needs all CSS files to be minified and compressed as it can save up to 210.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (39%)

Requests Now

33

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Segment Fault. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

segmentfault.com

segmentfault.com

1527 ms

global.css

global.css

84 ms

qa_all.css

qa_all.css

80 ms

responsive.css

responsive.css

78 ms

debug.js

debug.js

75 ms

dropzone.css

dropzone.css

17 ms

codemirror.css

codemirror.css

18 ms

eclipse.css

eclipse.css

16 ms

solarized_light.css

solarized_light.css

16 ms

font-awesome.min.css

font-awesome.min.css

17 ms

jquery.atwho.css

jquery.atwho.css

16 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

17 ms

logo-b.svg

logo-b.svg

8 ms

icon-sn.svg

icon-sn.svg

16 ms

2420922714-56cecb24dfffc_big64

2420922714-56cecb24dfffc_big64

2386 ms

2121827898-1030000000596906_big64

2121827898-1030000000596906_big64

2382 ms

2387875497-56b5b8b2569be_big64

2387875497-56b5b8b2569be_big64

2395 ms

1818709072-556c566198be9_big64

1818709072-556c566198be9_big64

2387 ms

1630517265-56c57691721f6_big64

1630517265-56c57691721f6_big64

2397 ms

user-64.png

user-64.png

11 ms

3550384662-5491731491fc7_big64

3550384662-5491731491fc7_big64

2386 ms

3602242875-56cf0d5105a69_big64

3602242875-56cf0d5105a69_big64

2383 ms

3046988269-5644b84c17ed3_big64

3046988269-5644b84c17ed3_big64

2628 ms

883658877-54281918d345b_big64

883658877-54281918d345b_big64

2610 ms

3401963472-56cd3725670bd_big64

3401963472-56cd3725670bd_big64

2392 ms

1188800450-54c0d1512f59a_big64

1188800450-54c0d1512f59a_big64

2631 ms

2907608864-54ba085f192cc_big64

2907608864-54ba085f192cc_big64

2393 ms

3054230534-561d20a868d2e_big64

3054230534-561d20a868d2e_big64

2396 ms

appQrcode.png

appQrcode.png

93 ms

assets.js

assets.js

70 ms

index.js

index.js

81 ms

analytics.js

analytics.js

67 ms

hm.js

hm.js

3607 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

48 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

47 ms

collect

collect

13 ms

collect

collect

57 ms

Accessibility Review

segmentfault.com accessibility score

70

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-*] attributes do not match their roles

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

segmentfault.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

segmentfault.com SEO score

100

Search Engine Optimization Advices

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

segmentfault.com

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