10 sec in total
2 sec
7.4 sec
520 ms
Welcome to yamaroku-moku.jp homepage info - get ready to check Yamaroku Moku best content for Japan right away, or after learning these important things about yamaroku-moku.jp
新潟県(長岡・三条・見附)で注文住宅・企画住宅・セレクト住宅をお考えなら山六木材へ。こだわった自然素材を使い、高性能かつコストパフォーマンスに長けた家をご提供している創業50年の工務店です。家から街を作り、地元新潟を「帰りたい」「応援したい」街づくりに貢献していきます。
Visit yamaroku-moku.jpWe analyzed Yamaroku-moku.jp page load time and found that the first response time was 2 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yamaroku-moku.jp performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value9.7 s
0/100
25%
Value10.4 s
8/100
10%
Value290 ms
80/100
30%
Value0.947
3/100
15%
Value8.3 s
40/100
10%
2039 ms
174 ms
324 ms
502 ms
341 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 81% of them (94 requests) were addressed to the original Yamaroku-moku.jp, 9% (10 requests) were made to Static.xx.fbcdn.net and 5% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Yamaroku-moku.jp.
Page size can be reduced by 560.0 kB (12%)
4.7 MB
4.1 MB
In fact, the total size of Yamaroku-moku.jp main page is 4.7 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. 50% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 43.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. 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 43.6 kB or 76% of the original size.
Potential reduce by 236.5 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. Yamaroku Moku images are well optimized though.
Potential reduce by 250.7 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 250.7 kB or 70% of the original size.
Potential reduce by 29.3 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. Yamaroku-moku.jp needs all CSS files to be minified and compressed as it can save up to 29.3 kB or 78% of the original size.
Number of requests can be reduced by 30 (26%)
115
85
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yamaroku Moku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
yamaroku-moku.jp
2039 ms
style.css
174 ms
import.css
324 ms
jquery.js
502 ms
common.js
341 ms
jquery-1.7.2.min.js
526 ms
pagenavi-css.css
344 ms
slimbox2.css
357 ms
jquery.js
650 ms
jquery-migrate.min.js
512 ms
slimbox2.js
521 ms
slimbox2_autoload.js
536 ms
top.css
668 ms
flexslider.css
679 ms
jquery.flexslider.js
694 ms
wp-embed.min.js
696 ms
reset.css
391 ms
structure.css
483 ms
header.css
512 ms
footer.css
522 ms
globalnavi.css
555 ms
navigation.css
548 ms
textdecorations.css
581 ms
wp-emoji-release.min.js
175 ms
banner_logo_195_60.gif
1121 ms
header_description.png
229 ms
header_logo.png
230 ms
h_nav01.png
231 ms
h_nav02.png
232 ms
h_nav03.png
230 ms
g_nav.png
492 ms
kv_link.png
314 ms
lineup_tit.png
497 ms
lineup_h3_01.png
358 ms
lineup_01.png
833 ms
lineup_04.png
886 ms
lineup_h3_02.png
473 ms
lineup_02.png
875 ms
lineup_03.png
941 ms
lineup_05.png
1001 ms
lineup_06.png
994 ms
h2_01.png
1000 ms
btn_more01.png
1046 ms
news_info.png
1091 ms
news_event.png
1098 ms
news_juku.png
1161 ms
h2_02.png
1164 ms
btn_more02.png
1168 ms
IMG_6205-175x175.jpg
1219 ms
IMG_6090-300x200-175x175.jpg
1270 ms
IMG_5706-300x200-175x175.jpg
1255 ms
IMG_1672-300x225-175x175.jpg
1326 ms
h2_03.png
1334 ms
btn_more03.png
1339 ms
03-640x509-175x175.jpg
1390 ms
h2_04.png
1412 ms
btn_more04.png
1448 ms
20141029kas1-175x250.jpg
1494 ms
20141107kas1-175x250.jpg
1664 ms
20141113nag1-175x250.jpg
1494 ms
sdk.js
157 ms
blog_tit01.png
1342 ms
blog_tit03.png
1355 ms
blog_tit04.png
1405 ms
blog_tit02.png
1439 ms
bnr_top.png
1795 ms
top_img.png
2190 ms
69 ms
xd_arbiter.php
146 ms
xd_arbiter.php
249 ms
right_bnr01.png
1427 ms
right_bnr02.png
1455 ms
right_bnr04.png
1692 ms
right_bnr11.png
1348 ms
right_bnr12.png
1402 ms
right_bnr05.png
1339 ms
right_bnr06.png
1130 ms
right_bnr07.png
1170 ms
right_bnr08.png
1231 ms
right_bnr09.png
1202 ms
right_bnr10.png
1213 ms
side_twitter.png
1333 ms
btn_pagetop.png
1303 ms
footer_logo.png
1253 ms
footer_tel.png
1270 ms
footer_btn.png
1210 ms
kv05.png
2004 ms
kv01.png
2343 ms
kv02.png
2200 ms
kv04.png
2133 ms
kv03.png
2193 ms
lineup_line.png
1316 ms
footer_bg.png
1483 ms
footer_point01.png
1648 ms
footer_point02.png
1769 ms
footer_point03.png
1920 ms
footer_point04.png
1886 ms
footer_point05.png
2028 ms
flexslider-icon.woff
173 ms
page.php
88 ms
cv4ERr8UMUY.css
160 ms
1kPfZUdGrka.js
270 ms
AeiIQ53iqZ6.js
349 ms
Qd7TTBR3F_S.js
321 ms
12046824_886651184736500_6936905116857810571_n.jpg
161 ms
10481388_712996912101929_9219112969062069210_n.jpg
196 ms
1977423_328722800650518_3467849466411865905_n.jpg
235 ms
12107799_845071292276589_4209321406542694640_n.jpg
272 ms
10354686_10150004552801856_220367501106153455_n.jpg
273 ms
10553607_965784066765787_2486569751034657409_n.jpg
273 ms
wL6VQj7Ab77.png
44 ms
s7jcwEQH7Sx.png
44 ms
R9GKCzjAnbk.js
40 ms
AWWjhOengNF.js
41 ms
YnSasnyq68i.js
44 ms
kQf_jlUv-kX.js
76 ms
yamaroku-moku.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Links do not have a discernible name
yamaroku-moku.jp 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
yamaroku-moku.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Yamaroku-moku.jp 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 Yamaroku-moku.jp 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.
yamaroku-moku.jp
Open Graph description is not detected on the main page of Yamaroku Moku. 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: