Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

watts.hateblo.jp

wattsの備忘録

Page Load Speed

30.8 sec in total

First Response

561 ms

Resources Loaded

23.6 sec

Page Rendered

6.6 sec

watts.hateblo.jp screenshot

About Website

Click here to check amazing Watts Hateblo content for Japan. Otherwise, check out these important facts you probably never knew about watts.hateblo.jp

Apple新製品とFF14で気になることをかいてます

Visit watts.hateblo.jp

Key Findings

We analyzed Watts.hateblo.jp page load time and found that the first response time was 561 ms and then it took 30.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

watts.hateblo.jp performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value18.9 s

0/100

10%

TBT (Total Blocking Time)

Value9,090 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value39.8 s

0/100

10%

Network Requests Diagram

watts.hateblo.jp

561 ms

blog.css

846 ms

5874f79b1f8515966b71d6507aff8bf01b87b612

557 ms

adsbygoogle.js

51 ms

hatena_dfp2.js

1024 ms

Our browser made a total of 186 requests to load all elements on the main page. We found that 4% of them (8 requests) were addressed to the original Watts.hateblo.jp, 8% (14 requests) were made to Apis.google.com and 6% (11 requests) were made to Blog.st-hatena.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source S.st-hatena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (14%)

Content Size

13.3 MB

After Optimization

11.4 MB

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

HTML Optimization

-80%

Potential reduce by 124.4 kB

  • Original 155.2 kB
  • After minification 145.9 kB
  • After compression 30.8 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 124.4 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 1.1 MB

  • Original 12.2 MB
  • After minification 11.1 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. Watts Hateblo images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 595.3 kB

  • Original 869.3 kB
  • After minification 719.3 kB
  • After compression 274.0 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 595.3 kB or 68% of the original size.

CSS Optimization

-77%

Potential reduce by 5.9 kB

  • Original 7.7 kB
  • After minification 5.7 kB
  • After compression 1.8 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. Watts.hateblo.jp needs all CSS files to be minified and compressed as it can save up to 5.9 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 94 (56%)

Requests Now

169

After Optimization

75

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

Accessibility Review

watts.hateblo.jp accessibility score

85

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

watts.hateblo.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

watts.hateblo.jp SEO score

84

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

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

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Watts.hateblo.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 Watts.hateblo.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

Open Graph data is detected on the main page of Watts Hateblo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: