Tools & Wizards About Us

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

ooyanet.jp

頑張れ！DX大家さん！大家さんが情報発信する側に立つ！大家さんがデジタルトランスフォーメーション（DX）を起こすと日本の賃貸は変わる　大家ネット

Page Load Speed

2.6 sec in total

First Response

408 ms

Resources Loaded

1.7 sec

Page Rendered

454 ms

About Website

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

大家業のススメ！社会実験　賃貸DX「大家さんがホームページを持ったら日本の賃貸は変わるか？」がんばれ大家さん。金融業から大家業に！大家ネット　大家さんがデジタルトランスフォーメーション（DX）を起こすと日本の賃貸は変わる。大家の空室対策！ネットワーク経営　大家さんがホームページを持ち、相互営業のネットワークを組むと集客コストが限りなくゼロになる。結いの賃貸　賃貸のブロックチェーン、シェアリングエコ...

Visit ooyanet.jp

Key Findings

We analyzed Ooyanet.jp page load time and found that the first response time was 408 ms and then it took 2.2 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

ooyanet.jp performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

ooyanet.jp

408 ms

t9TiM_XLrOI

148 ms

ooyanet.jpeg

639 ms

1.gif

639 ms

www-player.css

13 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 21% of them (3 requests) were addressed to the original Ooyanet.jp, 43% (6 requests) were made to Youtube.com and 14% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (639 ms) belongs to the original domain Ooyanet.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 339.8 kB (74%)

Content Size

460.9 kB

After Optimization

121.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ooyanet.jp main page is 460.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. 70% of websites need less resources to load. CSS take 366.7 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 5.7 kB

  • Original 9.3 kB
  • After minification 9.2 kB
  • After compression 3.6 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 5.7 kB or 62% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 33.9 kB
  • After minification 33.9 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. Ooyanet images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 24.3 kB

  • Original 51.1 kB
  • After minification 51.1 kB
  • After compression 26.8 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 24.3 kB or 47% of the original size.

CSS Optimization

-85%

Potential reduce by 309.8 kB

  • Original 366.7 kB
  • After minification 366.5 kB
  • After compression 56.8 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. Ooyanet.jp needs all CSS files to be minified and compressed as it can save up to 309.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (45%)

Requests Now

11

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

ooyanet.jp accessibility score

70

Accessibility Issues

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

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

Page has valid source maps

SEO Factors

ooyanet.jp SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

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

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