Tools & Wizards About Us
aeha.or.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

aeha.or.jp

一般財団法人 家電製品協会

Page Load Speed

4.4 sec in total

First Response

681 ms

Resources Loaded

3.6 sec

Page Rendered

135 ms

aeha.or.jp screenshot

About Website

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

一般財団法人家電製品協会の公式サイトです。製品安全への取組、省エネルギーへの取組、ユニバーサルデザインへの取組、環境への取組、家電リサイクルへの取組、家電に関する資格、家電製品PLセンターなどの家電に関する情報を掲載しています。

Visit aeha.or.jp

Key Findings

We analyzed Aeha.or.jp page load time and found that the first response time was 681 ms and then it took 3.7 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

aeha.or.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value24.2 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.107

88/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

aeha.or.jp

681 ms

gtm.js

68 ms

reset.css

338 ms

common.css

504 ms

index.css

347 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 73% of them (41 requests) were addressed to the original Aeha.or.jp, 7% (4 requests) were made to Googletagmanager.com and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Aeha.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.5 kB (5%)

Content Size

3.4 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 19.3 kB

  • Original 24.0 kB
  • After minification 17.4 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 6.6 kB, which is 27% 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 19.3 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 73.8 kB

  • Original 3.3 MB
  • After minification 3.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. Aeha images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 35.7 kB

  • Original 91.0 kB
  • After minification 88.9 kB
  • After compression 55.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 35.7 kB or 39% of the original size.

CSS Optimization

-59%

Potential reduce by 25.7 kB

  • Original 43.4 kB
  • After minification 35.4 kB
  • After compression 17.7 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. Aeha.or.jp needs all CSS files to be minified and compressed as it can save up to 25.7 kB or 59% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aeha.or.jp

aeha.or.jp

681 ms

gtm.js

gtm.js

68 ms

reset.css

reset.css

338 ms

common.css

common.css

504 ms

index.css

index.css

347 ms

all.css

all.css

41 ms

jquery.min.js

jquery.min.js

28 ms

common.js

common.js

344 ms

js

js

109 ms

js

js

68 ms

analytics.js

analytics.js

19 ms

collect

collect

13 ms

collect

collect

132 ms

js

js

127 ms

collect

collect

136 ms

header_menu_icon01.png

header_menu_icon01.png

160 ms

header_menu_icon02.png

header_menu_icon02.png

174 ms

header_menu_icon03.png

header_menu_icon03.png

175 ms

header_menu_icon04.png

header_menu_icon04.png

169 ms

header_menu_icon05.png

header_menu_icon05.png

170 ms

icon_lock.png

icon_lock.png

173 ms

header_icon_global.png

header_icon_global.png

316 ms

header_logo.png

header_logo.png

504 ms

header_icon_global.png

header_icon_global.png

337 ms

header_member_bg.png

header_member_bg.png

344 ms

menu.png

menu.png

346 ms

header_menu_icon01.png

header_menu_icon01.png

348 ms

header_menu_icon02.png

header_menu_icon02.png

474 ms

header_menu_icon03.png

header_menu_icon03.png

505 ms

header_menu_icon04.png

header_menu_icon04.png

515 ms

header_menu_icon05.png

header_menu_icon05.png

520 ms

mainvisual01.jpg

mainvisual01.jpg

1567 ms

mainvisual02.jpg

mainvisual02.jpg

1419 ms

mainvisual03.jpg

mainvisual03.jpg

1343 ms

mainvisual04.jpg

mainvisual04.jpg

1345 ms

side_text_01.png

side_text_01.png

1029 ms

side_text_02.png

side_text_02.png

866 ms

side_text_03.png

side_text_03.png

1214 ms

side_text_04.png

side_text_04.png

1373 ms

50th_banner.gif

50th_banner.gif

2430 ms

banner_top_06.png

banner_top_06.png

1511 ms

banner_top_02.png

banner_top_02.png

1513 ms

banner_top_04.png

banner_top_04.png

1545 ms

banner_3byourecycle.jpg

banner_3byourecycle.jpg

1577 ms

banner_bottom_03.png

banner_bottom_03.png

1680 ms

banner_bottom_01.png

banner_bottom_01.png

1681 ms

banner_bottom_02.png

banner_bottom_02.png

1716 ms

icon_ext.png

icon_ext.png

1739 ms

sitemap_bg.png

sitemap_bg.png

1734 ms

icon_lock.png

icon_lock.png

1848 ms

collect

collect

28 ms

fa-solid-900.woff

fa-solid-900.woff

22 ms

fa-regular-400.woff

fa-regular-400.woff

27 ms

menu.png

menu.png

1816 ms

collect

collect

14 ms

collect

collect

13 ms

Accessibility Review

aeha.or.jp accessibility score

71

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

aeha.or.jp best practices score

67

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

Browser errors were logged to the console

SEO Factors

aeha.or.jp SEO score

75

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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

aeha.or.jp

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