5.8 sec in total
1.1 sec
4 sec
731 ms
Welcome to kondokyosuke.net homepage info - get ready to check Kondokyosuke best content right away, or after learning these important things about kondokyosuke.net
カヌースラローム元日本代表選手によるカヤック講習会のご案内ページです
Visit kondokyosuke.netWe analyzed Kondokyosuke.net page load time and found that the first response time was 1.1 sec 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.
kondokyosuke.net performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value13.1 s
0/100
25%
Value11.1 s
6/100
10%
Value280 ms
81/100
30%
Value0.465
19/100
15%
Value7.0 s
53/100
10%
1111 ms
1216 ms
868 ms
376 ms
621 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 79% of them (52 requests) were addressed to the original Kondokyosuke.net, 9% (6 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Dflzqrzibliy5.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Kondokyosuke.net.
Page size can be reduced by 471.6 kB (27%)
1.8 MB
1.3 MB
In fact, the total size of Kondokyosuke.net main page is 1.8 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 46.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. This page needs HTML code to be minified as it can gain 14.1 kB, which is 24% 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 46.5 kB or 79% of the original size.
Potential reduce by 50.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. Kondokyosuke images are well optimized though.
Potential reduce by 210.9 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 210.9 kB or 72% of the original size.
Potential reduce by 163.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. Kondokyosuke.net needs all CSS files to be minified and compressed as it can save up to 163.9 kB or 83% of the original size.
Number of requests can be reduced by 28 (49%)
57
29
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kondokyosuke. 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 11 to 1 for CSS and as a result speed up the page load time.
kondokyosuke.net
1111 ms
bootstrap.min.css
1216 ms
main.css
868 ms
supersized.css
376 ms
supersized.shutter.css
621 ms
jquery.fancybox.css
624 ms
fonts.css
930 ms
shortcodes.css
751 ms
bootstrap-responsive.min.css
989 ms
responsive.css
829 ms
css
40 ms
modernizr.js
949 ms
form.calculations.css
42 ms
jquery.min.js
27 ms
bootstrap.min.js
744 ms
supersized.3.2.7.min.js
496 ms
waypoints.js
568 ms
waypoints-sticky.js
595 ms
jquery.isotope.js
637 ms
jquery.fancybox.pack.js
742 ms
jquery.fancybox-media.js
778 ms
jquery.tweet.js
786 ms
plugins.js
826 ms
main.js
845 ms
jquery.zrssfeed.js
888 ms
ga.js
47 ms
menu-mobile.png
232 ms
logo.png
240 ms
concept-01.jpg
452 ms
concept-02.jpg
858 ms
concept-03.jpg
659 ms
concept-04.jpg
497 ms
about-01.jpg
800 ms
about-02.jpg
804 ms
about-03.jpg
829 ms
about-04.jpg
845 ms
whyfeather-01.jpg
833 ms
whyfeather-02.jpg
1392 ms
whyfeather-05.jpg
1169 ms
whyfeather-03.jpg
1020 ms
whyfeather-06.jpg
1015 ms
whyfeather-07.jpg
1028 ms
whyfeather-04.jpg
1048 ms
whyfeather-08.jpg
1364 ms
profile-00.jpg
1212 ms
profile-01.jpg
1203 ms
profile-02.jpg
1446 ms
profile-03.jpg
1546 ms
profile-04.jpg
1378 ms
Icons.woff
1375 ms
anMUvcNT0H1YN4FII8wprwwHpU-8OKeXrGSDRtNNsHg.ttf
34 ms
anMUvcNT0H1YN4FII8wpr8emR1SRkPORqDWOmtmtNc0.ttf
36 ms
7XUFZ5tgS-tD6QamInJTcbFJZbTbly0V4A-kMlrADXE.ttf
38 ms
anMUvcNT0H1YN4FII8wprxgm6d0i0FjSmyQ0ElZwmAs.ttf
37 ms
anMUvcNT0H1YN4FII8wpr4Lwop_k4MQ3dpbbWEft-78.ttf
36 ms
anMUvcNT0H1YN4FII8wpr1zXIWw14BneefDORbJjy9A.ttf
37 ms
form.calculations.js
33 ms
__utm.gif
29 ms
interactive123cf.js
37 ms
load
441 ms
progress.gif
1313 ms
image04.jpg
1674 ms
image01.jpg
1753 ms
image02.jpg
1923 ms
placeholder.js
1378 ms
placeholder.js
177 ms
kondokyosuke.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
Image elements do not have [alt] attributes
Links do not have a discernible name
kondokyosuke.net 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
kondokyosuke.net 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kondokyosuke.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 Kondokyosuke.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.
kondokyosuke.net
Open Graph description is not detected on the main page of Kondokyosuke. 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: