Tools & Wizards About Us
zigsow.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

zigsow.jp

ジグソー | レビューメディア

Page Load Speed

7.4 sec in total

First Response

1.7 sec

Resources Loaded

5.5 sec

Page Rendered

205 ms

zigsow.jp screenshot

About Website

Click here to check amazing Zigsow content for Japan. Otherwise, check out these important facts you probably never knew about zigsow.jp

ZIGSOW (ジグソー) は、いいもの広めるレビューコミュニティ。自分のもちものの良いところ、気に入っているところを自分の言葉で紹介しよう！レアな情報も、ZIGSOWなら見つかる！プレミアムレビューで豪華商品をGET！口コミ情報を元にいろんな繋がりを探そう！

Visit zigsow.jp

Key Findings

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

Performance Metrics

zigsow.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.062

97/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

zigsow.jp

1684 ms

zigsow.min.css

376 ms

zigsow.min.js

851 ms

lazyload.min.js

522 ms

js

57 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 57% of them (38 requests) were addressed to the original Zigsow.jp, 13% (9 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Zigsow.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 409.6 kB (32%)

Content Size

1.3 MB

After Optimization

854.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zigsow.jp main page is 1.3 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 613.6 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 130.2 kB

  • Original 217.5 kB
  • After minification 212.1 kB
  • After compression 87.3 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 130.2 kB or 60% of the original size.

Image Optimization

-1%

Potential reduce by 5.2 kB

  • Original 613.6 kB
  • After minification 608.4 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. Zigsow images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.9 kB

  • Original 129.6 kB
  • After minification 129.6 kB
  • After compression 127.8 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

-90%

Potential reduce by 272.4 kB

  • Original 303.1 kB
  • After minification 303.1 kB
  • After compression 30.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. Zigsow.jp needs all CSS files to be minified and compressed as it can save up to 272.4 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (27%)

Requests Now

66

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zigsow.jp

zigsow.jp

1684 ms

zigsow.min.css

zigsow.min.css

376 ms

zigsow.min.js

zigsow.min.js

851 ms

lazyload.min.js

lazyload.min.js

522 ms

js

js

57 ms

a1386782.js

a1386782.js

825 ms

spnx-logger.js

spnx-logger.js

32 ms

gtm.js

gtm.js

133 ms

img.php

img.php

464 ms

js

js

76 ms

zigcon.woff

zigcon.woff

386 ms

uwt.js

uwt.js

81 ms

sdk.js

sdk.js

76 ms

footer_logo@2x.png

footer_logo@2x.png

192 ms

banner

banner

208 ms

analytics.js

analytics.js

35 ms

sdk.js

sdk.js

8 ms

collect

collect

12 ms

adsct

adsct

71 ms

adsct

adsct

71 ms

collect

collect

17 ms

ga-audiences

ga-audiences

32 ms

img.php

img.php

528 ms

relay.html

relay.html

20 ms

img.php

img.php

241 ms

img.php

img.php

568 ms

img.php

img.php

238 ms

img.php

img.php

572 ms

img.php

img.php

434 ms

img.php

img.php

443 ms

img.php

img.php

713 ms

img.php

img.php

712 ms

img.php

img.php

845 ms

img.php

img.php

844 ms

img.php

img.php

846 ms

img.php

img.php

849 ms

img.php

img.php

910 ms

img.php

img.php

906 ms

img.php

img.php

1051 ms

img.php

img.php

1050 ms

img.php

img.php

1049 ms

img.php

img.php

1049 ms

img.php

img.php

1101 ms

img.php

img.php

1106 ms

img.php

img.php

1300 ms

img.php

img.php

1299 ms

img.php

img.php

1301 ms

img.php

img.php

1299 ms

img.php

img.php

1293 ms

img.php

img.php

1330 ms

img.php

img.php

1486 ms

img.php

img.php

1505 ms

img.php

img.php

1506 ms

page.php

page.php

113 ms

relay.js

relay.js

5 ms

S5yp7r4Ff9D.css

S5yp7r4Ff9D.css

30 ms

RsWZ-myCkRn.js

RsWZ-myCkRn.js

36 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

36 ms

71nLmDRGsWE.js

71nLmDRGsWE.js

36 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

33 ms

5hjr18zii08.js

5hjr18zii08.js

64 ms

zYzGplAqD4J.js

zYzGplAqD4J.js

66 ms

p55HfXW__mM.js

p55HfXW__mM.js

68 ms

309986459_517312413733844_2543961216523612690_n.jpg

309986459_517312413733844_2543961216523612690_n.jpg

35 ms

309180501_517312410400511_7412476596297056086_n.jpg

309180501_517312410400511_7412476596297056086_n.jpg

9 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

6 ms

page

page

180 ms

Accessibility Review

zigsow.jp accessibility score

51

Accessibility Issues

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

zigsow.jp best practices score

75

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

SEO Factors

zigsow.jp SEO score

81

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

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 Zigsow.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 Zigsow.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

zigsow.jp

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