Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

villagehouse.jp

全国の賃貸物件 | 安いアパート・マンション探しはビレッジハウス

Page Load Speed

10 sec in total

First Response

358 ms

Resources Loaded

8.2 sec

Page Rendered

1.4 sec

villagehouse.jp screenshot

About Website

Welcome to villagehouse.jp homepage info - get ready to check Villagehouse best content for Japan right away, or after learning these important things about villagehouse.jp

敷金なし✔️更新料なし✔️礼金なし✔️仲介手数料無料の賃貸おすすめサイト!お仕事や進学の関係でお引越しをお考えですか?ワンルーム、1DK、2DKなどといった不動産賃貸物件を全国から集めました。リノベーション済みのお部屋探しはこちらから!

Visit villagehouse.jp

Key Findings

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

Performance Metrics

villagehouse.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value19.9 s

0/100

10%

TBT (Total Blocking Time)

Value47,560 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value60.0 s

0/100

10%

Network Requests Diagram

villagehouse.jp

358 ms

www.villagehouse.jp

634 ms

454 ms

jquery-ui.min.css

138 ms

css_VillageHouse_en.css

1238 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 10% of them (8 requests) were addressed to the original Villagehouse.jp, 29% (24 requests) were made to D1drfpduvreqeu.cloudfront.net and 6% (5 requests) were made to Dbimx453hpd6x.cloudfront.net. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source D1drfpduvreqeu.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.0 kB (10%)

Content Size

705.1 kB

After Optimization

634.1 kB

In fact, the total size of Villagehouse.jp main page is 705.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 428.5 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 65.3 kB

  • Original 89.4 kB
  • After minification 89.3 kB
  • After compression 24.1 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 65.3 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 2.9 kB

  • Original 428.5 kB
  • After minification 425.5 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. Villagehouse images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 2.8 kB

  • Original 76.9 kB
  • After minification 76.7 kB
  • After compression 74.2 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

-0%

Potential reduce by 0 B

  • Original 110.4 kB
  • After minification 110.4 kB
  • After compression 110.4 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. Villagehouse.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (59%)

Requests Now

59

After Optimization

24

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

Accessibility Review

villagehouse.jp accessibility score

73

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

villagehouse.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

villagehouse.jp SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Villagehouse.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Villagehouse.jp main page’s claimed encoding is iso-8859-1. 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

Open Graph data is detected on the main page of Villagehouse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: