Tools & Wizards About Us
care-care.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

care-care.jp

高齢者,介護情報サイト:ケアケアweb

Page Load Speed

6.5 sec in total

First Response

2.1 sec

Resources Loaded

4.2 sec

Page Rendered

116 ms

care-care.jp screenshot

About Website

Welcome to care-care.jp homepage info - get ready to check Care best content right away, or after learning these important things about care-care.jp

高齢者、介護の情報から住宅探しまでサポートする情報発信サイトケアケアweb

Visit care-care.jp

Key Findings

We analyzed Care-care.jp page load time and found that the first response time was 2.1 sec 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

care-care.jp performance score

0

Network Requests Diagram

care-care.jp

2128 ms

common.css

536 ms

index.css

394 ms

style01.css

603 ms

widgets.js

89 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 39% of them (22 requests) were addressed to the original Care-care.jp, 16% (9 requests) were made to Google.com and 14% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Care-care.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.8 kB (66%)

Content Size

116.3 kB

After Optimization

39.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Care-care.jp main page is 116.3 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. 60% of websites need less resources to load. CSS take 65.0 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 14.4 kB

  • Original 20.8 kB
  • After minification 19.2 kB
  • After compression 6.4 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 14.4 kB or 69% of the original size.

Image Optimization

-18%

Potential reduce by 519 B

  • Original 2.8 kB
  • After minification 2.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. Obviously, Care needs image optimization as it can save up to 519 B or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-22%

Potential reduce by 6.1 kB

  • Original 27.6 kB
  • After minification 27.6 kB
  • After compression 21.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 6.1 kB or 22% of the original size.

CSS Optimization

-86%

Potential reduce by 55.9 kB

  • Original 65.0 kB
  • After minification 43.5 kB
  • After compression 9.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. Care-care.jp needs all CSS files to be minified and compressed as it can save up to 55.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (57%)

Requests Now

51

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

care-care.jp

care-care.jp

2128 ms

common.css

common.css

536 ms

index.css

index.css

394 ms

style01.css

style01.css

603 ms

widgets.js

widgets.js

89 ms

jsapi

jsapi

26 ms

conversion.js

conversion.js

51 ms

ga.js

ga.js

57 ms

bg_body.gif

bg_body.gif

367 ms

bg_head.gif

bg_head.gif

541 ms

logo_head.gif

logo_head.gif

370 ms

sicon_cate11.gif

sicon_cate11.gif

374 ms

arrow.gif

arrow.gif

444 ms

sidebtn_login_fac.gif

sidebtn_login_fac.gif

444 ms

btn_pagetop.gif

btn_pagetop.gif

759 ms

logo_foot.gif

logo_foot.gif

745 ms

like.php

like.php

95 ms

plusone.js

plusone.js

94 ms

__utm.gif

__utm.gif

15 ms

18 ms

default+ja.css

default+ja.css

7 ms

minimalist.css

minimalist.css

13 ms

default+ja.I.js

default+ja.I.js

87 ms

minimalist.css

minimalist.css

65 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

133 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

148 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

56 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

91 ms

fastbutton

fastbutton

103 ms

bg_foot.gif

bg_foot.gif

568 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

164 ms

map_topsearch00.gif

map_topsearch00.gif

521 ms

map_topsearch01.gif

map_topsearch01.gif

571 ms

map_topsearch02.gif

map_topsearch02.gif

727 ms

map_topsearch03.gif

map_topsearch03.gif

854 ms

map_topsearch04.gif

map_topsearch04.gif

867 ms

map_topsearch05.gif

map_topsearch05.gif

882 ms

map_topsearch06.gif

map_topsearch06.gif

910 ms

map_topsearch07.gif

map_topsearch07.gif

948 ms

map_topsearch08.gif

map_topsearch08.gif

1105 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

29 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

28 ms

postmessageRelay

postmessageRelay

91 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

60 ms

67 ms

43 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

59 ms

rpc:shindig_random.js

rpc:shindig_random.js

30 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

45 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

2 ms

jot

jot

93 ms

jot

jot

24 ms

async-ads.js

async-ads.js

37 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

32 ms

small-logo.png

small-logo.png

21 ms

clear.gif

clear.gif

103 ms

SEO Factors

care-care.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Care-care.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 Care-care.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

care-care.jp

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