Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

talk.ninghao.net

ninghao.net

Page Load Speed

26.4 sec in total

First Response

1.9 sec

Resources Loaded

23.8 sec

Page Rendered

757 ms

talk.ninghao.net screenshot

About Website

Welcome to talk.ninghao.net homepage info - get ready to check Talk Ninghao best content for China right away, or after learning these important things about talk.ninghao.net

WordPress - Drupal - Laravel - Bootstrap 中文论坛

Visit talk.ninghao.net

Key Findings

We analyzed Talk.ninghao.net page load time and found that the first response time was 1.9 sec and then it took 24.5 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

talk.ninghao.net performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value340 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

talk.ninghao.net

1872 ms

desktop_def38fcfeb316b2479ee64fe1cd7d65bbc19014f.css

6629 ms

7e202ef2-56d7-47d5-98d8-a9c8d15e57dd.css

1687 ms

preload_store-8d9173c7fdb49e0fc758a572fc829b20.js

1058 ms

zh_CN-e90b05f6d4826fb6ee2186b9d8751d25.js

4236 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 89% of them (8 requests) were addressed to the original Talk.ninghao.net, 11% (1 request) were made to Analytics.ninghao.net. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Talk.ninghao.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.9 kB (73%)

Content Size

378.7 kB

After Optimization

102.8 kB

In fact, the total size of Talk.ninghao.net main page is 378.7 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 5% of websites need less resources to load. Javascripts take 163.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 42.5 kB

  • Original 55.0 kB
  • After minification 54.3 kB
  • After compression 12.4 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 42.5 kB or 77% of the original size.

JavaScript Optimization

-65%

Potential reduce by 106.7 kB

  • Original 163.9 kB
  • After minification 163.8 kB
  • After compression 57.3 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 106.7 kB or 65% of the original size.

CSS Optimization

-79%

Potential reduce by 126.7 kB

  • Original 159.8 kB
  • After minification 159.4 kB
  • After compression 33.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. Talk.ninghao.net needs all CSS files to be minified and compressed as it can save up to 126.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (50%)

Requests Now

6

After Optimization

3

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

Accessibility Review

talk.ninghao.net accessibility score

68

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.

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 valid value for its [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

Form elements do not have associated labels

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

talk.ninghao.net 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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

talk.ninghao.net SEO score

89

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

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

    ZH

  • Encoding

    UTF-8

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

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