Tools & Wizards About Us
wakitani.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

wakitani.com

かみ合わせによる頭痛、肩こり、腰痛は川崎市麻生区の歯医者│脇谷歯科医院

Page Load Speed

5.2 sec in total

First Response

788 ms

Resources Loaded

3.4 sec

Page Rendered

998 ms

wakitani.com screenshot

About Website

Welcome to wakitani.com homepage info - get ready to check Wakitani best content right away, or after learning these important things about wakitani.com

新百合ヶ丘の歯医者「脇谷歯科医院」では、かみ合わせ・歯並びが原因の頭痛や肩こり、腰痛を治します。かみ合わせが体に及ぼす影響、筋肉反射テスト、ホメオパシーを採用した治療法などをご紹介します。

Visit wakitani.com

Key Findings

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

Performance Metrics

wakitani.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value3,310 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.27

45/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

wakitani.com

788 ms

style.css

354 ms

rollover.js

427 ms

AC_RunActiveContent.js

414 ms

489 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 85% of them (33 requests) were addressed to the original Wakitani.com, 15% (6 requests) were made to Rays-counter.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Wakitani.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.8 kB (24%)

Content Size

154.6 kB

After Optimization

117.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 24.1 kB

  • Original 33.2 kB
  • After minification 31.8 kB
  • After compression 9.1 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 24.1 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 3.6 kB

  • Original 109.6 kB
  • After minification 106.0 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. Wakitani images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 7.2 kB

  • Original 9.4 kB
  • After minification 6.4 kB
  • After compression 2.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 7.2 kB or 77% of the original size.

CSS Optimization

-77%

Potential reduce by 1.9 kB

  • Original 2.4 kB
  • After minification 1.7 kB
  • After compression 546 B

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. Wakitani.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (55%)

Requests Now

38

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wakitani.com

wakitani.com

788 ms

style.css

style.css

354 ms

rollover.js

rollover.js

427 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

414 ms

489 ms

img_bg.gif

img_bg.gif

267 ms

img_bg02.gif

img_bg02.gif

268 ms

img_frame_01_1.gif

img_frame_01_1.gif

819 ms

menu00.gif

menu00.gif

268 ms

menu_line.gif

menu_line.gif

357 ms

z.gif

z.gif

408 ms

menu01.gif

menu01.gif

387 ms

menu06.gif

menu06.gif

436 ms

menu02.gif

menu02.gif

410 ms

menu03.gif

menu03.gif

549 ms

menu07.gif

menu07.gif

576 ms

menu04.gif

menu04.gif

610 ms

menu05.gif

menu05.gif

596 ms

bnr_blog.jpg

bnr_blog.jpg

1025 ms

qr.gif

qr.gif

754 ms

img_frame_16.gif

img_frame_16.gif

766 ms

img_name_kami.gif

img_name_kami.gif

791 ms

img_top_sebone.gif

img_top_sebone.gif

993 ms

logo21.gif

logo21.gif

935 ms

img_kochira.gif

img_kochira.gif

1138 ms

ttl_01.gif

ttl_01.gif

982 ms

img_line2.gif

img_line2.gif

1019 ms

logo1.gif

logo1.gif

1115 ms

main_logo.jpg

main_logo.jpg

2092 ms

1.3.jpg

1.3.jpg

1361 ms

GetAttachment.jpg1,1.jpg

GetAttachment.jpg1,1.jpg

1235 ms

counter_01.gif

counter_01.gif

476 ms

counter_02.gif

counter_02.gif

493 ms

counter_03.gif

counter_03.gif

527 ms

counter_04.gif

counter_04.gif

544 ms

counter_05.gif

counter_05.gif

544 ms

menu03_.gif

menu03_.gif

182 ms

menu04_.gif

menu04_.gif

194 ms

menu05_.gif

menu05_.gif

214 ms

Accessibility Review

wakitani.com accessibility score

87

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

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

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

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

wakitani.com

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