Tools & Wizards About Us
yeah.net screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

yeah.net

Yeah.net网易免费邮-快乐 分享 成长

Page Load Speed

10 sec in total

First Response

752 ms

Resources Loaded

9.2 sec

Page Rendered

112 ms

yeah.net screenshot

About Website

Click here to check amazing Yeah content for China. Otherwise, check out these important facts you probably never knew about yeah.net

网易yeah免费邮箱，你的专业电子邮局。网易出品，超过20年的邮箱运营经验，系统快速稳定，支持超大附件和网盘服务。网易邮箱官方App“邮箱大师”帮您高效处理邮件，支持所有邮箱，并可在手机、Windows和Mac上多端协同使用。

Visit yeah.net

Key Findings

We analyzed Yeah.net page load time and found that the first response time was 752 ms and then it took 9.3 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

yeah.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

yeah.net

752 ms

yeah.net

1011 ms

message.js

1368 ms

es5-polyfill.js

1443 ms

bundle.tracing.min.js

1691 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Yeah.net, 42% (16 requests) were made to Mimg.127.net and 11% (4 requests) were made to Urswebzj-v6.nosdn.127.net. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Passport-v6.yeah.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.5 kB (10%)

Content Size

316.3 kB

After Optimization

283.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-56%

Potential reduce by 31.0 kB

  • Original 54.9 kB
  • After minification 54.6 kB
  • After compression 23.9 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 31.0 kB or 56% of the original size.

Image Optimization

-2%

Potential reduce by 29 B

  • Original 1.4 kB
  • After minification 1.4 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. Yeah images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.0 kB

  • Original 220.3 kB
  • After minification 220.2 kB
  • After compression 219.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 420 B

  • Original 39.8 kB
  • After minification 39.8 kB
  • After compression 39.4 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. Yeah.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (43%)

Requests Now

30

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yeah.net

yeah.net

752 ms

yeah.net

yeah.net

1011 ms

message.js

message.js

1368 ms

es5-polyfill.js

es5-polyfill.js

1443 ms

bundle.tracing.min.js

bundle.tracing.min.js

1691 ms

style.0a213fbf80c07ae91697.css

style.0a213fbf80c07ae91697.css

1710 ms

year.js

year.js

1443 ms

mailad-sdk-0.0.19.js

mailad-sdk-0.0.19.js

1733 ms

mailscanlogin-1.2.3.js

mailscanlogin-1.2.3.js

1905 ms

index-0.0.1.js

index-0.0.1.js

1759 ms

index-promote.js

index-promote.js

1732 ms

vendors~126~163~yeah.d682f31523baefee0c00.js

vendors~126~163~yeah.d682f31523baefee0c00.js

2249 ms

yeah.481ced5ff8f3405d349b.js

yeah.481ced5ff8f3405d349b.js

1980 ms

t.gif

t.gif

298 ms

gonganlogo.png

gonganlogo.png

302 ms

detail

detail

266 ms

login_index.json

login_index.json

281 ms

39628e5a6146f059949210bebf88d697.png

39628e5a6146f059949210bebf88d697.png

1311 ms

getConf

getConf

1405 ms

config.do

config.do

1372 ms

form3

form3

1302 ms

loading_s.gif

loading_s.gif

272 ms

index_dl2_new.html

index_dl2_new.html

2749 ms

fingerprint-2.1.2.min.js

fingerprint-2.1.2.min.js

285 ms

i

i

1593 ms

init

init

564 ms

get.do

get.do

307 ms

get.do

get.do

616 ms

stat.gif

stat.gif

1252 ms

54d46d33-810a-4f3d-9e14-a8671608feeb

54d46d33-810a-4f3d-9e14-a8671608feeb

1560 ms

preload6.htm

preload6.htm

1093 ms

i

i

247 ms

urs.yeah.87467054.css

urs.yeah.87467054.css

327 ms

i

i

247 ms

webzjconf.js

webzjconf.js

173 ms

fingerprint2.min-1.6.1.js

fingerprint2.min-1.6.1.js

417 ms

pp_index_dl_9d10a0e93c13e629e99c5fb42a18350d.js

pp_index_dl_9d10a0e93c13e629e99c5fb42a18350d.js

1406 ms

i

i

247 ms

Accessibility Review

yeah.net accessibility score

55

Accessibility Issues

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

High

Links do not have a discernible name

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

yeah.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

yeah.net 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

    ZH

  • Encoding

    UTF-8

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

yeah.net

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