Tools & Wizards About Us
yakugai.gr.jp screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

yakugai.gr.jp

薬害オンブズパースン会議 Medwatcher Japan

Page Load Speed

4.7 sec in total

First Response

583 ms

Resources Loaded

3.9 sec

Page Rendered

136 ms

yakugai.gr.jp screenshot

About Website

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

「薬害オンブズパースン会議」は民間の医薬品監視機関です。

Visit yakugai.gr.jp

Key Findings

We analyzed Yakugai.gr.jp page load time and found that the first response time was 583 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

yakugai.gr.jp performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

yakugai.gr.jp

583 ms

www.yakugai.gr.jp

630 ms

home.css

400 ms

jquery.js

981 ms

jquery.function.js

406 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 91% of them (29 requests) were addressed to the original Yakugai.gr.jp, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Nakanohito.jp. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Yakugai.gr.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.7 kB (36%)

Content Size

203.6 kB

After Optimization

129.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yakugai.gr.jp main page is 203.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. 15% of websites need less resources to load. Images take 94.8 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.0 kB

  • Original 14.5 kB
  • After minification 14.2 kB
  • After compression 4.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 10.0 kB or 69% of the original size.

Image Optimization

-8%

Potential reduce by 7.3 kB

  • Original 94.8 kB
  • After minification 87.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. Yakugai images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 41.2 kB

  • Original 75.5 kB
  • After minification 74.0 kB
  • After compression 34.3 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 41.2 kB or 55% of the original size.

CSS Optimization

-81%

Potential reduce by 15.3 kB

  • Original 18.8 kB
  • After minification 12.7 kB
  • After compression 3.6 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. Yakugai.gr.jp needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (43%)

Requests Now

30

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yakugai.gr.jp

yakugai.gr.jp

583 ms

www.yakugai.gr.jp

www.yakugai.gr.jp

630 ms

home.css

home.css

400 ms

jquery.js

jquery.js

981 ms

jquery.function.js

jquery.function.js

406 ms

reset.css

reset.css

382 ms

base.css

base.css

386 ms

clear.css

clear.css

388 ms

contents.css

contents.css

388 ms

bg_logo.gif

bg_logo.gif

205 ms

logo.gif

logo.gif

388 ms

ic_link.gif

ic_link.gif

387 ms

bnr_melmaga.gif

bnr_melmaga.gif

389 ms

bg_nav.gif

bg_nav.gif

390 ms

bg_nav_on.gif

bg_nav_on.gif

398 ms

bg_nav_line.gif

bg_nav_line.gif

587 ms

bg_prnav.gif

bg_prnav.gif

755 ms

pr_01.jpg

pr_01.jpg

771 ms

pr_02.jpg

pr_02.jpg

773 ms

pr_03.jpg

pr_03.jpg

984 ms

pr_04.jpg

pr_04.jpg

976 ms

bg_section_list.gif

bg_section_list.gif

971 ms

IMG_0641-2_thum.jpg

IMG_0641-2_thum.jpg

1331 ms

P7276240_thum.JPG

P7276240_thum.JPG

1352 ms

DSC_8492_thum.JPG

DSC_8492_thum.JPG

1366 ms

ic_person.gif

ic_person.gif

1358 ms

ic_tieup.gif

ic_tieup.gif

1357 ms

bnr_cc_vaccine_qa_01.gif

bnr_cc_vaccine_qa_01.gif

1370 ms

copyright.gif

copyright.gif

1716 ms

ga.js

ga.js

5 ms

343 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

yakugai.gr.jp accessibility score

65

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

yakugai.gr.jp best practices score

58

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

yakugai.gr.jp SEO score

67

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yakugai.gr.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 Yakugai.gr.jp main page’s claimed encoding is euc-jp. 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

yakugai.gr.jp

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