Report Summary

  • 42

    Performance

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

  • 77

    SEO

    Google-friendlier than
    36% of websites

eai.hateblo.jp

酢飯をおかずにご飯を食べる。

Page Load Speed

10.6 sec in total

First Response

522 ms

Resources Loaded

8 sec

Page Rendered

2 sec

eai.hateblo.jp screenshot

About Website

Welcome to eai.hateblo.jp homepage info - get ready to check Eai Hateblo best content for Japan right away, or after learning these important things about eai.hateblo.jp

備忘録です。

Visit eai.hateblo.jp

Key Findings

We analyzed Eai.hateblo.jp page load time and found that the first response time was 522 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

eai.hateblo.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

84/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value3,660 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

eai.hateblo.jp

522 ms

blog.css

800 ms

3fafd58f5d840e92e250a3c976c6a99ddcd87336

346 ms

line-button.js

497 ms

hatena_afc_ydn-compiled.js

351 ms

Our browser made a total of 193 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Eai.hateblo.jp, 10% (19 requests) were made to Cdn-ak.f.st-hatena.com and 5% (9 requests) were made to Blog.st-hatena.com. The less responsive or slowest element that took the longest time to load (5.9 sec) relates to the external source Cdn-ak.f.st-hatena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (23%)

Content Size

7.0 MB

After Optimization

5.4 MB

In fact, the total size of Eai.hateblo.jp main page is 7.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 116.0 kB

  • Original 138.7 kB
  • After minification 125.4 kB
  • After compression 22.7 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 116.0 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 442.0 kB

  • Original 5.3 MB
  • After minification 4.8 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. Eai Hateblo images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 964.0 kB

  • Original 1.5 MB
  • After minification 1.3 MB
  • After compression 493.3 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 964.0 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 118.0 kB

  • Original 141.0 kB
  • After minification 111.0 kB
  • After compression 22.9 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. Eai.hateblo.jp needs all CSS files to be minified and compressed as it can save up to 118.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 93 (52%)

Requests Now

178

After Optimization

85

The browser has sent 178 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eai 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 59 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

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

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

eai.hateblo.jp SEO score

77

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 Eai.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 Eai.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 Eai Hateblo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: