Analyze 【大阪梅田駅直結】大阪で土地相続に強い相続専門税理士 相続ステーション【土地相続22,000件以上】


Page load speed analysis

  • 46/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    573 ms

  • Resources loaded

    6.6 sec

  • Page rendered

    723 ms

  • Total page load time

    7.9 sec

Visit now to see the best up-to-date Souzoku Rescue content for Japan and also check out these interesting facts you probably never knew about

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

Page optimization

  • HTML 65.5 kB
    Images 3.2 MB
    Javascripts 480.4 kB
    CSS 264.7 kB

    In fact, the total size of main page is 4.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.2 MB which makes up the majority of the site volume.

    • Original 65.5 kB
    • After minification 61.7 kB
    • After compression 15.7 kB

    HTML optimization

    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 49.8 kB or 76% of the original size.

    • Original 3.2 MB
    • After optimization 2.2 MB

    Image optimization

    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, Souzoku Rescue needs image optimization as it can save up to 1.1 MB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

    • Original 480.4 kB
    • After minification 454.7 kB
    • After compression 148.1 kB

    JavaScript optimization

    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 332.3 kB or 69% of the original size.

    • Original 264.7 kB
    • After minification 261.7 kB
    • After compression 45.8 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 218.9 kB or 83% of the original size.

Network requests diagram

  • base.css
  • common.css
  • js
  • util.js
  • mJxp-eI_haI
  • k5nPW-724So
  • 6cgBEwlbIV4
  • Logo.jpg
  • ImgLH1.jpg
  • BgLH3.jpg
  • Va1.jpg
  • Btn_Va01.jpg
  • BtnGlNav1_1.jpg
  • BtnGlNav1_2.jpg
  • BtnGlNav1_3.jpg
  • BtnGlNav1_4.jpg
  • BtnGlNav1_5.jpg
  • BtnGlNav1_6.jpg
  • BtnGlNav1_7.jpg
  • BgPage.jpg
  • img1.jpg
  • title1.jpg
  • ImgTop_point1.jpg
  • ImgTop_point2.jpg
  • ImgTop_point3.jpg
  • ImgTop1.jpg
  • BgSH1.jpg
  • media2014.png
  • top-md-neo27.1.14.fw.png
  • ImgTop13.jpg
  • neobk270628pmn.png
  • hayami1.png
  • ImgTtl1.jpg
  • sotop1.png
  • sotop2.png
  • sotop3.png
  • BgSDTop2W1.jpg
  • BgSDTop2W2.jpg
  • BgSDTop2Li1.jpg
  • spacer.gif
  • sotop4.png
  • sotop5.png
  • plusone.js
  • sotop6.png
  • sdk.js
  • analytics.js
  • sr.gif
  • tag.js
  • tag
  • collect
  • www-embed-player-vflfNyN_r.css
  • www-embed-player.js
  • base.js
  • cb=gapi.loaded_0
  • cb=gapi.loaded_1
  • person
  • xd_arbiter.php
  • xd_arbiter.php
  • postmessageRelay
  • ImgTtl3.jpg
  • rs=AGLTcCNp66tM0hVy40e06TtJciUTeCcbAg
  • rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
  • rs=AGLTcCPJ_Qx0HXwankZ8SJMM-SuxNwIccw
  • photo.jpg
  • rs=AGLTcCPJ_Qx0HXwankZ8SJMM-SuxNwIccw
  • grlryt2bdKIyfMSOhzd1eA.woff
  • d-QWLnp4didxos_6urzFtg.woff
  • vxNK-E6B13CyehuDCmvQvw.woff
  • ImgTop16.jpg
  • Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
  • ad_status.js
  • ImgTop17.jpg
  • rs=AGLTcCPJ_Qx0HXwankZ8SJMM-SuxNwIccw
  • 3193398744-postmessagerelay.js
  • rpc:shindig_random.js
  • 2UX7WLTfW3W8TclTUvlFyQ.woff
  • RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
  • ImgTop18.jpg
  • ASP_Conf.js
  • BgSDTop4W1.jpg
  • BgSDTop4W2.jpg
  • BgSDTop4Li1.jpg
  • cb=gapi.loaded_0
  • 201504foot.png
  • ImgTtl5.jpg
  • gtm.js
  • ya.js
  • ImgTop27.jpg
  • ImgTop28.jpg
  • collect
  • collect
  • page.php
  • hQThvcX2PmE.css
  • t3u7Vo4PVNb.css
  • q68gy-v_YMF.js
  • ehA1CqzHyzE.js
  • 0wM5s1Khldu.js
  • 1bNoFZUdlYZ.js
  • 1186842_1399174870308224_1651322026_n.png
  • 1507676_1485758438316533_1285300505_n.png
  • wL6VQj7Ab77.png
  • s7jcwEQH7Sx.png
  • ImgTop23.jpg
  • ImgTop24.jpg
  • I6-MnjEovm5.js
  • pQrUxxo5oQp.js
  • pb.js
  • [sr].gif
  • emd_pt.js
  • ImgTop25.jpg
  • ImgTop26.jpg
  • BgSH2.jpg
  • souzoku-rescue37_r7_c4.jpg
  • 20150806_2.png
  • HTTP_s.js
  • tvmd.fw.png
  • saiyo27-8.png
  • hayami2-2.png
  • koe201408.png
  • souzoku20140220.png
  • igonsidefee.png
  • zeisinkoku201312new.png
  • fudosan201312new.png
  • taisaku201312new.png
  • kanpu201312new.png
  • tochihyoka260124.png
  • st.php
  • sozoqa1.png
  • TtlLS1.jpg
  • ImgLS3.jpg
  • ImgLS4_1.jpg
  • eki.png
  • mphtb.png
  • ImgLS5.jpg
  • BgRSNav1LiCA1CS1.jpg
  • BgRSNav1LiCA1CS2.jpg
  • BgLF.jpg
  • sst.php
  • log_run.php
  • st.php
  • HTTP_s1_v4.js
  • print.css

Our browser made a total of 146 requests to load all elements on the main page. We found that 55% of them (81 requests) were addressed to the original, 8% (11 requests) were made to and 7% (10 requests) were made to The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain

Additional info on


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











Possible request optimization













Normal result


As for redirects, our browser was forwarded to before it reached this domain.

IP address

This IP address is dedicated to This is the best domain hosting practice .

Normal result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 298
NS 86400
NS 86400
NS 86400
NS 86400

Language and encoding

Good result


JA ja language flag


JA ja language flag





Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 100% of all visits is Japan. It’s good for that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Poor result

Social Sharing Optimization

Open Graph description is not detected on the main page of Souzoku Rescue. 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:

Share this report in social media

Analyze another website