7.4 sec in total
1.3 sec
5.8 sec
246 ms
Welcome to ssi-w.com homepage info - get ready to check SSI W best content for Japan right away, or after learning these important things about ssi-w.com
国際的な基準で物事を捉え、それらが抱える様々な問題点を消費者視点で提起し、その解決に向けた調査、研究のみならず、実践を伴うことにより改善を図り、世界に冠たる「日本酒」の確立を目指します。
Visit ssi-w.comWe analyzed Ssi-w.com page load time and found that the first response time was 1.3 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ssi-w.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value10.4 s
0/100
25%
Value14.6 s
1/100
10%
Value50 ms
100/100
30%
Value0.524
15/100
15%
Value8.9 s
34/100
10%
1291 ms
13 ms
167 ms
314 ms
321 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 67% of them (57 requests) were addressed to the original Ssi-w.com, 5% (4 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Ssi-w.com.
Page size can be reduced by 987.1 kB (32%)
3.1 MB
2.1 MB
In fact, the total size of Ssi-w.com main page is 3.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 34.6 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 34.6 kB or 79% of the original size.
Potential reduce by 474.3 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, SSI W needs image optimization as it can save up to 474.3 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 248.1 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 248.1 kB or 66% of the original size.
Potential reduce by 230.0 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. Ssi-w.com needs all CSS files to be minified and compressed as it can save up to 230.0 kB or 82% of the original size.
Number of requests can be reduced by 43 (52%)
82
39
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SSI W. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.ssi-w.com
1291 ms
ga.js
13 ms
styles.css
167 ms
styles.css
314 ms
meteor-slides.css
321 ms
kgvid_styles.css
329 ms
whats-new.css
338 ms
wp125.css
342 ms
jquery.min.js
12 ms
swfobject.js
363 ms
kgvid_video_embed.js
479 ms
jquery.cycle.all.js
496 ms
jquery.metadata.v2.js
493 ms
jquery.touchwipe.1.1.1.js
508 ms
slideshow.js
513 ms
logo-slideshow.css
543 ms
logo-slideshow.js
637 ms
style.css
659 ms
wpBannerizeStyleDefault.css
655 ms
jquery1.4.4.min.js
843 ms
script.js
680 ms
__utm.gif
13 ms
admin-ajax.php
745 ms
__utm.gif
4 ms
admin-ajax.php
766 ms
225_60_bnr_academy.jpg
718 ms
225_bnr_sake.jpg
741 ms
225_sho_bnr.jpg
716 ms
arrowSub.png
166 ms
mainnavBg.png
196 ms
80c165e97799cf6684a6d36ae9e4afce-960x350.png
1567 ms
slide_1504242-960x350.jpg
905 ms
top_slide_Academy-960x3501-960x350.jpg
967 ms
top_slide_14-960x350.jpg
1088 ms
top_slide_1-960x350.png
2022 ms
top_slide_4-960x350.png
1815 ms
arrow_left.gif
1059 ms
arrow_right.gif
1133 ms
135bnr_kiki2days15.png
1228 ms
135bnr_kiki_t.png
1269 ms
135bnr_kiki_dvd.png
1298 ms
135bnr_syo_t.png
1400 ms
135bnr_syo_dvd.png
1452 ms
border.png
1461 ms
bullet.png
1572 ms
new.png
1637 ms
list_003_b-trans.png
1622 ms
top_03.jpg
1746 ms
top_01.jpg
1916 ms
top_02.jpg
1803 ms
top_16.jpg
1834 ms
225_60_bnr_fbo.png
1923 ms
225_60_bnr_2.png
1975 ms
225_60_bnr_online.png
1983 ms
225_30_bnr_1.png
2026 ms
225_60bnr_ptl.png
2093 ms
225_60_bnr_sakesennin.png
2093 ms
225_60_bnr_1.png
2141 ms
225_60_dl_test.png
2149 ms
ssi-intl_btn.png
2188 ms
225_60_bnr_gundan.png
2209 ms
widgets.js
86 ms
225_60_bnr_kindle.png
2239 ms
otYLmINlwL0
130 ms
all.js
31 ms
T8HUgJqPzfY
99 ms
305 ms
xd_arbiter.php
47 ms
xd_arbiter.php
62 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
282 ms
www-embed-player-vfl-z2BtK.css
45 ms
www-embed-player.js
88 ms
base.js
131 ms
arrow.png
2106 ms
buttons.png
2133 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
63 ms
ad_status.js
67 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
76 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
75 ms
syndication
103 ms
299755474830626816
343 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
110 ms
twitter_ssi_normal.png
188 ms
jot
25 ms
ssi-w.com 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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Links do not have a discernible name
ssi-w.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ssi-w.com 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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ssi-w.com 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 Ssi-w.com 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.
ssi-w.com
Open Graph data is detected on the main page of SSI W. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: