Tools & Wizards About Us
yellowsubmarine.co.jp screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

yellowsubmarine.co.jp

ゲーム・ホビー商品の販売買取はイエローサブマリン｜委託販売・郵送買取も対応！

Page Load Speed

8.1 sec in total

First Response

535 ms

Resources Loaded

7.2 sec

Page Rendered

423 ms

yellowsubmarine.co.jp screenshot

About Website

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

イエローサブマリンでは、ボードゲーム・TRPG・TCG等アナログゲーム商品、プラモデル・フィギュア等ホビー商品の販売買取を行っています。委託販売や郵送買取についてもお気軽にお問い合せください。

Visit yellowsubmarine.co.jp

Key Findings

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

Performance Metrics

yellowsubmarine.co.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value29.0 s

0/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.546

13/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

yellowsubmarine.co.jp

535 ms

yellowsubmarine.co.jp

3231 ms

style.css

933 ms

jquery1.4.4.min.js

917 ms

script.js

602 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 90% of them (66 requests) were addressed to the original Yellowsubmarine.co.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Yellowsubmarine.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 974.0 kB (22%)

Content Size

4.4 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 86.8 kB

  • Original 103.3 kB
  • After minification 88.7 kB
  • After compression 16.5 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. This page needs HTML code to be minified as it can gain 14.6 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 86.8 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 60.3 kB

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

JavaScript Optimization

-68%

Potential reduce by 502.8 kB

  • Original 742.1 kB
  • After minification 737.4 kB
  • After compression 239.3 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 502.8 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 324.1 kB

  • Original 376.1 kB
  • After minification 274.1 kB
  • After compression 52.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. Yellowsubmarine.co.jp needs all CSS files to be minified and compressed as it can save up to 324.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (44%)

Requests Now

71

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yellowsubmarine.co.jp

yellowsubmarine.co.jp

535 ms

yellowsubmarine.co.jp

yellowsubmarine.co.jp

3231 ms

style.css

style.css

933 ms

jquery1.4.4.min.js

jquery1.4.4.min.js

917 ms

script.js

script.js

602 ms

jquery.easing.min.js

jquery.easing.min.js

29 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

605 ms

jquery.film_roll.min.js

jquery.film_roll.min.js

523 ms

analytics.js

analytics.js

20 ms

style.min.css

style.min.css

987 ms

all.min.css

all.min.css

1177 ms

bootstrap.min.css

bootstrap.min.css

1164 ms

front.css

front.css

1017 ms

fancybox.css

fancybox.css

1137 ms

pagenavi-css.css

pagenavi-css.css

1139 ms

jquery.js

jquery.js

1284 ms

jquery-migrate.min.js

jquery-migrate.min.js

1194 ms

popper.min.js

popper.min.js

1260 ms

bootstrap.min.js

bootstrap.min.js

1438 ms

front.js

front.js

1338 ms

jquery.fancybox.js

jquery.fancybox.js

1698 ms

css

css

298 ms

soliloquy.css

soliloquy.css

1033 ms

wp-polyfill.min.js

wp-polyfill.min.js

1264 ms

i18n.min.js

i18n.min.js

1124 ms

jquery.form.min.js

jquery.form.min.js

1173 ms

wp-embed.min.js

wp-embed.min.js

1209 ms

soliloquy-min.js

soliloquy-min.js

1272 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

671 ms

collect

collect

15 ms

collect

collect

31 ms

js

js

66 ms

ga-audiences

ga-audiences

107 ms

logo.png

logo.png

189 ms

hobbybase_logo.png

hobbybase_logo.png

350 ms

ic_cort.png

ic_cort.png

206 ms

bg_yellow.jpg

bg_yellow.jpg

217 ms

nav_home-1.png

nav_home-1.png

196 ms

%E6%BA%9D%E5%8F%A3%E5%91%8A%E7%9F%A5%E3%83%90%E3%83%8A%E3%83%BC.jpg

%E6%BA%9D%E5%8F%A3%E5%91%8A%E7%9F%A5%E3%83%90%E3%83%8A%E3%83%BC.jpg

384 ms

%E6%8E%A1%E7%94%A8%E6%83%85%E5%A0%B1.jpg

%E6%8E%A1%E7%94%A8%E6%83%85%E5%A0%B1.jpg

549 ms

banner-1.jpg

banner-1.jpg

535 ms

%E3%81%B5%E3%82%8B%E3%82%88%E3%81%AB%E3%83%90%E3%83%8A%E3%83%BC.jpg

%E3%81%B5%E3%82%8B%E3%82%88%E3%81%AB%E3%83%90%E3%83%8A%E3%83%BC.jpg

744 ms

%E9%83%B5%E9%80%81%E8%B2%B7%E5%8F%96%E3%83%90%E3%83%8A%E3%83%BC.jpg

%E9%83%B5%E9%80%81%E8%B2%B7%E5%8F%96%E3%83%90%E3%83%8A%E3%83%BC.jpg

1119 ms

prev01.png

prev01.png

519 ms

next01.png

next01.png

555 ms

%E6%A1%9C%E9%99%8D%E3%82%8B%E4%BB%A3%E3%81%AB%E6%B1%BA%E9%97%98-%E3%81%B5%E3%82%8B%E3%82%88%E3%81%AB%E3%83%90%E3%83%8A%E3%83%BC.jpg

%E6%A1%9C%E9%99%8D%E3%82%8B%E4%BB%A3%E3%81%AB%E6%B1%BA%E9%97%98-%E3%81%B5%E3%82%8B%E3%82%88%E3%81%AB%E3%83%90%E3%83%8A%E3%83%BC.jpg

1040 ms

%E6%8E%A1%E7%94%A8%E6%83%85%E5%A0%B1-1.jpg

%E6%8E%A1%E7%94%A8%E6%83%85%E5%A0%B1-1.jpg

876 ms

%E5%B7%9D%E8%B6%8A%E7%A7%BB%E8%BB%A2%E3%83%90%E3%83%8A%E3%83%BC.jpg

%E5%B7%9D%E8%B6%8A%E7%A7%BB%E8%BB%A2%E3%83%90%E3%83%8A%E3%83%BC.jpg

730 ms

banner-1-600x600_c.jpg

banner-1-600x600_c.jpg

1241 ms

%E9%83%B5%E9%80%81%E8%B2%B7%E5%8F%96%E3%83%90%E3%83%8A%E3%83%BC.jpg

%E9%83%B5%E9%80%81%E8%B2%B7%E5%8F%96%E3%83%90%E3%83%8A%E3%83%BC.jpg

1097 ms

60_charapracon2024.jpg

60_charapracon2024.jpg

944 ms

%E3%81%AA%E3%82%93%E3%81%B0%E6%9C%AC%E5%BA%97%E3%83%97%E3%83%A9%E3%82%B3%E3%83%B318.jpg

%E3%81%AA%E3%82%93%E3%81%B0%E6%9C%AC%E5%BA%97%E3%83%97%E3%83%A9%E3%82%B3%E3%83%B318.jpg

1226 ms

%E3%81%AA%E3%82%93%E3%81%B0%E6%9C%AC%E5%BA%97%E3%83%97%E3%83%A9%E3%82%B3%E3%83%B317.jpg

%E3%81%AA%E3%82%93%E3%81%B0%E6%9C%AC%E5%BA%97%E3%83%97%E3%83%A9%E3%82%B3%E3%83%B317.jpg

1132 ms

CPM2024.jpg

CPM2024.jpg

1219 ms

convention_bnr.png

convention_bnr.png

1275 ms

service_bnr01.png

service_bnr01.png

1295 ms

service_bnr02.png

service_bnr02.png

1310 ms

service_bnr03.png

service_bnr03.png

1390 ms

bg_black.jpg

bg_black.jpg

1396 ms

chuko_bnr01.png

chuko_bnr01.png

1412 ms

chuko_bnr02.png

chuko_bnr02.png

1453 ms

chuko_bnr06.png

chuko_bnr06.png

1470 ms

chuko_bnr05.png

chuko_bnr05.png

1486 ms

plus.png

plus.png

1561 ms

foot_bnr01.png

foot_bnr01.png

1566 ms

foot_bnr02.png

foot_bnr02.png

1583 ms

logo.png

logo.png

1630 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

1547 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

1563 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

1559 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

1548 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

1554 ms

preloader.gif

preloader.gif

180 ms

Accessibility Review

yellowsubmarine.co.jp accessibility score

81

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

yellowsubmarine.co.jp best practices score

83

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

Page has valid source maps

SEO Factors

yellowsubmarine.co.jp SEO score

77

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 doesn't use 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 Yellowsubmarine.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 Yellowsubmarine.co.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

yellowsubmarine.co.jp

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