4.7 sec in total
553 ms
3.5 sec
664 ms
Visit kunisawa.net now to see the best up-to-date Kunisawa content for Japan and also check out these interesting facts you probably never knew about kunisawa.net
車選び、最新車試乗記も満載 国沢光宏の公式サイト
Visit kunisawa.netWe analyzed Kunisawa.net page load time and found that the first response time was 553 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
kunisawa.net performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.6 s
59/100
25%
Value11.5 s
5/100
10%
Value3,480 ms
2/100
30%
Value0.007
100/100
15%
Value20.6 s
2/100
10%
553 ms
911 ms
178 ms
357 ms
512 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 38% of them (20 requests) were addressed to the original Kunisawa.net, 12% (6 requests) were made to Apis.google.com and 10% (5 requests) were made to Static.affiliate.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Xml.affiliate.rakuten.co.jp.
Page size can be reduced by 375.8 kB (43%)
880.1 kB
504.3 kB
In fact, the total size of Kunisawa.net main page is 880.1 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. 50% of websites need less resources to load. Javascripts take 465.9 kB which makes up the majority of the site volume.
Potential reduce by 115.1 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 115.1 kB or 81% of the original size.
Potential reduce by 321 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. Kunisawa images are well optimized though.
Potential reduce by 146.3 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 146.3 kB or 31% of the original size.
Potential reduce by 114.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. Kunisawa.net needs all CSS files to be minified and compressed as it can save up to 114.1 kB or 77% of the original size.
Number of requests can be reduced by 34 (71%)
48
14
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kunisawa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
kunisawa.net
553 ms
kunisawa.net
911 ms
2l5ja.css
178 ms
2l5ja.css
357 ms
2l5ja.css
512 ms
2l5ja.js
696 ms
adsbygoogle.js
121 ms
rakuten_widget.js
1198 ms
image-cdn.js
529 ms
jquery.optimum-lazy-load.min.js
535 ms
utility.js
540 ms
socialButton.js
535 ms
e-202419.js
23 ms
tag.js
112 ms
analytics.js
123 ms
kure-banner2.gif
120 ms
bg-dot.png
183 ms
icon-gnav.png
176 ms
bg-main-image.gif
178 ms
icon-arrow_r.png
188 ms
profile20141.jpg
182 ms
pokish_logo.gif
118 ms
collect
20 ms
js
60 ms
2l5ja.css
177 ms
mw_dynamic_view.html
308 ms
bg-footer-h3.gif
213 ms
icon-arrow02.png
194 ms
icon-arrow03.png
193 ms
bg-pagetop.gif
194 ms
25077.jpg
23 ms
25069.png
184 ms
widgets.js
156 ms
button-only@2x.png
43 ms
bookmark_button.js
43 ms
platform.js
74 ms
all.js
39 ms
all.js
4 ms
122 ms
cb=gapi.loaded_0
32 ms
cb=gapi.loaded_1
73 ms
fastbutton
66 ms
postmessageRelay
48 ms
developers.google.com
516 ms
3604799710-postmessagerelay.js
24 ms
rpc:shindig_random.js
17 ms
pc_pcview_all.css
36 ms
front_merged.js
35 ms
cb=gapi.loaded_0
7 ms
getMWConf.php
172 ms
loading.gif
45 ms
buttons.gif
43 ms
kunisawa.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
Form elements do not have associated labels
kunisawa.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
kunisawa.net SEO score
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 Kunisawa.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 Kunisawa.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.
kunisawa.net
Open Graph data is detected on the main page of Kunisawa. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: