Tools & Wizards About Us
62096.diarynote.jp screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% 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

62096.diarynote.jp

気まぐれ日記

Page Load Speed

7.6 sec in total

First Response

1.4 sec

Resources Loaded

5.9 sec

Page Rendered

331 ms

62096.diarynote.jp screenshot

About Website

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

ソリンイラストくそかっこいいから今回は取りに行く

Visit 62096.diarynote.jp

Key Findings

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

Performance Metrics

62096.diarynote.jp performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value4.9 s

64/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.137

79/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

62096.diarynote.jp

1393 ms

blog.css

333 ms

62096

342 ms

edit.gif

353 ms

common.css

331 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original 62096.diarynote.jp, 36% (9 requests) were made to Diarynote.jp and 16% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Ua.nakanohito.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.7 kB (32%)

Content Size

199.0 kB

After Optimization

136.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 62096.diarynote.jp main page is 199.0 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 72.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 46.8 kB

  • Original 59.4 kB
  • After minification 58.0 kB
  • After compression 12.5 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 46.8 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 3.4 kB

  • Original 58.2 kB
  • After minification 54.8 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. 62096 Diarynote images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 5.6 kB

  • Original 72.2 kB
  • After minification 72.2 kB
  • After compression 66.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. This website has mostly compressed JavaScripts.

CSS Optimization

-75%

Potential reduce by 6.9 kB

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

Requests Breakdown

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

Requests Now

24

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

62096.diarynote.jp

62096.diarynote.jp

1393 ms

blog.css

blog.css

333 ms

62096

62096

342 ms

edit.gif

edit.gif

353 ms

common.css

common.css

331 ms

widgets.js

widgets.js

23 ms

62096.jpg

62096.jpg

526 ms

62096_201603082120034406_1.jpg

62096_201603082120034406_1.jpg

352 ms

62096_201603032112501180_1.jpg

62096_201603032112501180_1.jpg

355 ms

62096.jpg

62096.jpg

357 ms

btn_link.gif

btn_link.gif

363 ms

ga.js

ga.js

23 ms

bi.js

bi.js

332 ms

ya.js

ya.js

373 ms

gtm.js

gtm.js

71 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

25 ms

__utm.gif

__utm.gif

45 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

78 ms

analytics.js

analytics.js

87 ms

uh.js

uh.js

456 ms

collect

collect

28 ms

370 ms

pb.js

pb.js

507 ms

3309 ms

jot.html

jot.html

2 ms

Accessibility Review

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

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

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

62096.diarynote.jp

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