Tools & Wizards About Us
tradio.timelog.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tradio.timelog.jp

今をメモするTimelog

Page Load Speed

6.7 sec in total

First Response

1.9 sec

Resources Loaded

4.6 sec

Page Rendered

184 ms

tradio.timelog.jp screenshot

About Website

Click here to check amazing Tradio Timelog content for Japan. Otherwise, check out these important facts you probably never knew about tradio.timelog.jp

株式会社ファッションストリームの運営するタイムログは、2007年に始まった老舗SNS。日本語に特化した機能による使いやすさと親しみやすさが、暖かいコミュニティによって支持されています。

Visit tradio.timelog.jp

Key Findings

We analyzed Tradio.timelog.jp page load time and found that the first response time was 1.9 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

tradio.timelog.jp performance score

0

Network Requests Diagram

tradio.timelog.jp

1929 ms

style_global_navi.css

534 ms

style_03.css

703 ms

prototype.js

1403 ms

timelog.js

539 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Tradio.timelog.jp, 71% (58 requests) were made to Img.timelog.jp and 23% (19 requests) were made to Timelog.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Tradio.timelog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 210.8 kB (61%)

Content Size

344.1 kB

After Optimization

133.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tradio.timelog.jp main page is 344.1 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 118.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 55.0 kB

  • Original 64.1 kB
  • After minification 64.1 kB
  • After compression 9.1 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 55.0 kB or 86% of the original size.

Image Optimization

-19%

Potential reduce by 22.4 kB

  • Original 118.9 kB
  • After minification 96.5 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, Tradio Timelog needs image optimization as it can save up to 22.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-82%

Potential reduce by 92.5 kB

  • Original 113.3 kB
  • After minification 82.2 kB
  • After compression 20.9 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 92.5 kB or 82% of the original size.

CSS Optimization

-85%

Potential reduce by 40.8 kB

  • Original 47.7 kB
  • After minification 39.0 kB
  • After compression 6.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. Tradio.timelog.jp needs all CSS files to be minified and compressed as it can save up to 40.8 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

81

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tradio.timelog.jp

tradio.timelog.jp

1929 ms

style_global_navi.css

style_global_navi.css

534 ms

style_03.css

style_03.css

703 ms

prototype.js

prototype.js

1403 ms

timelog.js

timelog.js

539 ms

lightbox.js

lightbox.js

738 ms

lightbox.css

lightbox.css

565 ms

style_main.css

style_main.css

349 ms

tradio.jpg

tradio.jpg

629 ms

blank.asp

blank.asp

303 ms

chart

chart

114 ms

tiicon.png

tiicon.png

181 ms

icn_pr.png

icn_pr.png

188 ms

group_menu.gif

group_menu.gif

345 ms

box_back_03.gif

box_back_03.gif

178 ms

prof_back.gif

prof_back.gif

195 ms

prof_back_foot.gif

prof_back_foot.gif

176 ms

timeline_menu_back.gif

timeline_menu_back.gif

345 ms

timeline_menu_back_03.gif

timeline_menu_back_03.gif

349 ms

msgbox_w_foot.gif

msgbox_w_foot.gif

353 ms

msgbox_w_back.gif

msgbox_w_back.gif

369 ms

foot_background_03.gif

foot_background_03.gif

382 ms

F9B7.gif

F9B7.gif

462 ms

F9CC.gif

F9CC.gif

482 ms

ico_yes.gif

ico_yes.gif

482 ms

suzumushi23_m.jpg

suzumushi23_m.jpg

653 ms

icn_youtube.gif

icn_youtube.gif

525 ms

icon_public.gif

icon_public.gif

618 ms

F9BB.gif

F9BB.gif

646 ms

comment.gif

comment.gif

647 ms

star.gif

star.gif

707 ms

staradd.gif

staradd.gif

763 ms

donot_m.jpg

donot_m.jpg

765 ms

bluesky319_m.jpg

bluesky319_m.jpg

805 ms

icn_url.gif

icn_url.gif

806 ms

rainywalk_m.jpg

rainywalk_m.jpg

810 ms

SirJones_m.jpg

SirJones_m.jpg

884 ms

morimasa_m.jpg

morimasa_m.jpg

909 ms

kabocha_m.jpg

kabocha_m.jpg

919 ms

ponkun_m.jpg

ponkun_m.jpg

969 ms

kuwakuwa_m.jpg

kuwakuwa_m.jpg

966 ms

tradio_l.jpg

tradio_l.jpg

1138 ms

icn_rss.gif

icn_rss.gif

1066 ms

F9E6.gif

F9E6.gif

1059 ms

F955.gif

F955.gif

1071 ms

icon_memo_12.gif

icon_memo_12.gif

1128 ms

icon_tag.gif

icon_tag.gif

1130 ms

darilyn8889_m.jpg

darilyn8889_m.jpg

1209 ms

soramimi_m.jpg

soramimi_m.jpg

1248 ms

okota2a_m.jpg

okota2a_m.jpg

1223 ms

skybike_m.jpg

skybike_m.jpg

1291 ms

kero1_m.jpg

kero1_m.jpg

1292 ms

noneob3_m.jpg

noneob3_m.jpg

1302 ms

gohgoyo209_m.jpg

gohgoyo209_m.jpg

1360 ms

kuxku_m.jpg

kuxku_m.jpg

1375 ms

asas12_m.jpg

asas12_m.jpg

1430 ms

kawahagi_m.jpg

kawahagi_m.jpg

1453 ms

kagura77_m.jpg

kagura77_m.jpg

999 ms

hironnn_m.jpg

hironnn_m.jpg

992 ms

makunosuke_m.jpg

makunosuke_m.jpg

1035 ms

kinocon_m.jpg

kinocon_m.jpg

1010 ms

n11m12_m.jpg

n11m12_m.jpg

1011 ms

tenderly_m.jpg

tenderly_m.jpg

1006 ms

yomohm_m.jpg

yomohm_m.jpg

976 ms

mushroomroom_m.jpg

mushroomroom_m.jpg

986 ms

rosesno1_m.jpg

rosesno1_m.jpg

1017 ms

subayarikimeshi_m.jpg

subayarikimeshi_m.jpg

982 ms

stepwgn_m.jpg

stepwgn_m.jpg

1039 ms

yashima8to7_m.jpg

yashima8to7_m.jpg

1023 ms

achroite_m.jpg

achroite_m.jpg

980 ms

capncap_m.jpg

capncap_m.jpg

994 ms

yukky0311_m.jpg

yukky0311_m.jpg

1008 ms

natsup_m.jpg

natsup_m.jpg

958 ms

syasinbu2_m.jpg

syasinbu2_m.jpg

1040 ms

hayano_m.jpg

hayano_m.jpg

1033 ms

momohands_m.jpg

momohands_m.jpg

1016 ms

petal78_m.jpg

petal78_m.jpg

997 ms

elis603_m.jpg

elis603_m.jpg

909 ms

ajaxwait.gif

ajaxwait.gif

929 ms

overlay.png

overlay.png

176 ms

loading.gif

loading.gif

152 ms

close.gif

close.gif

303 ms

SEO Factors

tradio.timelog.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tradio.timelog.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Tradio.timelog.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

tradio.timelog.jp

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