9.9 sec in total
1.4 sec
8.2 sec
374 ms
Click here to check amazing Yamajikaze content for Japan. Otherwise, check out these important facts you probably never knew about yamajikaze.net
アウトドアに関する総合情報。山小屋、温泉、キャンプ、高山植物、アウトドア用品などのジャンル別リンク集が充実
Visit yamajikaze.netWe analyzed Yamajikaze.net page load time and found that the first response time was 1.4 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yamajikaze.net performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value2.5 s
89/100
25%
Value2.6 s
97/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.0 s
99/100
10%
1358 ms
5120 ms
355 ms
6 ms
3434 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 75% of them (59 requests) were addressed to the original Yamajikaze.net, 8% (6 requests) were made to Pagead2.googlesyndication.com and 8% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Yamajikaze.net.
Page size can be reduced by 68.8 kB (18%)
386.2 kB
317.4 kB
In fact, the total size of Yamajikaze.net main page is 386.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. 50% of websites need less resources to load. Images take 302.8 kB which makes up the majority of the site volume.
Potential reduce by 42.3 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 42.3 kB or 75% of the original size.
Potential reduce by 18.8 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. Yamajikaze images are well optimized though.
Potential reduce by 6.6 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 6.6 kB or 26% of the original size.
Potential reduce by 1.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. Yamajikaze.net needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 70% of the original size.
Number of requests can be reduced by 23 (30%)
76
53
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yamajikaze. 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 as a result speed up the page load time.
yamajikaze.net
1358 ms
www.yamajikaze.net
5120 ms
main.css
355 ms
show_ads.js
6 ms
bg_00.png
3434 ms
blv40.png
3435 ms
yamajikaze_950.png
3442 ms
dream.cgi
3435 ms
sq07.png
3435 ms
logo_twitter.png
3436 ms
lakehappo.jpg
3440 ms
hanayama.png
3435 ms
circle_blue_2.png
3436 ms
hot.png
3448 ms
mail.png
3437 ms
yamagoya_01.png
3437 ms
line01.png
3436 ms
weston.png
3437 ms
new.png
3438 ms
fbtozan.png
3438 ms
upani.png
3440 ms
bnb_350news.png
3442 ms
circle_blue_3.png
3440 ms
bnb_120news.png
3441 ms
bnb_120tozan.png
3441 ms
bnb_120mtinfo.png
3442 ms
bnb_120akaishi.png
3443 ms
bnb_120hiroba.png
3442 ms
basccamp_02.png
3443 ms
circle_pnk.png
3443 ms
yamajikaze_950d.png
3431 ms
gd_0.png
3431 ms
ca-pub-3184352556909023.js
62 ms
zrt_lookup.html
52 ms
show_ads_impl.js
56 ms
m08.html
532 ms
Logo_25wht.gif
30 ms
yama_01.png
177 ms
ico9.png
192 ms
ico10.png
183 ms
ico11.png
175 ms
ico2.png
191 ms
ico12.png
364 ms
ico3.png
364 ms
ico13.png
366 ms
ico8.png
374 ms
ico7.png
381 ms
bng_120susume.png
682 ms
bnb_120sobi.png
684 ms
bng_120shikoku.png
713 ms
bng_480ring.png
925 ms
toyokawa.gif
1673 ms
bnb_120nyukai.png
704 ms
bnb_480banner.png
1188 ms
ringbn1.png
1194 ms
lumiere_title1.png
877 ms
lumiere_title.png
888 ms
lumiere.png
1054 ms
shirakawa.jpg
1237 ms
amorigawa_01.jpg
1110 ms
bnb_480qsp.png
1403 ms
plt_ptop.png
1295 ms
gd_2.png
1347 ms
ads
253 ms
osd.js
19 ms
ads
184 ms
ads
170 ms
ads
235 ms
topic.css
1186 ms
abg.js
17 ms
m_js_controller.js
3 ms
favicon
49 ms
s
25 ms
googlelogo_color_112x36dp.png
42 ms
nessie_icon_tiamat_white.png
27 ms
x_button_blue2.png
36 ms
favicon
40 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
7 ms
activeview
14 ms
yamajikaze.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
Form elements do not have associated labels
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.
yamajikaze.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
yamajikaze.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
Tap targets are not sized appropriately
N/A
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yamajikaze.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Yamajikaze.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.
yamajikaze.net
Open Graph description is not detected on the main page of Yamajikaze. 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: