5.7 sec in total
945 ms
3.5 sec
1.2 sec
Welcome to a-supplement.net homepage info - get ready to check A Supplement best content for Japan right away, or after learning these important things about a-supplement.net
天然で安心、安全なマカ、キャッツクロー、サメ軟骨を取り扱っております。天然で純粋なものにこだわり、完全有機栽培・無農薬・無添加・無加工の高品質の素材の商品を取り揃えております。
Visit a-supplement.netWe analyzed A-supplement.net page load time and found that the first response time was 945 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
a-supplement.net performance score
name
value
score
weighting
Value2.9 s
51/100
10%
Value2.9 s
79/100
25%
Value6.0 s
46/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value3.2 s
94/100
10%
945 ms
368 ms
360 ms
780 ms
1056 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 87% of them (55 requests) were addressed to the original A-supplement.net, 11% (7 requests) were made to Static.xx.fbcdn.net and 2% (1 request) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain A-supplement.net.
Page size can be reduced by 33.7 kB (26%)
127.2 kB
93.5 kB
In fact, the total size of A-supplement.net main page is 127.2 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. 35% of websites need less resources to load. Images take 86.9 kB which makes up the majority of the site volume.
Potential reduce by 17.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. This page needs HTML code to be minified as it can gain 3.6 kB, which is 15% 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 17.6 kB or 73% of the original size.
Potential reduce by 3.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. A Supplement images are well optimized though.
Potential reduce by 601 B
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 601 B or 75% of the original size.
Potential reduce by 12.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. A-supplement.net needs all CSS files to be minified and compressed as it can save up to 12.1 kB or 79% of the original size.
Number of requests can be reduced by 9 (16%)
58
49
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A Supplement. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
a-supplement.net
945 ms
reset.css
368 ms
style1.css
360 ms
index.css
780 ms
acctag.js
1056 ms
bg.gif
183 ms
acclog.cgi
195 ms
a_top740image.gif
403 ms
bg_menu.gif
176 ms
top_1image.gif
523 ms
a_kodawariimage.gif
355 ms
a_sup_macaimage.gif
377 ms
top_maca_imege.gif
526 ms
a_sup_catsimage.gif
376 ms
top_cats_image.gif
531 ms
a_sup_sameimage.gif
545 ms
top_same_image.gif
728 ms
top11.gif
591 ms
top2.gif
694 ms
a_sup_tokimage1.gif
700 ms
top_kotumitud_image.gif
705 ms
a_sup_bitaimage.gif
720 ms
a_sup_bitamin_image.gif
869 ms
a_sup_seikatu_image.gif
875 ms
a_sup_sutoresu_image.gif
877 ms
a_sup_himan_image.gif
881 ms
top4.gif
890 ms
aiko1-2.gif
902 ms
a_sup_anzenimage.gif
1044 ms
a_sup_746image.gif
1045 ms
a_sup_vidaimage.jpg
1221 ms
a_sup_capsimage.jpg
1056 ms
top18.gif
1227 ms
a_sup_otamesi.gif
1078 ms
a_sup_otamesiimage.png
1166 ms
a_sup_tokuimage.gif
1211 ms
a_sup_sourilyouimage.gif
1233 ms
a_sup_npimage.jpg
1253 ms
a_sup_e-collect.gif
1360 ms
a_sup_satusimage.gif
1383 ms
a_sup_24image.gif
1393 ms
a_sup_annaiimage.gif
1395 ms
likebox.php
194 ms
acclog.cgi
370 ms
a_sup_mailimage.gif
1248 ms
a_sup_tiyumonimage.gif
1265 ms
kyEKgjk51ZE.css
296 ms
FAHeNGXgPup.js
501 ms
FJmpeSpHpjS.js
634 ms
0wM5s1Khldu.js
586 ms
1bNoFZUdlYZ.js
587 ms
a_sup_telimage.gif
1208 ms
a_sup_faximage.gif
1190 ms
a_sup_faxyousiimage.gif
1200 ms
a_sup_osiharai.gif
1176 ms
a_sup_npcimage.gif
1074 ms
a_sup_sagawaimage.gif
1090 ms
a_sup_rinkimage.gif
1228 ms
banner3.gif
1195 ms
baner_k.gif
1239 ms
bg_menu.gif
1057 ms
I6-MnjEovm5.js
71 ms
pQrUxxo5oQp.js
137 ms
a-supplement.net accessibility score
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
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.
a-supplement.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
a-supplement.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A-supplement.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 A-supplement.net 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.
a-supplement.net
Open Graph description is not detected on the main page of A Supplement. 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: