Tools & Wizards About Us
royal-kaigo.jp screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

royal-kaigo.jp

腰痛改善のためのマットレス – 高齢者向け住宅

Page Load Speed

5.4 sec in total

First Response

978 ms

Resources Loaded

3.9 sec

Page Rendered

511 ms

royal-kaigo.jp screenshot

About Website

Click here to check amazing Royal Kaigo content. Otherwise, check out these important facts you probably never knew about royal-kaigo.jp

Visit royal-kaigo.jp

Key Findings

We analyzed Royal-kaigo.jp page load time and found that the first response time was 978 ms and then it took 4.4 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

royal-kaigo.jp performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

royal-kaigo.jp

978 ms

style.min.css

348 ms

a46b98388f6ac6725b8509ad21494b85.css

492 ms

ionicons.min.css

523 ms

slick.min.css

525 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 97% of them (30 requests) were addressed to the original Royal-kaigo.jp, 3% (1 request) were made to Www24.a8.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Royal-kaigo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.9 kB (14%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royal-kaigo.jp main page is 1.8 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. 25% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 50.5 kB

  • Original 63.3 kB
  • After minification 54.3 kB
  • After compression 12.8 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 9.0 kB, which is 14% 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 50.5 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 183.9 kB

  • Original 1.7 MB
  • After minification 1.5 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, Royal Kaigo needs image optimization as it can save up to 183.9 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

-9%

Potential reduce by 6.9 kB

  • Original 73.3 kB
  • After minification 73.3 kB
  • After compression 66.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. This website has mostly compressed JavaScripts.

CSS Optimization

-17%

Potential reduce by 8.5 kB

  • Original 49.6 kB
  • After minification 47.9 kB
  • After compression 41.1 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. Royal-kaigo.jp needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (59%)

Requests Now

29

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royal-kaigo.jp

royal-kaigo.jp

978 ms

style.min.css

style.min.css

348 ms

a46b98388f6ac6725b8509ad21494b85.css

a46b98388f6ac6725b8509ad21494b85.css

492 ms

ionicons.min.css

ionicons.min.css

523 ms

slick.min.css

slick.min.css

525 ms

magnific-popup.css

magnific-popup.css

527 ms

jquery.sidr.dark.css

jquery.sidr.dark.css

530 ms

aos.css

aos.css

565 ms

style.css

style.css

820 ms

jquery.min.js

jquery.min.js

701 ms

jquery-migrate.min.js

jquery-migrate.min.js

697 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

702 ms

slick.min.js

slick.min.js

707 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

752 ms

jquery.sidr.min.js

jquery.sidr.min.js

965 ms

theia-sticky-sidebar.min.js

theia-sticky-sidebar.min.js

964 ms

jquery.matchHeight.min.js

jquery.matchHeight.min.js

965 ms

aos.js

aos.js

966 ms

script.js

script.js

966 ms

ajax.js

ajax.js

981 ms

bgt

bgt

985 ms

%E9%AB%98%E9%BD%A2%E8%80%85%E5%90%91%E3%81%91%E7%A6%8F%E7%A5%89%E8%BB%8A%E4%B8%A1.jpg

%E9%AB%98%E9%BD%A2%E8%80%85%E5%90%91%E3%81%91%E7%A6%8F%E7%A5%89%E8%BB%8A%E4%B8%A1.jpg

883 ms

ionicons.woff

ionicons.woff

349 ms

%E9%AA%A8%E7%9B%A4%E8%AA%BF%E6%95%B4-300x197.jpg

%E9%AA%A8%E7%9B%A4%E8%AA%BF%E6%95%B4-300x197.jpg

178 ms

image-2-300x290.png

image-2-300x290.png

531 ms

image-1-300x214.png

image-1-300x214.png

329 ms

image-300x234.png

image-300x234.png

378 ms

%E9%AA%A8%E7%9B%A4%E8%AA%BF%E6%95%B4.jpg

%E9%AA%A8%E7%9B%A4%E8%AA%BF%E6%95%B4.jpg

712 ms

image-2.png

image-2.png

1125 ms

image-1-1024x731.png

image-1-1024x731.png

985 ms

image-1024x798.png

image-1024x798.png

1132 ms

Accessibility Review

royal-kaigo.jp accessibility score

78

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-*] attributes do not match their roles

High

ARIA IDs are not unique

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

Links do not have a discernible name

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

royal-kaigo.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

royal-kaigo.jp SEO score

84

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

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 Royal-kaigo.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 Royal-kaigo.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

royal-kaigo.jp

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