Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 95

    SEO

    Google-friendlier than
    91% of websites

Page Load Speed

27.4 sec in total

First Response

3 sec

Resources Loaded

23.6 sec

Page Rendered

803 ms

yinyueke.net screenshot

About Website

Visit yinyueke.net now to see the best up-to-date Yinyueke content and also check out these interesting facts you probably never knew about yinyueke.net

Visit yinyueke.net

Key Findings

We analyzed Yinyueke.net page load time and found that the first response time was 3 sec and then it took 24.4 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 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

yinyueke.net performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

yinyueke.net

2963 ms

style.css

690 ms

saySlide.css

644 ms

jquery-1.8.3.min.js

814 ms

jquery.saySlide.js

644 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 60% of them (24 requests) were addressed to the original Yinyueke.net, 38% (15 requests) were made to Yinyuekedata.qiniudn.com and 3% (1 request) were made to Js.users.51.la. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Yinyuekedata.qiniudn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.1 kB (51%)

Content Size

264.1 kB

After Optimization

129.0 kB

In fact, the total size of Yinyueke.net main page is 264.1 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 153.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 25.5 kB

  • Original 32.1 kB
  • After minification 30.3 kB
  • After compression 6.5 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 25.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 75.9 kB
  • After minification 75.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. Yinyueke images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 108.6 kB

  • Original 153.9 kB
  • After minification 141.1 kB
  • After compression 45.4 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 108.6 kB or 71% of the original size.

CSS Optimization

-45%

Potential reduce by 987 B

  • Original 2.2 kB
  • After minification 1.9 kB
  • After compression 1.2 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. Yinyueke.net needs all CSS files to be minified and compressed as it can save up to 987 B or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (19%)

Requests Now

32

After Optimization

26

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

Accessibility Review

yinyueke.net accessibility score

63

Accessibility Issues

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

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

yinyueke.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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yinyueke.net SEO score

95

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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