19.4 sec in total
520 ms
18 sec
905 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 520 ms and then it took 18.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
nattoku.jp performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value9.5 s
0/100
25%
Value10.7 s
7/100
10%
Value660 ms
45/100
30%
Value0.005
100/100
15%
Value8.8 s
35/100
10%
520 ms
2421 ms
510 ms
705 ms
533 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 77% of them (126 requests) were addressed to the original Nattoku.jp, 3% (5 requests) were made to Panda.kasika.io and 3% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (11 sec) belongs to the original domain Nattoku.jp.
Page size can be reduced by 260.6 kB (5%)
5.6 MB
5.3 MB
In fact, the total size of Nattoku.jp main page is 5.6 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. 70% of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 140.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 46.7 kB, which is 29% 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 140.5 kB or 86% of the original size.
Potential reduce by 42.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. Nattoku images are well optimized though.
Potential reduce by 68.5 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 68.5 kB or 27% of the original size.
Potential reduce by 9.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. Nattoku.jp needs all CSS files to be minified and compressed as it can save up to 9.1 kB or 16% of the original size.
Number of requests can be reduced by 58 (37%)
156
98
The browser has sent 156 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 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
nattoku.jp
520 ms
www.nattoku.jp
2421 ms
ipad.min.js
510 ms
style.min.css
705 ms
custom.css
533 ms
trans.js
25 ms
swiper.min.css
536 ms
top.min.css
1093 ms
jquery.bxslider.css
678 ms
top-group-circle.css
731 ms
gtm.js
61 ms
js
86 ms
js
87 ms
analytics.js
28 ms
ytag.js
929 ms
collect
39 ms
cam3.js
716 ms
logo_red.svg
407 ms
sp-header-icon.svg
398 ms
ico_telBtn.svg
404 ms
f-sns-ttl_sp.svg
396 ms
f-sns-ttl.svg
523 ms
icon_face.svg
528 ms
icon_youtube.svg
528 ms
icon_insta.svg
1916 ms
icon_line.svg
543 ms
open-tel-02.svg
528 ms
logo.svg
697 ms
openmenu-tel.svg
715 ms
group-close.svg
706 ms
group-circle.svg
713 ms
performance_ico01.svg
739 ms
performance_ico02.svg
876 ms
performance_ico03.svg
899 ms
performance_ico04.svg
896 ms
performance_ico05.svg
915 ms
sra-icon.svg
941 ms
event-ttl.svg
1046 ms
88d958284caf9f797c732e8576cea2b7.jpg
2012 ms
eb0212e993cf2026c5afe0f9943801e3.jpg
2406 ms
dc03b3b7fc33637c6dbf7e4d67877137.jpg
2540 ms
shizsam.jpg
3870 ms
99cd10ecba540d14be1e6b0d9994750a.jpg
1933 ms
2c0a851485d95327235d031d941ee581-1.jpg
2798 ms
544e166623799c39dc8abe18a7cec8a1-1.jpg
2816 ms
733a485808c2d27a124db0fa7cd14f85.jpg
2916 ms
gaikann-1.jpg
2977 ms
55b8c8a2a78619973d57e0c54f91c449-1.jpg
3973 ms
30cca7f572fb9c3c5c565af8ea7153d4.jpg
3509 ms
fbevents.js
403 ms
5mDfgNbMN4Kv5pf8ksus.js
803 ms
906 ms
config
1241 ms
544e166623799c39dc8abe18a7cec8a1.jpg
3868 ms
collect
527 ms
deac1d7e64a3e597a468314cbee41444-1.jpg
3845 ms
common.min.js
2799 ms
swiper.min.js
2994 ms
top.min.js
3174 ms
jquery.bxslider.js
3287 ms
top-group-circle.js
3387 ms
event-btn.svg
3470 ms
land-ttl.svg
3449 ms
sp-land-ttl.svg
3449 ms
land-btn.svg
3509 ms
sp-land-btn.svg
3501 ms
ga-audiences
74 ms
movie-ttl.svg
3489 ms
works-ttl.svg
3453 ms
works-btn.svg
3450 ms
create_new_id
637 ms
sp-works-btn.svg
3438 ms
concept-ttl.svg
3487 ms
sp-img_point01.jpg
3640 ms
num_point01.svg
3338 ms
sp-img_point02.jpg
3472 ms
num_point02.svg
3427 ms
sp-img_point03.jpg
3595 ms
num_point03.svg
3427 ms
sp-img_point04.jpg
3531 ms
main.js
3 ms
num_point04.svg
2573 ms
sp-img_point06.jpg
2651 ms
num_point05.svg
2528 ms
sp-img_point07.jpg
2153 ms
num_point06.svg
2137 ms
sp-img_point08.jpg
2078 ms
num_point07.svg
1894 ms
sp-img_point09.jpg
1995 ms
num_point08.svg
1780 ms
contact-ttl.svg
1557 ms
sp-contact-ttl.svg
1456 ms
contact-tel.svg
1372 ms
sp-contact-tel.svg
1363 ms
staff-blog-ttl.svg
1252 ms
style.css
62 ms
194 ms
825 ms
sp-staff-blog-ttl.svg
1177 ms
staff-blog-btn.svg
1188 ms
open-bg.png
10985 ms
list02-icon01.svg
1207 ms
list02-icon02.svg
1240 ms
lt.js
278 ms
f-sns-icon.svg
1148 ms
sp-staff-blog-btn.svg
1235 ms
news-ttl.svg
1261 ms
195 ms
news-btn.svg
1225 ms
sp-news-btn.svg
1266 ms
iecomi-ttl.svg
1265 ms
sp-iecomi-ttl.svg
1232 ms
iecomi-btn.svg
1262 ms
sp-iecomi-btn.svg
1271 ms
err.gif
696 ms
386 ms
showroom-modelhouse-ttl.svg
1278 ms
sp-showroom-modelhouse-ttl.svg
1265 ms
model-btn.svg
1231 ms
sp-model-btn.svg
1228 ms
img_link08.svg
1227 ms
img_link01.svg
1279 ms
img_link02.svg
1158 ms
img_link04.svg
1228 ms
img_link07.svg
1235 ms
img_link_housedo.svg
1212 ms
piwik.js
1154 ms
img_link_arcstyle.svg
1260 ms
img_link_arcdesignworks.svg
1258 ms
a.php
454 ms
img_link_architects.svg
1236 ms
boxft_area_ttl01.png
1229 ms
page_top.svg
1197 ms
banner_meeting.svg
1254 ms
banner_meeting2.svg
1164 ms
event-category-arrow.svg
1215 ms
land-tab-icon1.svg
1242 ms
land-tab-icon2.svg
1225 ms
movie-new-icon.svg
1260 ms
concept-bx-icon.svg
1256 ms
contact-bg.png
1410 ms
news-icon-hov.svg
1237 ms
news-icon.svg
1233 ms
iecomi-bg-icon.png
1258 ms
model-in-bg.png
1262 ms
model-icon1.svg
1258 ms
model-icon2.svg
1261 ms
gototop.svg
1301 ms
piwik.php
246 ms
get_cid_with_sv.php
194 ms
webfont.js
27 ms
hqdefault.jpg
398 ms
hqdefault.jpg
224 ms
hqdefault.jpg
330 ms
03767639roomlayoutL-1.png
224 ms
367491cf04e6174042082bde17d15acf-1.png
410 ms
63bf5a19ca421aff6896936aef361d65.jpg
586 ms
css
53 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35TS1g.ttf
53 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35TS1g.ttf
159 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35TS1g.ttf
161 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf
106 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
120 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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 data is detected on the main page of Nattoku. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: