11.5 sec in total
484 ms
8.3 sec
2.7 sec
Click here to check amazing Shaso content. Otherwise, check out these important facts you probably never knew about shaso.jp
社葬・お別れの会・合同葬なら信頼の葬祭ブランド【公益社】にお任せください。葬祭業界初の東証プライム上場。歴史に培われた社葬経験を活かしトータルサポートいたします。社葬・団体葬の式次第や流れ、式場の情報・社葬の実例・費用のことなどが満載。
Visit shaso.jpWe analyzed Shaso.jp page load time and found that the first response time was 484 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
shaso.jp performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value13.7 s
0/100
25%
Value10.4 s
8/100
10%
Value250 ms
84/100
30%
Value0.358
30/100
15%
Value11.2 s
20/100
10%
484 ms
1455 ms
636 ms
939 ms
1236 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 89% of them (97 requests) were addressed to the original Shaso.jp, 2% (2 requests) were made to Ssl.google-analytics.com and 2% (2 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Shaso.jp.
Page size can be reduced by 660.4 kB (26%)
2.6 MB
1.9 MB
In fact, the total size of Shaso.jp main page is 2.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. 45% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 29.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 7.2 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 29.4 kB or 76% of the original size.
Potential reduce by 361.9 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, Shaso needs image optimization as it can save up to 361.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 117.1 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 117.1 kB or 55% of the original size.
Potential reduce by 152.0 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. Shaso.jp needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 85% of the original size.
Number of requests can be reduced by 35 (33%)
105
70
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shaso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
shaso.jp
484 ms
www.shaso.jp
1455 ms
reset.css
636 ms
common.css
939 ms
style.css
1236 ms
wp-embed.min.js
162 ms
app.js
1085 ms
wp-emoji-release.min.js
317 ms
bg-header.jpg
502 ms
icon-common-sitemap-blue.png
172 ms
txt-header-inquiry.png
173 ms
txt-header-hurry.png
733 ms
logo-header.png
270 ms
txt-header-telnum.png
499 ms
icon-header-seminar.png
765 ms
btn-header-seminar.png
499 ms
btn-header-info.png
500 ms
bg-header.png
1074 ms
border-header-01.png
1039 ms
btn-header-01_off.png
629 ms
btn-header-02_off.png
822 ms
btn-header-03_off.png
787 ms
border-header-02.png
885 ms
btn-header-04_off.png
955 ms
btn-header-05_off.png
942 ms
btn-header-06_off.png
980 ms
btn-header-07_off.png
1060 ms
btn-header-08_off.png
1098 ms
bg-wrapper.jpg
1406 ms
bg-top-main.jpg
1583 ms
tit-top-main.png
1499 ms
bg-top-mean.png
1706 ms
icon-common-arrow-next.png
1228 ms
bg-top-large.png
1721 ms
bg-top-middle.png
1984 ms
img-top-border-point.png
1565 ms
icon-common-shaso.png
1654 ms
img-top-shaso.jpg
1724 ms
icon-common-owakare.png
1737 ms
img-top-owakare.jpg
1959 ms
icon-common-goudou.png
1862 ms
img-top-goudou.jpg
1779 ms
tag.js
26 ms
img-top-left-top.png
1757 ms
tag
22 ms
img-top-right-top.png
1723 ms
img-bottom-right-top.png
1850 ms
9cf266e340ebc165fd0c47cadb599fb29dec07f3.js
55 ms
img-bottom-left-top.png
1773 ms
bg-index-point.png
2607 ms
tit-top-point-main.png
1555 ms
icon-common-arrow-next-white.png
1624 ms
subtit-top-point-01.png
1645 ms
subtit-top-point-02.png
1676 ms
subtit-top-point-03.png
1571 ms
img-banner-seminar-large.png
1626 ms
icon-banner-seminar-large.png
1518 ms
icon-common-subtit.png
1514 ms
img-case-thumb-l-shasou1.jpg
1516 ms
bg_case_ttl.png
1468 ms
img-case-thumb-l-owakare1.jpg
1646 ms
img-case-thumb-l-goudousou2.jpg
1504 ms
img-index-hall-bg.png
1517 ms
img-index-hall.png
1618 ms
2-aoyamasougisho-1.jpg
1601 ms
17-imperialhotel-tokyo-1.jpg
1543 ms
21-hotelokura-tokyo-1.jpg
1853 ms
23-newotani-tokyo-1.jpg
1665 ms
18-palacehotel-tokyo-1.jpg
2125 ms
14-tsukijihongwanjihondou-1.jpg
1616 ms
68-senrikaikann-1.jpg
1546 ms
57-yasuragi-1.jpg
1768 ms
58-kitamido-1.jpg
1607 ms
67-rihga-osaka-1.jpg
1554 ms
59-miyakohotels-osaka-1.jpg
1696 ms
65-newotani-osaka-1.jpg
1693 ms
bg-bnr-desk-large.png
2123 ms
txt-bnr-desk-large-01.png
1558 ms
icon-bnr-desk.png
1619 ms
txt-bnr-desk-large-02.png
1690 ms
btn-banner-tel-large_off.png
1682 ms
icon-question.png
1622 ms
icon-footer-arrow.png
1677 ms
bnr-footer-recruit.png
2562 ms
bnr-footer-corporate.png
1689 ms
img-common-privacy.png
1680 ms
img-common-aaa.png
1617 ms
img-common-aed.png
1676 ms
logo-common.png
2017 ms
logo-footer-san.png
1695 ms
icon-common-blank.png
1765 ms
btn-footer-request_off.png
1675 ms
btn-footer-hurry_off.png
1832 ms
bnr-footer-telnum.png
1856 ms
btn-footer-pagetop.png
1925 ms
icon-common-minus-white.png
2202 ms
icon-common-minus-blue.png
1828 ms
icon-knowledge-flow-owakare.png
1761 ms
icon-knowledge-flow-goudou.png
1749 ms
icon-knowledge-flow-misso.png
1785 ms
conversion_async.js
47 ms
ya.js
719 ms
ga.js
54 ms
65 ms
80 ms
__utm.gif
14 ms
s31437642793171
8 ms
84 ms
64 ms
shaso.jp accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
shaso.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
shaso.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
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 Shaso.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 Shaso.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.
shaso.jp
Open Graph description is not detected on the main page of Shaso. 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: