Tools & Wizards About Us
rubikcube.jp screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

rubikcube.jp

ルービックキューブ公式 TOP | 株式会社メガハウス

Page Load Speed

4.8 sec in total

First Response

688 ms

Resources Loaded

3.8 sec

Page Rendered

313 ms

rubikcube.jp screenshot

About Website

Click here to check amazing Rubikcube content for Japan. Otherwise, check out these important facts you probably never knew about rubikcube.jp

年齢を問わず楽しめるルービックキューブは、まさに「一生遊べるパズル」。各世代の方々に改めてルービックの楽しさをお伝えしていきます。

Visit rubikcube.jp

Key Findings

We analyzed Rubikcube.jp page load time and found that the first response time was 688 ms and then it took 4.1 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

rubikcube.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value24.4 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

rubikcube.jp

688 ms

rubikcube.jp

748 ms

style.css

365 ms

all.css

37 ms

libs.js

708 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 52% of them (34 requests) were addressed to the original Rubikcube.jp, 17% (11 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Rubikcube.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.1 kB (5%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rubikcube.jp main page is 2.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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 9.9 kB

  • Original 14.6 kB
  • After minification 13.4 kB
  • After compression 4.7 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 9.9 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 488 B

  • Original 1.6 MB
  • After minification 1.6 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. Rubikcube images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 44.3 kB

  • Original 224.4 kB
  • After minification 224.4 kB
  • After compression 180.1 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 44.3 kB or 20% of the original size.

CSS Optimization

-37%

Potential reduce by 43.4 kB

  • Original 118.4 kB
  • After minification 114.5 kB
  • After compression 75.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. Rubikcube.jp needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (41%)

Requests Now

49

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rubikcube.jp

rubikcube.jp

688 ms

rubikcube.jp

rubikcube.jp

748 ms

style.css

style.css

365 ms

all.css

all.css

37 ms

libs.js

libs.js

708 ms

script.js

script.js

546 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

545 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

549 ms

js

js

70 ms

js

js

119 ms

notosansjp.css

notosansjp.css

32 ms

lt.js

lt.js

78 ms

dqAVI3T90fQ

dqAVI3T90fQ

165 ms

logo.svg

logo.svg

191 ms

icon_topic.svg

icon_topic.svg

455 ms

icon_product.svg

icon_product.svg

193 ms

icon_history.svg

icon_history.svg

192 ms

icon_strategy.svg

icon_strategy.svg

457 ms

ccicon.png

ccicon.png

500 ms

mcicon.png

mcicon.png

500 ms

btn_play.png

btn_play.png

499 ms

logo_index.png

logo_index.png

499 ms

topic_11.jpg

topic_11.jpg

1075 ms

topic_10.jpg

topic_10.jpg

1444 ms

topic_05.jpg

topic_05.jpg

862 ms

topic_04.jpg

topic_04.jpg

1287 ms

index_01-pc.png

index_01-pc.png

1410 ms

index_02-pc.png

index_02-pc.png

1263 ms

index_03-pc.png

index_03-pc.png

1045 ms

index_04-pc.png

index_04-pc.png

1229 ms

index_05-pc.png

index_05-pc.png

1252 ms

btn_top.svg

btn_top.svg

1412 ms

text_footer-pc.png

text_footer-pc.png

1431 ms

text_footer.png

text_footer.png

1445 ms

icon_twitter.png

icon_twitter.png

1475 ms

icon_facebook.png

icon_facebook.png

1593 ms

icon_youtube.png

icon_youtube.png

1593 ms

icon_arrow.svg

icon_arrow.svg

1607 ms

logo_footer.png

logo_footer.png

1632 ms

popup.jpg

popup.jpg

1808 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1p47sMC3Yw.ttf

46 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1p47sMC3Yw.ttf

159 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j35zS1p47sMC3Yw.ttf

396 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj35zS1p47sMC3Yw.ttf

400 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi35zS1p47sMC3Yw.ttf

398 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k35zS1p47sMC3Yw.ttf

395 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1p47sMC3Yw.ttf

399 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk35zS1p47sMC3Yw.ttf

477 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk35zS1p47sMC3Yw.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk35zS1p47sMC3Yw.ttf

563 ms

fa-solid-900.woff

fa-solid-900.woff

20 ms

fa-regular-400.woff

fa-regular-400.woff

29 ms

uwt.js

uwt.js

31 ms

err.gif

err.gif

809 ms

adsct

adsct

325 ms

adsct

adsct

220 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

30 ms

base.js

base.js

54 ms

ad_status.js

ad_status.js

171 ms

1AiCzlAXOvKBjKQ6-ZkwShm4tpQuZWMhqjO5xqGcWBk.js

1AiCzlAXOvKBjKQ6-ZkwShm4tpQuZWMhqjO5xqGcWBk.js

121 ms

embed.js

embed.js

58 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

9 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

9 ms

id

id

23 ms

Create

Create

107 ms

GenerateIT

GenerateIT

14 ms

Accessibility Review

rubikcube.jp accessibility score

93

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.

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

High

Links do not have a discernible name

Best Practices

rubikcube.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

rubikcube.jp SEO score

85

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

rubikcube.jp

Open Graph data is detected on the main page of Rubikcube. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: