Tools & Wizards About Us
omochaoukoku.co.jp screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

omochaoukoku.co.jp

おもちゃ王国 公式ＷＥＢ

Page Load Speed

5.8 sec in total

First Response

908 ms

Resources Loaded

4.8 sec

Page Rendered

140 ms

omochaoukoku.co.jp screenshot

About Website

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

おもちゃ王国公式ホームページ

Visit omochaoukoku.co.jp

Key Findings

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

Performance Metrics

omochaoukoku.co.jp performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

omochaoukoku.co.jp

908 ms

bg.gif

321 ms

main.gif

994 ms

shim.gif

1086 ms

spacer.gif

350 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 95% of them (58 requests) were addressed to the original Omochaoukoku.co.jp, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Omochaoukoku.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.9 kB (31%)

Content Size

34.6 kB

After Optimization

23.8 kB

  • HTML
  • JavaScript

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

HTML Optimization

-79%

Potential reduce by 10.8 kB

  • Original 13.7 kB
  • After minification 13.2 kB
  • After compression 2.8 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 10.8 kB or 79% of the original size.

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 35 (60%)

Requests Now

58

After Optimization

23

  • Images
  • JavaScript

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

Network Requests Diagram

omochaoukoku.co.jp

omochaoukoku.co.jp

908 ms

bg.gif

bg.gif

321 ms

main.gif

main.gif

994 ms

shim.gif

shim.gif

1086 ms

spacer.gif

spacer.gif

350 ms

top_r1_c3.gif

top_r1_c3.gif

365 ms

top_r1_c8.gif

top_r1_c8.gif

563 ms

top_r1_c14.gif

top_r1_c14.gif

630 ms

top_r2_c3.gif

top_r2_c3.gif

715 ms

top_o_r3_c1.gif

top_o_r3_c1.gif

683 ms

top_r3_c4.gif

top_r3_c4.gif

921 ms

top_r4_c4.gif

top_r4_c4.gif

958 ms

top_r4_c14.gif

top_r4_c14.gif

1025 ms

top_r5_c1.gif

top_r5_c1.gif

1107 ms

top_r5_c7.gif

top_r5_c7.gif

1271 ms

top_r5_c8.gif

top_r5_c8.gif

1301 ms

top_r5_c9.gif

top_r5_c9.gif

1358 ms

top_r5_c12.gif

top_r5_c12.gif

1391 ms

top_r5_c13.gif

top_r5_c13.gif

1385 ms

top_r6_c7.gif

top_r6_c7.gif

1443 ms

top_r6_c8.gif

top_r6_c8.gif

1609 ms

top_r6_c12.gif

top_r6_c12.gif

1677 ms

top_r7_c9.gif

top_r7_c9.gif

1763 ms

top_r7_c10.gif

top_r7_c10.gif

1786 ms

top_r7_c11.gif

top_r7_c11.gif

1805 ms

top_r8_c12.gif

top_r8_c12.gif

1836 ms

top_r9_c1.gif

top_r9_c1.gif

1946 ms

top_r9_c5.gif

top_r9_c5.gif

2006 ms

top_r9_c6.gif

top_r9_c6.gif

2141 ms

top_r10_c10.gif

top_r10_c10.gif

2166 ms

top_r11_c5.gif

top_r11_c5.gif

2199 ms

top_r12_c2.gif

top_r12_c2.gif

2240 ms

top_r12_c11.gif

top_r12_c11.gif

2108 ms

bottom.gif

bottom.gif

2395 ms

copy.gif

copy.gif

2325 ms

analytics.js

analytics.js

6 ms

collect

collect

12 ms

collect

collect

62 ms

top_r2_c2o.gif

top_r2_c2o.gif

177 ms

top_r2_c3o.gif

top_r2_c3o.gif

172 ms

top_r2_c4o.gif

top_r2_c4o.gif

334 ms

top_r2_c10o.gif

top_r2_c10o.gif

338 ms

top_r2_c13o.gif

top_r2_c13o.gif

360 ms

top_r2_c14o.gif

top_r2_c14o.gif

513 ms

top_r6_c5o.gif

top_r6_c5o.gif

526 ms

top_r5_c7o.gif

top_r5_c7o.gif

568 ms

top_r4_c7o.gif

top_r4_c7o.gif

687 ms

top_r4_c8o.gif

top_r4_c8o.gif

738 ms

top_r4_c11o.gif

top_r4_c11o.gif

728 ms

top_r5_c11o.gif

top_r5_c11o.gif

877 ms

top_o_r1_c3.gif

top_o_r1_c3.gif

901 ms

top_o_r1_c8.gif

top_o_r1_c8.gif

929 ms

top_o_r1_c14.gif

top_o_r1_c14.gif

1004 ms

top_o_r12_c2.gif

top_o_r12_c2.gif

1071 ms

top_o_r12_c11.gif

top_o_r12_c11.gif

1057 ms

top_o_r9_c5.gif

top_o_r9_c5.gif

1209 ms

top_o_r5_c7.gif

top_o_r5_c7.gif

1245 ms

top_o_r5_c8.gif

top_o_r5_c8.gif

1292 ms

top_o_r5_c12.gif

top_o_r5_c12.gif

1324 ms

top_o_r7_c10.gif

top_o_r7_c10.gif

1424 ms

top_o_r6_c7.gif

top_o_r6_c7.gif

1474 ms

Accessibility Review

omochaoukoku.co.jp accessibility score

66

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

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

Best Practices

omochaoukoku.co.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

omochaoukoku.co.jp SEO score

67

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omochaoukoku.co.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 Omochaoukoku.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

omochaoukoku.co.jp

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