11.5 sec in total
1.6 sec
9.4 sec
523 ms
Welcome to nattoku.jp homepage info - get ready to check Nattoku best content for Japan right away, or after learning these important things about nattoku.jp
静岡県の富士市・静岡市・浜松市・三島市で注文住宅をお考えの方はnattoku住宅にお任せください。静岡・埼玉で累計2350棟を超える実績でお客さまの理想の住まいを実現いたします。
Visit nattoku.jpWe analyzed Nattoku.jp page load time and found that the first response time was 1.6 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nattoku.jp performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value3.8 s
55/100
25%
Value6.0 s
46/100
10%
Value300 ms
79/100
30%
Value0.435
21/100
15%
Value5.1 s
75/100
10%
1624 ms
326 ms
813 ms
355 ms
368 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 88% of them (122 requests) were addressed to the original Nattoku.jp, 1% (2 requests) were made to Google-analytics.com and 1% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Nattoku.jp.
Page size can be reduced by 807.3 kB (19%)
4.2 MB
3.4 MB
In fact, the total size of Nattoku.jp main page is 4.2 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 3.4 MB which makes up the majority of the site volume.
Potential reduce by 39.2 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 39.2 kB or 74% of the original size.
Potential reduce by 152.1 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. Nattoku images are well optimized though.
Potential reduce by 327.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 327.6 kB or 68% of the original size.
Potential reduce by 288.5 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. Nattoku.jp needs all CSS files to be minified and compressed as it can save up to 288.5 kB or 83% of the original size.
Number of requests can be reduced by 45 (34%)
133
88
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nattoku. 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 13 to 1 for CSS and as a result speed up the page load time.
www.nattoku.jp
1624 ms
style.css
326 ms
top.css
813 ms
widget.css
355 ms
shutter-reloaded.css
368 ms
lightbox.min.css
492 ms
jquery.js
1274 ms
jquery-migrate.min.js
739 ms
shutter-reloaded.js
641 ms
jquery.cycle.all.min.js
849 ms
ngg.slideshow.min.js
803 ms
jquery.timers-1.1.2.js
768 ms
jquery.easing.1.3.js
813 ms
jquery.galleryview-2.0.js
979 ms
galleryview.css
856 ms
jquery.min.js
32 ms
flexslider.css
952 ms
jquery.flexslider-min.js
1135 ms
style.css
1353 ms
ga.js
30 ms
include.css
854 ms
jquery.touchwipe.min.js
814 ms
jquery.lightbox.min.js
818 ms
jquery.ui.core.min.js
870 ms
s_retargeting.js
592 ms
nggallery.css
1127 ms
base.css
291 ms
common.css
279 ms
sws_paging.css
280 ms
body_bg.jpg
175 ms
__utm.gif
12 ms
sdk.js
160 ms
collect
101 ms
logo.gif
177 ms
head_tell.gif
201 ms
link_bg.gif
160 ms
gn_voice.jpg
161 ms
gn_works.jpg
275 ms
gn_concept.jpg
330 ms
gn_information.jpg
330 ms
gn_showroom.jpg
412 ms
gn_contact.jpg
611 ms
0687d47b95292a63e5944df8a1c219b4.jpg
921 ms
ce4932871152d81978cc22a369e99c6a.jpg
745 ms
K.jpg
1125 ms
a4dd946b961fb3f44987c3a5393c4645.jpg
2124 ms
d4de75ee4a2307f2f8f09456eb24a8bd.jpg
1292 ms
035e7bc6c207bdc1b24eb5ec172688cb.jpg
1987 ms
32beb8b08ec30233dee6b85df7f37117.jpg
2180 ms
top_bnr_fuji.jpg
1364 ms
top_bnr_shizuoka.jpg
1349 ms
top_bnr_hamamatsu.jpg
1515 ms
top_bnr_mishima.jpg
1800 ms
mds_gallery.png
1819 ms
thumbs_n_tn_j9a2749-edit.jpg
1691 ms
thumbs_n_tn_j9a2153-edit.jpg
1867 ms
thumbs_n_tn_j9a1500.jpg
1959 ms
thumbs_n_tn_j9a9458-edit.jpg
1998 ms
thumbs_n_tn0j9a0894-edit.jpg
2043 ms
thumbs_n_tn0j9a7778-edit.jpg
2119 ms
thumbs_n_151201_004.jpg
2182 ms
thumbs_n_tn_j9a4820-edit.jpg
2241 ms
thumbs_img_5998.jpg
2220 ms
mds_voice.png
2289 ms
DSC_0125.jpg
3556 ms
DSC_0.jpg
2497 ms
12244802_781565355306397_4778355001640998015_o.jpg
2773 ms
DSC_0072.jpg
4194 ms
XDqWQRp_6hY
126 ms
flexslider-icon.woff
2341 ms
www-embed-player-vflRGs1ko.css
66 ms
www-embed-player.js
89 ms
25 ms
xd_arbiter.php
132 ms
xd_arbiter.php
264 ms
top_voice_contract.gif
2334 ms
top_voice_story.gif
2464 ms
top_voice_letter.gif
2450 ms
icon_letter.gif
2453 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
34 ms
ad_status.js
85 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
100 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
111 ms
mds_about.png
2530 ms
top_link_bg.jpg
2456 ms
arrow_circle.png
2498 ms
about_ethos.jpg
2564 ms
about_kubo.jpg
2344 ms
mds_concept.png
2241 ms
top_concept_bg.jpg
2066 ms
design.jpg
1990 ms
material.jpg
1882 ms
taishin.jpg
1795 ms
price.jpg
1802 ms
human.jpg
1759 ms
mds_link.png
1616 ms
sola.jpg
1546 ms
reform.jpg
1558 ms
ark.jpg
1573 ms
nsh.jpg
1508 ms
vivace.jpg
1547 ms
porta.jpg
1575 ms
bnr_group.jpg
1556 ms
side_tv.jpg
1519 ms
atsmile.jpg
1602 ms
resavation_PC.jpg
1705 ms
side_mds_tour.png
1588 ms
more.gif
1539 ms
side_mds_event.png
1558 ms
sws_new.gif
1622 ms
side_mds_news.png
1477 ms
side_mds_kubosblog.png
1479 ms
kubosblog.jpg
1472 ms
side_mds_staffblog.png
1425 ms
66834667eb1df42df8a3cf44167d84ae-40x40.jpg
1472 ms
Kasai_avatar_1453098543-40x40.jpg
1417 ms
632cb5dfad849da1f44dd282657b3681-40x40.jpg
1390 ms
arioka_avatar_1407819479-40x40.jpg
1507 ms
ohsugi_avatar_1453098517-40x40.jpg
1408 ms
A.Nakano_avatar_1453098633-40x40.jpg
1422 ms
otaki_avatar_1454321364-40x40.jpg
1327 ms
side_btn_fujistaff.gif
1394 ms
side_btn_shizuokastaff.gif
1390 ms
side_btn_hamamatsustaff.gif
1385 ms
side_btn_mishimastaff.gif
1293 ms
side_btn_backnumber.gif
1325 ms
side_mds_mm.png
1285 ms
side_bnr_sasshi.gif
1396 ms
bnr_book.jpg
1257 ms
pg_top.png
1248 ms
t_showroom.gif
1218 ms
SR_F_nattoku.jpg
1392 ms
SR_S_nattoku.jpg
1215 ms
SR_hamamatsu.jpg
1228 ms
SR_mishima.jpg
1205 ms
logo_foot.png
1168 ms
arrow_left.gif
1190 ms
arrow_right.gif
1238 ms
nattoku.jp 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
Links do not have a discernible name
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.
nattoku.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
Page has valid source maps
nattoku.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 Nattoku.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 Nattoku.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.
nattoku.jp
Open Graph description is not detected on the main page of Nattoku. 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: