Tools & Wizards About Us
timestmp.timelog.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

timestmp.timelog.jp

timestmp - 今をメモするTimelog

Page Load Speed

5.1 sec in total

First Response

1.3 sec

Resources Loaded

3.7 sec

Page Rendered

131 ms

timestmp.timelog.jp screenshot

About Website

Visit timestmp.timelog.jp now to see the best up-to-date Timestmp Timelog content for Japan and also check out these interesting facts you probably never knew about timestmp.timelog.jp

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

Visit timestmp.timelog.jp

Key Findings

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

Performance Metrics

timestmp.timelog.jp performance score

0

Network Requests Diagram

timestmp.timelog.jp

1320 ms

style_global_navi.css

727 ms

style_main.css

901 ms

prototype.js

1228 ms

timelog.js

746 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 13% of them (4 requests) were addressed to the original Timestmp.timelog.jp, 50% (16 requests) were made to Timelog.jp and 34% (11 requests) were made to Img.timelog.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Timestmp.timelog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.1 kB (73%)

Content Size

190.8 kB

After Optimization

50.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Timestmp.timelog.jp main page is 190.8 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. Only 10% of websites need less resources to load. Javascripts take 113.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.5 kB

  • Original 10.7 kB
  • After minification 10.6 kB
  • After compression 3.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 7.5 kB or 71% of the original size.

Image Optimization

-8%

Potential reduce by 1.8 kB

  • Original 22.1 kB
  • After minification 20.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. Timestmp Timelog images are well optimized though.

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

-86%

Potential reduce by 38.4 kB

  • Original 44.8 kB
  • After minification 36.6 kB
  • After compression 6.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. Timestmp.timelog.jp needs all CSS files to be minified and compressed as it can save up to 38.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (39%)

Requests Now

31

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

timestmp.timelog.jp

timestmp.timelog.jp

1320 ms

style_global_navi.css

style_global_navi.css

727 ms

style_main.css

style_main.css

901 ms

prototype.js

prototype.js

1228 ms

timelog.js

timelog.js

746 ms

lightbox.js

lightbox.js

970 ms

lightbox.css

lightbox.css

791 ms

icon_memo_12.gif

icon_memo_12.gif

696 ms

blank.asp

blank.asp

187 ms

chart

chart

81 ms

tiicon.png

tiicon.png

163 ms

icn_pr.png

icn_pr.png

154 ms

group_menu_title.gif

group_menu_title.gif

164 ms

group_menu.gif

group_menu.gif

557 ms

box_back_00.gif

box_back_00.gif

186 ms

prof_back.gif

prof_back.gif

164 ms

prof_back_foot.gif

prof_back_foot.gif

307 ms

timeline_menu_back.gif

timeline_menu_back.gif

324 ms

foot_background.gif

foot_background.gif

323 ms

star.gif

star.gif

712 ms

F955.gif

F955.gif

710 ms

F9B7.gif

F9B7.gif

717 ms

F9CC.gif

F9CC.gif

732 ms

ico_yes.gif

ico_yes.gif

733 ms

timestmp_l.jpg

timestmp_l.jpg

1141 ms

F9E6.gif

F9E6.gif

872 ms

icon_tag.gif

icon_tag.gif

870 ms

nearprv_m.jpg

nearprv_m.jpg

883 ms

ajaxwait.gif

ajaxwait.gif

1075 ms

overlay.png

overlay.png

164 ms

loading.gif

loading.gif

187 ms

close.gif

close.gif

345 ms

SEO Factors

timestmp.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 Timestmp.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 Timestmp.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

timestmp.timelog.jp

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