Tools & Wizards About Us
hanagasa.jp screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

hanagasa.jp

山形花笠まつり

Page Load Speed

13.3 sec in total

First Response

559 ms

Resources Loaded

11.8 sec

Page Rendered

926 ms

hanagasa.jp screenshot

About Website

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

山形花笠まつり公式ホームページです。

Visit hanagasa.jp

Key Findings

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

Performance Metrics

hanagasa.jp performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.238

52/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

hanagasa.jp

559 ms

hanagasa.jp

873 ms

jquery-3.3.1.min.js

552 ms

jquery-ui.min.js

792 ms

common.css

637 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 81% of them (54 requests) were addressed to the original Hanagasa.jp, 12% (8 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Hanagasa.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 551.5 kB (7%)

Content Size

7.9 MB

After Optimization

7.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hanagasa.jp main page is 7.9 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. Only a small number of websites need less resources to load. Images take 7.7 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 19.2 kB

  • Original 24.8 kB
  • After minification 22.2 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 19.2 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 374.3 kB

  • Original 7.7 MB
  • After minification 7.3 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. Hanagasa images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 96.8 kB

  • Original 148.7 kB
  • After minification 146.7 kB
  • After compression 51.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 96.8 kB or 65% of the original size.

CSS Optimization

-72%

Potential reduce by 61.3 kB

  • Original 85.2 kB
  • After minification 62.2 kB
  • After compression 23.8 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. Hanagasa.jp needs all CSS files to be minified and compressed as it can save up to 61.3 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (35%)

Requests Now

48

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hanagasa.jp

hanagasa.jp

559 ms

hanagasa.jp

hanagasa.jp

873 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

552 ms

jquery-ui.min.js

jquery-ui.min.js

792 ms

common.css

common.css

637 ms

size_xs.css

size_xs.css

488 ms

top.css

top.css

652 ms

jquery-mainmenu.js

jquery-mainmenu.js

494 ms

mainmenu.css

mainmenu.css

651 ms

custom.js

custom.js

658 ms

picturefill.min.js

picturefill.min.js

724 ms

news_include_top.js

news_include_top.js

798 ms

css2

css2

40 ms

all.css

all.css

41 ms

swiper.css

swiper.css

36 ms

swiper.js

swiper.js

48 ms

size_sm.css

size_sm.css

173 ms

size_md.css

size_md.css

166 ms

size_lg.css

size_lg.css

160 ms

size_xl.css

size_xl.css

159 ms

logo.png

logo.png

286 ms

icon_home_black.png

icon_home_black.png

285 ms

slider_buyou_s.jpg

slider_buyou_s.jpg

866 ms

slider_miss_s.jpg

slider_miss_s.jpg

711 ms

slider_yomoyama_s.jpg

slider_yomoyama_s.jpg

989 ms

slider_202103_s.jpg

slider_202103_s.jpg

857 ms

slider_202201_s.jpg

slider_202201_s.jpg

618 ms

topics_ad.jpg

topics_ad.jpg

934 ms

topics_goods.jpg

topics_goods.jpg

802 ms

topics_miss.jpg

topics_miss.jpg

1190 ms

topics_tobiiri.jpg

topics_tobiiri.jpg

989 ms

topics_photo.jpg

topics_photo.jpg

1679 ms

topics_youtube.jpg

topics_youtube.jpg

1025 ms

topics_instagram.jpg

topics_instagram.jpg

1100 ms

bn_tohoku_kizuna.png

bn_tohoku_kizuna.png

1162 ms

bn_natsumatsuri.jpg

bn_natsumatsuri.jpg

1156 ms

bn_hanagasadaiko.gif

bn_hanagasadaiko.gif

1185 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

146 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

198 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

265 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

265 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

423 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

445 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

446 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

447 ms

icon_hngs_pare.png

icon_hngs_pare.png

1129 ms

arrow_gray.png

arrow_gray.png

1182 ms

bg_hngs_pattern.png

bg_hngs_pattern.png

1404 ms

bg_footer.png

bg_footer.png

1716 ms

slider_buyou.jpg

slider_buyou.jpg

1887 ms

slider_miss.jpg

slider_miss.jpg

2120 ms

slider_yomoyama.jpg

slider_yomoyama.jpg

3298 ms

slider_202103.jpg

slider_202103.jpg

1601 ms

slider_202201.jpg

slider_202201.jpg

1888 ms

slide_buyou.jpg

slide_buyou.jpg

1774 ms

slide_miss.jpg

slide_miss.jpg

1878 ms

slide_yomoyama.jpg

slide_yomoyama.jpg

1945 ms

slide_message.jpg

slide_message.jpg

2036 ms

slide_buyou_s.jpg

slide_buyou_s.jpg

2043 ms

slide_miss_s.jpg

slide_miss_s.jpg

2050 ms

slide_yomoyama_s.jpg

slide_yomoyama_s.jpg

2116 ms

slide_message_s.jpg

slide_message_s.jpg

2194 ms

fa-brands-400.woff

fa-brands-400.woff

141 ms

top_genre.cgi

top_genre.cgi

2223 ms

news_85_t.png

news_85_t.png

179 ms

news_82_01.JPG

news_82_01.JPG

6955 ms

print.css

print.css

166 ms

Accessibility Review

hanagasa.jp accessibility score

97

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.

Best Practices

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

SEO Factors

hanagasa.jp SEO score

82

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

Links do not have descriptive text

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

hanagasa.jp

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