Tools & Wizards About Us
aicare.co.jp screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

aicare.co.jp

株式会社アイケアは介護保険申請代行、在宅系、施設系など、様々な介護サービスをトータルにご提供しています。

Page Load Speed

6.1 sec in total

First Response

545 ms

Resources Loaded

4.4 sec

Page Rendered

1.2 sec

aicare.co.jp screenshot

About Website

Visit aicare.co.jp now to see the best up-to-date Aicare content and also check out these interesting facts you probably never knew about aicare.co.jp

株式会社アイケアは介護保険申請代行、在宅系、施設系など、様々な介護サービスをトータルにご提供しています。

Visit aicare.co.jp

Key Findings

We analyzed Aicare.co.jp page load time and found that the first response time was 545 ms and then it took 5.6 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

aicare.co.jp performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.687

7/100

15%

TTI (Time to Interactive)

Value20.9 s

1/100

10%

Network Requests Diagram

aicare.co.jp

545 ms

www.aicare.co.jp

464 ms

www.aicare.co.jp

844 ms

common.css

144 ms

common02.css

286 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 81% of them (68 requests) were addressed to the original Aicare.co.jp, 7% (6 requests) were made to Youtube.com and 5% (4 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Aicare.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 197.5 kB (19%)

Content Size

1.1 MB

After Optimization

866.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aicare.co.jp main page is 1.1 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. 55% of websites need less resources to load. Images take 615.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 38.3 kB

  • Original 48.4 kB
  • After minification 46.7 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 38.3 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 7.2 kB

  • Original 615.8 kB
  • After minification 608.6 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. Aicare images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 100.6 kB

  • Original 280.5 kB
  • After minification 249.8 kB
  • After compression 179.9 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 100.6 kB or 36% of the original size.

CSS Optimization

-43%

Potential reduce by 51.4 kB

  • Original 119.5 kB
  • After minification 106.5 kB
  • After compression 68.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. Aicare.co.jp needs all CSS files to be minified and compressed as it can save up to 51.4 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (48%)

Requests Now

80

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aicare.co.jp

aicare.co.jp

545 ms

www.aicare.co.jp

www.aicare.co.jp

464 ms

www.aicare.co.jp

www.aicare.co.jp

844 ms

common.css

common.css

144 ms

common02.css

common02.css

286 ms

footercontact.css

footercontact.css

428 ms

formelement.css

formelement.css

429 ms

roundedmplus1c.css

roundedmplus1c.css

33 ms

mediation.js

mediation.js

430 ms

style.css

style.css

611 ms

browsercaution.js

browsercaution.js

475 ms

replaceimagefull.js

replaceimagefull.js

489 ms

js

js

74 ms

submenuopen.js

submenuopen.js

568 ms

menutoggle.js

menutoggle.js

569 ms

menuhighlight.js

menuhighlight.js

572 ms

smoothscroll.js

smoothscroll.js

677 ms

movepagetop.js

movepagetop.js

678 ms

ontouchstart.js

ontouchstart.js

768 ms

footercontact.js

footercontact.js

768 ms

formcommon.js

formcommon.js

1076 ms

formelement.js

formelement.js

769 ms

formassist.js

formassist.js

1190 ms

postalcode.js

postalcode.js

811 ms

inform.js

inform.js

1075 ms

logo.svg

logo.svg

627 ms

mascot_top.svg

mascot_top.svg

567 ms

toptel.svg

toptel.svg

626 ms

facebook.svg

facebook.svg

629 ms

topsearch_45a.svg

topsearch_45a.svg

630 ms

icon_external_45a.svg

icon_external_45a.svg

697 ms

icon_chevron_down_white.svg

icon_chevron_down_white.svg

698 ms

logo_sp.svg

logo_sp.svg

737 ms

submenu_arrow.svg

submenu_arrow.svg

694 ms

icon_chevron_right_white.svg

icon_chevron_right_white.svg

696 ms

icon_external_white.svg

icon_external_white.svg

695 ms

arrow_left.svg

arrow_left.svg

975 ms

arrow_right.svg

arrow_right.svg

976 ms

photo01.png

photo01.png

974 ms

photo02.png

photo02.png

973 ms

photo03.png

photo03.png

978 ms

photo04.png

photo04.png

979 ms

photo05.png

photo05.png

1074 ms

photo06.png

photo06.png

1077 ms

zaitakukyo.png

zaitakukyo.png

1074 ms

mascot_fukuroi.svg

mascot_fukuroi.svg

1075 ms

mascot_kakegawa.svg

mascot_kakegawa.svg

1419 ms

mascot_aicare.svg

mascot_aicare.svg

1078 ms

mascot_hamamatsu.svg

mascot_hamamatsu.svg

1202 ms

mascot_kosai.svg

mascot_kosai.svg

1204 ms

mascot_yaizu.svg

mascot_yaizu.svg

1309 ms

Mhh7AAyfuR4

Mhh7AAyfuR4

188 ms

brBGIZDhLMc

brBGIZDhLMc

575 ms

logo_footer.svg

logo_footer.svg

1155 ms

topofpage.svg

topofpage.svg

1167 ms

font

font

95 ms

topimage01.jpg

topimage01.jpg

1512 ms

topimage02.jpg

topimage02.jpg

1569 ms

topimage05.jpg

topimage05.jpg

1344 ms

breadcrumbsback.svg

breadcrumbsback.svg

1238 ms

icon_chevron_right_e79.svg

icon_chevron_right_e79.svg

1276 ms

www-player.css

www-player.css

16 ms

www-embed-player.js

www-embed-player.js

15 ms

base.js

base.js

58 ms

ad_status.js

ad_status.js

294 ms

icon_chevron_right_45a.svg

icon_chevron_right_45a.svg

1094 ms

j85XBmD3K-auBXRuR4gFy-YbXrRwDWE2e6ZsFqyJZWU.js

j85XBmD3K-auBXRuR4gFy-YbXrRwDWE2e6ZsFqyJZWU.js

239 ms

embed.js

embed.js

151 ms

slant1.svg

slant1.svg

997 ms

mark_tel.svg

mark_tel.svg

1050 ms

icon_chevron_right_gray.svg

icon_chevron_right_gray.svg

1026 ms

icon_chevron_right_888.svg

icon_chevron_right_888.svg

1084 ms

icon_chevron_up_888.svg

icon_chevron_up_888.svg

1078 ms

breadcrumbsback_on.svg

breadcrumbsback_on.svg

1081 ms

id

id

36 ms

top.php

top.php

1047 ms

ajaxloader.gif

ajaxloader.gif

1078 ms

icon_flag_off_gray.svg

icon_flag_off_gray.svg

1118 ms

Create

Create

235 ms

Create

Create

331 ms

GenerateIT

GenerateIT

22 ms

GenerateIT

GenerateIT

25 ms

icon_new_red.svg

icon_new_red.svg

144 ms

icon_pdf.svg

icon_pdf.svg

145 ms

Accessibility Review

aicare.co.jp accessibility score

68

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

aicare.co.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

High

Page has valid source maps

SEO Factors

aicare.co.jp SEO score

85

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

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 Aicare.co.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 Aicare.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

aicare.co.jp

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