Tools & Wizards About Us
henari1.jp screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

henari1.jp

ドライブ＆ツーリングのネタ帳ORRの道路調査報告書

Page Load Speed

4.5 sec in total

First Response

823 ms

Resources Loaded

3.4 sec

Page Rendered

290 ms

henari1.jp screenshot

About Website

Welcome to henari1.jp homepage info - get ready to check Henari 1 best content for Japan right away, or after learning these important things about henari1.jp

日本全国の峠道をバイクで実走調査。廃道／隧道／酷道／旧道／林道の５部門に分け、数万枚の画像と共に累計１０００枚超に及ぶレポートで構成。全国の古い峠道を探訪し、古老への聞き取りを中心に考証考察を重ねた「歴史の道踏査報告書」も。

Visit henari1.jp

Key Findings

We analyzed Henari1.jp page load time and found that the first response time was 823 ms and then it took 3.7 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

henari1.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.313

37/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

henari1.jp

823 ms

lhs-acc.js

364 ms

counter.php

188 ms

writeBlogPartsObject.js

303 ms

urchin.js

5 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 55% of them (16 requests) were addressed to the original Henari1.jp, 14% (4 requests) were made to Counter1-cdn.fc2.com and 7% (2 requests) were made to Counter1.fc2.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Henari1.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.7 kB (74%)

Content Size

166.9 kB

After Optimization

43.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Henari1.jp main page is 166.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. HTML takes 134.1 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 118.2 kB

  • Original 134.1 kB
  • After minification 131.1 kB
  • After compression 16.0 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 118.2 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 790 B

  • Original 20.6 kB
  • After minification 19.8 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. Henari 1 images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 4.7 kB

  • Original 12.2 kB
  • After minification 11.5 kB
  • After compression 7.5 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 4.7 kB or 39% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

15

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

henari1.jp

henari1.jp

823 ms

lhs-acc.js

lhs-acc.js

364 ms

counter.php

counter.php

188 ms

writeBlogPartsObject.js

writeBlogPartsObject.js

303 ms

urchin.js

urchin.js

5 ms

cm

cm

250 ms

image001.gif

image001.gif

171 ms

image002.gif

image002.gif

2336 ms

image003.gif

image003.gif

320 ms

image004.gif

image004.gif

318 ms

image005.jpg

image005.jpg

834 ms

image006.gif

image006.gif

825 ms

image007.gif

image007.gif

1069 ms

image008.jpg

image008.jpg

474 ms

image009.gif

image009.gif

1401 ms

image010.jpg

image010.jpg

636 ms

image011.gif

image011.gif

1259 ms

image012.gif

image012.gif

1320 ms

image013.gif

image013.gif

1494 ms

image014.gif

image014.gif

1249 ms

counter_js.php

counter_js.php

95 ms

7.gif

7.gif

234 ms

3.gif

3.gif

232 ms

6.gif

6.gif

67 ms

0.gif

0.gif

79 ms

__utm.gif

__utm.gif

20 ms

ap-search-go-btn.gif

ap-search-go-btn.gif

15 ms

156 ms

searchbox-logo-126x32.gif

searchbox-logo-126x32.gif

8 ms

Accessibility Review

henari1.jp accessibility score

81

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

henari1.jp best practices score

67

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

henari1.jp SEO score

67

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

Document uses plugins

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Henari1.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Henari1.jp 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

henari1.jp

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