6.7 sec in total
656 ms
5.7 sec
329 ms
Welcome to saiseiya.com homepage info - get ready to check Saiseiya best content for Japan right away, or after learning these important things about saiseiya.com
Visit saiseiya.comWe analyzed Saiseiya.com page load time and found that the first response time was 656 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
saiseiya.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value2.4 s
91/100
25%
Value4.6 s
70/100
10%
Value70 ms
99/100
30%
Value0.473
18/100
15%
Value4.0 s
87/100
10%
656 ms
348 ms
609 ms
423 ms
10 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 10% of them (11 requests) were addressed to the original Saiseiya.com, 49% (52 requests) were made to Img02.shop-pro.jp and 26% (28 requests) were made to Img.shop-pro.jp. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Img02.shop-pro.jp.
Page size can be reduced by 430.9 kB (16%)
2.6 MB
2.2 MB
In fact, the total size of Saiseiya.com main page is 2.6 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. 35% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 28.5 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 28.5 kB or 79% of the original size.
Potential reduce by 186.2 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. Saiseiya images are well optimized though.
Potential reduce by 190.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 190.2 kB or 68% of the original size.
Potential reduce by 25.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. Saiseiya.com needs all CSS files to be minified and compressed as it can save up to 25.9 kB or 81% of the original size.
Number of requests can be reduced by 27 (26%)
105
78
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saiseiya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
saiseiya.com
656 ms
cross-border-cart.css
348 ms
index.css
609 ms
top.css
423 ms
jquery.min.js
10 ms
jquery.bxslider.css
334 ms
jquery.bxslider.min.js
339 ms
gmo_header.js.php
348 ms
gmo_header.css.php
338 ms
cart.js
340 ms
product_stock.js
680 ms
li.php
506 ms
li.php
513 ms
0101_wrapper_bg.gif
411 ms
calendar.fcgi
1502 ms
0101_header_search.gif
440 ms
0101_header_cart.gif
585 ms
0101_header_login.gif
448 ms
0101_header_mypage.gif
394 ms
0101_header_globalnavi.gif
288 ms
0101_side_category_h3.gif
329 ms
0101_icon_arrow.gif
688 ms
0101_side_group_h3.gif
637 ms
0101_side_menu_h3.gif
666 ms
0101_side_cart_h3.gif
700 ms
0101_side_mailmaga_h3.gif
706 ms
0101_side_mobile_h3.gif
901 ms
0101_side_seller_h3.gif
1096 ms
0101_side_feed.gif
927 ms
0101_side_h3.gif
1087 ms
PA01127316.jpg
292 ms
qrcode.jpg
285 ms
97789496_th.jpg
451 ms
43394981_th.jpg
465 ms
61468587_th.jpg
268 ms
calendar.gif
282 ms
slideshow_img0.jpg
1154 ms
slideshow_img2.jpg
939 ms
slideshow_img3.jpg
1518 ms
slideshow_img4.jpg
1101 ms
slideshow_img5.jpg
1650 ms
slideshow_img6.jpg
1369 ms
Wimax%C6%C3%BD%B8.jpg
1925 ms
450Mbpswlan%C6%C3%BD%B8.jpg
1570 ms
HD%C6%C3%BD%B8.jpg
2173 ms
Bluetooth4.0%C6%C3%BD%B8.jpg
2028 ms
Thinkpadparts%C6%C3%BD%B8.jpg
2506 ms
96797126_th.jpg
2036 ms
97897105_th.jpg
2206 ms
98292817_th.jpg
2194 ms
98329003_th.jpg
2482 ms
99403754_th.jpg
2319 ms
99442763_th.jpg
2444 ms
99443675_th.jpg
2449 ms
63968243_th.jpg
2659 ms
35829122_th.jpg
2591 ms
64831415_th.jpg
2713 ms
64948130_th.jpg
3001 ms
66532609_th.jpg
2863 ms
69529102_th.jpg
2877 ms
72817487_th.jpg
2900 ms
72871014_th.jpg
2973 ms
72951231_th.jpg
3545 ms
72958037_th.jpg
3137 ms
74790130_th.jpg
3179 ms
icons15.gif
178 ms
icons42.gif
183 ms
88305622_th.jpg
3319 ms
0101_main_info_h2.gif
917 ms
0101_main_arrival_h2.gif
927 ms
0101_main_recommend_h2.gif
1101 ms
0101_sub_push_h2.gif
1143 ms
0101_sub_seller_h2.gif
1184 ms
0101_sub_seller_1.gif
1151 ms
0101_sub_seller_2.gif
1300 ms
0101_sub_seller_3.gif
1346 ms
0101_sub_seller_4.gif
1371 ms
0101_sub_seller_5.gif
1409 ms
0101_pickup_h2.gif
1399 ms
0101_footer_pagetop.gif
1725 ms
secure.shop-pro.jp
546 ms
bx_loader.gif
346 ms
95978614_th.jpg
2963 ms
33566108_th.jpg
2986 ms
64945353_th.jpg
3322 ms
60422061_th.jpg
3151 ms
33478665_th.jpg
3043 ms
39872733_th.jpg
3313 ms
jquery-1.6.4.min.js
1114 ms
easyXDM.min.js
511 ms
gmohd_logo2.gif
186 ms
login.gif
184 ms
regist.gif
184 ms
31718984_th.jpg
2881 ms
33478876_th.jpg
2723 ms
64012960_th.jpg
2650 ms
40001243_th.jpg
2447 ms
cal_left.png
199 ms
cal_right.png
355 ms
44305922_th.jpg
2484 ms
60474572_th.jpg
2475 ms
30021681_th.jpg
2525 ms
gmohd_bg.gif
4 ms
checkSession.do
938 ms
47177944_th.jpg
2428 ms
easyXDM.js
1661 ms
saiseiya.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 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
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
saiseiya.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
Browser errors were logged to the console
saiseiya.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saiseiya.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 Saiseiya.com main page’s claimed encoding is euc-jp. 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.
saiseiya.com
Open Graph description is not detected on the main page of Saiseiya. 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: