Tools & Wizards About Us
qinyang.me screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

qinyang.me

Page Load Speed

7.9 sec in total

First Response

2.5 sec

Resources Loaded

4.1 sec

Page Rendered

1.3 sec

qinyang.me screenshot

About Website

Click here to check amazing Qinyang content. Otherwise, check out these important facts you probably never knew about qinyang.me

Visit qinyang.me

Key Findings

We analyzed Qinyang.me page load time and found that the first response time was 2.5 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

qinyang.me performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

qinyang.me

2523 ms

wp-emoji-release.min.js

513 ms

style.css

730 ms

mediaelementplayer.min.css

522 ms

wp-mediaelement.css

364 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that all of those requests were addressed to Qinyang.me and no external sources were called. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Qinyang.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.0 kB (46%)

Content Size

794.4 kB

After Optimization

426.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qinyang.me main page is 794.4 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. Images take 366.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 67.3 kB

  • Original 82.2 kB
  • After minification 75.0 kB
  • After compression 14.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 67.3 kB or 82% of the original size.

Image Optimization

-15%

Potential reduce by 53.3 kB

  • Original 366.7 kB
  • After minification 313.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. Obviously, Qinyang needs image optimization as it can save up to 53.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 163.6 kB

  • Original 242.7 kB
  • After minification 239.8 kB
  • After compression 79.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 163.6 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 83.8 kB

  • Original 102.8 kB
  • After minification 99.4 kB
  • After compression 19.0 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. Qinyang.me needs all CSS files to be minified and compressed as it can save up to 83.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (32%)

Requests Now

34

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qinyang.me

qinyang.me

2523 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

513 ms

style.css

style.css

730 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

522 ms

wp-mediaelement.css

wp-mediaelement.css

364 ms

colorbox.min.css

colorbox.min.css

400 ms

jquery.js

jquery.js

1056 ms

jquery-migrate.min.js

jquery-migrate.min.js

608 ms

jquery.colorbox.1.5.9-min.js

jquery.colorbox.1.5.9-min.js

678 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

370 ms

wp-mediaelement.js

wp-mediaelement.js

171 ms

custom.js

custom.js

274 ms

comments-ajax.js

comments-ajax.js

337 ms

Plugins.js

Plugins.js

359 ms

black_bg.jpg

black_bg.jpg

324 ms

black_header.jpg

black_header.jpg

324 ms

you.jpg

you.jpg

323 ms

black_nav.png

black_nav.png

320 ms

black_post.jpg

black_post.jpg

321 ms

black_line3.jpg

black_line3.jpg

320 ms

mento.png

mento.png

361 ms

1.jpg

1.jpg

710 ms

11.jpg

11.jpg

534 ms

2.jpg

2.jpg

533 ms

3-183x300.jpg

3-183x300.jpg

374 ms

4-300x156.jpg

4-300x156.jpg

405 ms

5.jpg

5.jpg

530 ms

6-272x300.jpg

6-272x300.jpg

560 ms

7-300x159.jpg

7-300x159.jpg

607 ms

1-300x181.jpg

1-300x181.jpg

710 ms

2-300x174.jpg

2-300x174.jpg

722 ms

pal-300x122.jpg

pal-300x122.jpg

719 ms

black_line2.png

black_line2.png

741 ms

net.png

net.png

806 ms

shadow.png

shadow.png

871 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

560 ms

icomoon.woff

icomoon.woff

574 ms

Accessibility Review

qinyang.me 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

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

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

qinyang.me 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

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

qinyang.me SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qinyang.me 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), while the claimed language is Chinese. Our system also found out that Qinyang.me 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

qinyang.me

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