Tools & Wizards About Us
roykung.com screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

roykung.com

Roy Lin 林昆彥

Page Load Speed

3.6 sec in total

First Response

370 ms

Resources Loaded

1.3 sec

Page Rendered

1.9 sec

roykung.com screenshot

About Website

Visit roykung.com now to see the best up-to-date Roy Kung content and also check out these interesting facts you probably never knew about roykung.com

林昆彥 (Roy Lin). I'm a dreamer, singer and basketball player, loving jogging, reading and cooking, and now running a startup in Taipei, Taiwan.

Visit roykung.com

Key Findings

We analyzed Roykung.com page load time and found that the first response time was 370 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

roykung.com performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

95/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.4 s

99/100

10%

Network Requests Diagram

roykung.com

370 ms

pre_tumblelog.js

12 ms

css

24 ms

css

36 ms

lightbox.css

15 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Roykung.com, 21% (9 requests) were made to Assets.tumblr.com and 12% (5 requests) were made to Static.tumblr.com. The less responsive or slowest element that took the longest time to load (370 ms) belongs to the original domain Roykung.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.0 kB (44%)

Content Size

966.2 kB

After Optimization

542.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Roykung.com main page is 966.2 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. 50% of websites need less resources to load. Javascripts take 539.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 72.2 kB

  • Original 103.6 kB
  • After minification 96.0 kB
  • After compression 31.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. 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 72.2 kB or 70% of the original size.

Image Optimization

-2%

Potential reduce by 5.6 kB

  • Original 313.9 kB
  • After minification 308.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. Roy Kung images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 339.3 kB

  • Original 539.9 kB
  • After minification 538.2 kB
  • After compression 200.6 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 339.3 kB or 63% of the original size.

CSS Optimization

-78%

Potential reduce by 6.9 kB

  • Original 8.8 kB
  • After minification 6.8 kB
  • After compression 1.9 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. Roykung.com needs all CSS files to be minified and compressed as it can save up to 6.9 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (68%)

Requests Now

38

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roy Kung. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

roykung.com

roykung.com

370 ms

pre_tumblelog.js

pre_tumblelog.js

12 ms

css

css

24 ms

css

css

36 ms

lightbox.css

lightbox.css

15 ms

css

css

45 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

13 ms

stylesheet.css

stylesheet.css

14 ms

tweets.js

tweets.js

344 ms

jquery.min.js

jquery.min.js

35 ms

jquery.jflickrfeed.js

jquery.jflickrfeed.js

10 ms

flickr_instagram_dribbble_1.js

flickr_instagram_dribbble_1.js

9 ms

jquery.photoset-grid.min.js

jquery.photoset-grid.min.js

9 ms

lightbox.js

lightbox.js

13 ms

index.js

index.js

12 ms

widgets.js

widgets.js

26 ms

like_iframe.html

like_iframe.html

33 ms

count.js

count.js

51 ms

tumblr_inline_n7kejnpUvK1r9avs6.jpg

tumblr_inline_n7kejnpUvK1r9avs6.jpg

142 ms

tumblr_inline_n7ln1pTZbw1r9avs6.jpg

tumblr_inline_n7ln1pTZbw1r9avs6.jpg

98 ms

tumblr_inline_n7kemxix9N1r9avs6.png

tumblr_inline_n7kemxix9N1r9avs6.png

79 ms

ga.js

ga.js

105 ms

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

102 ms

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

104 ms

4wfhKe93QxmsFlDQSCQ5wg.ttf

4wfhKe93QxmsFlDQSCQ5wg.ttf

104 ms

BmiPqZorq0QiT-p6kf1paaCWcynf_cDxXwCLxiixG1c.ttf

BmiPqZorq0QiT-p6kf1paaCWcynf_cDxXwCLxiixG1c.ttf

103 ms

impixu

impixu

237 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

262 ms

impixu

impixu

139 ms

analytics.html

analytics.html

241 ms

login_check.html

login_check.html

135 ms

__utm.gif

__utm.gif

72 ms

avatar_8a5f7ca486aa_40.png

avatar_8a5f7ca486aa_40.png

18 ms

iframe_logo.png

iframe_logo.png

18 ms

rapid-3.36.js

rapid-3.36.js

49 ms

rapidworker-1.2.js

rapidworker-1.2.js

52 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

31 ms

ga.js

ga.js

66 ms

analytics.js

analytics.js

54 ms

cs.js

cs.js

61 ms

__utm.gif

__utm.gif

19 ms

cedexis.radar.js

cedexis.radar.js

8 ms

jot

jot

86 ms

Accessibility Review

roykung.com accessibility score

97

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

roykung.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

roykung.com 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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roykung.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Roykung.com 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

roykung.com

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