Tools & Wizards About Us
ai.jsaweb.jp screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ai.jsaweb.jp

一般社団法人 日本アレルギー学会

Page Load Speed

5 sec in total

First Response

571 ms

Resources Loaded

4 sec

Page Rendered

402 ms

ai.jsaweb.jp screenshot

About Website

Visit ai.jsaweb.jp now to see the best up-to-date Ai Jsaweb content for Japan and also check out these interesting facts you probably never knew about ai.jsaweb.jp

一般社団法人日本アレルギー学会公式サイト

Visit ai.jsaweb.jp

Key Findings

We analyzed Ai.jsaweb.jp page load time and found that the first response time was 571 ms and then it took 4.4 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

ai.jsaweb.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.355

31/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

ai.jsaweb.jp

571 ms

www.allergologyinternational.com

392 ms

getSharedSiteSession

480 ms

getSharedSiteSession

73 ms

consumeSharedSessionAction

146 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ai.jsaweb.jp, 48% (29 requests) were made to Allergologyinternational.com and 5% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Allergologyinternational.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 803.6 kB (67%)

Content Size

1.2 MB

After Optimization

403.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ai.jsaweb.jp main page is 1.2 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. 55% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 132.2 kB

  • Original 175.5 kB
  • After minification 147.6 kB
  • After compression 43.3 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 27.9 kB, which is 16% 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 132.2 kB or 75% of the original size.

Image Optimization

-14%

Potential reduce by 1.9 kB

  • Original 13.7 kB
  • After minification 11.8 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. Obviously, Ai Jsaweb needs image optimization as it can save up to 1.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 669.5 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 348.4 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 669.5 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (60%)

Requests Now

48

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ai.jsaweb.jp

ai.jsaweb.jp

571 ms

www.allergologyinternational.com

www.allergologyinternational.com

392 ms

getSharedSiteSession

getSharedSiteSession

480 ms

getSharedSiteSession

getSharedSiteSession

73 ms

consumeSharedSessionAction

consumeSharedSessionAction

146 ms

consumeSharedSessionAction

consumeSharedSessionAction

135 ms

www.allergologyinternational.com

www.allergologyinternational.com

338 ms

537390469.js

537390469.js

47 ms

embed.js

embed.js

10 ms

product.css

product.css

225 ms

head_1_53_158_167_22390_22392.css

head_1_53_158_167_22390_22392.css

364 ms

ha.css

ha.css

166 ms

product.js

product.js

734 ms

altmetric_badges-98e4a0c5363439e08b1f025f231428bc.js

altmetric_badges-98e4a0c5363439e08b1f025f231428bc.js

86 ms

0.png

0.png

99 ms

getMessage

getMessage

685 ms

satelliteLib-8e350dc4ceceb17a5d77c03f66d95608807a5585.js

satelliteLib-8e350dc4ceceb17a5d77c03f66d95608807a5585.js

82 ms

bg_main.png

bg_main.png

228 ms

bg_adHoriz.gif

bg_adHoriz.gif

227 ms

logo.jpg

logo.jpg

395 ms

cover.tif.jpg

cover.tif.jpg

569 ms

alit-impact.gif

alit-impact.gif

357 ms

jsaLogo.png

jsaLogo.png

357 ms

elsevier.jpg

elsevier.jpg

559 ms

January2016GA.jpg

January2016GA.jpg

637 ms

January2016GA2.jpg

January2016GA2.jpg

688 ms

January2016GA3.jpg

January2016GA3.jpg

686 ms

gr2.jpg

gr2.jpg

994 ms

gr1.jpg

gr1.jpg

1051 ms

gtm.js

gtm.js

43 ms

gpt.js

gpt.js

13 ms

bg_header.png

bg_header.png

693 ms

icon_arrow_off.gif

icon_arrow_off.gif

755 ms

bg_fragmentHeader.png

bg_fragmentHeader.png

811 ms

bell.png

bell.png

815 ms

pubads_impl_82.js

pubads_impl_82.js

23 ms

arrow_right.png

arrow_right.png

799 ms

elsevierwordmark-regular-OA.woff

elsevierwordmark-regular-OA.woff

926 ms

platformFile

platformFile

175 ms

addthis_widget.js

addthis_widget.js

93 ms

satellite-5628673864746d59120020a6.js

satellite-5628673864746d59120020a6.js

59 ms

analytics.js

analytics.js

47 ms

ads

ads

247 ms

container.html

container.html

207 ms

rd

rd

208 ms

s-code-contents-87ff59abfc9acf73289bd658598e0b01359c7df7.js

s-code-contents-87ff59abfc9acf73289bd658598e0b01359c7df7.js

203 ms

ui-icons_222222_256x240.png

ui-icons_222222_256x240.png

817 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

745 ms

collect

collect

36 ms

id

id

101 ms

collect

collect

54 ms

ga-audiences

ga-audiences

55 ms

s83310963686089

s83310963686089

10 ms

small-device.css

small-device.css

74 ms

conversion_async.js

conversion_async.js

32 ms

300lo.json

300lo.json

16 ms

385.a1b89ff397c1dae17be0.js

385.a1b89ff397c1dae17be0.js

35 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

27 ms

42 ms

16 ms

Accessibility Review

ai.jsaweb.jp accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

Links do not have a discernible name

Best Practices

ai.jsaweb.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

High

Page has valid source maps

SEO Factors

ai.jsaweb.jp SEO score

90

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ai.jsaweb.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Ai.jsaweb.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

ai.jsaweb.jp

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