Tools & Wizards About Us
idex.jp screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

idex.jp

HP移転のお知らせ　IDEX|アイデックス株式会社

Page Load Speed

1.2 sec in total

First Response

578 ms

Resources Loaded

602 ms

Page Rendered

67 ms

idex.jp screenshot

About Website

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

Visit idex.jp

Key Findings

We analyzed Idex.jp page load time and found that the first response time was 578 ms and then it took 669 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

idex.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

idex.jp

578 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Idex.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (578 ms) belongs to the original domain Idex.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.9 kB (41%)

Content Size

117.7 kB

After Optimization

69.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Idex.jp main page is 117.7 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Javascripts take 60.5 kB which makes up the majority of the site volume.

HTML Optimization

-24%

Potential reduce by 70 B

  • Original 296 B
  • After minification 293 B
  • After compression 226 B

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 70 B or 24% of the original size.

Image Optimization

-2%

Potential reduce by 957 B

  • Original 47.4 kB
  • After minification 46.4 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. IDEX images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 40.1 kB

  • Original 60.5 kB
  • After minification 56.6 kB
  • After compression 20.4 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 40.1 kB or 66% of the original size.

CSS Optimization

-71%

Potential reduce by 6.8 kB

  • Original 9.5 kB
  • After minification 7.6 kB
  • After compression 2.7 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. Idex.jp needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 71% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Network Requests Diagram

idex.jp

idex.jp

578 ms

Accessibility Review

idex.jp accessibility score

88

Accessibility Issues

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

idex.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

idex.jp SEO score

64

Search Engine Optimization Advices

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

idex.jp

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