Tools & Wizards About Us
plup.jp screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

plup.jp

5つ女優や人気モデル愛用の腕時計をご紹介 - The Watch Company

Page Load Speed

2.9 sec in total

First Response

56 ms

Resources Loaded

2.4 sec

Page Rendered

474 ms

plup.jp screenshot

About Website

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

新品、中古ブランド時計の販売・買取ならThe Watch Company。東京中野に実店舗があり、ロレックス・オメガ・チュードル・パネライ・ウブロ ・ハミルトンなど腕時計の在庫を豊富に取り揃えています！全国送料無料、ラッピング、サイズ調整無料！海外発送にも対応しております！

Visit plup.jp

Key Findings

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

Performance Metrics

plup.jp performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

plup.jp

56 ms

10 ms

blog.min.css

9 ms

require.min.js

13 ms

requirejs-min-resolver.min.js

16 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Plup.jp, 86% (114 requests) were made to Thewatchcompany.co.jp and 5% (6 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (875 ms) relates to the external source Thewatchcompany.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 242.3 kB (26%)

Content Size

929.1 kB

After Optimization

686.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plup.jp main page is 929.1 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. 65% of websites need less resources to load. Images take 332.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 230.7 kB

  • Original 284.4 kB
  • After minification 262.3 kB
  • After compression 53.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 230.7 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 10.2 kB

  • Original 332.9 kB
  • After minification 322.7 kB

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. Plup images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.4 kB

  • Original 303.4 kB
  • After minification 303.2 kB
  • After compression 302.0 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.

CSS Optimization

-0%

Potential reduce by 18 B

  • Original 8.4 kB
  • After minification 8.4 kB
  • After compression 8.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. Plup.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 105 (83%)

Requests Now

127

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

plup.jp

plup.jp

56 ms

10 ms

blog.min.css

blog.min.css

9 ms

require.min.js

require.min.js

13 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

16 ms

mixins.min.js

mixins.min.js

15 ms

requirejs-config.min.js

requirejs-config.min.js

17 ms

api.js

api.js

47 ms

addthis_widget.js

addthis_widget.js

29 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

8 ms

dataPost.min.js

dataPost.min.js

4 ms

bootstrap.min.js

bootstrap.min.js

4 ms

translate-inline.min.js

translate-inline.min.js

6 ms

jquery.min.js

jquery.min.js

74 ms

template.min.js

template.min.js

7 ms

confirm.min.js

confirm.min.js

7 ms

main.min.js

main.min.js

6 ms

mute-migrate.min.js

mute-migrate.min.js

7 ms

translate.min.js

translate.min.js

11 ms

underscore-min.js

underscore-min.js

185 ms

modal.min.js

modal.min.js

8 ms

scripts.min.js

scripts.min.js

57 ms

mage.min.js

mage.min.js

58 ms

text.min.js

text.min.js

55 ms

key-codes.min.js

key-codes.min.js

55 ms

recaptcha__en.js

recaptcha__en.js

225 ms

gtm.js

gtm.js

389 ms

space.gif

space.gif

875 ms

ja_icon.png

ja_icon.png

112 ms

en_icon.png

en_icon.png

109 ms

menu_bg.gif

menu_bg.gif

112 ms

logo-header.svg

logo-header.svg

109 ms

twc_logo.svg

twc_logo.svg

111 ms

tax_free.png

tax_free.png

127 ms

Loader.gif

Loader.gif

127 ms

placeholder.jpg

placeholder.jpg

127 ms

post_5_5943.jpg

post_5_5943.jpg

168 ms

post_5_5973_s.jpg

post_5_5973_s.jpg

127 ms

post_5_4301_s.jpg

post_5_4301_s.jpg

168 ms

tel_icon.svg

tel_icon.svg

174 ms

twc-icon-contact.svg

twc-icon-contact.svg

175 ms

twc_blog_topbanner.jpg

twc_blog_topbanner.jpg

225 ms

MiniCart.js

MiniCart.js

176 ms

customer-data.min.js

customer-data.min.js

223 ms

translator.min.js

translator.min.js

223 ms

polyfill.min.js

polyfill.min.js

477 ms

domReady.min.js

domReady.min.js

225 ms

quick-search.min.js

quick-search.min.js

223 ms

advanceSearch.min.js

advanceSearch.min.js

225 ms

theme.min.js

theme.min.js

224 ms

lazyload.min.js

lazyload.min.js

226 ms

modal-popup.html

modal-popup.html

221 ms

modal-slide.html

modal-slide.html

220 ms

modal-custom.html

modal-custom.html

222 ms

common.min.js

common.min.js

216 ms

jquery-migrate.min.js

jquery-migrate.min.js

155 ms

jquery-ui.min.js

jquery-ui.min.js

106 ms

jquery.cookie.min.js

jquery.cookie.min.js

369 ms

icons.woff

icons.woff

730 ms

page-cache.min.js

page-cache.min.js

68 ms

my-account-minicart.min.js

my-account-minicart.min.js

65 ms

addThis.min.js

addThis.min.js

66 ms

validation.min.js

validation.min.js

66 ms

cookies.min.js

cookies.min.js

68 ms

catalog-add-to-cart.min.js

catalog-add-to-cart.min.js

66 ms

section-config.min.js

section-config.min.js

67 ms

invalidation-processor.min.js

invalidation-processor.min.js

67 ms

app.min.js

app.min.js

67 ms

modal.min.js

modal.min.js

20 ms

knockout-min.js

knockout-min.js

106 ms

storage.min.js

storage.min.js

13 ms

webfont.min.js

webfont.min.js

12 ms

sticky.min.js

sticky.min.js

10 ms

modernizr.min.js

modernizr.min.js

11 ms

twc-custom.min.js

twc-custom.min.js

10 ms

addthis_widget.js

addthis_widget.js

11 ms

validation.min.js

validation.min.js

10 ms

console-logger.min.js

console-logger.min.js

8 ms

product-ids-resolver.min.js

product-ids-resolver.min.js

9 ms

element.min.js

element.min.js

95 ms

tab.min.js

tab.min.js

87 ms

types.min.js

types.min.js

87 ms

layout.min.js

layout.min.js

87 ms

url.min.js

url.min.js

129 ms

swiper-trigger.js

swiper-trigger.js

86 ms

local.min.js

local.min.js

45 ms

product-ids.min.js

product-ids.min.js

44 ms

transition.min.js

transition.min.js

37 ms

matchMedia.min.js

matchMedia.min.js

37 ms

jquery.colorbox.min.js

jquery.colorbox.min.js

37 ms

moment.min.js

moment.min.js

20 ms

jquery.metadata.min.js

jquery.metadata.min.js

19 ms

logger.min.js

logger.min.js

18 ms

entry-factory.min.js

entry-factory.min.js

19 ms

console-output-handler.min.js

console-output-handler.min.js

18 ms

formatter.min.js

formatter.min.js

19 ms

message-pool.min.js

message-pool.min.js

19 ms

levels-pool.min.js

levels-pool.min.js

19 ms

logger-utils.min.js

logger-utils.min.js

20 ms

main.min.js

main.min.js

19 ms

registry.min.js

registry.min.js

19 ms

events.min.js

events.min.js

20 ms

class.min.js

class.min.js

19 ms

swiper-bundle.min.js

swiper-bundle.min.js

57 ms

links.min.js

links.min.js

21 ms

jquery.storageapi.min.js

jquery.storageapi.min.js

206 ms

collapse.min.js

collapse.min.js

22 ms

dropdown.min.js

dropdown.min.js

22 ms

jquery.validate.min.js

jquery.validate.min.js

43 ms

template.min.js

template.min.js

8 ms

es6-collections.min.js

es6-collections.min.js

7 ms

wrapper.min.js

wrapper.min.js

7 ms

entry.min.js

entry.min.js

9 ms

arrays.min.js

arrays.min.js

10 ms

compare.min.js

compare.min.js

8 ms

misc.min.js

misc.min.js

9 ms

objects.min.js

objects.min.js

8 ms

strings.min.js

strings.min.js

9 ms

FormData.min.js

FormData.min.js

4 ms

storage-manager.min.js

storage-manager.min.js

6 ms

storage-service.min.js

storage-service.min.js

4 ms

ids-storage.min.js

ids-storage.min.js

5 ms

data-storage.min.js

data-storage.min.js

3 ms

ids-storage-compare.min.js

ids-storage-compare.min.js

5 ms

query-builder.min.js

query-builder.min.js

4 ms

react.production.min.js

react.production.min.js

22 ms

react-dom.production.min.js

react-dom.production.min.js

49 ms

qrcode@1.png

qrcode@1.png

719 ms

bottom_logo.svg

bottom_logo.svg

22 ms

js-translation.json

js-translation.json

624 ms

website-rule.min.js

website-rule.min.js

3 ms

space.gif

space.gif

374 ms

Accessibility Review

plup.jp accessibility score

92

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.

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

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

High

Page has valid source maps

SEO Factors

plup.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 Plup.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 Plup.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

plup.jp

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