Tools & Wizards About Us
ihouse.jp screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

ihouse.jp

大阪市旭区、鶴見区、城東区・守口市・門真市の不動産のことなら株式会社インターアクティブ　TEL:06-6992-3020

Page Load Speed

3.8 sec in total

First Response

850 ms

Resources Loaded

2.5 sec

Page Rendered

435 ms

ihouse.jp screenshot

About Website

Welcome to ihouse.jp homepage info - get ready to check Ihouse best content right away, or after learning these important things about ihouse.jp

【ihouse.jp(株式会社インターアクティブ　新築一戸建て】関西で新築分譲・建売住宅のマイホーム購入を考えているあなたをトータルにサポートする一軒家・一戸建て購入のウェブサイトです。関西の新築一戸建て・建て売り住宅販売の最新情報を毎日更新、さなざまなエリアから検索できます。

Visit ihouse.jp

Key Findings

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

Performance Metrics

ihouse.jp performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

68/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

Network Requests Diagram

ihouse.jp

850 ms

style.css

175 ms

openclose.js

335 ms

slide_simple_pack.js

389 ms

toplogo.gif

217 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 92% of them (22 requests) were addressed to the original Ihouse.jp, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ihouse.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.5 kB (2%)

Content Size

1.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ihouse.jp main page is 1.4 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. 25% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 21.8 kB

  • Original 27.3 kB
  • After minification 23.0 kB
  • After compression 5.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 4.3 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 21.8 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 7.0 kB

  • Original 1.4 MB
  • After minification 1.4 MB

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. Ihouse images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 1.1 kB

  • Original 23.7 kB
  • After minification 23.7 kB
  • After compression 22.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-50%

Potential reduce by 2.7 kB

  • Original 5.3 kB
  • After minification 5.3 kB
  • After compression 2.6 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. Ihouse.jp needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 50% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

23

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ihouse. According to our analytics all requests are already optimized.

Network Requests Diagram

ihouse.jp

ihouse.jp

850 ms

style.css

style.css

175 ms

openclose.js

openclose.js

335 ms

slide_simple_pack.js

slide_simple_pack.js

389 ms

toplogo.gif

toplogo.gif

217 ms

topbunner1.jpg

topbunner1.jpg

497 ms

00004615.jpg

00004615.jpg

825 ms

00004605.jpg

00004605.jpg

661 ms

00004594.jpg

00004594.jpg

684 ms

00004483.jpg

00004483.jpg

673 ms

00004573.jpg

00004573.jpg

683 ms

00004553.jpg

00004553.jpg

831 ms

00004543.jpg

00004543.jpg

1157 ms

00004533.jpg

00004533.jpg

1011 ms

00004523.jpg

00004523.jpg

1199 ms

00004513.jpg

00004513.jpg

1197 ms

00004327.jpg

00004327.jpg

995 ms

00004274.jpg

00004274.jpg

1165 ms

00004055.jpg

00004055.jpg

1169 ms

00003773.jpg

00003773.jpg

1342 ms

00003697.jpg

00003697.jpg

1330 ms

analytics.js

analytics.js

20 ms

collect

collect

13 ms

btn_net2.png

btn_net2.png

169 ms

Accessibility Review

ihouse.jp accessibility score

71

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

ihouse.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

ihouse.jp SEO score

75

Search Engine Optimization Advices

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

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

Social Sharing Optimization

ihouse.jp

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