Tools & Wizards About Us
cnodejs.org screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

cnodejs.org

CNode：Node.js专业中文社区

Page Load Speed

4.2 sec in total

First Response

342 ms

Resources Loaded

3.7 sec

Page Rendered

179 ms

cnodejs.org screenshot

About Website

Visit cnodejs.org now to see the best up-to-date CNode Js content for China and also check out these interesting facts you probably never knew about cnodejs.org

CNode：Node.js专业中文社区

Visit cnodejs.org

Key Findings

We analyzed Cnodejs.org page load time and found that the first response time was 342 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

cnodejs.org performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

cnodejs.org

342 ms

cnodejs.org

909 ms

index.min.23a5b1ca.min.css

1014 ms

index.min.f7c13f64.min.js

1029 ms

FtG0YVgQ6iginiLpf9W4_ShjiLfU

1320 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Cnodejs.org, 44% (24 requests) were made to Avatars.githubusercontent.com and 20% (11 requests) were made to Gravatar.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Static.cnodejs.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.0 kB (24%)

Content Size

460.5 kB

After Optimization

350.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Cnodejs.org main page is 460.5 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. 40% of websites need less resources to load. Images take 260.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 39.9 kB

  • Original 47.4 kB
  • After minification 42.2 kB
  • After compression 7.5 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 5.2 kB, which is 11% 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 39.9 kB or 84% of the original size.

Image Optimization

-15%

Potential reduce by 38.2 kB

  • Original 260.4 kB
  • After minification 222.2 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, CNode Js needs image optimization as it can save up to 38.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-21%

Potential reduce by 32.0 kB

  • Original 152.7 kB
  • After minification 152.7 kB
  • After compression 120.8 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 32.0 kB or 21% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

53

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CNode Js. According to our analytics all requests are already optimized.

Network Requests Diagram

cnodejs.org

cnodejs.org

342 ms

cnodejs.org

cnodejs.org

909 ms

index.min.23a5b1ca.min.css

index.min.23a5b1ca.min.css

1014 ms

index.min.f7c13f64.min.js

index.min.f7c13f64.min.js

1029 ms

FtG0YVgQ6iginiLpf9W4_ShjiLfU

FtG0YVgQ6iginiLpf9W4_ShjiLfU

1320 ms

17956058

17956058

93 ms

0c548defc5ce885128ab3f161af106bb

0c548defc5ce885128ab3f161af106bb

209 ms

5692360

5692360

107 ms

16604995

16604995

104 ms

28948481

28948481

106 ms

d208089afa27a6ed03a54889d59d4ac7

d208089afa27a6ed03a54889d59d4ac7

201 ms

01a8eee6b922bea3bfee5bfc3771c094

01a8eee6b922bea3bfee5bfc3771c094

203 ms

0f2e156a68ef787beab9436eddddd73f

0f2e156a68ef787beab9436eddddd73f

198 ms

44e6e7335a26a7770ccb6138f22fbd83

44e6e7335a26a7770ccb6138f22fbd83

209 ms

33ee21f65770bcc4a41de11e9141c3c8

33ee21f65770bcc4a41de11e9141c3c8

203 ms

c88cab1441af543536b6bed02a22d9a8

c88cab1441af543536b6bed02a22d9a8

273 ms

f1cba3e4c55e637af5569aec55e3de41

f1cba3e4c55e637af5569aec55e3de41

274 ms

25ba4bf56fbb8c0c377ae2960d77f85d

25ba4bf56fbb8c0c377ae2960d77f85d

273 ms

24da742fd9638ecf9960be55a5ad584a

24da742fd9638ecf9960be55a5ad584a

274 ms

e5cd38a1c1ccbbf5271a5958a0ea792d

e5cd38a1c1ccbbf5271a5958a0ea792d

275 ms

8219031

8219031

92 ms

156269

156269

91 ms

23241972

23241972

94 ms

14976489

14976489

98 ms

24246985

24246985

101 ms

3118295

3118295

101 ms

734818

734818

106 ms

7269202

7269202

105 ms

62868950

62868950

106 ms

19259623

19259623

109 ms

30584594

30584594

105 ms

26357769

26357769

106 ms

46402151

46402151

115 ms

7334950

7334950

110 ms

16065346

16065346

111 ms

32998077

32998077

115 ms

16661897

16661897

114 ms

1061012

1061012

110 ms

33950951

33950951

116 ms

9712830

9712830

135 ms

5040078

5040078

134 ms

26410064

26410064

134 ms

13534626

13534626

136 ms

5820929

5820929

134 ms

cnodejs_light.svg

cnodejs_light.svg

1006 ms

search.e53b380a.hashed.png

search.e53b380a.hashed.png

104 ms

ruby-china-20150529.png

ruby-china-20150529.png

1072 ms

golangtc-logo.png

golangtc-logo.png

1111 ms

phphub-logo.png

phphub-logo.png

106 ms

digitalocean.png

digitalocean.png

135 ms

qiniu.png

qiniu.png

135 ms

analytics.js

analytics.js

73 ms

collect

collect

16 ms

collect

collect

30 ms

js

js

62 ms

Accessibility Review

cnodejs.org accessibility score

55

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.

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

cnodejs.org 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

cnodejs.org SEO score

84

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

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

    N/A

  • Encoding

    UTF-8

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

cnodejs.org

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