12.8 sec in total
2.5 sec
9.8 sec
446 ms
Welcome to yellowfish.jp homepage info - get ready to check Yellowfish best content for Russia right away, or after learning these important things about yellowfish.jp
中古釣具のイエローフィッシュは、ルアー、リール、竿などの釣り道具の通販・買取をしており、兵庫県神戸市、、徳島県小松島市、愛媛県松山市、沖縄県宜野湾市に店舗があります。ぜひ一度、YellowFishをご利用ください!
Visit yellowfish.jpWe analyzed Yellowfish.jp page load time and found that the first response time was 2.5 sec and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Yellowfish.jp rating and web reputation
yellowfish.jp performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value23.8 s
0/100
25%
Value12.5 s
3/100
10%
Value140 ms
95/100
30%
Value0.264
47/100
15%
Value6.4 s
60/100
10%
2521 ms
356 ms
579 ms
1182 ms
2216 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 88% of them (113 requests) were addressed to the original Yellowfish.jp, 3% (4 requests) were made to Google.com and 3% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Yellowfish.jp.
Page size can be reduced by 1.5 MB (27%)
5.4 MB
4.0 MB
In fact, the total size of Yellowfish.jp main page is 5.4 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. 45% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 98.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. This page needs HTML code to be minified as it can gain 38.8 kB, which is 34% 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 98.2 kB or 86% of the original size.
Potential reduce by 943.6 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. Obviously, Yellowfish needs image optimization as it can save up to 943.6 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 348.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 348.3 kB or 78% of the original size.
Potential reduce by 70.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. Yellowfish.jp needs all CSS files to be minified and compressed as it can save up to 70.8 kB or 84% of the original size.
Number of requests can be reduced by 37 (29%)
127
90
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yellowfish. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
yellowfish.jp
2521 ms
import.css
356 ms
jquery.lightbox-0.5.css
579 ms
jquery.js
1182 ms
jquery-1.6.4.js
2216 ms
jquery.lightbox-0.5.js
942 ms
dw_common.js
549 ms
JUDGE.JS
588 ms
smartRollover.js
731 ms
shadowbox.css
788 ms
shadowbox.js
1905 ms
jquery.min.js
74 ms
jquery.easing.1.3.js
1218 ms
slides.min.jquery.js
1144 ms
content.css
1254 ms
base.css
2163 ms
top.css
1162 ms
form.css
1246 ms
shop.css
1351 ms
jsapi
44 ms
state2.js
1278 ms
analytics.js
22 ms
logo.jpg
585 ms
choice.jpg
577 ms
beginner.jpg
194 ms
favorite.jpg
396 ms
cart.jpg
355 ms
login.jpg
188 ms
gear01_off.jpg
393 ms
g_icon.gif
395 ms
gear02_off.jpg
706 ms
gear03_off.jpg
561 ms
gear04_off.jpg
578 ms
gear05_off.jpg
771 ms
gear06_off.jpg
744 ms
webbnr01_off.jpg
1152 ms
webbnr02_off.jpg
1153 ms
webbnr03_off.jpg
962 ms
qr.jpg
1058 ms
shopping_guide.jpg
926 ms
guidebnr01_off.jpg
1157 ms
guidebnr02_off.jpg
1109 ms
guidebnr03_off.jpg
1154 ms
guidebnr04_off.jpg
1474 ms
guidebnr05_off.jpg
1323 ms
guidebnr06_off.jpg
1387 ms
news_topics.jpg
1383 ms
rss.jpg
1390 ms
ncate01_off.jpg
1389 ms
ncate02_off.jpg
1504 ms
ncate03_off.jpg
1575 ms
ncate04_off.jpg
1580 ms
ncate05_off.jpg
1582 ms
news_icon01.jpg
1581 ms
news_icon02.jpg
1648 ms
news_icon04.jpg
1689 ms
news_icon03.jpg
1770 ms
blog_off.jpg
1775 ms
widgets.js
47 ms
collect
56 ms
12 ms
default+en.css
3 ms
default+en.I.js
8 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
23 ms
syndication
94 ms
451713731144056832
140 ms
ti-da_blog.jpg
1786 ms
1452744630-555017_1.png
3526 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
2 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
6 ms
LLEVSugq_normal.jpeg
43 ms
1451610489-314135_1.jpg
2009 ms
1426323651-405317_1.jpg
2072 ms
1440664765-125905_1.jpg
2344 ms
1452838957-565514_1.jpg
1952 ms
1453787683-481710_1.jpg
2185 ms
prev.png
1969 ms
next.png
1984 ms
main_bnr03_off.jpg
2071 ms
jot
27 ms
main_bnr02_off.jpg
2012 ms
main_bnr04_off.jpg
2010 ms
search.jpg
2061 ms
search_btn.jpg
1967 ms
main_bnr01.jpg
2161 ms
latest_gear.jpg
1882 ms
new2.jpg
1838 ms
1456804663-173821_1.jpg
2416 ms
1456733884-385376_1.jpg
2286 ms
1456733716-825387_1.jpg
2369 ms
1456804940-563085_1.jpg
2765 ms
products_borderLine.jpg
1994 ms
1456804427-888095_1.jpg
2515 ms
1456729531-437163_1.jpg
2583 ms
1456733526-709026_1.jpg
2526 ms
1456729702-511654_1.jpg
2546 ms
1456732908-227210_1.jpg
3027 ms
1456800307-700729_1.jpg
2790 ms
1456801409-745085_1.jpg
2737 ms
1456804800-696445_1.jpg
2761 ms
1456800013-923421_1.jpg
2741 ms
1456733164-212638_1.jpg
2755 ms
1456729296-507027_1.jpg
3033 ms
1456800617-145807_1.jpg
3016 ms
rank.jpg
2735 ms
all.jpg
2745 ms
tenpo.jpg
2565 ms
guide_top.jpg
2335 ms
bnr_btm06_off.jpg
2329 ms
footer_logo.jpg
2239 ms
deliver.jpg
2192 ms
about_payment.jpg
2322 ms
credit.jpg
2229 ms
about_payment-51.jpg
2178 ms
footer_btn01_off.jpg
2144 ms
footer_btn02_off.jpg
2158 ms
footer_btn03_off.jpg
2178 ms
footer_btn04_off.jpg
2233 ms
flash_bnr.jpg
2183 ms
search_bg.jpg
2118 ms
pic_frame_middle.jpg
2142 ms
pic_frame_top.jpg
1975 ms
pic_frame_btm.jpg
1812 ms
guide_btm.jpg
1796 ms
footer_bg.jpg
1723 ms
payment_bg.jpg
1702 ms
cost_bg.jpg
1565 ms
1452744630-555017_1.png
2021 ms
loading.gif
1490 ms
yellowfish.jp 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-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
yellowfish.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
yellowfish.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yellowfish.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 Yellowfish.jp main page’s claimed encoding is euc-jp. 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.
yellowfish.jp
Open Graph description is not detected on the main page of Yellowfish. 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: