Tools & Wizards About Us
peg.or.jp screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% 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

812 ms

Resources Loaded

2.7 sec

Page Rendered

140 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 812 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 55% of websites can load faster.

Performance Metrics

peg.or.jp performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

peg.or.jp

812 ms

lecture.css

331 ms

layout_test.css

386 ms

basic.css

391 ms

ui.tabs.css

452 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 89% of them (51 requests) were addressed to the original Peg.or.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Peg.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.7 kB (31%)

Content Size

373.1 kB

After Optimization

258.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 16.7 kB

  • Original 23.6 kB
  • After minification 22.8 kB
  • After compression 6.8 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 16.7 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 79 B

  • Original 185.7 kB
  • After minification 185.6 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

-55%

Potential reduce by 74.2 kB

  • Original 133.9 kB
  • After minification 131.4 kB
  • After compression 59.8 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 74.2 kB or 55% of the original size.

CSS Optimization

-79%

Potential reduce by 23.7 kB

  • Original 30.0 kB
  • After minification 23.9 kB
  • After compression 6.2 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 23.7 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 56 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 5 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

812 ms

lecture.css

lecture.css

331 ms

layout_test.css

layout_test.css

386 ms

basic.css

basic.css

391 ms

ui.tabs.css

ui.tabs.css

452 ms

jquery.min.js

jquery.min.js

8 ms

ui.core.js

ui.core.js

462 ms

ui.tabs.js

ui.tabs.js

461 ms

analytics.js

analytics.js

74 ms

title.png

title.png

254 ms

headnav_home.png

headnav_home.png

256 ms

headnav_mail.png

headnav_mail.png

257 ms

headnav_shop.png

headnav_shop.png

255 ms

mainvisual940.jpg

mainvisual940.jpg

493 ms

nav.png

nav.png

257 ms

top-connector.png

top-connector.png

390 ms

mera-1.jpg

mera-1.jpg

391 ms

topsub_kanren.png

topsub_kanren.png

453 ms

bnr-kurukuru.png

bnr-kurukuru.png

454 ms

top_brs.png

top_brs.png

456 ms

top_paper.png

top_paper.png

585 ms

top_techou.png

top_techou.png

585 ms

top_sunmedix.jpg

top_sunmedix.jpg

678 ms

top_ve.png

top_ve.png

681 ms

top_oral.png

top_oral.png

682 ms

top_shop.png

top_shop.png

656 ms

top_patients.png

top_patients.png

779 ms

top_lecture.png

top_lecture.png

780 ms

top_danwa.png

top_danwa.png

820 ms

top_seminar.png

top_seminar.png

904 ms

orange.png

orange.png

906 ms

green.png

green.png

909 ms

subtitle04.gif

subtitle04.gif

974 ms

li_img01.gif

li_img01.gif

975 ms

new.png

new.png

985 ms

new-co.png

new-co.png

1130 ms

bg02.gif

bg02.gif

1132 ms

top_touroku.gif

top_touroku.gif

1137 ms

top_tourokuform.gif

top_tourokuform.gif

1168 ms

bnr_donation.png

bnr_donation.png

1169 ms

peg-products.png

peg-products.png

1149 ms

en-products.png

en-products.png

1357 ms

products.png

products.png

1358 ms

haiben_control.png

haiben_control.png

1364 ms

top_eiyou.png

top_eiyou.png

1257 ms

collect

collect

27 ms

collect

collect

27 ms

js

js

63 ms

ga-audiences

ga-audiences

123 ms

taikenbtn.gif

taikenbtn.gif

1112 ms

heq.png

heq.png

1113 ms

pteg.png

pteg.png

1226 ms

top_academia.png

top_academia.png

1331 ms

top_kanrenbook.png

top_kanrenbook.png

1330 ms

adobereader.gif

adobereader.gif

1171 ms

footbg.gif

footbg.gif

1170 ms

tab.png

tab.png

1143 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: