Tools & Wizards About Us
mikimotoharuhiko.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

mikimotoharuhiko.com

美樹本晴彦 公式サイト -Interlude-

Page Load Speed

4.3 sec in total

First Response

622 ms

Resources Loaded

3.5 sec

Page Rendered

93 ms

mikimotoharuhiko.com screenshot

About Website

Welcome to mikimotoharuhiko.com homepage info - get ready to check Mikimotoharuhiko best content for Japan right away, or after learning these important things about mikimotoharuhiko.com

美樹本晴彦 公式サイト

Visit mikimotoharuhiko.com

Key Findings

We analyzed Mikimotoharuhiko.com page load time and found that the first response time was 622 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

mikimotoharuhiko.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

mikimotoharuhiko.com

622 ms

top.css

185 ms

common.js

357 ms

analytics.js

21 ms

btn_environment.gif

548 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 94% of them (34 requests) were addressed to the original Mikimotoharuhiko.com, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Mikimotoharuhiko.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.5 kB (1%)

Content Size

622.9 kB

After Optimization

615.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mikimotoharuhiko.com main page is 622.9 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. 15% of websites need less resources to load. Images take 589.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.5 kB

  • Original 9.2 kB
  • After minification 7.8 kB
  • After compression 2.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 1.4 kB, which is 16% 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 6.5 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 589.9 kB
  • After minification 589.9 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. Mikimotoharuhiko images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 755 B

  • Original 22.6 kB
  • After minification 22.6 kB
  • After compression 21.9 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

-21%

Potential reduce by 251 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 970 B

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. Mikimotoharuhiko.com needs all CSS files to be minified and compressed as it can save up to 251 B or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (31%)

Requests Now

35

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mikimotoharuhiko.com

mikimotoharuhiko.com

622 ms

top.css

top.css

185 ms

common.js

common.js

357 ms

analytics.js

analytics.js

21 ms

btn_environment.gif

btn_environment.gif

548 ms

btn_sitemap.gif

btn_sitemap.gif

558 ms

btn_link.gif

btn_link.gif

641 ms

foot_txt.gif

foot_txt.gif

643 ms

mikimoto_site.gif

mikimoto_site.gif

212 ms

logo.gif

logo.gif

232 ms

main_image_2023.jpg

main_image_2023.jpg

2210 ms

btn_info.gif

btn_info.gif

371 ms

btn_profile.gif

btn_profile.gif

372 ms

btn_gallery.gif

btn_gallery.gif

351 ms

btn_works.gif

btn_works.gif

429 ms

btn_diary.gif

btn_diary.gif

410 ms

btn_fanmail.gif

btn_fanmail.gif

528 ms

title_info.gif

title_info.gif

543 ms

marker01.gif

marker01.gif

543 ms

marker02.gif

marker02.gif

639 ms

info_foot.gif

info_foot.gif

641 ms

title_now.gif

title_now.gif

718 ms

title_diary.gif

title_diary.gif

714 ms

diary_foot.gif

diary_foot.gif

715 ms

btn_contact.gif

btn_contact.gif

816 ms

collect

collect

27 ms

btn_environment_f2.gif

btn_environment_f2.gif

179 ms

btn_sitemap_f2.gif

btn_sitemap_f2.gif

178 ms

btn_link_f2.gif

btn_link_f2.gif

183 ms

btn_info_f2.gif

btn_info_f2.gif

182 ms

btn_profile_f2.gif

btn_profile_f2.gif

179 ms

btn_gallery_f2.gif

btn_gallery_f2.gif

174 ms

btn_works_f2.gif

btn_works_f2.gif

173 ms

btn_diary_f2.gif

btn_diary_f2.gif

178 ms

btn_fanmail_f2.gif

btn_fanmail_f2.gif

173 ms

btn_contact_f2.gif

btn_contact_f2.gif

344 ms

Accessibility Review

mikimotoharuhiko.com accessibility score

78

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

Image elements do not have [alt] attributes

Best Practices

mikimotoharuhiko.com 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

mikimotoharuhiko.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mikimotoharuhiko.com 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 Mikimotoharuhiko.com main page’s claimed encoding is euc-jp. 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

mikimotoharuhiko.com

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