Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

zaikaku.com

【口コミ・評判】PR | おすすめ商品の口コミや評判、効果、お試しトライアル、キャンペーン情報などをご紹介しています。(※PR広告含む)

Page Load Speed

6.2 sec in total

First Response

1.9 sec

Resources Loaded

4.1 sec

Page Rendered

249 ms

About Website

Visit zaikaku.com now to see the best up-to-date Zaikaku content and also check out these interesting facts you probably never knew about zaikaku.com

ローソンでイオンが取り扱う電子マネー「WAON(ワオン)」を 2015年12月から導入することが決定しました。 これにより、全国のローソン店舗で「WAON決済」が出来るほか、 イオンカード(WAON内蔵)や「WAON(ワオン)カード」に 現金のチャージ(入金)もできるようになります。 WAON(ワオン

Visit zaikaku.com

Key Findings

We analyzed Zaikaku.com page load time and found that the first response time was 1.9 sec and then it took 4.3 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

zaikaku.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

zaikaku.com

1875 ms

style.css

1070 ms

font-awesome.min.css

904 ms

style.css

416 ms

extension.css

417 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 76% of them (22 requests) were addressed to the original Zaikaku.com, 7% (2 requests) were made to Connect.facebook.net and 3% (1 request) were made to Www20.a8.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Zaikaku.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 210.9 kB (46%)

Content Size

453.5 kB

After Optimization

242.6 kB

In fact, the total size of Zaikaku.com main page is 453.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 180.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 40.7 kB

  • Original 50.8 kB
  • After minification 47.6 kB
  • After compression 10.1 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 40.7 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 10.0 kB

  • Original 180.3 kB
  • After minification 170.3 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. Zaikaku images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 87.1 kB

  • Original 131.5 kB
  • After minification 125.8 kB
  • After compression 44.5 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 87.1 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 73.1 kB

  • Original 90.8 kB
  • After minification 67.5 kB
  • After compression 17.7 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. Zaikaku.com needs all CSS files to be minified and compressed as it can save up to 73.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (44%)

Requests Now

27

After Optimization

15

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

Accessibility Review

zaikaku.com accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

zaikaku.com 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

SEO Factors

zaikaku.com SEO score

93

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

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

    JA

  • Encoding

    UTF-8

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

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