10.3 sec in total
3.3 sec
6.7 sec
320 ms
Welcome to sho-yaku.seesaa.net homepage info - get ready to check Sho Yaku Seesaa best content for Japan right away, or after learning these important things about sho-yaku.seesaa.net
漢方薬には多くの種類があり、そしてそれらには様々な生薬が配合されています。
Visit sho-yaku.seesaa.netWe analyzed Sho-yaku.seesaa.net page load time and found that the first response time was 3.3 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sho-yaku.seesaa.net performance score
name
value
score
weighting
Value12.9 s
0/100
10%
Value13.1 s
0/100
25%
Value30.5 s
0/100
10%
Value3,400 ms
2/100
30%
Value0
100/100
15%
Value28.2 s
0/100
10%
3332 ms
343 ms
330 ms
373 ms
293 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Sho-yaku.seesaa.net, 18% (23 requests) were made to Blog.seesaa.jp and 7% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Sho-yaku.seesaa.net.
Page size can be reduced by 418.8 kB (69%)
606.7 kB
187.9 kB
In fact, the total size of Sho-yaku.seesaa.net main page is 606.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. 70% of websites need less resources to load. Javascripts take 368.7 kB which makes up the majority of the site volume.
Potential reduce by 56.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 56.0 kB or 80% of the original size.
Potential reduce by 334 B
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. Sho Yaku Seesaa images are well optimized though.
Potential reduce by 236.6 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 236.6 kB or 64% of the original size.
Potential reduce by 125.9 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. Sho-yaku.seesaa.net needs all CSS files to be minified and compressed as it can save up to 125.9 kB or 90% of the original size.
Number of requests can be reduced by 76 (63%)
120
44
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sho Yaku Seesaa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
sho-yaku.seesaa.net
3332 ms
styles-index.css
343 ms
user-common.css
330 ms
common_header.js
373 ms
l.j
293 ms
ad_plugin.js
375 ms
show_ads.js
8 ms
bl-bookmarks.js
439 ms
tag_cloud.js
294 ms
rakuten_widget.js
849 ms
trace_searcher.js
321 ms
adstir.js
610 ms
analytics-seesaa-net.js
337 ms
bg.gif
161 ms
fan_read.gif
215 ms
fan_received.gif
215 ms
seesaablog.gif
262 ms
common-header.css
271 ms
ot_square.pl
354 ms
AdLantisLoader.js
390 ms
common_header_sb.js
291 ms
4.gif
370 ms
ico_pr2.gif
188 ms
ico_pr3.gif
148 ms
embed.js
672 ms
common_header_sb.css
163 ms
common_header_sb1.gif
192 ms
common_header_sb.gif
201 ms
x.gif
184 ms
l73.f
372 ms
ts.gif
314 ms
header.gif
193 ms
ca-pub-7879573690400254.js
56 ms
zrt_lookup.html
63 ms
show_ads_impl.js
64 ms
listCategoryArticle.gif
165 ms
sidetitle.gif
148 ms
ads
204 ms
bookmark_button.js
377 ms
sdk.js
285 ms
widgets.js
4 ms
bookmarks_iframe.html
167 ms
expansion_embed.js
15 ms
button-only@2x.png
390 ms
osd.js
12 ms
mtwidget04.affiliate.rakuten.co.jp
346 ms
ads
263 ms
ads
163 ms
mtwidget04.affiliate.rakuten.co.jp
387 ms
trace_searcher.css
166 ms
plugins.js
362 ms
plusone.js
85 ms
widgets.js
61 ms
share.js
364 ms
css
139 ms
m_js_controller.js
43 ms
abg.js
81 ms
cb=gapi.loaded_0
50 ms
cb=gapi.loaded_1
114 ms
fastbutton
173 ms
fastbutton
195 ms
fastbutton
192 ms
ad
360 ms
242 ms
xd_arbiter.php
303 ms
xd_arbiter.php
510 ms
nessie_icon_tiamat_white.png
36 ms
s
29 ms
googlelogo_color_112x36dp.png
112 ms
x_button_blue2.png
95 ms
postmessageRelay
146 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
59 ms
pc_pcview_all.css
113 ms
front_merged.js
126 ms
PuwvqkdbcqU-fCZ9Ed-b7b3hpw3pgy2gAi-Ip7WPMi0.woff
131 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
40 ms
261 ms
266 ms
262 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
387 ms
getMWConf.php
342 ms
xZQOmYg4x3YaWkTJi1kErvesZW2xOQ-xsNqO47m55DA.woff
127 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
425 ms
getMWConf.php
315 ms
loading.gif
12 ms
buttons.gif
12 ms
api.js
42 ms
core:rpc:shindig.random:shindig.sha1.js
42 ms
2536007149-postmessagerelay.js
54 ms
sh.adingo.jp
343 ms
reset.css
5 ms
entry-button.css
6 ms
bbtn-l_v3.png
3 ms
4987138466747.jpg
250 ms
a.gif
345 ms
4987138466266.jpg
225 ms
4987138466358.jpg
423 ms
delivery
190 ms
a.gif
294 ms
sync
315 ms
u.html
64 ms
i.adingo.jp
326 ms
i.adingo.jp
373 ms
analytics.js
30 ms
adlantis.www.js
1092 ms
swfobject.js
1115 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
44 ms
collect
5 ms
collect
68 ms
cs
979 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
32 ms
like.php
53 ms
like.php
69 ms
-1cfYrhulAt.js
491 ms
LVx-xkvaJ0b.png
552 ms
like.php
84 ms
318 ms
jot.html
6 ms
activeview
15 ms
activeview
16 ms
626 ms
161 ms
377 ms
load_script
355 ms
sho-yaku.seesaa.net 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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sho-yaku.seesaa.net 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
Browser errors were logged to the console
sho-yaku.seesaa.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sho-yaku.seesaa.net 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 Sho-yaku.seesaa.net 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.
sho-yaku.seesaa.net
Open Graph description is not detected on the main page of Sho Yaku Seesaa. 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: