Report Summary

  • 100

    Performance

    Renders faster than
    97% 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

  • 55

    SEO

    Google-friendlier than
    20% of websites

pianyi.cc

pianyi.cc

Page Load Speed

42 sec in total

First Response

1 sec

Resources Loaded

40.8 sec

Page Rendered

130 ms

pianyi.cc screenshot

About Website

Welcome to pianyi.cc homepage info - get ready to check Pianyi best content right away, or after learning these important things about pianyi.cc

pianyi.cc

Visit pianyi.cc

Key Findings

We analyzed Pianyi.cc page load time and found that the first response time was 1 sec and then it took 41 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

pianyi.cc performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

pianyi.cc

1034 ms

jquery.js

19817 ms

style.css

1430 ms

stencil.css

11893 ms

j-pic.jpg

7357 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 13% of them (1 request) were addressed to the original Pianyi.cc, 75% (6 requests) were made to 4.cn and 13% (1 request) were made to Libs.baidu.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source 4.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.6 kB (55%)

Content Size

109.3 kB

After Optimization

49.6 kB

In fact, the total size of Pianyi.cc main page is 109.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 65.6 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 2.9 kB

  • Original 4.7 kB
  • After minification 3.9 kB
  • After compression 1.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 722 B, which is 15% 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 2.9 kB or 63% of the original size.

Image Optimization

-7%

Potential reduce by 2.7 kB

  • Original 39.0 kB
  • After minification 36.3 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. Pianyi images are well optimized though.

CSS Optimization

-82%

Potential reduce by 54.0 kB

  • Original 65.6 kB
  • After minification 56.8 kB
  • After compression 11.6 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. Pianyi.cc needs all CSS files to be minified and compressed as it can save up to 54.0 kB or 82% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pianyi. According to our analytics all requests are already optimized.

Accessibility Review

pianyi.cc accessibility score

68

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

Document doesn't have a <title> element

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

pianyi.cc best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

pianyi.cc SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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