13.2 sec in total
1.9 sec
10.9 sec
468 ms
Visit smtrc.jp now to see the best up-to-date Smtrc content for Japan and also check out these interesting facts you probably never knew about smtrc.jp
不動産購入、売却、売買なら、三井住友信託銀行グループの三井住友トラスト不動産。中古マンション、新築・中古一戸建て、土地などの物件検索、不動産売買のノウハウが満載です。
Visit smtrc.jpWe analyzed Smtrc.jp page load time and found that the first response time was 1.9 sec and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
smtrc.jp performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value19.8 s
0/100
25%
Value15.4 s
1/100
10%
Value7,110 ms
0/100
30%
Value0.353
31/100
15%
Value28.8 s
0/100
10%
1855 ms
373 ms
826 ms
1236 ms
971 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 92% of them (136 requests) were addressed to the original Smtrc.jp, 3% (4 requests) were made to Click.showcase-tv.jp and 1% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Smtrc.jp.
Page size can be reduced by 461.2 kB (17%)
2.7 MB
2.2 MB
In fact, the total size of Smtrc.jp main page is 2.7 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. 40% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 105.2 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 33.1 kB, which is 28% 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 105.2 kB or 88% of the original size.
Potential reduce by 118.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. Smtrc images are well optimized though.
Potential reduce by 195.7 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 195.7 kB or 68% of the original size.
Potential reduce by 41.5 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. Smtrc.jp needs all CSS files to be minified and compressed as it can save up to 41.5 kB or 84% of the original size.
Number of requests can be reduced by 17 (12%)
143
126
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smtrc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
smtrc.jp
1855 ms
common.css
373 ms
format.css
826 ms
jquery-1.7.1.min.js
1236 ms
jsset.js
971 ms
includesAct.js
970 ms
fontSizeChange.js
730 ms
rollover.js
1060 ms
top.css
1075 ms
top.js
1135 ms
u.changeTab.js
1338 ms
ah-placeholder.js
1338 ms
elementSlideLib.js
1717 ms
elementSlide.js
1415 ms
searchKeyword.js
1292 ms
cmpMypage.js
862 ms
conversion.js
14 ms
ClickIndex.js
539 ms
bg.jpg
365 ms
logo.jpg
757 ms
logo_group.jpg
369 ms
bg_header.jpg
366 ms
btn_navi_urirai.png
368 ms
btn_navi_kaitai.png
366 ms
btn_navi_toushi.png
754 ms
btn_navi_store.png
755 ms
btn_navi_useful.png
757 ms
main_image_07.jpg
1457 ms
main_image_04.jpg
1113 ms
main_image_03.jpg
1825 ms
main_image_08.jpg
2248 ms
main_image_01.jpg
1457 ms
main_bn_07.png
1106 ms
main_bn_04.png
1455 ms
main_bn_03.png
1458 ms
main_bn_08.png
1455 ms
main_bn_01.png
1590 ms
btn_top_uritai.jpg
1644 ms
btn_top_kaitai.jpg
1728 ms
btn_top_toushi.jpg
1742 ms
btn_top_tenpo.jpg
2423 ms
btn_search_top.png
1959 ms
title_tokushu_mansion.png
2132 ms
img_tokushu_towermansion.jpg
2082 ms
title_tokushu_kodate.png
2152 ms
img_tokushu_kodate_high.jpg
2274 ms
title_tokushu_tochi.png
2434 ms
img_tokushu_tochi.jpg
2496 ms
img_tokushu_100heibeimansion.jpg
2480 ms
img_tokushu_kodate.jpg
2627 ms
img_tokushu_chikuasa.jpg
2589 ms
img_kobetsu.jpg
2737 ms
img_seminar.jpg
2768 ms
img_support_04.jpg
2449 ms
img_support_01.jpg
2505 ms
img_support_05.jpg
2543 ms
img_support_02.jpg
2632 ms
h4_useful_column.jpg
2689 ms
CONDENSEicon.woff
2738 ms
photo_arai_naoko.jpg
2426 ms
icon_new.png
2301 ms
img_column_02.jpg
2475 ms
photo_otani_ikuo.jpg
2258 ms
photo_tanaka_koji.jpg
2319 ms
photo_segawa_toru.jpg
1915 ms
img_writer_tamiya.jpg
1986 ms
photo_yoshimoto_kaori2.jpg
2014 ms
photo_sagawa_akira.jpg
2091 ms
photo_market.jpg
2272 ms
img_jyutakukurashi_guide.jpg
2241 ms
38 ms
ga.js
48 ms
56 ms
__utm.gif
19 ms
20100528.js
558 ms
20110426205637.js
334 ms
exec.js
385 ms
collect
65 ms
36 ms
h4_useful_advice.jpg
2207 ms
ga-audiences
18 ms
img_advice_16.jpg
2129 ms
img_advice_15.jpg
2072 ms
img_advice_14.jpg
1966 ms
img_advice_12.jpg
2188 ms
img_advice_11.jpg
2063 ms
img_advice_09.jpg
1831 ms
img_advice_08.jpg
1974 ms
img_advice_07.jpg
2012 ms
img_advice_06.jpg
1879 ms
img_advice_10.jpg
1827 ms
img_advice_05.jpg
1905 ms
img_advice_04.jpg
1904 ms
img_advice_03.jpg
1985 ms
img_advice_02.jpg
1944 ms
img_advice_01.jpg
1865 ms
h4_useful_guide.jpg
1906 ms
img_useful_kounyu.jpg
1904 ms
img_useful_zeikin.jpg
1885 ms
img_useful_souzoku.jpg
1964 ms
img_useful_toushi.jpg
1917 ms
img_archive_01.jpg
1927 ms
img_archive_02.jpg
1907 ms
img_allabout.jpg
1905 ms
img_other_02.jpg
1916 ms
h3_group.jpg
1997 ms
bn_group_hd.jpg
1938 ms
img_logo_shintakuginko.jpg
1971 ms
bn_group_loan-finance.jpg
1910 ms
bn_group_sumishin-sbi.jpg
1901 ms
bn_group_panasonic-finance.jpg
1858 ms
bn_group_labo.jpg
2004 ms
h3_icon_mypage.png
1815 ms
icon_mypage_muryo.png
1843 ms
btn_right_mypage_join.png
1882 ms
btn_login.png
1933 ms
btn_renew.jpg
1884 ms
btn_blogtop.jpg
1832 ms
20160105142636.gif
1958 ms
20151001094438.gif
1979 ms
index_bt017.gif
1977 ms
bg_search.jpg
1947 ms
bg_cloumn_slide.jpg
1757 ms
bn_openhouse.jpg
1906 ms
icon_news.jpg
1835 ms
bn_shosai.jpg
2157 ms
bn_saiyou.jpg
1951 ms
btn_prev.png
1873 ms
btn_next.png
1968 ms
btn_search_top_r.png
351 ms
btn_right_mypage_join_r.png
393 ms
btn_login_r.png
351 ms
btn_renew_r.jpg
392 ms
bn_openhouse_r.jpg
501 ms
btn_blogtop_r.jpg
334 ms
bn_shosai_r.jpg
956 ms
bn_saiyou_r.jpg
682 ms
btn_navi_urirai_r.png
688 ms
btn_navi_kaitai_r.png
765 ms
btn_navi_toushi_r.png
766 ms
btn_navi_store_r.png
921 ms
btn_navi_useful_r.png
1014 ms
btn_top_uritai_r.jpg
1365 ms
btn_top_kaitai_r.jpg
1674 ms
btn_top_toushi_r.jpg
1496 ms
btn_top_tenpo_r.jpg
1429 ms
btn_prev_s.png
1113 ms
btn_next_s.png
1181 ms
smtrc.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
smtrc.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
smtrc.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 Smtrc.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 Smtrc.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.
smtrc.jp
Open Graph description is not detected on the main page of Smtrc. 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: