7.7 sec in total
526 ms
4.6 sec
2.6 sec
Click here to check amazing Sakase content for Japan. Otherwise, check out these important facts you probably never knew about sakase.com
医療・産業分野における収納・搬送をトータルにサポートするキャビネット・カートの製造販売、プラスチック・シリコーン樹脂の成形・精密成形品の受託製造、機能性特殊カートの開発・製造などや、これらの特注・別注品の製造販売および成形品を核とした複合製品の紹介をデジタルカタログとのコラボレーションで行っています。
Visit sakase.comWe analyzed Sakase.com page load time and found that the first response time was 526 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sakase.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value18.9 s
0/100
25%
Value12.3 s
3/100
10%
Value740 ms
40/100
30%
Value0.453
20/100
15%
Value17.8 s
4/100
10%
526 ms
858 ms
45 ms
335 ms
487 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 83% of them (68 requests) were addressed to the original Sakase.com, 10% (8 requests) were made to Cdn.jsdelivr.net and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Sakase.com.
Page size can be reduced by 1.2 MB (7%)
17.5 MB
16.4 MB
In fact, the total size of Sakase.com main page is 17.5 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. 70% of websites need less resources to load. Images take 16.4 MB which makes up the majority of the site volume.
Potential reduce by 27.7 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 9.6 kB, which is 29% 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 27.7 kB or 82% of the original size.
Potential reduce by 230.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. Sakase images are well optimized though.
Potential reduce by 379.8 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 379.8 kB or 71% of the original size.
Potential reduce by 515.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. Sakase.com needs all CSS files to be minified and compressed as it can save up to 515.1 kB or 87% of the original size.
Number of requests can be reduced by 20 (27%)
73
53
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sakase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
sakase.com
526 ms
sakase.com
858 ms
all.css
45 ms
lib.min.css
335 ms
slick.css
487 ms
slick-theme.css
502 ms
rhinoslider-1.05.css
504 ms
lity.min.css
503 ms
css
37 ms
yakuhanjp.min.css
21 ms
style.css
1521 ms
img-logo.svg
524 ms
hd_icon_mail@2x.png
646 ms
hd_icon_map@2x.png
669 ms
hd_icon_global@2x.png
670 ms
hd_icon_book@2x.png
670 ms
mv4_sp@2x.jpg
1608 ms
mv6_sp@2x.jpg
1777 ms
mv2_sp@2x.jpg
1342 ms
mv3_sp@2x.jpg
1675 ms
mv5_sp@2x.jpg
1674 ms
mv1_sp@2x.jpg
1847 ms
close@2x.png
1526 ms
top_bnr2@2x.jpg
1576 ms
top_bnr3@2x.jpg
1682 ms
top_bnr7@2x.jpg
1681 ms
top_bnr1@2x.jpg
1695 ms
top_bnr6@2x.jpg
1750 ms
top_bnr4@2x.jpg
1775 ms
top_bnr5@2x.jpg
1855 ms
promise01_img.jpg
1852 ms
promise02_img.jpg
1854 ms
promise03_img.jpg
1866 ms
top_products1_sp@2x.jpg
2098 ms
arrow@2x.png
1936 ms
top_products2_sp@2x.jpg
2194 ms
top_products3_sp@2x.jpg
2189 ms
top_products4_sp@2x.jpg
2191 ms
products_logo@2x.jpg
2034 ms
top_spirits1@2x.jpg
2259 ms
js
61 ms
swiper-bundle.min.css
2202 ms
jquery.min.js
2105 ms
bootstrap.bundle.min.js
2039 ms
lib.min.js
2029 ms
common.js
2035 ms
slick.min.js
2038 ms
rhinoslider-1.05.js
2064 ms
ofi.min.js
1968 ms
swiper-bundle.min.js
2022 ms
home_new.js
2039 ms
top_spirits2@2x.jpg
2045 ms
top_spirits3@2x.jpg
1537 ms
css2
21 ms
top_spirits4@2x.jpg
1212 ms
YakuHanJP-Regular.woff
4 ms
YakuHanJP-Medium.woff
12 ms
YakuHanJP-DemiLight.woff
10 ms
YakuHanJP-Light.woff
12 ms
YakuHanJP-Thin.woff
11 ms
YakuHanJP-Bold.woff
10 ms
YakuHanJP-Black.woff
48 ms
top_ex1@2x.jpg
1351 ms
top_ex2@2x.jpg
1185 ms
top_ex3@2x.jpg
1188 ms
top_ex4@2x.jpg
1176 ms
top_ex5@2x.jpg
1177 ms
top_ex6@2x.jpg
1260 ms
top_thumb_ex1@2x.jpg
1194 ms
top_thumb_ex2@2x.jpg
1192 ms
top_thumb_ex3@2x.jpg
1200 ms
top_thumb_ex4@2x.jpg
1219 ms
top_thumb_ex5@2x.jpg
1220 ms
top_thumb_ex6@2x.jpg
1274 ms
fixed-bnr-catalog-sp.jpg
1194 ms
instagram.png
1363 ms
page-top.png
1197 ms
img-logo-02.svg
1210 ms
top_spirits_bg@2x.jpg
1214 ms
spirits_arrow@2x.png
1179 ms
ga.js
22 ms
__utm.gif
12 ms
sakase.com accessibility score
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
Links do not have a discernible name
sakase.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
sakase.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Sakase.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 Sakase.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.
sakase.com
Open Graph description is not detected on the main page of Sakase. 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: