Tools & Wizards About Us
pazdesign.co.jp screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

pazdesign.co.jp

Pazdesign

Page Load Speed

10 sec in total

First Response

665 ms

Resources Loaded

8.6 sec

Page Rendered

725 ms

pazdesign.co.jp screenshot

About Website

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

It wants to be partner for anglers. 創業30周年を迎えたパズデザイン。皆様の思い出に残る物作りを目指して、これからも進み続けます。

Visit pazdesign.co.jp

Key Findings

We analyzed Pazdesign.co.jp page load time and found that the first response time was 665 ms and then it took 9.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.

Performance Metrics

pazdesign.co.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value19.9 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.194

63/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

pazdesign.co.jp

665 ms

pazdesign.co.jp

782 ms

main.css

191 ms

styles.css

377 ms

menu.css

493 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 62% of them (58 requests) were addressed to the original Pazdesign.co.jp, 20% (19 requests) were made to Static.xx.fbcdn.net and 11% (10 requests) were made to Pazdesign.sakura.ne.jp. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Pazdesign.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 515.9 kB (8%)

Content Size

6.6 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pazdesign.co.jp main page is 6.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 14.0 kB

  • Original 17.6 kB
  • After minification 16.8 kB
  • After compression 3.5 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 14.0 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 417.6 kB

  • Original 6.5 MB
  • After minification 6.0 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. Pazdesign images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 54.1 kB

  • Original 135.2 kB
  • After minification 133.9 kB
  • After compression 81.2 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 54.1 kB or 40% of the original size.

CSS Optimization

-80%

Potential reduce by 30.2 kB

  • Original 38.0 kB
  • After minification 28.6 kB
  • After compression 7.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. Pazdesign.co.jp needs all CSS files to be minified and compressed as it can save up to 30.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (34%)

Requests Now

91

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pazdesign.co.jp

pazdesign.co.jp

665 ms

pazdesign.co.jp

pazdesign.co.jp

782 ms

main.css

main.css

191 ms

styles.css

styles.css

377 ms

menu.css

menu.css

493 ms

css

css

52 ms

jquery.min.js

jquery.min.js

62 ms

tool.js

tool.js

508 ms

pagescroll.js

pagescroll.js

529 ms

opacity-rollover2.1.js

opacity-rollover2.1.js

560 ms

jquery.bxslider.js

jquery.bxslider.js

1206 ms

jquery.bxslider.css

jquery.bxslider.css

609 ms

a2.jpg

a2.jpg

224 ms

sale2024.jpg

sale2024.jpg

1808 ms

MB.jpg

MB.jpg

2454 ms

240214.jpg

240214.jpg

2860 ms

2024.jpg

2024.jpg

1327 ms

outletsale_2023.jpg

outletsale_2023.jpg

1455 ms

tagiri.jpg

tagiri.jpg

1903 ms

pic1.jpg

pic1.jpg

2628 ms

pic2.jpg

pic2.jpg

3260 ms

pic3.jpg

pic3.jpg

2633 ms

pic4.jpg

pic4.jpg

3201 ms

life.jpg

life.jpg

2850 ms

blog.jpg

blog.jpg

2792 ms

webshop2.jpg

webshop2.jpg

2800 ms

b_tweet.jpg

b_tweet.jpg

2955 ms

b_insta.jpg

b_insta.jpg

2962 ms

yt346.jpg

yt346.jpg

3051 ms

wc2024.jpg

wc2024.jpg

3032 ms

p01.jpg

p01.jpg

3117 ms

p02.jpg

p02.jpg

3126 ms

p03.jpg

p03.jpg

3209 ms

p04.jpg

p04.jpg

3256 ms

p05.jpg

p05.jpg

3280 ms

p06.jpg

p06.jpg

3290 ms

p07.jpg

p07.jpg

3384 ms

p08.jpg

p08.jpg

3382 ms

p09.jpg

p09.jpg

3455 ms

p10.jpg

p10.jpg

3456 ms

p11.jpg

p11.jpg

3443 ms

p12.jpg

p12.jpg

3455 ms

b5.jpg

b5.jpg

4521 ms

0_shop.jpg

0_shop.jpg

3570 ms

0_wc4.jpg

0_wc4.jpg

3605 ms

0_com.jpg

0_com.jpg

4512 ms

blog_list2.php

blog_list2.php

4551 ms

page.php

page.php

292 ms

header.html

header.html

3547 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYw.woff

22 ms

footer.html

footer.html

4307 ms

wHv3n85j7BM.css

wHv3n85j7BM.css

39 ms

4y3x7HWmaNc.css

4y3x7HWmaNc.css

111 ms

fuU9ChcFal0.css

fuU9ChcFal0.css

142 ms

P3oGiqMdZw7.js

P3oGiqMdZw7.js

192 ms

guwKwycnxkZ.js

guwKwycnxkZ.js

154 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

141 ms

J8JpUDMoOct.js

J8JpUDMoOct.js

190 ms

p55HfXW__mM.js

p55HfXW__mM.js

189 ms

ALTQi95mOyD.js

ALTQi95mOyD.js

287 ms

j6FwKUdWUaU.js

j6FwKUdWUaU.js

290 ms

CLQrTjyR28S.js

CLQrTjyR28S.js

294 ms

TQ0fyYGyml-.js

TQ0fyYGyml-.js

298 ms

2vViO7gHnuy.js

2vViO7gHnuy.js

298 ms

daRG11v-d-4.js

daRG11v-d-4.js

289 ms

JZ930Hfx3Dz.js

JZ930Hfx3Dz.js

333 ms

DPxpTcknHiI.js

DPxpTcknHiI.js

332 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

332 ms

423694197_791828012984103_8511140872130833478_n.jpg

423694197_791828012984103_8511140872130833478_n.jpg

195 ms

308930728_466042882229286_6417316328019861359_n.jpg

308930728_466042882229286_6417316328019861359_n.jpg

194 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

164 ms

n9_pe5S4ng8.js

n9_pe5S4ng8.js

17 ms

title_back.jpg

title_back.jpg

3224 ms

rssback.jpg

rssback.jpg

3098 ms

bg_b.jpg

bg_b.jpg

2737 ms

bx_loader.gif

bx_loader.gif

2651 ms

controls.png

controls.png

2109 ms

jquery.min.js

jquery.min.js

862 ms

logo.png

logo.png

385 ms

logo2.png

logo2.png

334 ms

icon-facebook.png

icon-facebook.png

867 ms

icon-instagram.jpg

icon-instagram.jpg

1073 ms

twitter.png

twitter.png

1005 ms

icon-youtube.png

icon-youtube.png

1024 ms

icon-mail.png

icon-mail.png

1212 ms

b_psl.png

b_psl.png

1175 ms

b_line.jpg

b_line.jpg

1066 ms

b_pd.png

b_pd.png

1354 ms

b_reed.png

b_reed.png

1392 ms

b_astro.png

b_astro.png

1225 ms

rss.css

rss.css

201 ms

main_mobile.css

main_mobile.css

289 ms

styles_mobile.css

styles_mobile.css

200 ms

menu_mobile.css

menu_mobile.css

191 ms

Accessibility Review

pazdesign.co.jp accessibility score

58

Accessibility Issues

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-hidden="true"] elements contain focusable descendents

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pazdesign.co.jp best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pazdesign.co.jp SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pazdesign.co.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 Pazdesign.co.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

pazdesign.co.jp

Open Graph description is not detected on the main page of Pazdesign. 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: