18.9 sec in total
2.4 sec
16.1 sec
500 ms
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.comWe 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.
talk.163.com performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value12.1 s
0/100
25%
Value40.7 s
0/100
10%
Value580 ms
51/100
30%
Value0.088
92/100
15%
Value20.3 s
2/100
10%
2373 ms
1448 ms
11 ms
16 ms
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 size can be reduced by 116.3 kB (21%)
557.5 kB
441.2 kB
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.
Potential reduce by 58.6 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.
Potential reduce by 7.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.
Potential reduce by 23.0 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.
Potential reduce by 26.8 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.
Number of requests can be reduced by 10 (28%)
36
26
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.
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
theotherside_new.1022736.css
23 ms
json3.js
8230 ms
message.js
6623 ms
cnav2013.1065242.min.js
27 ms
topapp.jpg
9 ms
201603171128243ed0f.jpg
1173 ms
20160316115709144ba.jpg
13 ms
2016031501431778301.jpg
678 ms
20160316121739d475a.jpg
13 ms
2016031612160881667.jpg
11 ms
2016031111335788155.jpg
330 ms
logo2.png
6 ms
r_logo.jpg
10 ms
btn.jpg
12 ms
201603161154396bffe.jpg
10 ms
20160316121351a396f.jpg
10 ms
2016031612185467c46.JPG
851 ms
201603161207033dbd9.jpg
845 ms
channel_logo.png
9 ms
nav_sprite_v37.png
9 ms
jquery.js
7 ms
respond.src.992025.min.js
7 ms
theotherside_new.1014002.min.js
8 ms
wrating.js
5 ms
ntes.js
1094 ms
analysis.350ctAoOoFtN.12.js
5 ms
icons.png
75 ms
backtop.png
67 ms
ntes
1152 ms
1185 ms
605 ms
2834 ms
551 ms
talk.163.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
talk.163.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
talk.163.com SEO score
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
Document uses legible font sizes
ZH
N/A
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.
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: