10 sec in total
511 ms
9.1 sec
459 ms
Welcome to watson.jp homepage info - get ready to check Watson best content for Japan right away, or after learning these important things about watson.jp
ホームページ運営なら、ずっと使えるレンタルサーバー「ロリポップ!」簡単、無料SSL、充実サポート、高速性能で、初心者から商用サイトまで安心してご利用いただけます。WordPress、EC-CUBEもたったの60秒で設置可能。無料お試し10日間。
Visit watson.jpWe analyzed Watson.jp page load time and found that the first response time was 511 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
watson.jp performance score
511 ms
1403 ms
338 ms
631 ms
482 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Watson.jp, 53% (71 requests) were made to Lolipop.jp and 8% (11 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Lolipop.jp.
Page size can be reduced by 440.1 kB (36%)
1.2 MB
778.2 kB
In fact, the total size of Watson.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. 40% of websites need less resources to load. Images take 707.6 kB which makes up the majority of the site volume.
Potential reduce by 143.2 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 143.2 kB or 85% of the original size.
Potential reduce by 125.4 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, Watson needs image optimization as it can save up to 125.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 73.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 73.0 kB or 32% of the original size.
Potential reduce by 98.4 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. Watson.jp needs all CSS files to be minified and compressed as it can save up to 98.4 kB or 85% of the original size.
Number of requests can be reduced by 66 (57%)
116
50
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watson. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
watson.jp
511 ms
lolipop.jp
1403 ms
default.css
338 ms
common.css
631 ms
background.css
482 ms
text_m.css
493 ms
home.css
498 ms
lightbox.css
503 ms
owl.carousel.css
508 ms
jquery.min.js
64 ms
base.js
641 ms
lightbox.min.js
563 ms
owl.carousel.min.js
667 ms
home.js
598 ms
scrollReveal.min.js
599 ms
pixel.js
631 ms
mixpanel.js
628 ms
fbds.js
142 ms
mixpanel-2-latest.min.js
125 ms
bg_night.gif
329 ms
close.png
548 ms
loading.gif
539 ms
prev.png
537 ms
next.png
544 ms
bg_content_side.png
547 ms
bg_main_bottom.gif
549 ms
bg_main_1column.png
693 ms
bg_submenu_top.gif
707 ms
h2_home_title.png
1851 ms
megaphone.svg
1559 ms
obj_home_plan_economy.svg
1542 ms
obj_home_plan_lite.svg
1539 ms
obj_home_plan_standard.svg
1537 ms
obj_home_plan_ribbon.svg
1556 ms
obj_home_plan_enterprise.svg
1708 ms
btn_home_plan_function_detail.png
1858 ms
btn_home_plan_price_detail.png
1713 ms
bnr_lolipop_nextgen_201601.png
2240 ms
h3_home_title.png
2396 ms
obj_home_feature_wordpress.png
2198 ms
line_dot_11.gif
1899 ms
obj_home_feature_backup.png
2172 ms
obj_home_feature_utilization.png
2175 ms
obj_home_feature_support.png
2390 ms
h3_home_functions.png
2530 ms
obj_home_functions_list.png
2689 ms
btn_feature._function_detail.png
2527 ms
btn_infomation_more.png
2543 ms
badge_light.png
116 ms
line_dot_02.gif
2493 ms
widgets.js
56 ms
icon_star.gif
2494 ms
btn_h_serch.png
2586 ms
line_dot_08.gif
2589 ms
22 ms
131 ms
btn_pagetop.gif
2595 ms
dc.js
64 ms
obj_lolipop_logo.png
2731 ms
obj_ojisan_normal.png
2728 ms
__utm.gif
16 ms
__utm.gif
12 ms
__utm.gif
21 ms
__utm.gif
31 ms
obj_header_banner_text.png
2686 ms
btn_header_order.png
2532 ms
bg_header_simple.png
2895 ms
obj_ppb_by_logo.png
2459 ms
obj_order_count_text.png
2464 ms
pixel
304 ms
pixel
58 ms
Pug
73 ms
sync.ad-stir.com
634 ms
sync
52 ms
sync
989 ms
is
1195 ms
headerstyle.min.css
208 ms
sd
8 ms
pixel
16 ms
186 ms
tag.js
41 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
4 ms
tag
60 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
20 ms
jot
96 ms
obj_numbers.png
1664 ms
menu_btn.png
1874 ms
menu_dot.gif
1773 ms
arrow_menu.gif
1759 ms
obj_logo_ppb.png
1769 ms
obj_prev_item_icon.png
1667 ms
obj_next_item_icon.png
1763 ms
obj_dhw_ac_jp_thumb.jpg
1799 ms
obj_mtblanc_jp_thumb.jpg
1784 ms
obj_foresthuntingone_com_thumb.jpg
1825 ms
obj_sakelife_jp_thumb.jpg
1576 ms
lolipop.jp
1197 ms
lolipop.jp
1994 ms
lolipop.jp
1692 ms
lolipop.jp
1278 ms
lolipop.jp
1604 ms
nr-768.min.js
107 ms
__utm.gif
28 ms
roundtrip.js
100 ms
btn.png
35 ms
conversion_async.js
52 ms
37 ms
__utm.gif
22 ms
logo201601.png
51 ms
open_footer.png
76 ms
close_footer.png
106 ms
58 ms
conversion.js
1280 ms
15936ac739
127 ms
51 ms
QGNG2UAG2ZAKJNSEXUXBMN.js
117 ms
out
10 ms
tr
39 ms
out
6 ms
out
12 ms
out
34 ms
out
35 ms
out
35 ms
out
35 ms
out
35 ms
out
33 ms
u.php
77 ms
42 ms
sync
21 ms
sd
149 ms
sd
30 ms
in
16 ms
377928.gif
6 ms
tap.php
156 ms
in
6 ms
watson.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watson.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 Watson.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.
watson.jp
Open Graph data is detected on the main page of Watson. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: