Tools & Wizards About Us
whitehouse.jp screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

whitehouse.jp

不動産会社ランキング | 口コミで評判の賃貸物件ナビ

Page Load Speed

3.2 sec in total

First Response

757 ms

Resources Loaded

2.2 sec

Page Rendered

262 ms

whitehouse.jp screenshot

About Website

Click here to check amazing Whitehouse content. Otherwise, check out these important facts you probably never knew about whitehouse.jp

サイトの利用者に聞いたおすすめの不動産会社をランキングで紹介。ネットでの賃貸会社への問い合わせから部屋探しで訪問する際に知っておきたい注意事項や、引越しのスケジュールで失敗しないためのチェック事項をまとめています。

Visit whitehouse.jp

Key Findings

We analyzed Whitehouse.jp page load time and found that the first response time was 757 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

whitehouse.jp performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

Network Requests Diagram

whitehouse.jp

757 ms

style-css.css

347 ms

img1.jpg

716 ms

apaman1.jpg

900 ms

mast1.jpg

949 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 83% of them (19 requests) were addressed to the original Whitehouse.jp, 13% (3 requests) were made to J1.ax.xrea.com and 4% (1 request) were made to Wj.ax.xrea.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Whitehouse.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.5 kB (11%)

Content Size

476.2 kB

After Optimization

422.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-67%

Potential reduce by 8.0 kB

  • Original 11.9 kB
  • After minification 10.9 kB
  • After compression 4.0 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. 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 8.0 kB or 67% of the original size.

Image Optimization

-8%

Potential reduce by 33.7 kB

  • Original 448.4 kB
  • After minification 414.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. Whitehouse images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 3.9 kB

  • Original 6.5 kB
  • After minification 6.3 kB
  • After compression 2.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.9 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 7.9 kB

  • Original 9.4 kB
  • After minification 6.4 kB
  • After compression 1.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. Whitehouse.jp needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

22

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whitehouse.jp

whitehouse.jp

757 ms

style-css.css

style-css.css

347 ms

img1.jpg

img1.jpg

716 ms

apaman1.jpg

apaman1.jpg

900 ms

mast1.jpg

mast1.jpg

949 ms

chintai1.jpg

chintai1.jpg

964 ms

able1.jpg

able1.jpg

858 ms

athome1.jpg

athome1.jpg

533 ms

dot-r1.jpg

dot-r1.jpg

898 ms

arrow.gif

arrow.gif

720 ms

l.j

l.j

460 ms

bg.gif

bg.gif

724 ms

top.jpg

top.jpg

1283 ms

bbg.gif

bbg.gif

787 ms

check.gif

check.gif

803 ms

th2.jpg

th2.jpg

882 ms

th.jpg

th.jpg

895 ms

st.gif

st.gif

900 ms

li.gif

li.gif

972 ms

fbg.gif

fbg.gif

992 ms

l122.f

l122.f

512 ms

x.gif

x.gif

153 ms

ts.gif

ts.gif

299 ms

Accessibility Review

whitehouse.jp accessibility score

76

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

whitehouse.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

whitehouse.jp SEO score

92

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 uses legible font sizes

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 Whitehouse.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 Whitehouse.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

whitehouse.jp

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