8 sec in total
762 ms
6.7 sec
542 ms
Welcome to get-fishing.jp homepage info - get ready to check Get Fishing best content right away, or after learning these important things about get-fishing.jp
アリゲーター&剛樹正規販売代理店「GETフィッシング」(ゲットフィッシング)のサイト。アリゲーター&剛樹ロッドをはじめ、アリゲーター技研&剛樹製品については豊富なノウハウがあります。大物釣り 泳がせ釣り 遠征釣り 深場釣りなど、船釣りのことならおまかせください。
Visit get-fishing.jpWe analyzed Get-fishing.jp page load time and found that the first response time was 762 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
get-fishing.jp performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value2.2 s
94/100
25%
Value5.5 s
55/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value2.1 s
99/100
10%
762 ms
975 ms
192 ms
381 ms
759 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that all of those requests were addressed to Get-fishing.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Get-fishing.jp.
Page size can be reduced by 112.8 kB (1%)
7.5 MB
7.4 MB
In fact, the total size of Get-fishing.jp main page is 7.5 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. 35% of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.
Potential reduce by 19.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. 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 19.7 kB or 77% of the original size.
Potential reduce by 44.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. Get Fishing images are well optimized though.
Potential reduce by 11.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 11.1 kB or 75% of the original size.
Potential reduce by 37.4 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. Get-fishing.jp needs all CSS files to be minified and compressed as it can save up to 37.4 kB or 92% of the original size.
We found no issues to fix!
49
49
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Get Fishing. According to our analytics all requests are already optimized.
get-fishing.jp
762 ms
get-fishing.jp
975 ms
AC_RunActiveContent.js
192 ms
get_fishing.js
381 ms
get_fishing.css
759 ms
wcax.js
623 ms
menu01_r1_c1.jpg
494 ms
menu01_r1_c2.jpg
322 ms
menu01_r2_c2.jpg
653 ms
menu01_r2_c3.jpg
557 ms
menu01_r2_c4.jpg
564 ms
menu01_r2_c5.jpg
714 ms
menu01_r2_c6.jpg
714 ms
menu01_r3_c2.jpg
713 ms
img1214a2452_1.jpg
1497 ms
spacer.gif
753 ms
menu02_r1_c1.jpg
861 ms
menu02_r1_c2.jpg
933 ms
menu02_r1_c7.jpg
1179 ms
menu02_r1_c3.jpg
948 ms
menu02_r1_c4.jpg
941 ms
menu02_r1_c5.jpg
1068 ms
menu02_r1_c6.jpg
1152 ms
img096fi4557_1.jpg
1130 ms
banner05.jpg
1183 ms
banner03.jpg
1275 ms
banner01.jpg
1320 ms
img1043f2010_1.jpg
1370 ms
img1015b4943_1.jpg
1411 ms
img182ca5325_1.jpg
1418 ms
img1825f5303_1.jpg
1483 ms
info_ttl.gif
1508 ms
img247kb1145_1.JPG
4207 ms
img247ka5845_1.jpg
1876 ms
tenpo_ttl.gif
1653 ms
img0952a2056_1.jpg
2310 ms
img093uh0752_1.JPG
2908 ms
img0952a2141_1.jpg
2076 ms
access.gif
1888 ms
img197s62405_1.jpg
2109 ms
tenpo_photo02.jpg
1891 ms
tenpo_photo03.jpg
1950 ms
img197s62733_1.jpg
2366 ms
bg.jpg
2341 ms
top_left_area.jpg
2091 ms
menu01_r2_c2_f2.jpg
379 ms
menu01_r2_c3_f2.jpg
241 ms
menu01_r2_c4_f2.jpg
212 ms
menu01_r2_c5_f2.jpg
220 ms
menu01_r2_c6_f2.jpg
237 ms
menu01_r2_c7_f2.jpg
238 ms
get-fishing.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
get-fishing.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
get-fishing.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Get-fishing.jp 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 Get-fishing.jp 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.
get-fishing.jp
Open Graph description is not detected on the main page of Get Fishing. 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: