Tools & Wizards About Us

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

timelog.jp

今をメモするTimelog

Page Load Speed

13.9 sec in total

First Response

5.5 sec

Resources Loaded

8.2 sec

Page Rendered

287 ms

About Website

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

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

Visit timelog.jp

Key Findings

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

Performance Metrics

timelog.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

71/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value4.7 s

81/100

10%

Network Requests Diagram

timelog.jp

5453 ms

defaultfs.css

331 ms

style_global_navi.css

350 ms

jquery.min.js

7 ms

jquery.nailthumb.1.1.js

527 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 29% of them (17 requests) were addressed to the original Timelog.jp, 52% (30 requests) were made to Img.timelog.jp and 14% (8 requests) were made to Img1.timelog.jp. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Timelog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.3 kB (4%)

Content Size

4.6 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Timelog.jp main page is 4.6 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. 45% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 15.2 kB

  • Original 20.0 kB
  • After minification 20.0 kB
  • After compression 4.9 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 15.2 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 83.1 kB

  • Original 4.4 MB
  • After minification 4.4 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. Timelog images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 87.4 kB

  • Original 124.8 kB
  • After minification 113.8 kB
  • After compression 37.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 87.4 kB or 70% of the original size.

CSS Optimization

-75%

Potential reduce by 7.7 kB

  • Original 10.2 kB
  • After minification 7.7 kB
  • After compression 2.6 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. Timelog.jp needs all CSS files to be minified and compressed as it can save up to 7.7 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (14%)

Requests Now

56

After Optimization

48

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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

Accessibility Review

timelog.jp accessibility score

70

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

timelog.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

timelog.jp SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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