Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

iko-yo.net

子供とお出かけ情報「いこーよ」

Page Load Speed

7.9 sec in total

First Response

958 ms

Resources Loaded

6.1 sec

Page Rendered

803 ms

iko-yo.net screenshot

About Website

Visit iko-yo.net now to see the best up-to-date Iko Yo content for Japan and also check out these interesting facts you probably never knew about iko-yo.net

子供とお出かけ情報サイト「いこーよ」は、親子で平日にお出かけできる遊び場、連休や週末のファミリー向けイベント情報が満載! おむつ替え台や授乳室、ベビーカー、託児所の有無など気になる情報がひと目でわかります。おでかけ施設の最新情報やアクセス人気ランキング、口コミ情報やお得なクーポンも。いこーよを活用して、家族でたくさんおでかけしよう!

Visit iko-yo.net

Key Findings

We analyzed Iko-yo.net page load time and found that the first response time was 958 ms and then it took 6.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

iko-yo.net performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value4,160 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.322

36/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

iko-yo.net

958 ms

application-e2c3eff51f2003ac813cda2effcdbd40.css

53 ms

application2-c128d67ac448abbebf5d395bc726c7b6.css

32 ms

application3-104a92d65b56605533e86194e1b034dc.css

23 ms

application-68f28d4a37c978ce456cb7f284808b89.js

74 ms

Our browser made a total of 183 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Iko-yo.net, 44% (81 requests) were made to D2goguvysdoarq.cloudfront.net and 9% (17 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source D2goguvysdoarq.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (40%)

Content Size

3.0 MB

After Optimization

1.8 MB

In fact, the total size of Iko-yo.net main page is 3.0 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 233.9 kB

  • Original 315.9 kB
  • After minification 315.7 kB
  • After compression 82.0 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 233.9 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 36.4 kB

  • Original 1.3 MB
  • After minification 1.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. Iko Yo images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 556.8 kB

  • Original 921.5 kB
  • After minification 921.3 kB
  • After compression 364.7 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 556.8 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 384.2 kB

  • Original 459.9 kB
  • After minification 456.3 kB
  • After compression 75.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. Iko-yo.net needs all CSS files to be minified and compressed as it can save up to 384.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (33%)

Requests Now

177

After Optimization

118

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

Accessibility Review

iko-yo.net accessibility score

77

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

iko-yo.net 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

iko-yo.net SEO score

92

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Iko-yo.net 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 Iko-yo.net 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 Iko Yo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: