3.3 sec in total
806 ms
2.4 sec
138 ms
Click here to check amazing Kenyo content for Japan. Otherwise, check out these important facts you probably never knew about kenyo.net
酵素栄養学と代替医療で誰でもできるセルフケアのすすめ
Visit kenyo.netWe analyzed Kenyo.net page load time and found that the first response time was 806 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
kenyo.net performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value2.0 s
97/100
25%
Value2.6 s
97/100
10%
Value20 ms
100/100
30%
Value0.003
100/100
15%
Value2.2 s
99/100
10%
806 ms
6 ms
1076 ms
10 ms
321 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 94% of them (50 requests) were addressed to the original Kenyo.net, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Yahoo.co.jp. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Kenyo.net.
Page size can be reduced by 27.8 kB (47%)
59.4 kB
31.6 kB
In fact, the total size of Kenyo.net main page is 59.4 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. 15% of websites need less resources to load. HTML takes 33.5 kB 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 10.5 kB, which is 31% 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 83% of the original size.
Potential reduce by 0 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. Kenyo images are well optimized though.
Potential reduce by 34 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 28 (55%)
51
23
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kenyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
kenyo.net
806 ms
ga.js
6 ms
recip_sm.gif
1076 ms
__utm.gif
10 ms
g3_r1_c1.gif
321 ms
g3_r1_c2.gif
447 ms
g3_r1_c3.gif
480 ms
g3_r1_c4.gif
395 ms
g3_r2_c1.gif
412 ms
g3_r2_c2.gif
485 ms
g3_r2_c4.gif
497 ms
g3_r3_c1.gif
556 ms
g3_r3_c2.gif
573 ms
g3_r3_c3.gif
597 ms
g3_r3_c4.gif
640 ms
g3_r4_c1.gif
655 ms
g3_r5_c1.gif
672 ms
spacer.gif
718 ms
p.gif
735 ms
green_line.gif
746 ms
collect1.gif
804 ms
payment.gif
838 ms
g3_r6_c1.gif
853 ms
dayx.cgi
922 ms
report.cgi
906 ms
lime.cgi
901 ms
top_space.gif
962 ms
heiwa_s.jpg
861 ms
vinegar_all_s.jpg
883 ms
tegaru.gif
903 ms
cap_s.jpg
920 ms
jikianime1_s.gif
936 ms
nowprinting.gif
974 ms
i-320.gif
1029 ms
spacer.gif
1058 ms
na_r1_c1.gif
1052 ms
na_r2_c1.gif
1081 ms
na_r2_c2.gif
1096 ms
na_r2_c3.gif
1132 ms
na_r2_c4.gif
1199 ms
na_r2_c5.gif
1036 ms
na_r2_c6.gif
993 ms
na_r2_c7.gif
984 ms
na_r2_c8.gif
966 ms
na_r2_c9.gif
966 ms
na_r3_c2.gif
1043 ms
na_r3_c4.gif
1021 ms
na_r3_c6.gif
1010 ms
na_r3_c8.gif
984 ms
na_r2_c2_f2.gif
178 ms
na_r2_c4_f2.gif
164 ms
na_r2_c6_f2.gif
164 ms
na_r2_c8_f2.gif
152 ms
kenyo.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
kenyo.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
kenyo.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
JA
N/A
SHIFT_JIS;
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kenyo.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Kenyo.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.
kenyo.net
Open Graph description is not detected on the main page of Kenyo. 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: