Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

resix.jp

不動産再生 株式会社レジックス

Page Load Speed

4 sec in total

First Response

546 ms

Resources Loaded

3 sec

Page Rendered

405 ms

resix.jp screenshot

About Website

Visit resix.jp now to see the best up-to-date Resix content and also check out these interesting facts you probably never knew about resix.jp

投資用不動産(日本全国)を中心に不動産再生事業、不動産の有効活用、購入・売却・資産価値向上に取り組んでいます。不動産再生はレジックス

Visit resix.jp

Key Findings

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

Performance Metrics

resix.jp performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

resix.jp

546 ms

jquery.min.js

8 ms

jquery.slider.min.js

180 ms

jquery.slider.css

344 ms

style.css

342 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 99% of them (72 requests) were addressed to the original Resix.jp, 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Resix.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.9 kB (30%)

Content Size

228.7 kB

After Optimization

159.8 kB

In fact, the total size of Resix.jp main page is 228.7 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. 25% of websites need less resources to load. Images take 121.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 7.4 kB

  • Original 9.9 kB
  • After minification 9.0 kB
  • After compression 2.5 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 7.4 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 29 B

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

JavaScript Optimization

-63%

Potential reduce by 61.2 kB

  • Original 96.5 kB
  • After minification 96.5 kB
  • After compression 35.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 61.2 kB or 63% of the original size.

CSS Optimization

-20%

Potential reduce by 240 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 950 B

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. Resix.jp needs all CSS files to be minified and compressed as it can save up to 240 B or 20% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

44

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

Accessibility Review

resix.jp accessibility score

100

Accessibility Issues

Best Practices

resix.jp best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

resix.jp SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    X-SJIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Resix.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 Resix.jp main page’s claimed encoding is x-sjis. 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 Resix. 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: