2.7 sec in total
198 ms
2.4 sec
142 ms
Visit nexavar.jp now to see the best up-to-date Nexavar content for Japan and also check out these interesting facts you probably never knew about nexavar.jp
医療関係者及び患者様とそのご家族の方向けに、バイエル薬品の抗悪性腫瘍剤ネクサバールを適正にご使用いただくための情報を提供しています。
Visit nexavar.jpWe analyzed Nexavar.jp page load time and found that the first response time was 198 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
nexavar.jp performance score
198 ms
122 ms
95 ms
189 ms
196 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 99% of them (102 requests) were addressed to the original Nexavar.jp, 1% (1 request) were made to Bayeryakuhin.112.2o7.net. The less responsive or slowest element that took the longest time to load (847 ms) belongs to the original domain Nexavar.jp.
Page size can be reduced by 359.3 kB (54%)
666.7 kB
307.4 kB
In fact, the total size of Nexavar.jp main page is 666.7 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. CSS take 225.9 kB which makes up the majority of the site volume.
Potential reduce by 8.0 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 8.0 kB or 70% of the original size.
Potential reduce by 13.7 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. Nexavar images are well optimized though.
Potential reduce by 148.2 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 148.2 kB or 68% of the original size.
Potential reduce by 189.5 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. Nexavar.jp needs all CSS files to be minified and compressed as it can save up to 189.5 kB or 84% of the original size.
Number of requests can be reduced by 80 (79%)
101
21
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nexavar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 53 to 1 for CSS and as a result speed up the page load time.
nexavar.jp
198 ms
index.php
122 ms
import.css
95 ms
import-block.css
189 ms
import-block2.css
196 ms
responsive-tables.css
198 ms
announcement.css
185 ms
jquery-1.9.1.min.js
522 ms
jquery.cookie.js
205 ms
jquery.tile.js
278 ms
jquery.jcarousel.min.js
373 ms
jcarousel.responsive.js
285 ms
smoothRollOver.js
287 ms
jquery.rollover.js
319 ms
scroll.js
380 ms
lightbox.js
463 ms
jquery.magnific-popup.min.js
474 ms
jquery.placeholder.min.js
422 ms
responsive-tables.js
472 ms
easing.js
483 ms
jquery.ui.totop.js
527 ms
common.js
567 ms
s_code.js
738 ms
html5reset-1.6.1.css
480 ms
adjust.css
488 ms
basic.css
530 ms
layout.css
551 ms
layout-detail.css
657 ms
common-class.css
669 ms
row-column.css
751 ms
lightbox.css
632 ms
magnific-popup.css
665 ms
jcarousel.responsive.css
732 ms
ui.totop.css
755 ms
title.css
666 ms
detail.css
689 ms
content_separate.css
670 ms
strong.css
755 ms
list_normal.css
755 ms
list_link.css
765 ms
list_order.css
756 ms
list_date.css
758 ms
list_faq.css
791 ms
list_button.css
847 ms
list_history.css
768 ms
list_float.css
755 ms
list_shortcut.css
756 ms
list_none.css
726 ms
list_flow.css
719 ms
list_inline.css
764 ms
pager.css
712 ms
faq_detail.css
674 ms
table_normal.css
667 ms
table_line.css
684 ms
table_no_style.css
722 ms
button_part.css
712 ms
form_button.css
702 ms
notes.css
663 ms
more.css
663 ms
link.css
682 ms
caption.css
701 ms
line_part.css
689 ms
secondly_content.css
598 ms
content_banner.css
593 ms
target_block.css
575 ms
whatsnew.css
613 ms
image.css
667 ms
topic_path.css
605 ms
hr.css
573 ms
overflow_content.css
581 ms
include_data.css
586 ms
w_bg.png
366 ms
h_nexavar_logo.png
95 ms
h_nexavar_icon.png
108 ms
h_nexavar_slogan.png
99 ms
h_bayer_logo.png
95 ms
h_secondly_text.png
96 ms
h_thirdly_text_1.png
198 ms
h_thirdly_icon.png
198 ms
h_thirdly_text_2.png
188 ms
h_thirdly_text_3.png
206 ms
h_fourthly_text_1.png
208 ms
h_fourthly_text_2.png
293 ms
common_bg_c.png
301 ms
hr_bg.png
301 ms
title_level_3_icon.png
312 ms
icon_tri_white.png
321 ms
icon_tri_blu.png
390 ms
bg_gray_transparent.png
395 ms
f_banner_bg.png
406 ms
RI_banner_170x50.jpg
419 ms
f_banner_eob.png
424 ms
f_banner_nerisona.png
452 ms
f_banner_adalat.png
481 ms
f_banner_bayer_health.png
486 ms
f_banner_levitra.png
499 ms
h_secondly_icon.png
459 ms
h_fourthly_bg.png
468 ms
h_fourthly_bg_li_a.png
478 ms
loading.gif
502 ms
close.png
520 ms
ui.totop.png
521 ms
s85772182685323
84 ms
nexavar.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nexavar.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 Nexavar.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.
nexavar.jp
Open Graph description is not detected on the main page of Nexavar. 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: