Tools & Wizards About Us
cafescream.diarynote.jp screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

cafescream.diarynote.jp

キャベツ太郎（20円）のテルヤスな日々

Page Load Speed

5.7 sec in total

First Response

718 ms

Resources Loaded

3 sec

Page Rendered

2 sec

cafescream.diarynote.jp screenshot

About Website

Click here to check amazing Cafescream Diarynote content for Japan. Otherwise, check out these important facts you probably never knew about cafescream.diarynote.jp

ベースにしたのはプロツアーでTomoharu Saitoが使用したキオーラバント。変更点はメインの思考ジェイス4枚を3枚にして霊気渦竜巻を1枚追加。サイドの否認1枚と次元の浄化3枚をテューンの大天使、

Visit cafescream.diarynote.jp

Key Findings

We analyzed Cafescream.diarynote.jp page load time and found that the first response time was 718 ms and then it took 5 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

cafescream.diarynote.jp performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.069

96/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

cafescream.diarynote.jp

718 ms

blog.css

360 ms

edit.gif

372 ms

common.css

502 ms

0004423.jpg

518 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Cafescream.diarynote.jp, 48% (15 requests) were made to Diarynote.jp and 13% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Diarynote.jp.

Page Optimization Overview & Recommendations

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

Content Size

276.4 kB

After Optimization

153.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cafescream.diarynote.jp main page is 276.4 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. 30% of websites need less resources to load. Javascripts take 103.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 73.2 kB

  • Original 97.4 kB
  • After minification 96.0 kB
  • After compression 24.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. 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 73.2 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 5.3 kB

  • Original 66.5 kB
  • After minification 61.2 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. Cafescream Diarynote images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 37.5 kB

  • Original 103.6 kB
  • After minification 103.6 kB
  • After compression 66.1 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 37.5 kB or 36% of the original size.

CSS Optimization

-75%

Potential reduce by 6.6 kB

  • Original 8.9 kB
  • After minification 6.7 kB
  • After compression 2.2 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. Cafescream.diarynote.jp needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 75% of the original size.

Requests Breakdown

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

Requests Now

30

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cafescream.diarynote.jp

cafescream.diarynote.jp

718 ms

blog.css

blog.css

360 ms

edit.gif

edit.gif

372 ms

common.css

common.css

502 ms

0004423.jpg

0004423.jpg

518 ms

widgets.js

widgets.js

42 ms

102921_201401311216041986_1.jpg

102921_201401311216041986_1.jpg

788 ms

102921_201401311216041986_2.jpg

102921_201401311216041986_2.jpg

808 ms

102921_201312021429395867_1.jpg

102921_201312021429395867_1.jpg

832 ms

102921_201312021429395867_2.jpg

102921_201312021429395867_2.jpg

888 ms

102921_201311090632211890_1.jpg

102921_201311090632211890_1.jpg

881 ms

102921_201310150557577912_1.jpg

102921_201310150557577912_1.jpg

835 ms

102921_201310150557577912_2.jpg

102921_201310150557577912_2.jpg

1712 ms

102921_201309030649274173_1.jpg

102921_201309030649274173_1.jpg

1726 ms

102921_201309020810244952_1.jpg

102921_201309020810244952_1.jpg

1742 ms

102921.jpg

102921.jpg

1756 ms

btn_link.gif

btn_link.gif

1643 ms

ga.js

ga.js

8 ms

bi.js

bi.js

332 ms

ya.js

ya.js

347 ms

gtm.js

gtm.js

65 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

25 ms

__utm.gif

__utm.gif

16 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

68 ms

analytics.js

analytics.js

14 ms

uh.js

uh.js

466 ms

collect

collect

13 ms

395 ms

pb.js

pb.js

426 ms

319 ms

jot.html

jot.html

2 ms

Accessibility Review

cafescream.diarynote.jp accessibility score

82

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.

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

Form elements do not have associated labels

Best Practices

cafescream.diarynote.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

cafescream.diarynote.jp SEO score

64

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cafescream.diarynote.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 Cafescream.diarynote.jp 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

cafescream.diarynote.jp

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