Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

niugoo.com

Wordpress&Discuz镜像(Windows版本),本镜像由Websoft9提供

Page Load Speed

36.3 sec in total

First Response

10.3 sec

Resources Loaded

25.6 sec

Page Rendered

392 ms

niugoo.com screenshot

About Website

Click here to check amazing Niugoo content. Otherwise, check out these important facts you probably never knew about niugoo.com

牛股论坛-牛股网 牛股论坛 - 牛股行情-超赢数据-上市公司新闻 - Discuz! Board

Visit niugoo.com

Key Findings

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

Performance Metrics

niugoo.com performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.8 s

100/100

10%

Network Requests Diagram

niugoo.com

10334 ms

style_49_common.css

1937 ms

common.js

1942 ms

minisite.weather.js

3965 ms

555.gif

3687 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 73% of them (38 requests) were addressed to the original Niugoo.com, 15% (8 requests) were made to Bbs.niugoo.com and 6% (3 requests) were made to Image.sinajs.cn. The less responsive or slowest element that took the longest time to load (15.7 sec) relates to the external source Fw.qq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.4 kB (67%)

Content Size

123.5 kB

After Optimization

41.1 kB

In fact, the total size of Niugoo.com main page is 123.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. 25% of websites need less resources to load. HTML takes 48.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 38.0 kB

  • Original 48.8 kB
  • After minification 47.9 kB
  • After compression 10.8 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 38.0 kB or 78% of the original size.

JavaScript Optimization

-29%

Potential reduce by 8.3 kB

  • Original 28.5 kB
  • After minification 28.5 kB
  • After compression 20.2 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 8.3 kB or 29% of the original size.

CSS Optimization

-78%

Potential reduce by 36.1 kB

  • Original 46.2 kB
  • After minification 45.4 kB
  • After compression 10.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. Niugoo.com needs all CSS files to be minified and compressed as it can save up to 36.1 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (30%)

Requests Now

50

After Optimization

35

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

Accessibility Review

niugoo.com accessibility score

76

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

Best Practices

niugoo.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

niugoo.com SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Niugoo.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Niugoo.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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