Tools & Wizards About Us
drscholls.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

drscholls.jp

Page Load Speed

5.6 sec in total

First Response

409 ms

Resources Loaded

4.9 sec

Page Rendered

269 ms

drscholls.jp screenshot

About Website

Visit drscholls.jp now to see the best up-to-date Drscholls content and also check out these interesting facts you probably never knew about drscholls.jp

ようこそ、ドクター・ショールのホームページへ。フットケア、メディキュットやインソールなどの製品情報を始め、フットウェアやキャンペンなどお得な情報が満載です。ほかにも、靴の選び方や足の構造などの豆知識も紹介しています。

Visit drscholls.jp

Key Findings

We analyzed Drscholls.jp page load time and found that the first response time was 409 ms and then it took 5.2 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

drscholls.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value17.0 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

drscholls.jp

409 ms

drscholl.jp

550 ms

seo.css

369 ms

common.css

366 ms

styles.css

369 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Drscholls.jp, 84% (57 requests) were made to Drscholl.jp and 6% (4 requests) were made to Navicast.jp. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Drscholl.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.3 kB (12%)

Content Size

486.1 kB

After Optimization

425.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 15.4 kB

  • Original 21.0 kB
  • After minification 20.0 kB
  • After compression 5.6 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 15.4 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 3.2 kB

  • Original 395.9 kB
  • After minification 392.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. Drscholls images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 35.1 kB

  • Original 60.1 kB
  • After minification 41.1 kB
  • After compression 25.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 35.1 kB or 58% of the original size.

CSS Optimization

-74%

Potential reduce by 6.7 kB

  • Original 9.1 kB
  • After minification 7.2 kB
  • After compression 2.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. Drscholls.jp needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (24%)

Requests Now

62

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

drscholls.jp

drscholls.jp

409 ms

drscholl.jp

drscholl.jp

550 ms

seo.css

seo.css

369 ms

common.css

common.css

366 ms

styles.css

styles.css

369 ms

slick.css

slick.css

370 ms

slick-theme.css

slick-theme.css

380 ms

swfobject.js

swfobject.js

517 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

552 ms

slick.min.js

slick.min.js

554 ms

jquery.rollover.js

jquery.rollover.js

564 ms

NavicastApi.js

NavicastApi.js

775 ms

contents_bg.gif

contents_bg.gif

213 ms

header_bg_top.gif

header_bg_top.gif

342 ms

nav0_top.gif

nav0_top.gif

400 ms

nav1.gif

nav1.gif

539 ms

nav2.gif

nav2.gif

564 ms

nav3.gif

nav3.gif

560 ms

nav5.gif

nav5.gif

559 ms

nav6.gif

nav6.gif

721 ms

Drscholl_VS_bnr_150908.jpg

Drscholl_VS_bnr_150908.jpg

1805 ms

bnr_VS_2steprefill.jpg

bnr_VS_2steprefill.jpg

1430 ms

bnr_VS_harf.jpg

bnr_VS_harf.jpg

1474 ms

bnr_SF_half.jpg

bnr_SF_half.jpg

1703 ms

hardskin_bnr.jpg

hardskin_bnr.jpg

958 ms

navi_bg.gif

navi_bg.gif

1068 ms

navi_title.gif

navi_title.gif

1327 ms

navi01.jpg

navi01.jpg

1469 ms

navi02.jpg

navi02.jpg

1690 ms

navi03.jpg

navi03.jpg

1784 ms

navi04.jpg

navi04.jpg

1841 ms

category_title.gif

category_title.gif

1857 ms

category1.gif

category1.gif

2057 ms

category2.gif

category2.gif

2079 ms

category3.gif

category3.gif

2155 ms

category4.gif

category4.gif

2166 ms

category5.gif

category5.gif

2212 ms

category6.gif

category6.gif

2221 ms

category7.gif

category7.gif

2420 ms

category8.gif

category8.gif

2446 ms

news_title.gif

news_title.gif

2508 ms

news_drscholl.gif

news_drscholl.gif

2531 ms

news_partyfeet.gif

news_partyfeet.gif

2588 ms

news_info.gif

news_info.gif

2601 ms

ga.js

ga.js

6 ms

news_mediqtto.gif

news_mediqtto.gif

2711 ms

__utm.gif

__utm.gif

12 ms

lineup_bg.gif

lineup_bg.gif

2626 ms

lineup_title.gif

lineup_title.gif

2684 ms

lineup_mediqtto.jpg

lineup_mediqtto.jpg

2702 ms

lineup_partyfeet.jpg

lineup_partyfeet.jpg

2954 ms

lineup_makizume.jpg

lineup_makizume.jpg

2660 ms

lineup_biomechanics.jpg

lineup_biomechanics.jpg

2734 ms

NavicastTmg.php

NavicastTmg.php

197 ms

lineup_spray.jpg

lineup_spray.jpg

2650 ms

lineup_fs.jpg

lineup_fs.jpg

2874 ms

sitemap_bg.gif

sitemap_bg.gif

2724 ms

bullet_sitemap.gif

bullet_sitemap.gif

2829 ms

NavicastApi2.php

NavicastApi2.php

200 ms

NavicastApi2.php

NavicastApi2.php

567 ms

footer_bg.gif

footer_bg.gif

2770 ms

footer_RB.gif

footer_RB.gif

2553 ms

footer_DS.gif

footer_DS.gif

2483 ms

nGfNsPhF6M0B

nGfNsPhF6M0B

326 ms

footer_copyright.gif

footer_copyright.gif

2296 ms

hs=1458190075000

hs=1458190075000

470 ms

gtm.js

gtm.js

46 ms

iui3

iui3

110 ms

Accessibility Review

drscholls.jp accessibility score

85

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Buttons do not have an accessible name

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

drscholls.jp SEO score

100

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drscholls.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Drscholls.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

drscholls.jp

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