Tools & Wizards About Us
thinkjs.org screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

thinkjs.org

ThinkJS - 使用 ES6/7 特性开发 Node.js 项目，支持 TypeScript

Page Load Speed

30.7 sec in total

First Response

1.3 sec

Resources Loaded

28.7 sec

Page Rendered

628 ms

thinkjs.org screenshot

About Website

Welcome to thinkjs.org homepage info - get ready to check ThinkJS best content for China right away, or after learning these important things about thinkjs.org

ThinkJS 是一款可以使用 ES6/7 特性开发项目的 Node.js 框架，使用 async/await 或者 */yield 彻底解决异步回调的问题。同时支持 TypeScript。

Visit thinkjs.org

Key Findings

We analyzed Thinkjs.org page load time and found that the first response time was 1.3 sec and then it took 29.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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

thinkjs.org performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

thinkjs.org

1340 ms

thinkjs.org

7013 ms

t011ecfe4c0d20c9816.jpg

19521 ms

t0119a49f86068b0dae.jpg

11349 ms

t01f8a5c470a4af951f.png

4330 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 50% of them (6 requests) were addressed to the original Thinkjs.org, 50% (6 requests) were made to P.ssl.qhimg.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source P.ssl.qhimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.9 kB (47%)

Content Size

65.3 kB

After Optimization

34.4 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Thinkjs.org main page is 65.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. Only 10% of websites need less resources to load. CSS take 36.0 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 5.9 kB

  • Original 8.9 kB
  • After minification 8.7 kB
  • After compression 3.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. 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 5.9 kB or 66% of the original size.

Image Optimization

-12%

Potential reduce by 2.5 kB

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

CSS Optimization

-62%

Potential reduce by 22.4 kB

  • Original 36.0 kB
  • After minification 36.0 kB
  • After compression 13.6 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. Thinkjs.org needs all CSS files to be minified and compressed as it can save up to 22.4 kB or 62% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

  • Images

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

Network Requests Diagram

thinkjs.org

thinkjs.org

1340 ms

thinkjs.org

thinkjs.org

7013 ms

t011ecfe4c0d20c9816.jpg

t011ecfe4c0d20c9816.jpg

19521 ms

t0119a49f86068b0dae.jpg

t0119a49f86068b0dae.jpg

11349 ms

t01f8a5c470a4af951f.png

t01f8a5c470a4af951f.png

4330 ms

t01ffe5d417f62a9fc5.jpg

t01ffe5d417f62a9fc5.jpg

8947 ms

t014dddfb13c608b813.jpg

t014dddfb13c608b813.jpg

20331 ms

t01f6cf13057caf9f91.jpg

t01f6cf13057caf9f91.jpg

20332 ms

star.svg

star.svg

232 ms

version.svg

version.svg

487 ms

build.svg

build.svg

697 ms

coverage.svg

coverage.svg

714 ms

Accessibility Review

thinkjs.org accessibility score

55

Accessibility Issues

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

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

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

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

SEO Factors

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

    N/A

  • Encoding

    UTF-8

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

thinkjs.org

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