Tools & Wizards About Us
riumachi.jp screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

riumachi.jp

ホームページ | リウマチe-ネット | ファイザー

Page Load Speed

5.9 sec in total

First Response

165 ms

Resources Loaded

5.3 sec

Page Rendered

407 ms

riumachi.jp screenshot

About Website

Click here to check amazing Riumachi content for Japan. Otherwise, check out these important facts you probably never knew about riumachi.jp

リウマチeネットは関節リウマチの原因・症状など病気の情報から診断・検査や治療に関するサポート情報、日常生活の注意点などのお役立ち情報を掲載しています。本サイトはファイザー株式会社が制作・提供しています。

Visit riumachi.jp

Key Findings

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

Performance Metrics

riumachi.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

riumachi.jp

165 ms

riumachi.jp

1116 ms

www.riumachi.jp

1407 ms

all.js

38 ms

css_JTDlifT_2h7e-OehoY-FOuhIODw5GYmkqSwM32hcdsk.css

78 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 77% of them (43 requests) were addressed to the original Riumachi.jp, 5% (3 requests) were made to Static.addtoany.com and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Riumachi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.3 kB (9%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 84.4 kB

  • Original 116.7 kB
  • After minification 111.2 kB
  • After compression 32.3 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 84.4 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 713 B

  • Original 1.2 MB
  • After minification 1.2 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. Riumachi images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 66.0 kB

  • Original 264.1 kB
  • After minification 264.0 kB
  • After compression 198.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 66.0 kB or 25% of the original size.

CSS Optimization

-0%

Potential reduce by 163 B

  • Original 146.7 kB
  • After minification 146.6 kB
  • After compression 146.5 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. Riumachi.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (31%)

Requests Now

52

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

riumachi.jp

riumachi.jp

165 ms

riumachi.jp

riumachi.jp

1116 ms

www.riumachi.jp

www.riumachi.jp

1407 ms

all.js

all.js

38 ms

css_JTDlifT_2h7e-OehoY-FOuhIODw5GYmkqSwM32hcdsk.css

css_JTDlifT_2h7e-OehoY-FOuhIODw5GYmkqSwM32hcdsk.css

78 ms

css_BzfEEVS8kJ8eQCqCqcnUrMfsJEwnaBQn6z67-oq3_3M.css

css_BzfEEVS8kJ8eQCqCqcnUrMfsJEwnaBQn6z67-oq3_3M.css

110 ms

sawarabimincho.css

sawarabimincho.css

51 ms

css_EqNAQ_0AgKAFMQXkYvl3tZIC0AAlMt7skzJHB4ZcxL0.css

css_EqNAQ_0AgKAFMQXkYvl3tZIC0AAlMt7skzJHB4ZcxL0.css

97 ms

launch-4c93d6f60ba6.min.js

launch-4c93d6f60ba6.min.js

36 ms

urlconfig.js

urlconfig.js

74 ms

seckit.document_write.js

seckit.document_write.js

121 ms

seckit.no_body.css

seckit.no_body.css

1083 ms

js_PceL9QxdIzsCuMsxwoTCM2CYkjFBNNWtxdai4hIpfE0.js

js_PceL9QxdIzsCuMsxwoTCM2CYkjFBNNWtxdai4hIpfE0.js

148 ms

page.js

page.js

72 ms

js_Km-9y4kP2uInpEwuol8YJHSH81RoIzIh989z79cdKyM.js

js_Km-9y4kP2uInpEwuol8YJHSH81RoIzIh989z79cdKyM.js

179 ms

all.js

all.js

16 ms

37 ms

logo.png

logo.png

89 ms

pic_riumachikouza.png

pic_riumachikouza.png

182 ms

ico_fb.png

ico_fb.png

1123 ms

ico_tw.png

ico_tw.png

46 ms

ico_line.png

ico_line.png

66 ms

h_logo.png

h_logo.png

74 ms

main_ico_t.png

main_ico_t.png

90 ms

main_top_banner.jpg

main_top_banner.jpg

184 ms

main_top_banner_sp.jpg

main_top_banner_sp.jpg

183 ms

ico1_0.png

ico1_0.png

180 ms

ico2.png

ico2.png

255 ms

ico3.png

ico3.png

211 ms

btn1_bg.png

btn1_bg.png

219 ms

btn1_bg_m_0.png

btn1_bg_m_0.png

211 ms

btn2_bg_1.png

btn2_bg_1.png

225 ms

btn2_bg_m_0.png

btn2_bg_m_0.png

231 ms

btn3_bg.png

btn3_bg.png

303 ms

btn3_bg_m_0.png

btn3_bg_m_0.png

296 ms

bnr_caution_0.png

bnr_caution_0.png

295 ms

s1_recipe.png

s1_recipe.png

325 ms

bnr_w_worrysymptoms_0.png

bnr_w_worrysymptoms_0.png

362 ms

s1_lifestyle.png

s1_lifestyle.png

366 ms

box2_t.png

box2_t.png

1314 ms

box2_b.png

box2_b.png

402 ms

s_btn1.png

s_btn1.png

382 ms

a57507dcf098a6a90c43.png

a57507dcf098a6a90c43.png

1711 ms

07482e17d8dc550e8b27.png

07482e17d8dc550e8b27.png

1710 ms

7fadbf18c865e0720f89.png

7fadbf18c865e0720f89.png

1466 ms

e993636610378cb65376.png

e993636610378cb65376.png

2517 ms

391a67e983cb83768a9b.png

391a67e983cb83768a9b.png

1209 ms

07a5bf6b660bd645cb01.png

07a5bf6b660bd645cb01.png

1285 ms

pagetop.png

pagetop.png

1380 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

20 ms

sm.25.html

sm.25.html

31 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

59 ms

pf_appmeasurement.js

pf_appmeasurement.js

23 ms

iframe_api

iframe_api

109 ms

8QIRdiDaitzr7brc8ahpxt6GcIJjKqJL.ttf

8QIRdiDaitzr7brc8ahpxt6GcIJjKqJL.ttf

18 ms

www-widgetapi.js

www-widgetapi.js

6 ms

Accessibility Review

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

riumachi.jp best practices score

92

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

SEO Factors

riumachi.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 Riumachi.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 Riumachi.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

riumachi.jp

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