4.9 sec in total
998 ms
3.7 sec
177 ms
Click here to check amazing Saso content. Otherwise, check out these important facts you probably never knew about saso.or.jp
兵庫県西宮市にある総合・救急病院です。駐車場完備の総合・救急病院です。笹生病院の最寄駅はJR・芦屋駅・さくら夙川駅・阪急・夙川駅・阪神・打出駅・香櫨園駅です。個人様として、または勤務先や加入団体様の人間ドックの受診者様としてご利用下さい。
Visit saso.or.jpWe analyzed Saso.or.jp page load time and found that the first response time was 998 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
saso.or.jp performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value18.1 s
0/100
25%
Value13.9 s
1/100
10%
Value870 ms
33/100
30%
Value0.785
5/100
15%
Value16.8 s
5/100
10%
998 ms
576 ms
945 ms
595 ms
1557 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 93% of them (38 requests) were addressed to the original Saso.or.jp, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Saso.or.jp.
Page size can be reduced by 124.7 kB (33%)
379.3 kB
254.5 kB
In fact, the total size of Saso.or.jp main page is 379.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. 20% of websites need less resources to load. Images take 211.7 kB which makes up the majority of the site volume.
Potential reduce by 10.0 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 2.5 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 10.0 kB or 72% of the original size.
Potential reduce by 20.2 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. Saso images are well optimized though.
Potential reduce by 71.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 71.9 kB or 57% of the original size.
Potential reduce by 22.6 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. Saso.or.jp needs all CSS files to be minified and compressed as it can save up to 22.6 kB or 80% of the original size.
Number of requests can be reduced by 15 (38%)
39
24
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
saso.or.jp
998 ms
reset.css
576 ms
layout.css
945 ms
top.css
595 ms
jquery.min.js
1557 ms
jquery.page-scroller-308.js
785 ms
jquery.biggerlink.min.js
597 ms
base.js
757 ms
jquery.cookie.js
788 ms
fontsizechange.js
795 ms
ga.js
940 ms
ga.js
33 ms
top-bg.jpg
368 ms
get_flash_player.gif
31 ms
subject-schedule.jpg
195 ms
logo.gif
200 ms
logo-jcqhc.jpg
196 ms
btn-font-change-s.jpg
188 ms
btn-font-change-m.jpg
197 ms
btn-font-change-l.jpg
194 ms
glnavi.png
556 ms
side-bn-outpatient.jpg
387 ms
side-bn-family.jpg
768 ms
side-bn-medical-check.jpg
770 ms
side-bn-overtime.jpg
627 ms
side-tel-number.png
708 ms
top-bn-arrow.gif
579 ms
arrow.gif
740 ms
dotted-line.gif
771 ms
footer-saso-hospitalimage.jpg
1217 ms
footer-qr-code.gif
892 ms
footer-bn-kenshin.jpg
925 ms
footer-bn-kango.jpg
1150 ms
footer-bn-seiwa-kouroen.jpg
962 ms
footer-bn-soyokaze.jpg
1152 ms
btn-font-change-m_ov.jpg
1074 ms
btn-font-change-m_ov_ov.jpg
1111 ms
medical-check.jpg
359 ms
cooperation-room.jpg
958 ms
__utm.gif
13 ms
www.saso.or.jp
367 ms
saso.or.jp accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
saso.or.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
saso.or.jp SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saso.or.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 Saso.or.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.
saso.or.jp
Open Graph description is not detected on the main page of Saso. 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: