Access j-reit.jp. J-REIT.jp　（Jリート） | Jリート（不動産投資信託）の総合情報サイト

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value29.2 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value1.089

1/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

j-reit.jp

543 ms

j-reit.jp

1718 ms

main.css

654 ms

responsive.css

491 ms

style.css

505 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 78% of them (59 requests) were addressed to the original J-reit.jp, 12% (9 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain J-reit.jp.

Content Size

567.3 kB

After Optimization

408.5 kB

In fact, the total size of J-reit.jp main page is 567.3 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 a small number of websites need less resources to load. Images take 289.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 37.8 kB

Original 46.1 kB
After minification 37.6 kB
After compression 8.3 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 8.5 kB, which is 18% 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 37.8 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 23.2 kB

Original 289.3 kB
After minification 266.2 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. J REIT images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 89.0 kB

Original 208.2 kB
After minification 208.0 kB
After compression 119.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 89.0 kB or 43% of the original size.

CSS Optimization

-38%

Potential reduce by 8.9 kB

Original 23.7 kB
After minification 23.6 kB
After compression 14.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. J-reit.jp needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 38% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

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.

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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/).

High

Document uses 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 J-reit.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 J-reit.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

j-reit.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

J-REIT.jp （Jリート） | Jリート（不動産投資信託）の総合情報サイト

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

j-reit.jp

j-reit.jp

main.css

responsive.css

style.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

j-reit.jp

j-reit.jp

main.css

responsive.css

style.css

mainvisual.css

jquery.js

util.js

main.js

parts.js

jquery.easing.1.3.js

jquery.flatHeightAll.min.js

tweenmax.min.js

jquery.cookie.js

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.js

index.js

accessibility.css

init.js

jkl-parsexml.js

remodal.css

remodal-default-theme.css

remodal.js

reset.css

util.css

fonts.css

notosansjapanese.css

css

jquery.mousewheel.min.js

gtm.js

ga.js

space.gif

all.js

parts.html

bnr-esg.jpg

main-osaka.gif

lead01.png

lead02.png

main-osaka-sp.gif

bnr-newnisa_s.png

bnr-jreit_guide_s.png

bnr-unyoshisan.png

bnr-jreit_rekishi.png

J-REIT.jp　（Jリート） | Jリート（不動産投資信託）の総合情報サイト