Tools & Wizards About Us
dugout.jp screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

dugout.jp

UNKNOWN, WAISTED PARIS, HUF, LAID BACK, 人気ストリートブランド取り扱いセレクトショップ【dugout/ダグアウト】

Page Load Speed

7.7 sec in total

First Response

590 ms

Resources Loaded

5.9 sec

Page Rendered

1.2 sec

dugout.jp screenshot

About Website

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

AFGK, a good bad influence, HUF, LAID BACK, PCC VISION, SOMEIT, TRAVS, UNKNOWN, WASTED PARIS, ストリートブランド, ストリート系の人気ブランドを取り扱い。

Visit dugout.jp

Key Findings

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

Performance Metrics

dugout.jp performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.381

27/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

dugout.jp

590 ms

www.dugout.jp

850 ms

sps_common.css

336 ms

default.css

707 ms

jquery.min.js

23 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 53% of them (58 requests) were addressed to the original Dugout.jp, 37% (40 requests) were made to Image1.shopserve.jp and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Image1.shopserve.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 801.1 kB (9%)

Content Size

9.1 MB

After Optimization

8.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 133.1 kB

  • Original 150.1 kB
  • After minification 125.4 kB
  • After compression 17.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 24.7 kB, which is 16% 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 133.1 kB or 89% of the original size.

Image Optimization

-7%

Potential reduce by 607.9 kB

  • Original 8.8 MB
  • After minification 8.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. Dugout images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 44.2 kB

  • Original 145.0 kB
  • After minification 145.0 kB
  • After compression 100.8 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.2 kB or 30% of the original size.

CSS Optimization

-32%

Potential reduce by 15.9 kB

  • Original 49.1 kB
  • After minification 49.1 kB
  • After compression 33.2 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. Dugout.jp needs all CSS files to be minified and compressed as it can save up to 15.9 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (22%)

Requests Now

106

After Optimization

83

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dugout.jp

dugout.jp

590 ms

www.dugout.jp

www.dugout.jp

850 ms

sps_common.css

sps_common.css

336 ms

default.css

default.css

707 ms

jquery.min.js

jquery.min.js

23 ms

css

css

41 ms

slick.css

slick.css

503 ms

slick-theme.css

slick-theme.css

510 ms

slick.min.js

slick.min.js

521 ms

common.js

common.js

520 ms

floating_menu.js

floating_menu.js

522 ms

js

js

80 ms

drawer_menu.js

drawer_menu.js

672 ms

cal.js

cal.js

517 ms

estore_beacon.js

estore_beacon.js

14 ms

analytics.js

analytics.js

253 ms

uh.js

uh.js

741 ms

DISTRESSEDHAT1.png

DISTRESSEDHAT1.png

414 ms

responsive1_header_logo.png

responsive1_header_logo.png

503 ms

LINEcouponbana.png

LINEcouponbana.png

872 ms

agbi.png

agbi.png

912 ms

modtee24ss.png

modtee24ss.png

971 ms

laurel.png

laurel.png

1046 ms

TRAVS.png

TRAVS.png

1230 ms

eesentials.png

eesentials.png

1001 ms

WP1.png

WP1.png

1564 ms

mod.png

mod.png

1429 ms

chrislv.png

chrislv.png

1299 ms

valabasas.png

valabasas.png

1502 ms

AGBIBAGss.png

AGBIBAGss.png

1392 ms

top_bnt_newitem.jpg

top_bnt_newitem.jpg

1399 ms

top_bnt_SALE.jpg

top_bnt_SALE.jpg

1463 ms

brand_img01.jpg

brand_img01.jpg

1567 ms

brand_img02.jpg

brand_img02.jpg

1570 ms

brand_img03.jpg

brand_img03.jpg

1602 ms

brand_img04.jpg

brand_img04.jpg

1629 ms

brand_img05.jpg

brand_img05.jpg

1670 ms

brand_img06.jpg

brand_img06.jpg

1739 ms

brand_img07.jpg

brand_img07.jpg

1743 ms

brand_img08.jpg

brand_img08.jpg

1740 ms

brand_img09.jpg

brand_img09.jpg

1776 ms

brand_img10.jpg

brand_img10.jpg

1797 ms

brand_img11.jpg

brand_img11.jpg

1838 ms

brand_img12.jpg

brand_img12.jpg

1913 ms

sns_instagram02.png

sns_instagram02.png

1908 ms

sns_instagram01.png

sns_instagram01.png

1917 ms

sns_youtube.png

sns_youtube.png

1948 ms

sns_line.png

sns_line.png

1961 ms

sns_twitter.png

sns_twitter.png

2004 ms

icon_new.png

icon_new.png

2078 ms

t_search.jpg

t_search.jpg

2086 ms

submitSearch.gif

submitSearch.gif

2089 ms

kaiinn-side.png

kaiinn-side.png

2119 ms

DISTRESSEDCAP1.png

DISTRESSEDCAP1.png

1165 ms

OVERKAP1.png

OVERKAP1.png

1264 ms

modtee16.png

modtee16.png

419 ms

modtee11.png

modtee11.png

587 ms

modtee6.png

modtee6.png

590 ms

modtee1.png

modtee1.png

750 ms

nylonshorts1.png

nylonshorts1.png

755 ms

HELLRAZORTRUCKER1.png

HELLRAZORTRUCKER1.png

771 ms

rednighttee11.png

rednighttee11.png

774 ms

rednighttee1.png

rednighttee1.png

1087 ms

bondage1.png

bondage1.png

1277 ms

SHORTS1.png

SHORTS1.png

1478 ms

crack1.png

crack1.png

1129 ms

PANTALONHAMMERSICK1.png

PANTALONHAMMERSICK1.png

1265 ms

HEAVY_JERSEY_OATMEAL1.png

HEAVY_JERSEY_OATMEAL1.png

1626 ms

HEAVY_JERSEY_BLK1.png

HEAVY_JERSEY_BLK1.png

1341 ms

ESSENTIALS_MINT1.png

ESSENTIALS_MINT1.png

1759 ms

ESSENTIALS1.png

ESSENTIALS1.png

1442 ms

21ss_shorts1.png

21ss_shorts1.png

1459 ms

21ss_shorts_OAT1.png

21ss_shorts_OAT1.png

2349 ms

SACRIFICE1.png

SACRIFICE1.png

2243 ms

NIGHTERS1.png

NIGHTERS1.png

2285 ms

LONDON1.png

LONDON1.png

1991 ms

Destroy1.png

Destroy1.png

1803 ms

facehoodie1.png

facehoodie1.png

1932 ms

WATERTHEPLANTWTPTHUNDER1.png

WATERTHEPLANTWTPTHUNDER1.png

2475 ms

SASORI1.png

SASORI1.png

2784 ms

RAMDARKBLUE1.png

RAMDARKBLUE1.png

2519 ms

QUANTICO1.png

QUANTICO1.png

2585 ms

PERS1.png

PERS1.png

2463 ms

triangle1.png

triangle1.png

2527 ms

challenger1.png

challenger1.png

3307 ms

SKULLROSELSTBEIGE1.png

SKULLROSELSTBEIGE1.png

3292 ms

L_VINTAGE4.png

L_VINTAGE4.png

2688 ms

DARKVINTAGE4.png

DARKVINTAGE4.png

2865 ms

line-side.png

line-side.png

2093 ms

linkid.js

linkid.js

13 ms

ec.js

ec.js

12 ms

collect

collect

15 ms

collect

collect

4 ms

js

js

48 ms

INFERNO_BLK1.png

INFERNO_BLK1.png

2363 ms

BANJO4.png

BANJO4.png

2455 ms

cart.png

cart.png

1675 ms

BANDIT1.png

BANDIT1.png

2361 ms

V-SCRAWL1.png

V-SCRAWL1.png

2371 ms

pagetop.gif

pagetop.gif

1384 ms

responsive1_icon_search.png

responsive1_icon_search.png

1354 ms

tracking.php

tracking.php

1315 ms

rsp_arrow01.png

rsp_arrow01.png

1296 ms

calendar_pleft.gif

calendar_pleft.gif

1251 ms

calendar_pright.gif

calendar_pright.gif

1115 ms

responsive1_button_pagetop.png

responsive1_button_pagetop.png

1123 ms

ajax-loader.gif

ajax-loader.gif

1043 ms

responsive1_slider_arrow_prev.png

responsive1_slider_arrow_prev.png

1063 ms

responsive1_slider_arrow_next.png

responsive1_slider_arrow_next.png

1041 ms

Accessibility Review

dugout.jp accessibility score

83

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

Best Practices

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

SEO Factors

dugout.jp SEO score

82

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

dugout.jp

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