Tools & Wizards About Us
talk.163.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

Page Load Speed

18.9 sec in total

First Response

2.4 sec

Resources Loaded

16.1 sec

Page Rendered

500 ms

talk.163.com screenshot

About Website

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

Visit talk.163.com

Key Findings

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

Performance Metrics

talk.163.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value40.7 s

0/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.088

92/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

talk.163.com

2373 ms

view.163.com

1448 ms

news.BmDT9sluSdyy.23.css

11 ms

ntes_jslib_1.x.js

16 ms

ne.js

13 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Talk.163.com, 42% (16 requests) were made to Img1.cache.netease.com and 11% (4 requests) were made to Img2.cache.netease.com. The less responsive or slowest element that took the longest time to load (8.2 sec) relates to the external source Webzj.reg.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.3 kB (21%)

Content Size

557.5 kB

After Optimization

441.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Talk.163.com main page is 557.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. 35% of websites need less resources to load. Images take 418.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 58.6 kB

  • Original 68.3 kB
  • After minification 51.7 kB
  • After compression 9.7 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 16.6 kB, which is 24% 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 58.6 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 7.9 kB

  • Original 418.9 kB
  • After minification 410.9 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. Talk 163 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 23.0 kB

  • Original 36.1 kB
  • After minification 36.1 kB
  • After compression 13.1 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 23.0 kB or 64% of the original size.

CSS Optimization

-78%

Potential reduce by 26.8 kB

  • Original 34.3 kB
  • After minification 33.8 kB
  • After compression 7.5 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.163.com needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (28%)

Requests Now

36

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

talk.163.com

talk.163.com

2373 ms

view.163.com

view.163.com

1448 ms

news.BmDT9sluSdyy.23.css

news.BmDT9sluSdyy.23.css

11 ms

ntes_jslib_1.x.js

ntes_jslib_1.x.js

16 ms

ne.js

ne.js

13 ms

theotherside_new.1022736.css

theotherside_new.1022736.css

23 ms

json3.js

json3.js

8230 ms

message.js

message.js

6623 ms

cnav2013.1065242.min.js

cnav2013.1065242.min.js

27 ms

topapp.jpg

topapp.jpg

9 ms

201603171128243ed0f.jpg

201603171128243ed0f.jpg

1173 ms

20160316115709144ba.jpg

20160316115709144ba.jpg

13 ms

2016031501431778301.jpg

2016031501431778301.jpg

678 ms

20160316121739d475a.jpg

20160316121739d475a.jpg

13 ms

2016031612160881667.jpg

2016031612160881667.jpg

11 ms

2016031111335788155.jpg

2016031111335788155.jpg

330 ms

logo2.png

logo2.png

6 ms

r_logo.jpg

r_logo.jpg

10 ms

btn.jpg

btn.jpg

12 ms

201603161154396bffe.jpg

201603161154396bffe.jpg

10 ms

20160316121351a396f.jpg

20160316121351a396f.jpg

10 ms

2016031612185467c46.JPG

2016031612185467c46.JPG

851 ms

201603161207033dbd9.jpg

201603161207033dbd9.jpg

845 ms

channel_logo.png

channel_logo.png

9 ms

nav_sprite_v37.png

nav_sprite_v37.png

9 ms

jquery.js

jquery.js

7 ms

respond.src.992025.min.js

respond.src.992025.min.js

7 ms

theotherside_new.1014002.min.js

theotherside_new.1014002.min.js

8 ms

wrating.js

wrating.js

5 ms

ntes.js

ntes.js

1094 ms

analysis.350ctAoOoFtN.12.js

analysis.350ctAoOoFtN.12.js

5 ms

icons.png

icons.png

75 ms

backtop.png

backtop.png

67 ms

ntes

ntes

1152 ms

1185 ms

605 ms

2834 ms

551 ms

Accessibility Review

talk.163.com accessibility score

87

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.

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

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

talk.163.com best practices score

83

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

talk.163.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

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Talk.163.com 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 Talk.163.com main page’s claimed encoding is gbk. 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

talk.163.com

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