Tools & Wizards About Us
inakanet.jp screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

inakanet.jp

田舎暮らし物件情報『田舎ねっと.日本』 古民家・地方移住・田舎暮らし不動産

Page Load Speed

5.9 sec in total

First Response

560 ms

Resources Loaded

5 sec

Page Rendered

270 ms

inakanet.jp screenshot

About Website

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

田舎暮らし・地方移住を全国ネットで応援する田舎暮らし物件サイト。毎日更新の古民家、ログハウス、別荘、戸建、土地情報の他、家庭菜園、畑、自給自足ができる田舎物件や田舎不動産、移住向不動産満載！『田舎ねっと.日本』

Visit inakanet.jp

Key Findings

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

Performance Metrics

inakanet.jp performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

inakanet.jp

560 ms

www.inakanet.jp

1054 ms

home_main.css

352 ms

jquery.js

875 ms

jquery.innerfade.js

354 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 92% of them (86 requests) were addressed to the original Inakanet.jp, 5% (5 requests) were made to Mail.inakanet.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Inakanet.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.4 kB (36%)

Content Size

434.9 kB

After Optimization

277.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inakanet.jp main page is 434.9 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. 35% of websites need less resources to load. Images take 224.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 67.7 kB

  • Original 81.2 kB
  • After minification 68.3 kB
  • After compression 13.5 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 12.8 kB, which is 16% 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 67.7 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 707 B

  • Original 224.3 kB
  • After minification 223.6 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. Inakanet images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 74.5 kB

  • Original 111.7 kB
  • After minification 103.0 kB
  • After compression 37.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 74.5 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 14.5 kB

  • Original 17.7 kB
  • After minification 12.1 kB
  • After compression 3.2 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. Inakanet.jp needs all CSS files to be minified and compressed as it can save up to 14.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (42%)

Requests Now

91

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inakanet.jp

inakanet.jp

560 ms

www.inakanet.jp

www.inakanet.jp

1054 ms

home_main.css

home_main.css

352 ms

jquery.js

jquery.js

875 ms

jquery.innerfade.js

jquery.innerfade.js

354 ms

home_index.css

home_index.css

355 ms

txtscroll.js

txtscroll.js

355 ms

form.cgi

form.cgi

556 ms

form.cgi

form.cgi

600 ms

urchin.js

urchin.js

7 ms

head_inakanet_home.gif

head_inakanet_home.gif

350 ms

btn_bookmark.gif

btn_bookmark.gif

176 ms

img_mailde.gif

img_mailde.gif

178 ms

ic_list_inaho.gif

ic_list_inaho.gif

178 ms

v2_bnr_book01.gif

v2_bnr_book01.gif

354 ms

sell_img01b.jpg

sell_img01b.jpg

179 ms

sell_img02.gif

sell_img02.gif

352 ms

inbnr_bizpt255.jpg

inbnr_bizpt255.jpg

351 ms

ic_guide.gif

ic_guide.gif

352 ms

img_ranking.gif

img_ranking.gif

354 ms

ic_rank1.gif

ic_rank1.gif

525 ms

ic_rank2.gif

ic_rank2.gif

527 ms

ic_rank3.gif

ic_rank3.gif

527 ms

ic_rank4.gif

ic_rank4.gif

527 ms

ic_rank5.gif

ic_rank5.gif

528 ms

ic_rank6.gif

ic_rank6.gif

530 ms

ic_rank7.gif

ic_rank7.gif

700 ms

ic_rank8.gif

ic_rank8.gif

701 ms

ic_rank9.gif

ic_rank9.gif

702 ms

ic_rank10.gif

ic_rank10.gif

702 ms

sp_kominka.jpg

sp_kominka.jpg

703 ms

ic_list_house.gif

ic_list_house.gif

706 ms

img_house_soudan.gif

img_house_soudan.gif

875 ms

bn_surugabank.jpg

bn_surugabank.jpg

1050 ms

img_koga2.jpg

img_koga2.jpg

877 ms

bn_kominka.gif

bn_kominka.gif

876 ms

ic_up.gif

ic_up.gif

881 ms

pref_nagano.gif

pref_nagano.gif

882 ms

ic_hot.gif

ic_hot.gif

1050 ms

pref_saitama.gif

pref_saitama.gif

1051 ms

pref_hyogo.gif

pref_hyogo.gif

1052 ms

ic_new.gif

ic_new.gif

1056 ms

pref_nara.gif

pref_nara.gif

1059 ms

pref_okayama.gif

pref_okayama.gif

1225 ms

pref_miyagi.gif

pref_miyagi.gif

1225 ms

pref_mie.gif

pref_mie.gif

1209 ms

__utm.gif

__utm.gif

3 ms

pref_chiba.gif

pref_chiba.gif

1054 ms

pref_kyoto.gif

pref_kyoto.gif

1059 ms

pref_yamanashi.gif

pref_yamanashi.gif

1062 ms

area1.jpg

area1.jpg

1226 ms

area2.jpg

area2.jpg

1055 ms

area3.jpg

area3.jpg

1053 ms

area4.jpg

area4.jpg

1054 ms

area5.jpg

area5.jpg

1060 ms

area6.jpg

area6.jpg

1064 ms

area7.jpg

area7.jpg

1226 ms

area8.jpg

area8.jpg

1055 ms

area9.jpg

area9.jpg

1054 ms

area10.jpg

area10.jpg

1055 ms

area11.jpg

area11.jpg

1062 ms

area12.jpg

area12.jpg

1065 ms

arw_r_orgd.gif

arw_r_orgd.gif

1224 ms

new.gif

new.gif

1054 ms

ic_insta.gif

ic_insta.gif

1578 ms

ic_inakagurasiouenjuku.gif

ic_inakagurasiouenjuku.gif

1054 ms

map1.gif

map1.gif

1062 ms

img_search.jpg

img_search.jpg

1065 ms

KK_26238.jpg

KK_26238.jpg

1223 ms

TK_26234.jpg

TK_26234.jpg

1054 ms

TK_26311.jpg

TK_26311.jpg

1054 ms

TK_25224.jpg

TK_25224.jpg

1064 ms

TK_25899.jpg

TK_25899.jpg

1065 ms

CH_24382.jpg

CH_24382.jpg

1221 ms

SK_12210.jpg

SK_12210.jpg

1055 ms

logo_mojiSS.gif

logo_mojiSS.gif

1056 ms

address_br.gif

address_br.gif

1066 ms

ic_mail.gif

ic_mail.gif

1071 ms

banner_ohrai.gif

banner_ohrai.gif

1223 ms

bg_mailde2.jpg

bg_mailde2.jpg

1219 ms

bg_house_soudan2.jpg

bg_house_soudan2.jpg

1055 ms

ic_mushinegane_ss.gif

ic_mushinegane_ss.gif

1067 ms

ic_crown_ss.gif

ic_crown_ss.gif

1073 ms

ic_kominka_ss.gif

ic_kominka_ss.gif

1226 ms

ic_kirikabu_ss.gif

ic_kirikabu_ss.gif

1221 ms

bg_search1.gif

bg_search1.gif

1218 ms

bg_search2.gif

bg_search2.gif

1056 ms

bg_search3.gif

bg_search3.gif

1068 ms

search1_title.gif

search1_title.gif

1075 ms

search2_title.gif

search2_title.gif

1226 ms

form.cgi

form.cgi

211 ms

form.cgi

form.cgi

222 ms

form.cgi

form.cgi

210 ms

Accessibility Review

inakanet.jp accessibility score

63

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

inakanet.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inakanet.jp SEO score

64

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inakanet.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 Inakanet.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

inakanet.jp

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