Tools & Wizards About Us
rheuma.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

rheuma.jp

リウマチINFOナビ | 日本化薬株式会社

Page Load Speed

4.7 sec in total

First Response

626 ms

Resources Loaded

4 sec

Page Rendered

133 ms

rheuma.jp screenshot

About Website

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

日本化薬の「リウマチINFOナビ」です。リウマチに関する最新の治療薬の情報から、日々のケアに役立つ「リウマチ体操」動画まで、各種コンテンツが充実しています。リウマチについて気になることがあったら、ぜひとも当サイトをご活用ください。

Visit rheuma.jp

Key Findings

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

rheuma.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value25.6 s

0/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.231

54/100

15%

TTI (Time to Interactive)

Value35.9 s

0/100

10%

Network Requests Diagram

rheuma.jp

626 ms

normalize.css

201 ms

bootstrap.css

870 ms

main.css

349 ms

style.css

796 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 94% of them (32 requests) were addressed to the original Rheuma.jp, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Cs.nakanohito.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Rheuma.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (36%)

Content Size

3.5 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 7.9 kB

  • Original 10.9 kB
  • After minification 9.1 kB
  • After compression 2.9 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. This page needs HTML code to be minified as it can gain 1.8 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 7.9 kB or 73% of the original size.

Image Optimization

-25%

Potential reduce by 662.4 kB

  • Original 2.7 MB
  • After minification 2.0 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. Obviously, Rheuma needs image optimization as it can save up to 662.4 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 413.0 kB

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

CSS Optimization

-85%

Potential reduce by 175.8 kB

  • Original 207.9 kB
  • After minification 164.2 kB
  • After compression 32.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. Rheuma.jp needs all CSS files to be minified and compressed as it can save up to 175.8 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

32

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rheuma.jp

rheuma.jp

626 ms

normalize.css

normalize.css

201 ms

bootstrap.css

bootstrap.css

870 ms

main.css

main.css

349 ms

style.css

style.css

796 ms

print.css

print.css

399 ms

jquery-ui.min.css

jquery-ui.min.css

597 ms

owl.carousel.min.css

owl.carousel.min.css

399 ms

jquery.min.js

jquery.min.js

1217 ms

jquery-ui.min.js

jquery-ui.min.js

1593 ms

jquery.numeric.js

jquery.numeric.js

598 ms

vendor.js

vendor.js

796 ms

bootstrap.js

bootstrap.js

995 ms

owl.carousel.min.js

owl.carousel.min.js

994 ms

common.js

common.js

995 ms

top.js

top.js

1043 ms

gtm.js

gtm.js

96 ms

bi.js

bi.js

513 ms

riumachi_logo.png

riumachi_logo.png

315 ms

slider1.png

slider1.png

1314 ms

slider2.png

slider2.png

1312 ms

slider3.png

slider3.png

1040 ms

search_icon.png

search_icon.png

517 ms

treatment_icon.png

treatment_icon.png

517 ms

life_icon.png

life_icon.png

690 ms

Interview_icon.png

Interview_icon.png

736 ms

dictionary_icon.png

dictionary_icon.png

864 ms

bio_banner.png

bio_banner.png

913 ms

taisou_banner.png

taisou_banner.png

914 ms

hospital_search.png

hospital_search.png

1040 ms

nk_logo.png

nk_logo.png

1112 ms

arrow.png

arrow.png

1114 ms

sc_top.png

sc_top.png

1213 ms

Hiragino%20Kaku%20Gothic%20Pro%20W3.otf

Hiragino%20Kaku%20Gothic%20Pro%20W3.otf

2419 ms

Accessibility Review

rheuma.jp accessibility score

46

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.

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 valid value for its [lang] attribute.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

rheuma.jp best practices score

75

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

SEO Factors

rheuma.jp SEO score

87

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JP

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rheuma.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed language. Our system also found out that Rheuma.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

rheuma.jp

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