Access izakazoku.com. いざ！安心家族～生活の知恵と小さな幸せのヒント～

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value2,940 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

izakazoku.com

1075 ms

style.css

714 ms

lp.css

389 ms

slidebars.css

393 ms

jquery.js

948 ms

Our browser made a total of 136 requests to load all elements on the main page. We found that 47% of them (64 requests) were addressed to the original Izakazoku.com, 8% (11 requests) were made to Cs.adingo.jp and 7% (10 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Bc.ads.gree.net.

Content Size

1.0 MB

After Optimization

512.4 kB

In fact, the total size of Izakazoku.com main page is 1.0 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. 40% of websites need less resources to load. Javascripts take 384.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 58.9 kB

Original 73.0 kB
After minification 68.3 kB
After compression 14.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 58.9 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 6.8 kB

Original 307.2 kB
After minification 300.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. Izakazoku images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 221.8 kB

Original 384.0 kB
After minification 368.7 kB
After compression 162.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 221.8 kB or 58% of the original size.

CSS Optimization

-86%

Potential reduce by 219.4 kB

Original 255.2 kB
After minification 200.5 kB
After compression 35.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. Izakazoku.com needs all CSS files to be minified and compressed as it can save up to 219.4 kB or 86% of the original size.

Requests Now

129

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

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

izakazoku.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

いざ！安心家族～生活の知恵と小さな幸せのヒント～

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

izakazoku.com

style.css

lp.css

slidebars.css

jquery.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

izakazoku.com

style.css

lp.css

slidebars.css

jquery.js

custom-js.js

styles.css

sb-type-std.css

sb-type-fb.css

sb-type-fb-flat.css

sb-type-ln.css

sb-type-ln-flat.css

sb-type-pink.css

sb-type-rtail.css

sb-type-drop.css

sb-type-think.css

sb-no-br.css

screen.min.css

wpp.css

jetpack.css

jquery.js

jquery-migrate.min.js

f.js

f.js

core.min.js

widget.min.js

tabs.min.js

jquery.form.min.js

scripts.js

front.min.js

devicepx-jetpack.js

gprofiles.js

wpgroho.js

jquery.sonar.min.js

lazy-load.js

e-201609.js

slidebars.js

widgets.js

ga.js

wp-emoji-release.min.js

__utm.gif

feedly-follow-rectangle-volume-small_2x.png

header1.jpg