Tools & Wizards About Us
nom-rent.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

nom-rent.com

理想のお部屋探しは野村の賃貸から

Page Load Speed

5.8 sec in total

First Response

552 ms

Resources Loaded

4.6 sec

Page Rendered

568 ms

nom-rent.com screenshot

About Website

Click here to check amazing Nom Rent content for Japan. Otherwise, check out these important facts you probably never knew about nom-rent.com

野村不動産グループがお届けする賃貸マンション。野村の賃貸公式サイトです。

Visit nom-rent.com

Key Findings

We analyzed Nom-rent.com page load time and found that the first response time was 552 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

nom-rent.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.408

24/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

nom-rent.com

552 ms

www.nom-rent.com

561 ms

reset.css

360 ms

common.css

363 ms

top.css

364 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 51% of them (50 requests) were addressed to the original Nom-rent.com, 3% (3 requests) were made to Kdex004.deqwas.net and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Nom-rent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.9 kB (23%)

Content Size

347.9 kB

After Optimization

269.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nom-rent.com main page is 347.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. 30% of websites need less resources to load. Images take 242.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 27.1 kB

  • Original 34.3 kB
  • After minification 26.9 kB
  • After compression 7.2 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 7.5 kB, which is 22% 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 27.1 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 8.0 kB

  • Original 242.5 kB
  • After minification 234.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. Nom Rent images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 43.8 kB

  • Original 71.1 kB
  • After minification 70.8 kB
  • After compression 27.3 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 43.8 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (52%)

Requests Now

77

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nom-rent.com

nom-rent.com

552 ms

www.nom-rent.com

www.nom-rent.com

561 ms

reset.css

reset.css

360 ms

common.css

common.css

363 ms

top.css

top.css

364 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

555 ms

yugaAutoLine.js

yugaAutoLine.js

386 ms

jquery.cookie.js

jquery.cookie.js

389 ms

jquery.page-scroller-306.js

jquery.page-scroller-306.js

711 ms

nomuraCommon.js

nomuraCommon.js

727 ms

common.js

common.js

744 ms

jquery.lazyload.js

jquery.lazyload.js

772 ms

analytics.js

analytics.js

45 ms

fbds.js

fbds.js

167 ms

bg.jpg

bg.jpg

1864 ms

nomuraPTlogo.png

nomuraPTlogo.png

325 ms

logo.png

logo.png

358 ms

tel.png

tel.png

364 ms

icon01.png

icon01.png

367 ms

icon02.png

icon02.png

373 ms

icon03.png

icon03.png

666 ms

icon04.png

icon04.png

684 ms

icon05.png

icon05.png

694 ms

icon06.png

icon06.png

714 ms

icon07.png

icon07.png

741 ms

searchBtn.png

searchBtn.png

1024 ms

imgArea.jpg

imgArea.jpg

1313 ms

imgRailway.jpg

imgRailway.jpg

1045 ms

imgMap.jpg

imgMap.jpg

1041 ms

phPROUDflat.jpg

phPROUDflat.jpg

1300 ms

PFlogo.png

PFlogo.png

1416 ms

phPRIMEueban.jpg

phPRIMEueban.jpg

1580 ms

PUlogo.png

PUlogo.png

1438 ms

bnrDownload.jpg

bnrDownload.jpg

1623 ms

bnrSupport.jpg

bnrSupport.jpg

1692 ms

bnrNomuraService.jpg

bnrNomuraService.jpg

1888 ms

ttl_topics.png

ttl_topics.png

1797 ms

ttl_newProperty.png

ttl_newProperty.png

1960 ms

ttl_recommend.png

ttl_recommend.png

1945 ms

bnrRecruit.jpg

bnrRecruit.jpg

2051 ms

bnrCompany.jpg

bnrCompany.jpg

2108 ms

pagetop.png

pagetop.png

2166 ms

tel.png

tel.png

2241 ms

nomuraLogo1.png

nomuraLogo1.png

2300 ms

copyright.png

copyright.png

2297 ms

nomuraLogo2.png

nomuraLogo2.png

2372 ms

gtm.js

gtm.js

98 ms

icon.png

icon.png

2434 ms

gNavBg.png

gNavBg.png

2464 ms

searchInput.png

searchInput.png

2559 ms

phNew.png

phNew.png

2576 ms

x.js

x.js

347 ms

collect

collect

19 ms

collect

collect

66 ms

collect

collect

5 ms

33 ms

icon.png

icon.png

2325 ms

loading.gif

loading.gif

2386 ms

top.js

top.js

305 ms

KcDeqwasAgent.js

KcDeqwasAgent.js

150 ms

Collection.aspx

Collection.aspx

152 ms

rtbsync.js

rtbsync.js

18 ms

Sync.aspx

Sync.aspx

354 ms

Sync.aspx

Sync.aspx

308 ms

Sync.aspx

Sync.aspx

350 ms

Sync.aspx

Sync.aspx

302 ms

Sync.aspx

Sync.aspx

372 ms

Sync.aspx

Sync.aspx

349 ms

Sync.aspx

Sync.aspx

303 ms

Sync.aspx

Sync.aspx

335 ms

Sync.aspx

Sync.aspx

305 ms

Sync.aspx

Sync.aspx

371 ms

Sync.aspx

Sync.aspx

333 ms

Sync.aspx

Sync.aspx

313 ms

Sync.aspx

Sync.aspx

322 ms

Sync.aspx

Sync.aspx

322 ms

Sync.aspx

Sync.aspx

315 ms

Sync.aspx

Sync.aspx

316 ms

DynamicRetargetUserSync.aspx

DynamicRetargetUserSync.aspx

312 ms

Collection.aspx

Collection.aspx

342 ms

304 ms

cookiesync

cookiesync

311 ms

cs

cs

329 ms

Sync.aspx

Sync.aspx

488 ms

sync

sync

661 ms

sync

sync

5 ms

sd

sd

24 ms

tap.php

tap.php

6 ms

mapuser

mapuser

149 ms

Collection.aspx

Collection.aspx

154 ms

Collection.aspx

Collection.aspx

164 ms

Collection.aspx

Collection.aspx

152 ms

Collection.aspx

Collection.aspx

155 ms

pixel

pixel

22 ms

Collection.aspx

Collection.aspx

157 ms

pixel

pixel

21 ms

Collection.aspx

Collection.aspx

151 ms

Collection.aspx

Collection.aspx

156 ms

Collection.aspx

Collection.aspx

312 ms

Accessibility Review

nom-rent.com accessibility score

88

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

<frame> or <iframe> elements do not have a title

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

nom-rent.com best practices score

75

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

High

Page has valid source maps

SEO Factors

nom-rent.com SEO score

90

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

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nom-rent.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nom-rent.com 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

nom-rent.com

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