Tools & Wizards About Us
dingyu.me screenshot

Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

dingyu.me

丁宇 | DING Yu

Page Load Speed

25.9 sec in total

First Response

416 ms

Resources Loaded

22.1 sec

Page Rendered

3.4 sec

dingyu.me screenshot

About Website

Click here to check amazing DING Yu content. Otherwise, check out these important facts you probably never knew about dingyu.me

Felix is a designer, product manager and Rails developer in Shanghai, China. He co-founded and runs...

Visit dingyu.me

Key Findings

We analyzed Dingyu.me page load time and found that the first response time was 416 ms and then it took 25.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

dingyu.me performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value3.8 s

83/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

dingyu.me

416 ms

pre_tumblelog.js

26 ms

font-awesome.min.css

30 ms

main2.0.min.css

33 ms

tumblelog_post_message_queue.js

19 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dingyu.me, 23% (19 requests) were made to Music.163.com and 11% (9 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Wr.da.netease.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 499.3 kB (20%)

Content Size

2.5 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dingyu.me main page is 2.5 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 98.3 kB

  • Original 128.6 kB
  • After minification 102.5 kB
  • After compression 30.2 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 26.1 kB, which is 20% 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 98.3 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 5.1 kB

  • Original 1.7 MB
  • After minification 1.7 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. DING Yu images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 365.9 kB

  • Original 574.2 kB
  • After minification 573.9 kB
  • After compression 208.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 365.9 kB or 64% of the original size.

CSS Optimization

-74%

Potential reduce by 29.9 kB

  • Original 40.3 kB
  • After minification 39.0 kB
  • After compression 10.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. Dingyu.me needs all CSS files to be minified and compressed as it can save up to 29.9 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (30%)

Requests Now

79

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dingyu.me

dingyu.me

416 ms

pre_tumblelog.js

pre_tumblelog.js

26 ms

font-awesome.min.css

font-awesome.min.css

30 ms

main2.0.min.css

main2.0.min.css

33 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

19 ms

stylesheet.css

stylesheet.css

22 ms

client-code.js

client-code.js

95 ms

jquery.min.js

jquery.min.js

90 ms

photosetgrid1.0.1.js

photosetgrid1.0.1.js

84 ms

app.min.js

app.min.js

83 ms

js

js

6 ms

index.build.js

index.build.js

84 ms

23697784359_b43c724f59_z.jpg

23697784359_b43c724f59_z.jpg

562 ms

24065776715_f26d9fb5be.jpg

24065776715_f26d9fb5be.jpg

776 ms

like_iframe.html

like_iframe.html

378 ms

22435308436_7fd6951c10_z.jpg

22435308436_7fd6951c10_z.jpg

761 ms

player

player

914 ms

player

player

900 ms

player

player

1060 ms

player

player

1111 ms

player

player

1110 ms

player

player

1114 ms

player

player

1285 ms

player

player

1291 ms

23770023090_c9e262fc4c_z.jpg

23770023090_c9e262fc4c_z.jpg

761 ms

23439005113_5442aef50c.jpg

23439005113_5442aef50c.jpg

689 ms

23941231491_b44e0cc7e6_z.jpg

23941231491_b44e0cc7e6_z.jpg

712 ms

23728119010_5393c8802f_z.jpg

23728119010_5393c8802f_z.jpg

746 ms

23941231391_dffc402825_z.jpg

23941231391_dffc402825_z.jpg

768 ms

23915561072_9f773a1e46_z.jpg

23915561072_9f773a1e46_z.jpg

834 ms

tumblr_static_ceasntv0megogc0s8s0wk44o8_2048_v2.jpg

tumblr_static_ceasntv0megogc0s8s0wk44o8_2048_v2.jpg

400 ms

22280918422_5c8212bab5_o.jpg

22280918422_5c8212bab5_o.jpg

687 ms

21939883140_930083c5ff_z.jpg

21939883140_930083c5ff_z.jpg

738 ms

21506959643_c9330e3fa6_z.jpg

21506959643_c9330e3fa6_z.jpg

721 ms

22099229266_e5ec89a20f_z.jpg

22099229266_e5ec89a20f_z.jpg

833 ms

23941231361_fc06e4ea79_z.jpg

23941231361_fc06e4ea79_z.jpg

721 ms

23997685576_79a13305ce_z.jpg

23997685576_79a13305ce_z.jpg

686 ms

23395567574_591531a1e4_z.jpg

23395567574_591531a1e4_z.jpg

763 ms

23915560872_63610f7640_z.jpg

23915560872_63610f7640_z.jpg

714 ms

23118554531_ca4347ef72_z.jpg

23118554531_ca4347ef72_z.jpg

876 ms

22471876451_bc27e6db3f_o.jpg

22471876451_bc27e6db3f_o.jpg

747 ms

analytics.js

analytics.js

336 ms

count.js

count.js

682 ms

impixu

impixu

666 ms

impixu

impixu

412 ms

embedr-loader.js

embedr-loader.js

391 ms

analytics.html

analytics.html

386 ms

in.php

in.php

409 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

169 ms

login_check.html

login_check.html

52 ms

collect

collect

131 ms

iframe_logo.png

iframe_logo.png

297 ms

avatar_c4da8d9bbb80_40.png

avatar_c4da8d9bbb80_40.png

286 ms

count-data.js

count-data.js

374 ms

rapid-3.36.1.js

rapid-3.36.1.js

39 ms

rapidworker-1.2.js

rapidworker-1.2.js

35 ms

embedr-5cfdc95dac01effa41001907e782e945.js

embedr-5cfdc95dac01effa41001907e782e945.js

227 ms

ga.js

ga.js

146 ms

analytics.js

analytics.js

119 ms

cs.js

cs.js

139 ms

yql

yql

319 ms

base.css

base.css

530 ms

outchain-player.css

outchain-player.css

577 ms

core.js

core.js

105 ms

pt_outchain_player.js

pt_outchain_player.js

97 ms

__utm.gif

__utm.gif

24 ms

yql

yql

124 ms

default_list.jpg

default_list.jpg

975 ms

audio_sprite.png

audio_sprite.png

438 ms

detail

detail

786 ms

ga.js

ga.js

19558 ms

detail

detail

889 ms

detail

detail

901 ms

detail

detail

794 ms

detail

detail

844 ms

detail

detail

839 ms

detail

detail

1101 ms

detail

detail

1210 ms

6620159511043895.jpg

6620159511043895.jpg

166 ms

6633353651269805.jpg

6633353651269805.jpg

28 ms

117647744184786.jpg

117647744184786.jpg

17 ms

2544269906708660.jpg

2544269906708660.jpg

20 ms

117647744184786.jpg

117647744184786.jpg

139 ms

Accessibility Review

dingyu.me accessibility score

93

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

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

dingyu.me SEO score

89

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dingyu.me can be misinterpreted by Google and other search engines. Our service has detected that English 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 Dingyu.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

dingyu.me

Open Graph data is detected on the main page of DING Yu. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: