Tools & Wizards About Us
whatnot.jp screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

whatnot.jp

WHATNOT HARDWEAR STORE | 金物の産地である兵庫県三木市でDIY・アウトドア商品を扱うショップ

Page Load Speed

6.7 sec in total

First Response

1.2 sec

Resources Loaded

5 sec

Page Rendered

592 ms

whatnot.jp screenshot

About Website

Welcome to whatnot.jp homepage info - get ready to check WHATNOT best content right away, or after learning these important things about whatnot.jp

WHATNOT HARDWEAR STOREは金物の産地である兵庫県三木市でDIY・アウトドアを扱うショップです。自分がほしいものを自分でカタチにできる、自分が住み暮らす空間を自分で作ることができるサービスを提供します。

Visit whatnot.jp

Key Findings

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

Performance Metrics

whatnot.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

whatnot.jp

1174 ms

css

50 ms

reset.css

223 ms

style.css

341 ms

top.css

389 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 71% of them (22 requests) were addressed to the original Whatnot.jp, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Whatnot.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.1 kB (3%)

Content Size

2.9 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 13.2 kB

  • Original 18.1 kB
  • After minification 16.8 kB
  • After compression 4.9 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 13.2 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 29.6 kB

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

JavaScript Optimization

-19%

Potential reduce by 32.4 kB

  • Original 168.5 kB
  • After minification 168.5 kB
  • After compression 136.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 32.4 kB or 19% of the original size.

CSS Optimization

-8%

Potential reduce by 1.0 kB

  • Original 12.4 kB
  • After minification 12.4 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. Whatnot.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (36%)

Requests Now

28

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatnot.jp

whatnot.jp

1174 ms

css

css

50 ms

reset.css

reset.css

223 ms

style.css

style.css

341 ms

top.css

top.css

389 ms

jquery.min.js

jquery.min.js

38 ms

global.js

global.js

400 ms

js

js

115 ms

analytics.js

analytics.js

42 ms

style.min.css

style.min.css

490 ms

insta-window.js

insta-window.js

49 ms

js

js

87 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

224 ms

logo.png

logo.png

388 ms

mainPanel_logo.png

mainPanel_logo.png

191 ms

sdgs_logo.png

sdgs_logo.png

782 ms

collect

collect

19 ms

icon_fb.png

icon_fb.png

223 ms

icon_insta.png

icon_insta.png

272 ms

mainPanel_01.jpg

mainPanel_01.jpg

2144 ms

mainPanel_02.jpg

mainPanel_02.jpg

3308 ms

mainPanel_03.jpg

mainPanel_03.jpg

2434 ms

mainPanel_wrap.png

mainPanel_wrap.png

442 ms

panel_about.jpg

panel_about.jpg

708 ms

panel_products.jpg

panel_products.jpg

948 ms

panel_staff.jpg

panel_staff.jpg

1096 ms

bg_topic.png

bg_topic.png

1495 ms

bg_content.jpg

bg_content.jpg

1623 ms

logo_footer.png

logo_footer.png

1291 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff

20 ms

js

js

83 ms

Accessibility Review

whatnot.jp accessibility score

96

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

Links do not have a discernible name

Best Practices

whatnot.jp best practices score

75

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

Browser errors were logged to the console

SEO Factors

whatnot.jp SEO score

99

Search Engine Optimization Advices

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 Whatnot.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 Whatnot.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

whatnot.jp

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