4.5 sec in total
618 ms
3.6 sec
352 ms
Visit bayaspirin.jp now to see the best up-to-date Bayaspirin content for Japan and also check out these interesting facts you probably never knew about bayaspirin.jp
Bayaspirin.JPは、バイエル薬品株式会社が抗血小板薬バイアスピリンに関する情報を発信する医療関係者向けオフィシャルサイトです。
Visit bayaspirin.jpWe analyzed Bayaspirin.jp page load time and found that the first response time was 618 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
bayaspirin.jp performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value7.2 s
5/100
25%
Value6.8 s
34/100
10%
Value2,380 ms
5/100
30%
Value0.34
33/100
15%
Value8.6 s
37/100
10%
618 ms
211 ms
194 ms
212 ms
200 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 99% of them (107 requests) were addressed to the original Bayaspirin.jp, 1% (1 request) were made to Bayeryakuhin.112.2o7.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Bayaspirin.jp.
Page size can be reduced by 435.4 kB (32%)
1.4 MB
935.4 kB
In fact, the total size of Bayaspirin.jp main page is 1.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. 35% of websites need less resources to load. Images take 991.6 kB which makes up the majority of the site volume.
Potential reduce by 41.4 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 8.5 kB, which is 18% 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 41.4 kB or 85% of the original size.
Potential reduce by 153.9 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, Bayaspirin needs image optimization as it can save up to 153.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 182.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 182.0 kB or 70% of the original size.
Potential reduce by 58.1 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. Bayaspirin.jp needs all CSS files to be minified and compressed as it can save up to 58.1 kB or 80% of the original size.
Number of requests can be reduced by 39 (36%)
107
68
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bayaspirin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
bayaspirin.jp
618 ms
screen.css
211 ms
layout.css
194 ms
bygnavi.css
212 ms
base.css
200 ms
bhvNew.css
213 ms
size1.css
288 ms
jquery-1.8.2.min.js
570 ms
swfobject-2.2.js
309 ms
popup.js
306 ms
cookie.js
316 ms
defaults.js
405 ms
bygnavi.js
398 ms
jquery.transit.min.js
412 ms
jquery.easing.1.3.js
407 ms
common.js
425 ms
bygridtype1.js
509 ms
bygridtype2.js
524 ms
bygridtype3.js
506 ms
bygridtype4.js
514 ms
jquery.masonry.min.js
551 ms
functions.js
609 ms
jquery.powertip.js
726 ms
jquery.powertip.min.js
612 ms
tooltip.js
640 ms
lightpopup.js
650 ms
base.css
669 ms
layout.css
708 ms
bygridtype1.css
722 ms
bygridtype2.css
752 ms
bygridtype3.css
748 ms
bygridtype4.css
764 ms
style.css
815 ms
jquery.powertip.css
833 ms
image_slide.css
834 ms
lightpopup.css
858 ms
s_code.js
905 ms
outline.css
669 ms
content.css
720 ms
slide_top.jpg
216 ms
icon_bullet.png
107 ms
icon_new.gif
215 ms
searchtxt.jpg
105 ms
searchbtn.jpg
107 ms
bayer_sma_logo.png
216 ms
top_banner.jpg
402 ms
icon.png
217 ms
title.png
217 ms
photo.png
325 ms
title.png
268 ms
arrow_right_out.png
292 ms
arrow_left_out.png
308 ms
arrow1.png
316 ms
iconseminar.png
383 ms
titleseminar.png
411 ms
photoSeminar.png
513 ms
icon2.png
429 ms
title2.png
433 ms
photoInfo.png
586 ms
movie_linebg.png
508 ms
movie_arrowbg.png
516 ms
movie_arrow.png
535 ms
movie_new.png
537 ms
icon.png
608 ms
title.png
630 ms
photo.png
844 ms
icon.png
636 ms
title.png
654 ms
photo.png
708 ms
btn1_out.png
709 ms
btn1_over.png
735 ms
btn2_out.png
736 ms
btn2_over.png
756 ms
photo.png
826 ms
icon.png
727 ms
title.png
739 ms
photo.png
930 ms
icon.png
668 ms
title.png
716 ms
box16.png
749 ms
photo.png
744 ms
movie_linebg.png
775 ms
movie_arrowbg.png
822 ms
movie_arrow.png
782 ms
icon.png
786 ms
title.png
761 ms
photo.png
882 ms
icon.png
813 ms
title.png
768 ms
photo.png
860 ms
icon.png
765 ms
title.png
758 ms
box10.jpg
823 ms
box12.jpg
765 ms
box13.jpg
762 ms
box11.png
772 ms
footer1.jpg
781 ms
footer2.jpg
852 ms
footer3.jpg
780 ms
s79785916924010
82 ms
footer4.jpg
779 ms
footer.png
768 ms
slide_img4.png
1159 ms
confirm.png
774 ms
btn.png
765 ms
print.css
113 ms
size2.css
104 ms
size3.css
113 ms
bayaspirin.jp accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
bayaspirin.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
bayaspirin.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bayaspirin.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 Bayaspirin.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.
bayaspirin.jp
Open Graph description is not detected on the main page of Bayaspirin. 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: