Tools & Wizards About Us
purefishing.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

purefishing.jp

釣具の総合メーカー　ピュア・フィッシング・ジャパン / PURE FISHING JAPAN

Page Load Speed

5 sec in total

First Response

334 ms

Resources Loaded

4.2 sec

Page Rendered

484 ms

purefishing.jp screenshot

About Website

Welcome to purefishing.jp homepage info - get ready to check PURE FISHING best content for Japan right away, or after learning these important things about purefishing.jp

釣具の総合メーカー　ピュア・フィッシング・ジャパン。最新の釣具製品からお知らせ、イベント情報、動画などをお届けいたします。

Visit purefishing.jp

Key Findings

We analyzed Purefishing.jp page load time and found that the first response time was 334 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

purefishing.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

purefishing.jp

334 ms

www.purefishing.jp

695 ms

gtm.js

64 ms

js

114 ms

cookie.min.js

172 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 66% of them (40 requests) were addressed to the original Purefishing.jp, 10% (6 requests) were made to Googletagmanager.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Purefishing.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.8 kB (3%)

Content Size

8.1 MB

After Optimization

7.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Purefishing.jp main page is 8.1 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. 65% of websites need less resources to load. Images take 7.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 21.7 kB

  • Original 27.5 kB
  • After minification 26.5 kB
  • After compression 5.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 21.7 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 118.0 kB

  • Original 7.2 MB
  • After minification 7.1 MB

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. PURE FISHING images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 59.4 kB

  • Original 747.4 kB
  • After minification 747.4 kB
  • After compression 688.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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 5.7 kB

  • Original 127.2 kB
  • After minification 127.2 kB
  • After compression 121.6 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. Purefishing.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (37%)

Requests Now

54

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

purefishing.jp

purefishing.jp

334 ms

www.purefishing.jp

www.purefishing.jp

695 ms

gtm.js

gtm.js

64 ms

js

js

114 ms

cookie.min.js

cookie.min.js

172 ms

ofi.min.js

ofi.min.js

341 ms

bundle2023.js

bundle2023.js

1477 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

672 ms

underscore-min.js

underscore-min.js

37 ms

commonScript.js

commonScript.js

505 ms

css

css

40 ms

swiper.min.css

swiper.min.css

508 ms

slick.css

slick.css

513 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

518 ms

common2023.css

common2023.css

1064 ms

customize.css

customize.css

669 ms

analytics.js

analytics.js

43 ms

destination

destination

63 ms

js

js

60 ms

js

js

75 ms

collect

collect

52 ms

collect

collect

97 ms

js

js

47 ms

search.json

search.json

1165 ms

logo_purefishing_2023.svg

logo_purefishing_2023.svg

170 ms

logo_purefishing_2023_white.svg

logo_purefishing_2023_white.svg

167 ms

logo_abugarcia_new20135_white.svg

logo_abugarcia_new20135_white.svg

176 ms

logo_berkley_new20135.svg

logo_berkley_new20135.svg

172 ms

PENN_Shield_logo.png

PENN_Shield_logo.png

332 ms

savagegear_header_main_white.svg

savagegear_header_main_white.svg

333 ms

plano_header_main.svg

plano_header_main.svg

331 ms

hardy_header_main.svg

hardy_header_main.svg

335 ms

Abugarcia_top1.jpg

Abugarcia_top1.jpg

988 ms

logo_abugarcia_2204.svg

logo_abugarcia_2204.svg

494 ms

Berkley_top2_withoutlogo.jpg

Berkley_top2_withoutlogo.jpg

1306 ms

PENN-Lifestyle-Slammer-IV-Exmouth-Alt28.jpg

PENN-Lifestyle-Slammer-IV-Exmouth-Alt28.jpg

1451 ms

SavageGear_top1_withoutlogo.jpg

SavageGear_top1_withoutlogo.jpg

1623 ms

Plano_top1_withoutlogo.jpg

Plano_top1_withoutlogo.jpg

672 ms

Hardy_top1_withoutlogo.jpg

Hardy_top1_withoutlogo.jpg

840 ms

logo_abugarcia_new20135.svg

logo_abugarcia_new20135.svg

1002 ms

logo_sns_instagram.svg

logo_sns_instagram.svg

1151 ms

logo_sns_x.svg

logo_sns_x.svg

1166 ms

savagegear_header_main.svg

savagegear_header_main.svg

1316 ms

Z32-fu6krKU.jpg

Z32-fu6krKU.jpg

1325 ms

7UtvBKHnPNo.jpg

7UtvBKHnPNo.jpg

1327 ms

VhJChU5TMCs.jpg

VhJChU5TMCs.jpg

1468 ms

FfgghkTCXxo.jpg

FfgghkTCXxo.jpg

1478 ms

PbEUjar_R-Y.jpg

PbEUjar_R-Y.jpg

1492 ms

logo_purefishing_2204_white.svg

logo_purefishing_2204_white.svg

1489 ms

ico_blank.png

ico_blank.png

1611 ms

uwt.js

uwt.js

49 ms

fbevents.js

fbevents.js

21 ms

lt.js

lt.js

191 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VQ.woff

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VQ.woff

48 ms

NotoSans-Regular.woff

NotoSans-Regular.woff

1594 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1Q.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1Q.woff

48 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RkBI95.woff

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RkBI95.woff

60 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

60 ms

adsct

adsct

103 ms

adsct

adsct

102 ms

err.gif

err.gif

729 ms

Accessibility Review

purefishing.jp accessibility score

87

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

purefishing.jp best practices score

83

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

Page has valid source maps

SEO Factors

purefishing.jp SEO score

82

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

High

robots.txt is not valid

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 Purefishing.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 Purefishing.jp 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

purefishing.jp

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