Access yume-souzoku.co.jp. 相続対策のご提案とサポート　相続実務士　相続コーディネート

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.145

77/100

15%

TTI (Time to Interactive)

Value28.3 s

0/100

10%

yume-souzoku.co.jp

598 ms

www.yume-souzoku.co.jp

2185 ms

wp-emoji-release.min.js

529 ms

style.min.css

697 ms

styles.css

528 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 85% of them (82 requests) were addressed to the original Yume-souzoku.co.jp, 3% (3 requests) were made to Ajax.googleapis.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Yume-souzoku.co.jp.

Content Size

9.9 MB

After Optimization

8.4 MB

In fact, the total size of Yume-souzoku.co.jp main page is 9.9 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 9.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 81.3 kB

Original 95.0 kB
After minification 77.9 kB
After compression 13.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. This page needs HTML code to be minified as it can gain 17.0 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 81.3 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 985.3 kB

Original 9.2 MB
After minification 8.2 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. Obviously, Yume Souzoku needs image optimization as it can save up to 985.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 189.4 kB

Original 373.8 kB
After minification 354.6 kB
After compression 184.4 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 189.4 kB or 51% of the original size.

CSS Optimization

-83%

Potential reduce by 234.0 kB

Original 282.4 kB
After minification 254.0 kB
After compression 48.4 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. Yume-souzoku.co.jp needs all CSS files to be minified and compressed as it can save up to 234.0 kB or 83% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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 interpretation of your content by users in different locales.

High

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

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

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

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

Page has valid source maps

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

N/A
Encoding

UTF-8

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

yume-souzoku.co.jp

Open Graph data is detected on the main page of Yume Souzoku. 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

yume-souzoku.co.jp

www.yume-souzoku.co.jp

wp-emoji-release.min.js

style.min.css

styles.css

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

yume-souzoku.co.jp

www.yume-souzoku.co.jp

wp-emoji-release.min.js

style.min.css

styles.css

pagenavi-css.css

wpp.css

mtssb-front.css

jquery.js

jquery-migrate.min.js

wpp.min.js

ajaxzip3.js

reset.css

page.css

add.css

quick.css

all.min.css

template.css

newstyle.css

bootstrap-grid.min.css

slick-theme.css

slick.css

jquery-latest.js

jquery.matchHeight.js

jquery.easing.1.3.js

common-new.js

common.js

jquery.min.js

ac.js

jquery.min.js

add.js

google-analytics.js

js

scripts.js

wp-embed.min.js

jquery.min.js

sp-menu.js

slick.min.js

index-new.js

quick.js

gtm.js

css2

analytics.js

相続対策のご提案とサポート　相続実務士　相続コーディネート｜株式会社夢相続