Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

stalemate.hateblo.jp

25セントの恋人ごっこ

Page Load Speed

5.8 sec in total

First Response

520 ms

Resources Loaded

4.7 sec

Page Rendered

534 ms

stalemate.hateblo.jp screenshot

About Website

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

ライトノベル作家兼労働者兼猫の下僕の備忘録です。

Visit stalemate.hateblo.jp

Key Findings

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

Performance Metrics

stalemate.hateblo.jp performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value2,800 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

stalemate.hateblo.jp

520 ms

blog.css

770 ms

5076e2b81631d1164f82ab72f8f6aff6e38f5d62

344 ms

line-button.js

350 ms

adsbygoogle.js

65 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Stalemate.hateblo.jp, 11% (9 requests) were made to Blog.st-hatena.com and 7% (6 requests) were made to B.st-hatena.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Blog.st-hatena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (79%)

Content Size

3.0 MB

After Optimization

618.5 kB

In fact, the total size of Stalemate.hateblo.jp main page is 3.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. 55% of websites need less resources to load. Javascripts take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 53.4 kB

  • Original 70.8 kB
  • After minification 65.0 kB
  • After compression 17.4 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 53.4 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 2.0 kB

  • Original 56.2 kB
  • After minification 54.3 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. Stalemate Hateblo images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 2.2 MB

  • Original 2.7 MB
  • After minification 2.0 MB
  • After compression 530.2 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 2.2 MB or 81% of the original size.

CSS Optimization

-83%

Potential reduce by 83.8 kB

  • Original 100.5 kB
  • After minification 82.9 kB
  • After compression 16.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. Stalemate.hateblo.jp needs all CSS files to be minified and compressed as it can save up to 83.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (61%)

Requests Now

72

After Optimization

28

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

Accessibility Review

stalemate.hateblo.jp accessibility score

97

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

Best Practices

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

stalemate.hateblo.jp SEO score

91

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

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