3.3 sec in total
967 ms
2.1 sec
225 ms
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.comWe analyzed Otomiya.com page load time and found that the first response time was 967 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
otomiya.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value6.1 s
12/100
25%
Value9.9 s
10/100
10%
Value12,220 ms
0/100
30%
Value0.14
79/100
15%
Value22.1 s
1/100
10%
967 ms
542 ms
16 ms
608 ms
60 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 34% of them (14 requests) were addressed to the original Otomiya.com, 12% (5 requests) were made to Pagead2.googlesyndication.com and 12% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (974 ms) belongs to the original domain Otomiya.com.
Page size can be reduced by 36.5 kB (24%)
151.1 kB
114.6 kB
In fact, the total size of Otomiya.com main page is 151.1 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. 25% of websites need less resources to load. Images take 70.7 kB which makes up the majority of the site volume.
Potential reduce by 20.1 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 20.1 kB or 69% of the original size.
Potential reduce by 1.0 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.
Potential reduce by 12.3 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 12.3 kB or 26% of the original size.
Potential reduce by 3.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. Otomiya.com needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 75% of the original size.
Number of requests can be reduced by 18 (46%)
39
21
The browser has sent 39 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 11 to 1 for JavaScripts and as a result speed up the page load time.
otomiya.com
967 ms
styles-top.css
542 ms
brand
16 ms
bbs256.gif
608 ms
brand
60 ms
show_ads.js
11 ms
ads.js
236 ms
dream.cgi
565 ms
bg.gif
192 ms
title-index.jpg
542 ms
folder.gif
244 ms
h3-bg.gif
379 ms
allow.gif
378 ms
ccg468.gif
758 ms
column468.gif
764 ms
otomiya120.gif
439 ms
otomiya1212.gif
974 ms
kamon120b.gif
566 ms
GLbanner120b.gif
635 ms
google_custom_search_watermark.gif
63 ms
ca-pub-1646051718105597.js
46 ms
zrt_lookup.html
38 ms
show_ads_impl.js
58 ms
ads-common.js
300 ms
ads
117 ms
osd.js
13 ms
ads
222 ms
abg.js
24 ms
cm
273 ms
ga.js
57 ms
m_js_controller.js
5 ms
s
11 ms
googlelogo_color_112x36dp.png
63 ms
imgad
19 ms
nessie_icon_tiamat_white.png
27 ms
x_button_blue2.png
27 ms
__utm.gif
13 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
4 ms
100-30.gif
9 ms
150 ms
519An+--y+L._SL80_.jpg
8 ms
otomiya.com accessibility score
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
[aria-*] attributes do not match their roles
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
otomiya.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
otomiya.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
SHIFT_JIS
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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Otomiya.com 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.
otomiya.com
Open Graph description is not detected on the main page of Otomiya. 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: