Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

hinata.me

hinata〜もっとそとが好きになる〜 | キャンプ・アウトドア情報メディアhinata

Page Load Speed

9.5 sec in total

First Response

533 ms

Resources Loaded

6.9 sec

Page Rendered

2.1 sec

hinata.me screenshot

About Website

Visit hinata.me now to see the best up-to-date Hinata content for Japan and also check out these interesting facts you probably never knew about hinata.me

hinataは「もっとそとが好きになる」をコンセプトに、キャンプ・アウトドアに関する情報を紹介するWEBマガジンです。キャンプで役に立つギア情報や、そと遊びが楽しくなる読み物を配信しています。

Visit hinata.me

Key Findings

We analyzed Hinata.me page load time and found that the first response time was 533 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

hinata.me performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value2,290 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

hinata.me

533 ms

hinata.me

996 ms

application-2a1edbd4515bb7b6d112691f8e1756e9fef4eabac2abfe8451c38e4564666b41.css

301 ms

adsbygoogle.js

36 ms

application-ecf3bdbab17bd2eb332d36ba9d3f346f8c0e5bff1a090f5d223fba7d6376d553.js

896 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 12% of them (14 requests) were addressed to the original Hinata.me, 38% (46 requests) were made to S3-ap-northeast-1.amazonaws.com and 11% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source S3-ap-northeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.4 kB (2%)

Content Size

11.8 MB

After Optimization

11.5 MB

In fact, the total size of Hinata.me main page is 11.8 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 11.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 91.1 kB

  • Original 108.5 kB
  • After minification 95.1 kB
  • After compression 17.3 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 13.3 kB, which is 12% 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 91.1 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 172.0 kB

  • Original 11.6 MB
  • After minification 11.4 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. Hinata images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 9.9 kB

  • Original 108.3 kB
  • After minification 108.1 kB
  • After compression 98.4 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

-72%

Potential reduce by 407 B

  • Original 564 B
  • After minification 538 B
  • After compression 157 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. Hinata.me needs all CSS files to be minified and compressed as it can save up to 407 B or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (32%)

Requests Now

117

After Optimization

79

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

Accessibility Review

hinata.me accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Links do not have a discernible name

Best Practices

hinata.me best practices score

77

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

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

hinata.me SEO score

91

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

    N/A

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

Open Graph data is detected on the main page of Hinata. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: