Tools & Wizards About Us
sugihori.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

sugihori.com

杉並堀ノ内クリニック | 内科・小児科・泌尿器科・皮膚科・整形外科・訪問診療〔杉並区堀ノ内・高円寺･方南町〕

Page Load Speed

6 sec in total

First Response

956 ms

Resources Loaded

4.7 sec

Page Rendered

356 ms

sugihori.com screenshot

About Website

Click here to check amazing Sugihori content. Otherwise, check out these important facts you probably never knew about sugihori.com

杉並区堀ノ内二丁目の総合クリニック。専門医を揃え、内科・小児科・泌尿器科・皮膚科・整形外科・在宅訪問診療と幅広い診療科に対応いたします。内科は土・日・祝日も診療。杉並区堀ノ内・和田・和泉・方南町・高円寺・中野からアクセス良好です。

Visit sugihori.com

Key Findings

We analyzed Sugihori.com page load time and found that the first response time was 956 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

sugihori.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

sugihori.com

956 ms

import.css

335 ms

jquery.min.js

63 ms

js

60 ms

my.jquery.js

341 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 63% of them (54 requests) were addressed to the original Sugihori.com, 15% (13 requests) were made to Maps.google.com and 10% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Sugihori.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 375.2 kB (32%)

Content Size

1.2 MB

After Optimization

814.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sugihori.com main page is 1.2 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. 55% of websites need less resources to load. Images take 659.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 30.0 kB

  • Original 36.8 kB
  • After minification 33.7 kB
  • After compression 6.8 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 30.0 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 13.6 kB

  • Original 659.9 kB
  • After minification 646.3 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. Sugihori images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 321.4 kB

  • Original 479.4 kB
  • After minification 474.5 kB
  • After compression 158.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 321.4 kB or 67% of the original size.

CSS Optimization

-75%

Potential reduce by 10.1 kB

  • Original 13.4 kB
  • After minification 9.6 kB
  • After compression 3.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. Sugihori.com needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (41%)

Requests Now

81

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sugihori.com

sugihori.com

956 ms

import.css

import.css

335 ms

jquery.min.js

jquery.min.js

63 ms

js

js

60 ms

my.jquery.js

my.jquery.js

341 ms

medica.js

medica.js

515 ms

heightLine.js

heightLine.js

544 ms

reset.css

reset.css

169 ms

common.css

common.css

348 ms

top.css

top.css

218 ms

page.css

page.css

497 ms

css3.css

css3.css

354 ms

sugihori.html

sugihori.html

589 ms

lg-hd-01.png

lg-hd-01.png

188 ms

hd-tel-01.png

hd-tel-01.png

172 ms

h-dt-font-01.png

h-dt-font-01.png

173 ms

h-btn-Small.png

h-btn-Small.png

167 ms

h-btn-Medium.png

h-btn-Medium.png

173 ms

h-btn-Large.png

h-btn-Large.png

177 ms

nvGlobal-01_ov.png

nvGlobal-01_ov.png

331 ms

nvGlobal-02.png

nvGlobal-02.png

341 ms

nvGlobal-03.png

nvGlobal-03.png

342 ms

nvGlobal-04.png

nvGlobal-04.png

343 ms

nvGlobal-05.png

nvGlobal-05.png

352 ms

nvGlobal-06.png

nvGlobal-06.png

370 ms

visual_top.jpg

visual_top.jpg

1664 ms

btn-menu-01.jpg

btn-menu-01.jpg

717 ms

btn-menu-02.jpg

btn-menu-02.jpg

721 ms

btn-menu-03.jpg

btn-menu-03.jpg

851 ms

btn-menu-04.jpg

btn-menu-04.jpg

879 ms

btn-menu-05.jpg

btn-menu-05.jpg

924 ms

btn-menu-06.jpg

btn-menu-06.jpg

1056 ms

service01.jpg

service01.jpg

1059 ms

service02.jpg

service02.jpg

1230 ms

img-topics-02.jpg

img-topics-02.jpg

1405 ms

img-topics-03.jpg

img-topics-03.jpg

1667 ms

bnr-side-03.jpg

bnr-side-03.jpg

1395 ms

side-bg-First.png

side-bg-First.png

1229 ms

side-arrow-First-01.png

side-arrow-First-01.png

1400 ms

ico-linkArrow-01.png

ico-linkArrow-01.png

1400 ms

bnr-side-01.jpg

bnr-side-01.jpg

1906 ms

bnr-side-02.jpg

bnr-side-02.jpg

1739 ms

bg-footer-01.png

bg-footer-01.png

1572 ms

bn-liFooter-01.png

bn-liFooter-01.png

1931 ms

bn-liFooter-02.png

bn-liFooter-02.png

1910 ms

bn-liFooter-03.png

bn-liFooter-03.png

1817 ms

bn-liFooter-04.png

bn-liFooter-04.png

2073 ms

img-clLiFooter-01.jpg

img-clLiFooter-01.jpg

1909 ms

img-clLiFooter-02.jpg

img-clLiFooter-02.jpg

1982 ms

img-clLiFooter-03.jpg

img-clLiFooter-03.jpg

1920 ms

img-clLiFooter-04.jpg

img-clLiFooter-04.jpg

2087 ms

img-clLiFooter-05.jpg

img-clLiFooter-05.jpg

1918 ms

img-clLiFooter-06.jpg

img-clLiFooter-06.jpg

1943 ms

img-clLiFooter-07.jpg

img-clLiFooter-07.jpg

2145 ms

img-clLiFooter-08.jpg

img-clLiFooter-08.jpg

2084 ms

img-clLiFooter-09.jpg

img-clLiFooter-09.jpg

1927 ms

ft-bg-copy-01.png

ft-bg-copy-01.png

1919 ms

common.js

common.js

16 ms

map.js

map.js

16 ms

util.js

util.js

108 ms

marker.js

marker.js

15 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

353 ms

onion.js

onion.js

33 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

118 ms

stats.js

stats.js

40 ms

controls.js

controls.js

34 ms

transparent.png

transparent.png

24 ms

css

css

82 ms

google4.png

google4.png

74 ms

mapcnt6.png

mapcnt6.png

151 ms

sv5.png

sv5.png

56 ms

spotlight-poi.png

spotlight-poi.png

57 ms

tmapctrl.png

tmapctrl.png

29 ms

cb_scout5.png

cb_scout5.png

31 ms

tmapctrl4.png

tmapctrl4.png

31 ms

imgs8.png

imgs8.png

31 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

18 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

90 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

76 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

88 ms

vt

vt

82 ms

vt

vt

80 ms

vt

vt

146 ms

vt

vt

77 ms

vt

vt

83 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

198 ms

Accessibility Review

sugihori.com accessibility score

72

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

sugihori.com 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

sugihori.com SEO score

67

Search Engine Optimization Advices

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

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 Sugihori.com 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 Sugihori.com 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

sugihori.com

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