Tools & Wizards About Us
yokohamashakyo.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

yokohamashakyo.jp

社会福祉法人 横浜市社会福祉協議会

Page Load Speed

7.6 sec in total

First Response

441 ms

Resources Loaded

5.2 sec

Page Rendered

1.9 sec

yokohamashakyo.jp screenshot

About Website

Welcome to yokohamashakyo.jp homepage info - get ready to check Yokohamashakyo best content for Japan right away, or after learning these important things about yokohamashakyo.jp

社会福祉法人 横浜市社会福祉協議会の「」ページです。

Visit yokohamashakyo.jp

Key Findings

We analyzed Yokohamashakyo.jp page load time and found that the first response time was 441 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

yokohamashakyo.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

yokohamashakyo.jp

441 ms

www.yokohamashakyo.jp

432 ms

style.min.css

37 ms

destyle.min.css

69 ms

style.min.css

59 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 75% of them (52 requests) were addressed to the original Yokohamashakyo.jp, 9% (6 requests) were made to V1.chamo-chat.com and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Yokohamashakyo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 303.7 kB (3%)

Content Size

10.6 MB

After Optimization

10.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yokohamashakyo.jp main page is 10.6 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 10.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 84.3 kB

  • Original 100.7 kB
  • After minification 86.9 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 13.8 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 84.3 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 218.2 kB

  • Original 10.4 MB
  • After minification 10.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. Yokohamashakyo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 86 B

  • Original 66.3 kB
  • After minification 66.3 kB
  • After compression 66.2 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

-33%

Potential reduce by 1.1 kB

  • Original 3.4 kB
  • After minification 3.4 kB
  • After compression 2.3 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. Yokohamashakyo.jp needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (27%)

Requests Now

67

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yokohamashakyo.jp

yokohamashakyo.jp

441 ms

www.yokohamashakyo.jp

www.yokohamashakyo.jp

432 ms

style.min.css

style.min.css

37 ms

destyle.min.css

destyle.min.css

69 ms

style.min.css

style.min.css

59 ms

slick.css

slick.css

27 ms

front-page.min.css

front-page.min.css

93 ms

jquery.min.js

jquery.min.js

30 ms

script.js

script.js

79 ms

slick.min.js

slick.min.js

27 ms

front-page.js

front-page.js

75 ms

information.js

information.js

77 ms

wp-embed.min.js

wp-embed.min.js

162 ms

gtm.js

gtm.js

83 ms

chamovps.js

chamovps.js

942 ms

logo.png

logo.png

81 ms

mv-bk.png

mv-bk.png

1064 ms

slider01-1024x573.jpg

slider01-1024x573.jpg

997 ms

shakyo_web_mainv-2.jpg

shakyo_web_mainv-2.jpg

1190 ms

shakyo_web_mainv-3.jpg

shakyo_web_mainv-3.jpg

1023 ms

slider_yokokifu-1024x547.jpg

slider_yokokifu-1024x547.jpg

1001 ms

wave-gray-bottom.png

wave-gray-bottom.png

370 ms

wave-blue-top.png

wave-blue-top.png

687 ms

wave-blue-bottom.png

wave-blue-bottom.png

1485 ms

about-thumbnail01.png

about-thumbnail01.png

1586 ms

about-thumbnail02.png

about-thumbnail02.png

1295 ms

about-thumbnail03.png

about-thumbnail03.png

1101 ms

about-thumbnail04.png

about-thumbnail04.png

1143 ms

about-thumbnail05.png

about-thumbnail05.png

1336 ms

about-thumbnail06.png

about-thumbnail06.png

1189 ms

facility-bk.png

facility-bk.png

3152 ms

facility-syafuku.png

facility-syafuku.png

1255 ms

facility-vol.png

facility-vol.png

1293 ms

facility-wil.png

facility-wil.png

1340 ms

facility-ansin.png

facility-ansin.png

1584 ms

facility-shien.png

facility-shien.png

1898 ms

facility-ayumi.png

facility-ayumi.png

1380 ms

facility-cp.png

facility-cp.png

1612 ms

facility-roujin.png

facility-roujin.png

2092 ms

facility-chiku.png

facility-chiku.png

1693 ms

wave-gray-top.png

wave-gray-top.png

1811 ms

kawasaki-law.gif

kawasaki-law.gif

2133 ms

bnr_nakanoma.gif

bnr_nakanoma.gif

2395 ms

keieishakai_logo_1.png

keieishakai_logo_1.png

2500 ms

bnr_misawa-law.gif

bnr_misawa-law.gif

2622 ms

yokohamasyakyo_cieloazul.png

yokohamasyakyo_cieloazul.png

2811 ms

yokohamashakyo_smenu.jpg

yokohamashakyo_smenu.jpg

2815 ms

index-btn-05.gif

index-btn-05.gif

2917 ms

index-btn-04.gif

index-btn-04.gif

3022 ms

other-bus.png

other-bus.png

3606 ms

other-rw.png

other-rw.png

3065 ms

js

js

127 ms

analytics.js

analytics.js

120 ms

other-minjy.png

other-minjy.png

3139 ms

collect

collect

14 ms

other-hartmade.png

other-hartmade.png

3589 ms

other-workule.png

other-workule.png

2393 ms

widget.js.php

widget.js.php

1063 ms

footer-top.png

footer-top.png

2125 ms

logo-text.png

logo-text.png

2162 ms

logo-akaihane.png

logo-akaihane.png

2373 ms

loader.gif

loader.gif

178 ms

td_chm_access.js

td_chm_access.js

800 ms

chamo_sm.gif

chamo_sm.gif

345 ms

chamo_sm_offline.gif

chamo_sm_offline.gif

511 ms

td.min.js

td.min.js

19 ms

aid

aid

804 ms

chamo_access_log

chamo_access_log

20 ms

chamo.pc.css

chamo.pc.css

178 ms

Accessibility Review

yokohamashakyo.jp accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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 IDs are not unique

Best Practices

yokohamashakyo.jp best practices score

75

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

yokohamashakyo.jp SEO score

83

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

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

yokohamashakyo.jp

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