Tools & Wizards About Us
aebs.or.jp screenshot

Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

aebs.or.jp

AEBS 電子出版制作・流通協議会 - [TOP]

Page Load Speed

3.9 sec in total

First Response

1.1 sec

Resources Loaded

2.2 sec

Page Rendered

605 ms

aebs.or.jp screenshot

About Website

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

電子出版制作・流通協議会,Association for E-publishing Business Solution,AEBS　日本の電子出版産業の成長と健全な発展のための環境の実現を目指し、電子出版の発展に貢献できる活動をいたします。

Visit aebs.or.jp

Key Findings

We analyzed Aebs.or.jp page load time and found that the first response time was 1.1 sec 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

aebs.or.jp performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

65/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

aebs.or.jp

1067 ms

main.css

465 ms

topLogo.gif

491 ms

topics_img.jpg

491 ms

share.jpg

38 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 87% of them (20 requests) were addressed to the original Aebs.or.jp, 9% (2 requests) were made to Static.evernote.com and 4% (1 request) were made to Lh5.googleusercontent.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Aebs.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 106.8 kB (46%)

Content Size

232.8 kB

After Optimization

126.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 29.5 kB

  • Original 38.0 kB
  • After minification 34.3 kB
  • After compression 8.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 29.5 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 9.8 kB

  • Original 114.3 kB
  • After minification 104.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. AEBS images are well optimized though.

JavaScript Optimization

-84%

Potential reduce by 53.7 kB

  • Original 63.8 kB
  • After minification 45.6 kB
  • After compression 10.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 53.7 kB or 84% of the original size.

CSS Optimization

-82%

Potential reduce by 13.8 kB

  • Original 16.8 kB
  • After minification 12.1 kB
  • After compression 3.0 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. Aebs.or.jp needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

21

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aebs.or.jp

aebs.or.jp

1067 ms

main.css

main.css

465 ms

topLogo.gif

topLogo.gif

491 ms

topics_img.jpg

topics_img.jpg

491 ms

share.jpg

share.jpg

38 ms

noteit.js

noteit.js

33 ms

mainVisual.jpg

mainVisual.jpg

967 ms

menu01_oshirase.gif

menu01_oshirase.gif

498 ms

menu02_news.gif

menu02_news.gif

457 ms

menu03_schejule.gif

menu03_schejule.gif

464 ms

menu01_oshirase_bar.gif

menu01_oshirase_bar.gif

467 ms

article-clipper-jp.png

article-clipper-jp.png

24 ms

backgroundGeneral.jpg

backgroundGeneral.jpg

246 ms

btn01.gif

btn01.gif

314 ms

btn12.gif

btn12.gif

323 ms

btn13.gif

btn13.gif

337 ms

bar.jpg

bar.jpg

363 ms

twitter_ico.png

twitter_ico.png

422 ms

footer_bg.gif

footer_bg.gif

374 ms

acs6.cgi

acs6.cgi

398 ms

mobile.css

mobile.css

194 ms

main_p.css

main_p.css

190 ms

speech.css

speech.css

179 ms

Accessibility Review

aebs.or.jp accessibility score

55

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

aebs.or.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

aebs.or.jp SEO score

92

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

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

    SHIFT_JIS

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

aebs.or.jp

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