Tools & Wizards About Us
yokokawa-mikosi.net screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

yokokawa-mikosi.net

横川神輿會公式サイト

Page Load Speed

16.2 sec in total

First Response

597 ms

Resources Loaded

15.2 sec

Page Rendered

377 ms

yokokawa-mikosi.net screenshot

About Website

Visit yokokawa-mikosi.net now to see the best up-to-date Yokokawa Mikosi content and also check out these interesting facts you probably never knew about yokokawa-mikosi.net

栃木県宇都宮市ふるさと宮まつりで渡御！横川神輿會公式サイト

Visit yokokawa-mikosi.net

Key Findings

We analyzed Yokokawa-mikosi.net page load time and found that the first response time was 597 ms and then it took 15.6 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

yokokawa-mikosi.net performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.178

68/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

yokokawa-mikosi.net

597 ms

www.yokokawa-mikosi.net

6686 ms

import.css

385 ms

jquery.min.js

225 ms

jquery-ui.min.js

305 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 82% of them (37 requests) were addressed to the original Yokokawa-mikosi.net, 4% (2 requests) were made to Ajax.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Yokokawa-mikosi.net.

Page Optimization Overview & Recommendations

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

Content Size

174.4 kB

After Optimization

144.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yokokawa-mikosi.net main page is 174.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. 20% of websites need less resources to load. Images take 126.1 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 11.5 kB

  • Original 16.6 kB
  • After minification 15.6 kB
  • After compression 5.2 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 11.5 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 245 B

  • Original 126.1 kB
  • After minification 125.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. Yokokawa Mikosi images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 10.4 kB

  • Original 19.5 kB
  • After minification 17.5 kB
  • After compression 9.1 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 10.4 kB or 53% of the original size.

CSS Optimization

-66%

Potential reduce by 8.0 kB

  • Original 12.1 kB
  • After minification 9.2 kB
  • After compression 4.1 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. Yokokawa-mikosi.net needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (58%)

Requests Now

43

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yokokawa Mikosi. 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 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yokokawa-mikosi.net

yokokawa-mikosi.net

597 ms

www.yokokawa-mikosi.net

www.yokokawa-mikosi.net

6686 ms

import.css

import.css

385 ms

jquery.min.js

jquery.min.js

225 ms

jquery-ui.min.js

jquery-ui.min.js

305 ms

smartRollover.js

smartRollover.js

391 ms

writeflash.js

writeflash.js

411 ms

swfobject.js

swfobject.js

394 ms

urchin.js

urchin.js

126 ms

reset.css

reset.css

416 ms

style.css

style.css

424 ms

structure.css

structure.css

426 ms

top.css

top.css

433 ms

topics.css

topics.css

427 ms

words.css

words.css

448 ms

goods.css

goods.css

829 ms

profiles.css

profiles.css

875 ms

link.css

link.css

855 ms

inquiry.css

inquiry.css

862 ms

photo.css

photo.css

899 ms

oitachi.css

oitachi.css

890 ms

iroiro.css

iroiro.css

1244 ms

schedule.css

schedule.css

1252 ms

top_on.gif

top_on.gif

1190 ms

topics_off.gif

topics_off.gif

1177 ms

greeting_off.gif

greeting_off.gif

1192 ms

schedule_off.gif

schedule_off.gif

1191 ms

photo_off.gif

photo_off.gif

1192 ms

words_off.gif

words_off.gif

1189 ms

profiles_off.gif

profiles_off.gif

1549 ms

goods_off.gif

goods_off.gif

1538 ms

recruiment_off.gif

recruiment_off.gif

1544 ms

inquiry_off.gif

inquiry_off.gif

1541 ms

side_bg_c.png

side_bg_c.png

1577 ms

blog.gif

blog.gif

1596 ms

footer_img.gif

footer_img.gif

3157 ms

all.js

all.js

264 ms

header.jpg

header.jpg

6229 ms

side_bg_b.png

side_bg_b.png

1996 ms

side_bg_a.png

side_bg_a.png

2013 ms

side_icon.png

side_icon.png

2930 ms

__utm.gif

__utm.gif

41 ms

139 ms

xd_arbiter.php

xd_arbiter.php

205 ms

xd_arbiter.php

xd_arbiter.php

443 ms

Accessibility Review

yokokawa-mikosi.net accessibility score

66

Accessibility Issues

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

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

yokokawa-mikosi.net 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

yokokawa-mikosi.net SEO score

71

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yokokawa-mikosi.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 Yokokawa-mikosi.net 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

yokokawa-mikosi.net

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