Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

hobbystock.jp

【HOBBY STOCK】ホビー・おもちゃ・フィギュア・ゲームの総合通販サイトならホビーストック

Page Load Speed

12.4 sec in total

First Response

536 ms

Resources Loaded

11.6 sec

Page Rendered

308 ms

hobbystock.jp screenshot

About Website

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

ホビーストックはホビー・おもちゃ・フィギュア・ゲームの総合通販サイトです。ホビー商品の魅力をいち早くご紹介!入手困難な人気商品でも、ご予約頂いた商品は確実に仕入れてお届け致します。

Visit hobbystock.jp

Key Findings

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

Performance Metrics

hobbystock.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

hobbystock.jp

536 ms

base.css

151 ms

module.css

296 ms

top.css

293 ms

jquery-1.9.1.min.js

445 ms

Our browser made a total of 412 requests to load all elements on the main page. We found that 19% of them (78 requests) were addressed to the original Hobbystock.jp, 74% (304 requests) were made to Hobbystock.s3-website-ap-northeast-1.amazonaws.com and 5% (21 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Hobbystock.s3-website-ap-northeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 762.5 kB (14%)

Content Size

5.4 MB

After Optimization

4.7 MB

In fact, the total size of Hobbystock.jp main page is 5.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. 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 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 254.6 kB

  • Original 279.6 kB
  • After minification 241.0 kB
  • After compression 25.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. This page needs HTML code to be minified as it can gain 38.7 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 254.6 kB or 91% of the original size.

Image Optimization

-7%

Potential reduce by 342.1 kB

  • Original 4.9 MB
  • After minification 4.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. HOBBY STOCK images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 103.6 kB

  • Original 161.8 kB
  • After minification 140.9 kB
  • After compression 58.2 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 103.6 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 62.1 kB

  • Original 73.5 kB
  • After minification 56.2 kB
  • After compression 11.4 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. Hobbystock.jp needs all CSS files to be minified and compressed as it can save up to 62.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (4%)

Requests Now

411

After Optimization

393

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

Accessibility Review

hobbystock.jp accessibility score

56

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

hobbystock.jp 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hobbystock.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 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 Hobbystock.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 Hobbystock.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

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