Tools & Wizards About Us
tusinbo.com screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

tusinbo.com

病院の通信簿 - 口コミ・評価で病院歯科検索

Page Load Speed

3 sec in total

First Response

608 ms

Resources Loaded

2.3 sec

Page Rendered

70 ms

tusinbo.com screenshot

About Website

Click here to check amazing Tusinbo content for Japan. Otherwise, check out these important facts you probably never knew about tusinbo.com

「病院の通信簿」は、患者さんの口コミ、評価、評判で病院や歯科を検索出来る日本最大級の病院口コミサイトです。実際の診察や治療を受け一人一人の声を集めて公開中。「病院の通信簿」では、あなたの投票を随時受け付けています。

Visit tusinbo.com

Key Findings

We analyzed Tusinbo.com page load time and found that the first response time was 608 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

tusinbo.com performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value1.8 s

100/100

10%

Network Requests Diagram

tusinbo.com

608 ms

tusinbo.com

683 ms

www.tusinbo.com

852 ms

h1_title.gif

168 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that all of those requests were addressed to Tusinbo.com and no external sources were called. The less responsive or slowest element that took the longest time to load (852 ms) belongs to the original domain Tusinbo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 837.7 kB (50%)

Content Size

1.7 MB

After Optimization

821.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tusinbo.com main page is 1.7 MB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-46%

Potential reduce by 653 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 757 B

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 653 B or 46% of the original size.

Image Optimization

-7%

Potential reduce by 34.7 kB

  • Original 479.2 kB
  • After minification 444.5 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. Tusinbo images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 738.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 361.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 738.0 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 64.4 kB

  • Original 79.4 kB
  • After minification 77.8 kB
  • After compression 15.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. Tusinbo.com needs all CSS files to be minified and compressed as it can save up to 64.4 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • Images

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tusinbo. According to our analytics all requests are already optimized.

Network Requests Diagram

tusinbo.com

tusinbo.com

608 ms

tusinbo.com

tusinbo.com

683 ms

www.tusinbo.com

www.tusinbo.com

852 ms

h1_title.gif

h1_title.gif

168 ms

Accessibility Review

tusinbo.com accessibility score

77

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

tusinbo.com SEO score

67

Search Engine Optimization Advices

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

tusinbo.com

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