Tools & Wizards About Us
yo-hemmi.net screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

yo-hemmi.net

辺見庸ブログ Yo Hemmi Weblog

Page Load Speed

2.6 sec in total

First Response

552 ms

Resources Loaded

1.8 sec

Page Rendered

234 ms

yo-hemmi.net screenshot

About Website

Visit yo-hemmi.net now to see the best up-to-date Yo Hemmi content for Japan and also check out these interesting facts you probably never knew about yo-hemmi.net

辺見庸公式ウェブサイト。近況,原稿発表,新刊刊行,活動予定その他のご案内。無断引用、転載を禁じます。

Visit yo-hemmi.net

Key Findings

We analyzed Yo-hemmi.net page load time and found that the first response time was 552 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

yo-hemmi.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value5,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

yo-hemmi.net

552 ms

insert-ad-legacy.min.js

669 ms

styles-index.css

157 ms

user-common.css

691 ms

ad_plugin.js

728 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Yo-hemmi.net, 45% (13 requests) were made to Blog.seesaa.jp and 14% (4 requests) were made to Yohemmi.up.seesaa.net. The less responsive or slowest element that took the longest time to load (786 ms) relates to the external source Blog.seesaa.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 21.0 kB (17%)

Content Size

121.4 kB

After Optimization

100.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yo-hemmi.net main page is 121.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. 25% of websites need less resources to load. Images take 84.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 17.4 kB

  • Original 23.1 kB
  • After minification 20.5 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 2.6 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.4 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 21 B

  • Original 84.1 kB
  • After minification 84.1 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. Yo Hemmi images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 1.4 kB

  • Original 10.6 kB
  • After minification 10.6 kB
  • After compression 9.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 1.4 kB or 13% of the original size.

CSS Optimization

-61%

Potential reduce by 2.2 kB

  • Original 3.6 kB
  • After minification 1.6 kB
  • After compression 1.4 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. Yo-hemmi.net needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (54%)

Requests Now

28

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

yo-hemmi.net

yo-hemmi.net

552 ms

insert-ad-legacy.min.js

insert-ad-legacy.min.js

669 ms

styles-index.css

styles-index.css

157 ms

user-common.css

user-common.css

691 ms

ad_plugin.js

ad_plugin.js

728 ms

bl-bookmarks.js

bl-bookmarks.js

786 ms

js

js

63 ms

E6B688E5A4B1-c6837-thumbnail2.jpg

E6B688E5A4B1-c6837-thumbnail2.jpg

29 ms

6E69C8830E697A5-thumbnail2.jpg

6E69C8830E697A5-thumbnail2.jpg

94 ms

E6A281E79FB3E697A5E38195E38293-thumbnail2.jpg

E6A281E79FB3E697A5E38195E38293-thumbnail2.jpg

266 ms

bg.gif

bg.gif

342 ms

fan_received.gif

fan_received.gif

180 ms

seesaablog.gif

seesaablog.gif

179 ms

body_bg.gif

body_bg.gif

338 ms

header.gif

header.gif

325 ms

sidetitle.gif

sidetitle.gif

334 ms

date.gif

date.gif

332 ms

listCategoryArticle.gif

listCategoryArticle.gif

337 ms

itm.js

itm.js

55 ms

bookmark_button.js

bookmark_button.js

50 ms

widgets.js

widgets.js

52 ms

button-only@2x.png

button-only@2x.png

73 ms

bookmark.gif

bookmark.gif

179 ms

sdk.js

sdk.js

42 ms

audience

audience

430 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

154 ms

sdk.js

sdk.js

6 ms

43 ms

settings

settings

72 ms

Accessibility Review

yo-hemmi.net accessibility score

62

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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

yo-hemmi.net best practices score

67

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

yo-hemmi.net SEO score

90

Search Engine Optimization Advices

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yo-hemmi.net 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 Yo-hemmi.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

yo-hemmi.net

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