Tools & Wizards About Us

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

idin.co.jp

SEO内部施策専門、内部対策、サイト制作は株式会社アイディーン

Page Load Speed

4.8 sec in total

First Response

671 ms

Resources Loaded

3.9 sec

Page Rendered

293 ms

About Website

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

被リンクに頼らないＳＥＯ内部施策を専門で行っております。SEO内部対策、サイト制作は、株式会社アイディーンにお任せ下さい。その他ＳＥＭ、リスティング運用、インターネット広告等もご相談下さい。

Visit idin.co.jp

Key Findings

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

Performance Metrics

idin.co.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value2,540 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.9 s

1/100

10%

Network Requests Diagram

idin.co.jp

671 ms

import.css

323 ms

jquery-1.4.4.min.js

868 ms

jquery.page-scroller-308.js

352 ms

opacity-rollover2.1.js

351 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 75% of them (55 requests) were addressed to the original Idin.co.jp, 7% (5 requests) were made to Youtube.com and 5% (4 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source V1.chamo-chat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.8 kB (11%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Idin.co.jp main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 736.9 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 13.2 kB

  • Original 18.5 kB
  • After minification 16.8 kB
  • After compression 5.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. 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 13.2 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 4.2 kB

  • Original 736.9 kB
  • After minification 732.7 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. Idin images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 78.8 kB

  • Original 291.5 kB
  • After minification 279.6 kB
  • After compression 212.6 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 78.8 kB or 27% of the original size.

CSS Optimization

-31%

Potential reduce by 29.6 kB

  • Original 94.7 kB
  • After minification 86.9 kB
  • After compression 65.0 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. Idin.co.jp needs all CSS files to be minified and compressed as it can save up to 29.6 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (34%)

Requests Now

70

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

idin.co.jp accessibility score

95

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

Best Practices

idin.co.jp 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

High

Page has valid source maps

SEO Factors

idin.co.jp 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

    EUC-JP

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