Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

i-x.cc

新宿区 株式会社イクス~不動産売買のご相談は株式会社イクスへ~(1都3県)

Page Load Speed

6.2 sec in total

First Response

297 ms

Resources Loaded

5.4 sec

Page Rendered

500 ms

i-x.cc screenshot

About Website

Click here to check amazing I X content. Otherwise, check out these important facts you probably never knew about i-x.cc

1都3県で不動産売買をご検討されているお客様は、新宿にある株式会社イクスにぜひご相談ください。弊社では、お客様本位の住みやすさや、資産価値の向上を考えて、コンサルタントサービスをご提供しております。ご不満やご要望も含めてお気軽にご相談ください。

Visit i-x.cc

Key Findings

We analyzed I-x.cc page load time and found that the first response time was 297 ms and then it took 5.9 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

i-x.cc performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value24.8 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.174

69/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

i-x.cc

297 ms

i-x.cc

596 ms

www.i-x.cc

288 ms

www.i-x.cc

666 ms

ui-meiriyo.css

172 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 78% of them (84 requests) were addressed to the original I-x.cc, 14% (15 requests) were made to Lab3cdn.ielove.jp 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) relates to the external source Cdn.img-asp.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.7 kB (5%)

Content Size

2.4 MB

After Optimization

2.3 MB

In fact, the total size of I-x.cc main page is 2.4 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 73.9 kB

  • Original 86.0 kB
  • After minification 53.2 kB
  • After compression 12.1 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 32.8 kB, which is 38% 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 73.9 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 42.7 kB

  • Original 2.3 MB
  • After minification 2.3 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. I X 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 28 (27%)

Requests Now

104

After Optimization

76

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

Accessibility Review

i-x.cc accessibility score

85

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Best Practices

i-x.cc best practices score

67

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

SEO Factors

i-x.cc SEO score

69

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

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 I-x.cc 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 I-x.cc 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 I X. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: