Tools & Wizards About Us
yangze.me screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

yangze.me

Page Load Speed

15.2 sec in total

First Response

2 sec

Resources Loaded

11 sec

Page Rendered

2.2 sec

yangze.me screenshot

About Website

Visit yangze.me now to see the best up-to-date Yangze content and also check out these interesting facts you probably never knew about yangze.me

Visit yangze.me

Key Findings

We analyzed Yangze.me page load time and found that the first response time was 2 sec and then it took 13.2 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

yangze.me performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value1.3 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)

Value1.3 s

100/100

10%

Network Requests Diagram

www.yangze.me

1995 ms

add2home.css

441 ms

add2home.js

673 ms

style.css

734 ms

shortcodes.css

1868 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 81% of them (64 requests) were addressed to the original Yangze.me, 8% (6 requests) were made to Farm2.staticflickr.com and 3% (2 requests) were made to Farm6.staticflickr.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Yangze.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 666.5 kB (24%)

Content Size

2.8 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yangze.me main page is 2.8 MB. 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 35.3 kB

  • Original 46.7 kB
  • After minification 41.0 kB
  • After compression 11.4 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 5.7 kB, which is 12% 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 35.3 kB or 76% of the original size.

Image Optimization

-16%

Potential reduce by 386.9 kB

  • Original 2.3 MB
  • After minification 2.0 MB

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, Yangze needs image optimization as it can save up to 386.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 197.3 kB

  • Original 298.8 kB
  • After minification 282.4 kB
  • After compression 101.5 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 197.3 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 47.1 kB

  • Original 57.3 kB
  • After minification 43.5 kB
  • After compression 10.3 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. Yangze.me needs all CSS files to be minified and compressed as it can save up to 47.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (40%)

Requests Now

77

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.yangze.me

www.yangze.me

1995 ms

add2home.css

add2home.css

441 ms

add2home.js

add2home.js

673 ms

style.css

style.css

734 ms

shortcodes.css

shortcodes.css

1868 ms

jquery.js

jquery.js

3480 ms

jquery-migrate.min.js

jquery-migrate.min.js

659 ms

core.min.js

core.min.js

881 ms

widget.min.js

widget.min.js

879 ms

accordion.min.js

accordion.min.js

902 ms

tabs.min.js

tabs.min.js

965 ms

zilla-shortcodes-lib.js

zilla-shortcodes-lib.js

1099 ms

snow-storm.js

snow-storm.js

1108 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

1397 ms

slides.min.jquery.js

slides.min.jquery.js

1194 ms

twitter.js

twitter.js

1315 ms

audio-player.js

audio-player.js

1560 ms

James-Taylor-Greatest-Hits-Vinyl-LP-Record.png

James-Taylor-Greatest-Hits-Vinyl-LP-Record.png

4009 ms

appIcon.png

appIcon.png

2414 ms

default.png

default.png

5238 ms

WWDC20131.png

WWDC20131.png

2290 ms

CAJViewerMac-1.png

CAJViewerMac-1.png

6308 ms

%E5%B1%8F%E5%B9%95%E5%BF%AB%E7%85%A7-2013-03-03-%E4%B8%8B%E5%8D%887.21.01.png

%E5%B1%8F%E5%B9%95%E5%BF%AB%E7%85%A7-2013-03-03-%E4%B8%8B%E5%8D%887.21.01.png

4428 ms

xmassanta.gif

xmassanta.gif

2515 ms

snowflake.png

snowflake.png

2738 ms

xmasrudolph.gif

xmasrudolph.gif

2962 ms

letitsnow3.png

letitsnow3.png

5439 ms

Football-Manager-2013-.png

Football-Manager-2013-.png

6278 ms

Clover_128x128-1.png

Clover_128x128-1.png

4471 ms

badge_code_v2.gne

badge_code_v2.gne

219 ms

Twitter.png

Twitter.png

4560 ms

Weibo.png

Weibo.png

4665 ms

Instagram.png

Instagram.png

4778 ms

Facebook.png

Facebook.png

4895 ms

foursquare.png

foursquare.png

4995 ms

Douban.png

Douban.png

5128 ms

Google+.png

Google+.png

5213 ms

respond.min.js

respond.min.js

5228 ms

wp-embed.min.js

wp-embed.min.js

5237 ms

Path.png

Path.png

5077 ms

500px.png

500px.png

5212 ms

css

css

25 ms

Zhihu.png

Zhihu.png

5154 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

5470 ms

V2EX.png

V2EX.png

5072 ms

Dribbble.png

Dribbble.png

5207 ms

Windows.png

Windows.png

5155 ms

Pinterest.png

Pinterest.png

5072 ms

Disqus.png

Disqus.png

5224 ms

YouTube.png

YouTube.png

5325 ms

Mail.png

Mail.png

5205 ms

Flickr.png

Flickr.png

5160 ms

TencentWeibo.png

TencentWeibo.png

5019 ms

bg.jpg

bg.jpg

5397 ms

sep-light.gif

sep-light.gif

2970 ms

icons.png

icons.png

3080 ms

bg-content.gif

bg-content.gif

3135 ms

arrow-right.gif

arrow-right.gif

3157 ms

bg-rtl.jpg

bg-rtl.jpg

3624 ms

arrow-left.gif

arrow-left.gif

3189 ms

24586740243_faec6fd1c9_s.jpg

24586740243_faec6fd1c9_s.jpg

798 ms

23319550173_8624416a8e_s.jpg

23319550173_8624416a8e_s.jpg

44 ms

23420898342_0fc982e0bc_s.jpg

23420898342_0fc982e0bc_s.jpg

96 ms

p

p

47 ms

24497778943_7fe6a3ba0a_s.jpg

24497778943_7fe6a3ba0a_s.jpg

788 ms

25013906616_a6354f2842_s.jpg

25013906616_a6354f2842_s.jpg

850 ms

24695413946_6c1fd1f2f8_s.jpg

24695413946_6c1fd1f2f8_s.jpg

781 ms

24565909041_5446fb7f39_s.jpg

24565909041_5446fb7f39_s.jpg

787 ms

24310902871_b5f442df13_s.jpg

24310902871_b5f442df13_s.jpg

793 ms

23530580530_4b8fb83711_s.jpg

23530580530_4b8fb83711_s.jpg

40 ms

ga.js

ga.js

41 ms

__utm.gif

__utm.gif

12 ms

sep-dark.png

sep-dark.png

2911 ms

search.png

search.png

2368 ms

bg-menu-hover.png

bg-menu-hover.png

2288 ms

bg-menu.png

bg-menu.png

2183 ms

bg-sidebar-title.png

bg-sidebar-title.png

2225 ms

bg-button.png

bg-button.png

2163 ms

Mac9527.json

Mac9527.json

39 ms

Accessibility Review

yangze.me accessibility score

75

Accessibility Issues

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

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

SEO Factors

yangze.me SEO score

100

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

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

yangze.me

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