Tools & Wizards About Us
navitasclinic.jp screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

navitasclinic.jp

駅直結、夜まであいてる内科・小児科・皮膚科クリニック | 駅ナカにあって、夜まであいてる診療所

Page Load Speed

9.8 sec in total

First Response

576 ms

Resources Loaded

8 sec

Page Rendered

1.2 sec

navitasclinic.jp screenshot

About Website

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

JR新宿駅・立川駅・川崎駅に直結した内科・小児科・皮膚科診療なら、ナビタスクリニックへ。最寄り改札から2分、お出かけのついでや仕事の合間に、雨の日も濡れずに受診できます。新宿は土日祝も診療、立川・川崎は土曜17時まで診療しています。オンライン診療もご利用いただけます。HPVワクチン、帯状疱疹ワクチン、コロナワクチン、トラベル外来、女性内科、小児科もベテラン医師が対応します。発熱の場合も受診できます...

Visit navitasclinic.jp

Key Findings

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

Performance Metrics

navitasclinic.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

navitasclinic.jp

576 ms

navitasclinic.jp

4229 ms

js

80 ms

style.min.css

379 ms

theme.min.css

544 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 86% of them (61 requests) were addressed to the original Navitasclinic.jp, 6% (4 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Navitasclinic.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.1 kB (14%)

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 299.6 kB

  • Original 341.0 kB
  • After minification 326.6 kB
  • After compression 41.5 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 299.6 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 47.4 kB

  • Original 2.0 MB
  • After minification 1.9 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. Navitasclinic images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 398 B

  • Original 133.6 kB
  • After minification 133.6 kB
  • After compression 133.2 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

-3%

Potential reduce by 1.8 kB

  • Original 51.9 kB
  • After minification 51.9 kB
  • After compression 50.1 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. Navitasclinic.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (72%)

Requests Now

68

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

navitasclinic.jp

navitasclinic.jp

576 ms

navitasclinic.jp

navitasclinic.jp

4229 ms

js

js

80 ms

style.min.css

style.min.css

379 ms

theme.min.css

theme.min.css

544 ms

header-footer.min.css

header-footer.min.css

545 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

548 ms

post-5.css

post-5.css

559 ms

swiper.min.css

swiper.min.css

570 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

581 ms

global.css

global.css

725 ms

post-6.css

post-6.css

727 ms

post-323.css

post-323.css

730 ms

post-357.css

post-357.css

745 ms

post-8075.css

post-8075.css

761 ms

post-2846.css

post-2846.css

773 ms

post-2847.css

post-2847.css

904 ms

post-2848.css

post-2848.css

905 ms

post-2820.css

post-2820.css

909 ms

css

css

35 ms

css2

css2

53 ms

css2

css2

56 ms

css2

css2

58 ms

41d746012f.js

41d746012f.js

97 ms

custom-pro-widget-mega-menu.min.css

custom-pro-widget-mega-menu.min.css

936 ms

uc_animated_hamburger_icon.css

uc_animated_hamburger_icon.css

958 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

959 ms

widget-loop-builder.min.css

widget-loop-builder.min.css

1081 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

1081 ms

post-3348.css

post-3348.css

996 ms

post-3356.css

post-3356.css

997 ms

post-3809.css

post-3809.css

998 ms

animations.min.css

animations.min.css

998 ms

lazysizes.min.js

lazysizes.min.js

1091 ms

hello-frontend.min.js

hello-frontend.min.js

1090 ms

jquery.min.js

jquery.min.js

1275 ms

jquery-migrate.min.js

jquery-migrate.min.js

1119 ms

imagesloaded.min.js

imagesloaded.min.js

1162 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1165 ms

webpack.runtime.min.js

webpack.runtime.min.js

1265 ms

frontend-modules.min.js

frontend-modules.min.js

1268 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1305 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1353 ms

wp-polyfill.min.js

wp-polyfill.min.js

1360 ms

hooks.min.js

hooks.min.js

1256 ms

i18n.min.js

i18n.min.js

1094 ms

frontend.min.js

frontend.min.js

1102 ms

waypoints.min.js

waypoints.min.js

1129 ms

core.min.js

core.min.js

1176 ms

frontend.min.js

frontend.min.js

1174 ms

elements-handlers.min.js

elements-handlers.min.js

1237 ms

lb6dkzjjf8

lb6dkzjjf8

167 ms

icon-doctor.png

icon-doctor.png

866 ms

icon-recruit.png

icon-recruit.png

873 ms

icon-globe.png

icon-globe.png

912 ms

clarity.js

clarity.js

102 ms

icon-map-1.png

icon-map-1.png

811 ms

icon-clip.png

icon-clip.png

821 ms

icon-topics.png

icon-topics.png

884 ms

icon-phone.png

icon-phone.png

884 ms

top01.png

top01.png

2160 ms

top02.png

top02.png

2242 ms

top03.png

top03.png

2149 ms

icon-map01.png

icon-map01.png

1013 ms

icon-map.png

icon-map.png

1065 ms

icon-time.png

icon-time.png

1066 ms

icon-victim.png

icon-victim.png

1142 ms

icon-passport.png

icon-passport.png

1182 ms

icon-mobile.png

icon-mobile.png

1181 ms

5aU19_a8oxmIfJpbIRs.ttf

5aU19_a8oxmIfJpbIRs.ttf

24 ms

c.gif

c.gif

7 ms

Accessibility Review

navitasclinic.jp accessibility score

95

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

navitasclinic.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

navitasclinic.jp SEO score

93

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

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Navitasclinic.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 Navitasclinic.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

navitasclinic.jp

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