Tools & Wizards About Us
otomiya.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

otomiya.com

釣りのことなら｜魚と遊ぼ！海釣り道場

Page Load Speed

9.6 sec in total

First Response

568 ms

Resources Loaded

8.6 sec

Page Rendered

470 ms

otomiya.com screenshot

About Website

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

釣り入門からボウズ退散まで釣りの仕掛け・釣り方・釣り具選びを楽しい図解で解説。FAQやBBS・魚料理・WEB素材集など爆釣コンテンツ満載！

Visit otomiya.com

Key Findings

We analyzed Otomiya.com page load time and found that the first response time was 568 ms and then it took 9.1 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

otomiya.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.143

78/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

otomiya.com

568 ms

otomiya.com

1526 ms

js

72 ms

style.min.css

217 ms

styles.css

368 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 48% of them (39 requests) were addressed to the original Otomiya.com, 12% (10 requests) were made to Googleads.g.doubleclick.net and 9% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Otomiya.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 527.9 kB (30%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Otomiya.com main page is 1.7 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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 205.9 kB

  • Original 236.2 kB
  • After minification 231.6 kB
  • After compression 30.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. 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 205.9 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 931 B

  • Original 288.9 kB
  • After minification 287.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. Otomiya images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 185.2 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 830.0 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 185.2 kB or 18% of the original size.

CSS Optimization

-70%

Potential reduce by 135.8 kB

  • Original 192.9 kB
  • After minification 83.5 kB
  • After compression 57.0 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. Otomiya.com needs all CSS files to be minified and compressed as it can save up to 135.8 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (64%)

Requests Now

74

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

otomiya.com

otomiya.com

568 ms

otomiya.com

otomiya.com

1526 ms

js

js

72 ms

style.min.css

style.min.css

217 ms

styles.css

styles.css

368 ms

frontend.min.css

frontend.min.css

709 ms

flatpickr.min.css

flatpickr.min.css

534 ms

select2.min.css

select2.min.css

532 ms

style.css

style.css

892 ms

keyframes.css

keyframes.css

535 ms

font-awesome.min.css

font-awesome.min.css

538 ms

style.css

style.css

1095 ms

baguetteBox.min.css

baguetteBox.min.css

702 ms

swiper-bundle.min.css

swiper-bundle.min.css

83 ms

style.css

style.css

716 ms

keyframes.css

keyframes.css

718 ms

jquery.lazyloadxt.spinner.css

jquery.lazyloadxt.spinner.css

870 ms

jquery.min.js

jquery.min.js

81 ms

jquery-migrate.min.js

jquery-migrate.min.js

82 ms

flatpickr.min.js

flatpickr.min.js

1048 ms

select2.min.js

select2.min.js

1094 ms

adsbygoogle.js

adsbygoogle.js

205 ms

scripts.js

scripts.js

896 ms

frontend.min.js

frontend.min.js

1044 ms

api.js

api.js

82 ms

script.js

script.js

1055 ms

baguetteBox.min.js

baguetteBox.min.js

1107 ms

comment-reply.min.js

comment-reply.min.js

1230 ms

javascript.js

javascript.js

1230 ms

javascript.js

javascript.js

1233 ms

jquery.lazyloadxt.extra.min.js

jquery.lazyloadxt.extra.min.js

1265 ms

jquery.lazyloadxt.srcset.min.js

jquery.lazyloadxt.srcset.min.js

1264 ms

jquery.lazyloadxt.extend.js

jquery.lazyloadxt.extend.js

1265 ms

adsbygoogle.js

adsbygoogle.js

268 ms

clipboard.min.js

clipboard.min.js

80 ms

js

js

52 ms

analytics.js

analytics.js

16 ms

collect

collect

60 ms

access.php

access.php

5379 ms

title.png

title.png

646 ms

lazy_placeholder.gif

lazy_placeholder.gif

312 ms

loading.gif

loading.gif

369 ms

no-amp-logo.png

no-amp-logo.png

370 ms

footer.png

footer.png

370 ms

show_ads_impl.js

show_ads_impl.js

223 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1293 ms

recaptcha__en.js

recaptcha__en.js

84 ms

syogyo-wara.png

syogyo-wara.png

328 ms

biggner800-1.png

biggner800-1.png

420 ms

firstgear800.png

firstgear800.png

555 ms

dic800.png

dic800.png

882 ms

zrt_lookup.html

zrt_lookup.html

55 ms

ads

ads

502 ms

otomiya800.png

otomiya800.png

739 ms

ads

ads

455 ms

ads

ads

387 ms

load_preloaded_resource.js

load_preloaded_resource.js

265 ms

abg_lite.js

abg_lite.js

431 ms

s

s

49 ms

window_focus.js

window_focus.js

264 ms

qs_click_protection.js

qs_click_protection.js

283 ms

ufs_web_display.js

ufs_web_display.js

49 ms

bbcd6bf18c20baa1b2adeb195de9b551.js

bbcd6bf18c20baa1b2adeb195de9b551.js

47 ms

icon.png

icon.png

47 ms

reactive_library.js

reactive_library.js

244 ms

ads

ads

358 ms

ads

ads

315 ms

ads

ads

334 ms

ads

ads

331 ms

css

css

169 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

36 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

34 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

38 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

39 ms

activeview

activeview

174 ms

css

css

26 ms

css

css

150 ms

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

16 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

145 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

144 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

84 ms

font

font

85 ms

Accessibility Review

otomiya.com accessibility score

87

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

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

High

Page has valid source maps

SEO Factors

otomiya.com SEO score

90

Search Engine Optimization Advices

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

otomiya.com

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