Tools & Wizards About Us
peg.or.jp screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

peg.or.jp

胃ろう（胃瘻・PEG・ペグ）と栄養に関する情報を提供する｜NPO法人PDN

Page Load Speed

3.6 sec in total

First Response

837 ms

Resources Loaded

2.6 sec

Page Rendered

204 ms

peg.or.jp screenshot

About Website

Welcome to peg.or.jp homepage info - get ready to check PEG best content for Japan right away, or after learning these important things about peg.or.jp

経腸栄養法のひとつであるPEG(経皮内視鏡的胃瘻(いろう)造設術)および関連する栄養療法全般についての情報提供を行う、NPO法人PDNのホームページです。

Visit peg.or.jp

Key Findings

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

Performance Metrics

peg.or.jp performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

peg.or.jp

837 ms

lecture.css

531 ms

layout_test.css

544 ms

basic.css

546 ms

ui.tabs.css

373 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 81% of them (47 requests) were addressed to the original Peg.or.jp, 5% (3 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Peg.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 601.1 kB (57%)

Content Size

1.0 MB

After Optimization

444.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peg.or.jp main page is 1.0 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. 40% of websites need less resources to load. Javascripts take 696.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 126.4 kB

  • Original 166.1 kB
  • After minification 162.7 kB
  • After compression 39.7 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 126.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 3.0 kB

  • Original 155.2 kB
  • After minification 152.1 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. PEG images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 449.8 kB

  • Original 696.9 kB
  • After minification 694.5 kB
  • After compression 247.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 449.8 kB or 65% of the original size.

CSS Optimization

-79%

Potential reduce by 21.9 kB

  • Original 27.8 kB
  • After minification 22.1 kB
  • After compression 5.9 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. Peg.or.jp needs all CSS files to be minified and compressed as it can save up to 21.9 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

peg.or.jp

peg.or.jp

837 ms

lecture.css

lecture.css

531 ms

layout_test.css

layout_test.css

544 ms

basic.css

basic.css

546 ms

ui.tabs.css

ui.tabs.css

373 ms

jquery.min.js

jquery.min.js

29 ms

ui.core.js

ui.core.js

329 ms

ui.tabs.js

ui.tabs.js

564 ms

brand

brand

35 ms

brand

brand

57 ms

addthis_widget.js

addthis_widget.js

19 ms

analytics.js

analytics.js

34 ms

title.png

title.png

189 ms

headnav_home.png

headnav_home.png

191 ms

headnav_mail.png

headnav_mail.png

189 ms

headnav_shop.png

headnav_shop.png

192 ms

mainvisual940.jpg

mainvisual940.jpg

558 ms

ootsuka.png

ootsuka.png

248 ms

terumo.gif

terumo.gif

332 ms

boston.png

boston.png

354 ms

topsub_kanren.png

topsub_kanren.png

364 ms

top_paper.png

top_paper.png

366 ms

top_brs.png

top_brs.png

378 ms

top_techou.png

top_techou.png

497 ms

top_sunmedix.jpg

top_sunmedix.jpg

531 ms

top_ve.png

top_ve.png

545 ms

top_shop.png

top_shop.png

548 ms

top_patients.png

top_patients.png

565 ms

top_lecture.png

top_lecture.png

661 ms

top_danwa.png

top_danwa.png

706 ms

top_seminar.png

top_seminar.png

726 ms

subtitle04.gif

subtitle04.gif

729 ms

member.png

member.png

742 ms

top_touroku.gif

top_touroku.gif

751 ms

top_tourokuform.gif

top_tourokuform.gif

826 ms

bnr_donation.png

bnr_donation.png

882 ms

peg-products.png

peg-products.png

906 ms

en-products.png

en-products.png

909 ms

top_eiyou.png

top_eiyou.png

927 ms

taikenbtn.gif

taikenbtn.gif

939 ms

heq.png

heq.png

990 ms

pteg.png

pteg.png

1057 ms

top_kanrenbook.png

top_kanrenbook.png

1087 ms

adobereader.gif

adobereader.gif

1091 ms

nav.png

nav.png

1101 ms

bg01.gif

bg01.gif

1113 ms

orange.png

orange.png

1142 ms

green.png

green.png

1221 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

165 ms

collect

collect

54 ms

layers.3643cb2e25fb91c29386.js

layers.3643cb2e25fb91c29386.js

53 ms

300lo.json

300lo.json

74 ms

collect

collect

106 ms

li_img01.gif

li_img01.gif

1089 ms

bg02.gif

bg02.gif

1093 ms

footbg.gif

footbg.gif

1114 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

81 ms

tab.png

tab.png

1074 ms

Accessibility Review

peg.or.jp accessibility score

67

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Form elements do not have associated labels

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

peg.or.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

peg.or.jp SEO score

97

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peg.or.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Peg.or.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

peg.or.jp

Open Graph data is detected on the main page of PEG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: