Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

uhomes.co.jp

手が届く、憧れの港区・六本木の賃貸なら株式会社アーバンホームズにお任せ下さい

Page Load Speed

6.9 sec in total

First Response

366 ms

Resources Loaded

6.1 sec

Page Rendered

409 ms

About Website

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

株式会社アーバンホームズでは、港区・六本木の賃貸マンション、賃貸店舗、事務所情報を豊富に取り揃えています。長年六本木に根ざし、地域に精通したスタッフがご案内いたします。誠実・親切・すばやい対応でお客様の住まい探しを真剣に、全力でお手伝いいたします。

Visit uhomes.co.jp

Key Findings

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

Performance Metrics

uhomes.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.443

21/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

uhomes.co.jp

366 ms

uhomes.co.jp

598 ms

www.uhomes.co.jp

334 ms

www.uhomes.co.jp

1061 ms

common.css

182 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 77% of them (102 requests) were addressed to the original Uhomes.co.jp, 10% (13 requests) were made to Cdn.img-asp.jp and 8% (10 requests) were made to Lab3cdn.ielove.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Cdn.img-asp.jp.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.7 MB

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

HTML Optimization

-88%

Potential reduce by 129.0 kB

  • Original 146.0 kB
  • After minification 97.7 kB
  • After compression 17.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. This page needs HTML code to be minified as it can gain 48.3 kB, which is 33% 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 129.0 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 72.2 kB

  • Original 1.8 MB
  • After minification 1.7 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. Uhomes images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

Number of requests can be reduced by 19 (15%)

Requests Now

128

After Optimization

109

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

Accessibility Review

uhomes.co.jp accessibility score

90

Accessibility Issues

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

uhomes.co.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

uhomes.co.jp SEO score

83

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 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 Uhomes.co.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 Uhomes.co.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

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