Tools & Wizards About Us
iog.co.jp screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

iog.co.jp

イオグラフィック

Page Load Speed

1.7 sec in total

First Response

530 ms

Resources Loaded

1.1 sec

Page Rendered

112 ms

iog.co.jp screenshot

About Website

Welcome to iog.co.jp homepage info - get ready to check Iog best content for Japan right away, or after learning these important things about iog.co.jp

イオグラフィック

Visit iog.co.jp

Key Findings

We analyzed Iog.co.jp page load time and found that the first response time was 530 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

iog.co.jp performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

iog.co.jp

530 ms

base.css

182 ms

index.css

346 ms

index_mov.js

356 ms

ga.js

373 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 80% of them (8 requests) were addressed to the original Iog.co.jp, 20% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (530 ms) belongs to the original domain Iog.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

26.2 kB

After Optimization

23.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Iog.co.jp main page is 26.2 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 5% of websites need less resources to load. Javascripts take 23.2 kB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 681 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 756 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 681 B or 47% of the original size.

JavaScript Optimization

-5%

Potential reduce by 1.2 kB

  • Original 23.2 kB
  • After minification 23.0 kB
  • After compression 22.0 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.

CSS Optimization

-65%

Potential reduce by 1.0 kB

  • Original 1.6 kB
  • After minification 1.1 kB
  • After compression 548 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. Iog.co.jp needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 65% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iog. According to our analytics all requests are already optimized.

Network Requests Diagram

iog.co.jp

iog.co.jp

530 ms

base.css

base.css

182 ms

index.css

index.css

346 ms

index_mov.js

index_mov.js

356 ms

ga.js

ga.js

373 ms

logo.gif

logo.gif

370 ms

copyright.gif

copyright.gif

204 ms

btn_enter.gif

btn_enter.gif

186 ms

analytics.js

analytics.js

21 ms

collect

collect

12 ms

Accessibility Review

iog.co.jp accessibility score

60

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Tables and lists

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

Impact

Issue

High

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

Best Practices

iog.co.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

iog.co.jp SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iog.co.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Iog.co.jp main page’s claimed encoding is shift_jis. 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

iog.co.jp

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