livable.co.jp Website Information
Daily Unique Visits: 4,336
Daily Page Views: 17,344
Income Per Day: $49
Estimated Value: $26,460
livable.co.jp is registered under .JP top-level domain. Please check other sites in .JP zone.
No name server records were found.
and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.
The highest website livable.co.jp position in Alexa rank database was 6113 and the lowest rank position was 983098. Current position of livable.co.jp in Alexa rank database is 289441.
Desktop speed score of livable.co.jp (57/100) is better than the results of 31.79% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of livable.co.jp (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed score of livable.co.jp (28/100) is better than the results of 8.55% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
livable.co.jp Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
livable.co.jp whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]
Domain Information: [ドメイン情報]
a. [ドメイン名] LIVABLE.CO.JP
e. [そしきめい] とうきゅうりばぶるかぶしきがいしゃ
f. [組織名] 東急リバブル株式会社
g. [Organization] TOKYU LIVABLE.INC.
k. [組織種別] 株式会社
l. [Organization Type] INCORPORATED
m. [登録担当者] TY473JP
n. [技術連絡担当者] TY473JP
p. [ネームサーバ] ns-77.awsdns-09.com
p. [ネームサーバ] ns-1679.awsdns-17.co.uk
p. [ネームサーバ] ns-969.awsdns-57.net
p. [ネームサーバ] ns-1395.awsdns-46.org
s. [署名鍵]
[状態] Connected (2021/04/30)
[登録年月日] 1997/04/18
[接続年月日] 1998/03/09
[最終更新] 2020/05/01 01:02:24 (JST)
livable.co.jp server information
Servers Location
livable.co.jp desktop page speed rank
Last tested: 2016-10-11
livable.co.jp Desktop Speed Test Quick Summary
priority - 52Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 509.6KiB (78% reduction).
Compressing http://www.livable.co.jp/js/constants.js?d=2016-10-05_11-03-06 could save 114.6KiB (69% reduction).
Compressing http://www.livable.co.jp/ could save 51.1KiB (74% reduction).
Compressing http://www.livable.co.jp/css/structure.css could save 25.3KiB (82% reduction).
Compressing http://www.livable.co.jp/css/color.css could save 20.5KiB (88% reduction).
Compressing http://livable-inhale.team-rec.jp/js/tlab-dmp.js could save 19.8KiB (76% reduction).
Compressing http://www.livable.co.jp/js/lib/underscore.min.js?d=2016-10-05_11-03-06 could save 8KiB (66% reduction).
Compressing http://www.livable.co.jp/js/search/common.js?d=2016-10-05_11-03-06 could save 4.7KiB (70% reduction).
Compressing http://www.livable.co.jp/css/base.css could save 2.8KiB (64% reduction).
Compressing http://www.livable.co.jp/js/top/maparea.js?d=2016-10-05_11-03-06 could save 2.4KiB (75% reduction).
Compressing https://seal.verisign.com/getseal?host_name=www.li…ransparent=YES&lang=ja could save 1.8KiB (59% reduction).
Compressing http://www.livable.co.jp/js/lib/modernizr.js?d=2016-10-05_11-03-06 could save 1.7KiB (52% reduction).
Compressing http://www.livable.co.jp/js/top/sliderbanner.js?d=2016-10-05_11-03-06 could save 1.1KiB (54% reduction).
priority - 14Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
http://www.livable.co.jp/js/constants.js?d=2016-10-05_11-03-06
http://www.livable.co.jp/js/top/top/top.js?d=2016-10-05_11-03-06
http://www.livable.co.jp/js/top/maparea.js?d=2016-10-05_11-03-06
http://www.livable.co.jp/js/top/sliderbanner.js?d=2016-10-05_11-03-06
Optimize CSS Delivery of the following:
http://www.livable.co.jp/css/base.css
http://www.livable.co.jp/css/structure.css
http://www.livable.co.jp/css/module.css
http://www.livable.co.jp/css/color.css
http://fonts.googleapis.com/css?family=Abril+Fatface
priority - 7Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 64.2KiB (18% reduction).
Minifying http://www.livable.co.jp/css/color.css could save 10.1KiB (44% reduction).
Minifying http://www.livable.co.jp/css/structure.css could save 4.4KiB (15% reduction).
Minifying http://www.livable.co.jp/css/base.css could save 1.2KiB (28% reduction).
priority - 5Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://livable-inhale.team-rec.jp/js/tlab-dmp.js (expiration not specified)
https://s.yimg.jp/images/listing/tool/cv/conversion.js (10 minutes)
http://s.yjtag.jp/tag.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-MG5FDW (15 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://seal.verisign.com/getseal?host_name=www.li…ransparent=YES&lang=ja (59.1 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://seal.websecurity.norton.com/getseal?at=0&s…ang=ja&tpt=transparent (60 minutes)
http://stats.g.doubleclick.net/dc.js (2 hours)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 2Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 18.8KiB (26% reduction).
Compressing http://www.livable.co.jp/images/banner_sub_06.png could save 2.4KiB (12% reduction).
Compressing http://www.livable.co.jp/images/logo_03.png could save 1.6KiB (44% reduction).
Compressing http://www.livable.co.jp/images/label_keyword.png could save 1.5KiB (43% reduction).
Compressing http://www.livable.co.jp/images/label_map.png could save 1.4KiB (45% reduction).
Compressing http://www.livable.co.jp/images/bg_toplink_un_01.png could save 1.4KiB (11% reduction).
Compressing http://www.livable.co.jp/images/text_promo_rentout_02.png could save 1.3KiB (58% reduction).
Compressing http://www.livable.co.jp/images/ttl_service_01.png could save 1.2KiB (57% reduction).
Compressing http://www.livable.co.jp/images/ttl_tvcm.png could save 1.1KiB (28% reduction).
Compressing http://www.livable.co.jp/images/icn-link-blank.png could save 977B (85% reduction).
Compressing http://www.livable.co.jp/images/ttl_menu_10.png could save 952B (59% reduction).
Compressing http://www.livable.co.jp/images/top_bg_01.png could save 859B (87% reduction).
Compressing http://www.livable.co.jp/images/btn_my_livable_new.png could save 855B (34% reduction).
priority - 1Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 9.3KiB (36% reduction).
priority - 0Reduce server response time
livable.co.jp Desktop Resource Breakdown
Total Resources | 228 |
Number of Hosts | 26 |
Static Resources | 158 |
JavaScript Resources | 31 |
CSS Resources | 7 |
livable.co.jp mobile page speed rank
Last tested: 2019-12-16
livable.co.jp Mobile Speed Test Quick Summary
priority - 76Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 739.9KiB (84% reduction).
Compressing https://livable-inhale.team-rec.jp/js/tlab-dmp.js could save 24.1KiB (76% reduction).
Compressing https://d-track.send.microad.jp/js/blade_track_jp.js could save 2.7KiB (66% reduction).
Compressing https://seal.websecurity.norton.com/getseal?host_n…ransparent=YES&lang=ja could save 1.5KiB (58% reduction).
Compressing https://ad.atown.jp/adserver/js/lib/clickaction/click.js could save 1.2KiB (57% reduction).
Compressing https://s.yjtag.jp/lib/3c4655df884e7453073965cf8aa42248f1df0c75.js?v=2 could save 304B (50% reduction).
Compressing https://s.yjtag.jp/lib/f27602c44fe84c6dcca4e538e87b91bca5195e79.js?v=2 could save 304B (50% reduction).
Compressing https://s.yjtag.jp/lib/0667c11284280fc200f1ed29080e5114d0cf52f5.js?v=2 could save 299B (50% reduction).
Compressing https://s.yjtag.jp/lib/685ac1326b0e74c5b787b6cc8687d7b21862c520.js?v=2 could save 285B (49% reduction).
Compressing https://s.yjtag.jp/lib/d18b7fd427eb44a7bd0fa51248fb7eff514a0103.js?v=2 could save 285B (49% reduction).
Compressing https://s.yjtag.jp/lib/0758856cd77139a1dcb103a96bd8a1afbc5b00b1.js?v=2 could save 284B (49% reduction).
priority - 72Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://fonts.googleapis.com/css?family=Droid+Sans:400,700
https://fonts.googleapis.com/css?family=Noto+Sans+JP
https://fonts.googleapis.com/css?family=Droid+Sans
https://fonts.googleapis.com/css?family=Droid+Sans%7CNoto+Sans+JP
priority - 62Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 607.5KiB (52% reduction).
Compressing https://www.livable.co.jp/assets/images/original/264497 could save 21.2KiB (38% reduction).
Compressing https://www.livable.co.jp/assets/images/original/261519 could save 14.8KiB (32% reduction).
Compressing https://www.livable.co.jp/assets/images/original/260701 could save 12.7KiB (21% reduction).
Compressing https://www.livable.co.jp/assets/images/original/264990 could save 12.3KiB (12% reduction).
Compressing https://www.livable.co.jp/images/t0001/t0001_thumbs_21.jpg could save 11.2KiB (64% reduction).
Compressing https://seal.websecurity.norton.com/getseal?at=0&s…ang=ja&tpt=transparent could save 2.5KiB (45% reduction).
Compressing https://www.livable.co.jp/assets/images/original/t0001_001_thumbs_20_sp.png could save 1.5KiB (30% reduction).
Compressing https://www.livable.co.jp/assets/images/original/t0001_001_thumbs_11_sp.png could save 1.4KiB (11% reduction).
Compressing https://yt3.ggpht.com/-hLdn2pRAT00/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 977B (40% reduction).
Compressing https://www.livable.co.jp/assets/images/original/t0001_001_thumbs_15_sp.png could save 873B (23% reduction).
Compressing https://www.livable.co.jp/assets/images/original/t0001_001_thumbs_10_sp.png could save 784B (14% reduction).
Compressing https://www.livable.co.jp/assets/images/original/t0001_001_thumbs_13_sp.png could save 107B (15% reduction).
priority - 24Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://b90.yahoo.co.jp/conv.js (expiration not specified)
https://livable-inhale.team-rec.jp/js/tlab-dmp.js (expiration not specified)
https://res.pdq.team-rec.jp/aibot/driver.js (expiration not specified)
https://s.yjtag.jp/tag.js (expiration not specified)
https://sdk.amazonaws.com/js/aws-sdk-2.1.18.min.js (expiration not specified)
https://www.livable.co.jp/images/common/bg_balloon_01.png (expiration not specified)
https://www.livable.co.jp/images/common/livable_logo_blue.png (expiration not specified)
https://www.livable.co.jp/images/common/livable_logo_catchcopy.png (expiration not specified)
https://www.livable.co.jp/images/common/mainva_bg.jpg (expiration not specified)
https://www.livable.co.jp/images/t0001/t0001_favorability01.png (expiration not specified)
https://www.livable.co.jp/images/t0001/t0001_thumbs_20.png (expiration not specified)
https://www.livable.co.jp/images/t0001/t0001_thumbs_21.jpg (expiration not specified)
https://www.livable.co.jp/livable-recommend/js.recommend/tlab_v4.js (expiration not specified)
https://www.livable.co.jp/livable-recommend/js.recommend/tlab_v4_iframe.js (expiration not specified)
https://js.ptengine.jp/77afd665.js (5 minutes)
https://js.ptengine.jp/pta.js (5 minutes)
https://b92.yahoo.co.jp/js/s_retargeting.js (10 minutes)
https://s.yimg.jp/images/listing/tool/cv/conversion.js (10 minutes)
https://s.yimg.jp/images/listing/tool/cv/ytag.js (10 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-860316861 (15 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-970609300 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-NQM5TS3 (15 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://seal.websecurity.norton.com/getseal?host_n…ransparent=YES&lang=ja (58.4 minutes)
https://b97.yahoo.co.jp/pagead/conversion_async.js (60 minutes)
https://seal.websecurity.norton.com/getseal?at=0&s…ang=ja&tpt=transparent (60 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://code.usergram.info/js/usergram.js (2 hours)
https://stats.g.doubleclick.net/dc.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 19Reduce server response time
In our test, your server responded in 1.4 seconds.
priority - 8Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 1Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 14KiB (32% reduction).
Minifying https://res.pdq.team-rec.jp/aibot/driver.js could save 1.2KiB (22% reduction) after compression.
Minifying https://ad.atown.jp/adserver/js/lib/clickaction/click.js could save 797B (38% reduction).
Minifying https://d-track.send.microad.jp/js/blade_track_jp.js could save 584B (15% reduction).
Minifying https://s.yjtag.jp/lib/a28ef273b989a01a969138e174704ef6b30f800e.js?v=2 could save 284B (22% reduction) after compression.
priority - 0Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 269B (18% reduction).
livable.co.jp Mobile Resource Breakdown
Total Resources | 222 |
Number of Hosts | 47 |
Static Resources | 55 |
JavaScript Resources | 98 |
CSS Resources | 7 |
livable.co.jp mobile page usability
Last tested: 2019-12-16
livable.co.jp Mobile Usability Test Quick Summary
priority - 0Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<li class="slick-active">1</li>
and 4 others are close to other tap targets.The tap target
<button type="button">1</button>
and 4 others are close to other tap targets.livable.co.jp HTML validation
Warnings
The “type” attribute is unnecessary for JavaScript resources.
"... <script type="text/javascript">window..." Line: 1409 Column: 5 - 35
"...ter> <script type="text/javascript">(funct..."
Errors
End tag “nav” seen, but there were open elements.
"...</ul> </nav> ..."
Unclosed element “ul”.
"...l-nav"> <ul class="m-header-nav__list"> <..." Line: 1080 Column: 15 - 47
"... <ul class="o-footer__other-list"> ..."
Saw “<” when expecting an attribute name. Probable cause: Missing “>” immediately before.
"... </ul> ..."
A slash was not immediately followed by “>”.
"... </ul> ..."
End tag had attributes.
"... </ul> <..."
End tag “dd” seen, but there were open elements.
"... </dd> ..."
The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.
"...script> <iframe src="//b.yjtag.jp/iframe?c=bdOUpx1" width="1" height="1" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></ifra..."
The “scrolling” attribute on the “iframe” element is obsolete. Use CSS instead.
"...script> <iframe src="//b.yjtag.jp/iframe?c=bdOUpx1" width="1" height="1" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></ifra..."
The “marginheight” attribute on the “iframe” element is obsolete. Use CSS instead.
"...script> <iframe src="//b.yjtag.jp/iframe?c=bdOUpx1" width="1" height="1" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></ifra..."
The “marginwidth” attribute on the “iframe” element is obsolete. Use CSS instead.
"...script> <iframe src="//b.yjtag.jp/iframe?c=bdOUpx1" width="1" height="1" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></ifra..."
livable.co.jp similar domains
www.livable.net
www.livable.org
www.livable.info
www.livable.biz
www.livable.us
www.livable.mobi
www.ivable.co.jp
www.livable.co.jp
www.pivable.co.jp
www.lpivable.co.jp
www.plivable.co.jp
www.oivable.co.jp
www.loivable.co.jp
www.olivable.co.jp
www.kivable.co.jp
www.lkivable.co.jp
www.klivable.co.jp
www.lvable.co.jp
www.luvable.co.jp
www.liuvable.co.jp
www.luivable.co.jp
www.ljvable.co.jp
www.lijvable.co.jp
www.ljivable.co.jp
www.lkvable.co.jp
www.likvable.co.jp
www.lovable.co.jp
www.liovable.co.jp
www.liable.co.jp
www.licable.co.jp
www.livcable.co.jp
www.licvable.co.jp
www.lifable.co.jp
www.livfable.co.jp
www.lifvable.co.jp
www.ligable.co.jp
www.livgable.co.jp
www.ligvable.co.jp
www.libable.co.jp
www.livbable.co.jp
www.libvable.co.jp
www.livble.co.jp
www.livqble.co.jp
www.livaqble.co.jp
www.livqable.co.jp
www.livwble.co.jp
www.livawble.co.jp
www.livwable.co.jp
www.livsble.co.jp
www.livasble.co.jp
www.livsable.co.jp
www.livzble.co.jp
www.livazble.co.jp
www.livzable.co.jp
www.livale.co.jp
www.livavle.co.jp
www.livabvle.co.jp
www.livavble.co.jp
www.livagle.co.jp
www.livabgle.co.jp
www.livagble.co.jp
www.livahle.co.jp
www.livabhle.co.jp
www.livahble.co.jp
www.livanle.co.jp
www.livabnle.co.jp
www.livanble.co.jp
www.livabe.co.jp
www.livabpe.co.jp
www.livablpe.co.jp
www.livabple.co.jp
www.livaboe.co.jp
www.livabloe.co.jp
www.livabole.co.jp
www.livabke.co.jp
www.livablke.co.jp
www.livabkle.co.jp
www.livabl.co.jp
www.livablw.co.jp
www.livablew.co.jp
www.livablwe.co.jp
www.livabls.co.jp
www.livables.co.jp
www.livablse.co.jp
www.livabld.co.jp
www.livabled.co.jp
www.livablde.co.jp
www.livablr.co.jp
www.livabler.co.jp
www.livablre.co.jp
livable.co.jp Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
livable.co.jp TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.