4.5 sec in total
709 ms
3.6 sec
150 ms
Visit earth-architect.jp now to see the best up-to-date Earth Architect content and also check out these interesting facts you probably never knew about earth-architect.jp
ごく普通の日々の暮らしが豊かで心地良くなるような、そんな住まいを一緒に創っていく、アース・アーキテクツ
Visit earth-architect.jpWe analyzed Earth-architect.jp page load time and found that the first response time was 709 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
earth-architect.jp performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.6 s
60/100
25%
Value3.7 s
85/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value3.7 s
90/100
10%
709 ms
339 ms
22 ms
498 ms
727 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 71% of them (45 requests) were addressed to the original Earth-architect.jp, 10% (6 requests) were made to Google.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Earth-architect.jp.
Page size can be reduced by 62.8 kB (10%)
613.0 kB
550.2 kB
In fact, the total size of Earth-architect.jp main page is 613.0 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. 45% of websites need less resources to load. Images take 486.9 kB which makes up the majority of the site volume.
Potential reduce by 7.9 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 7.9 kB or 65% of the original size.
Potential reduce by 5.2 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. Earth Architect images are well optimized though.
Potential reduce by 22.8 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 22.8 kB or 29% of the original size.
Potential reduce by 26.9 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. Earth-architect.jp needs all CSS files to be minified and compressed as it can save up to 26.9 kB or 79% of the original size.
Number of requests can be reduced by 26 (43%)
61
35
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Earth Architect. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
earth-architect.jp
709 ms
imp.css
339 ms
jsapi
22 ms
jquery.nivo.slider.pack.js
498 ms
jquery.jqtransform.js
727 ms
jquery.fademover.js
359 ms
useragent.js
376 ms
script.js
386 ms
jsapi
17 ms
widgets.js
6 ms
plusone.js
70 ms
reset.css
172 ms
basis.css
365 ms
navigation.css
415 ms
top.css
242 ms
information.css
324 ms
profile.css
341 ms
message.css
439 ms
works.css
489 ms
other.css
511 ms
jquery.min.js
8 ms
13 ms
default+en.css
3 ms
default+en.I.js
5 ms
ga.js
28 ms
bg.gif
173 ms
hdbg.png
185 ms
contact.gif
191 ms
mainPicture01.jpg
1157 ms
mainPicture02.jpg
1352 ms
mainPicture03.jpg
1382 ms
workflow.jpg
343 ms
portfolio.jpg
545 ms
map.gif
377 ms
ftimg.jpg
513 ms
navigation.gif
548 ms
loading.gif
665 ms
__utm.gif
23 ms
banner.jpg
863 ms
news.gif
710 ms
cprbg.gif
814 ms
scrolltop.gif
899 ms
pp.gif
985 ms
sitemap.gif
1045 ms
footerbg.gif
1087 ms
ftline.gif
1155 ms
fthd01.gif
1227 ms
fticon.gif
1275 ms
fthd02.gif
1273 ms
fthd03.gif
1326 ms
fthd04.gif
1413 ms
fthd05.gif
1438 ms
ftcmpn.gif
1462 ms
phone.gif
1495 ms
cb=gapi.loaded_0
13 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
20 ms
like.php
156 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
24 ms
jot
92 ms
qeKvIRsJabD.js
494 ms
LVx-xkvaJ0b.png
557 ms
Gfeeds
613 ms
arrows.png
174 ms
earth-architect.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.
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.
earth-architect.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
earth-architect.jp 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
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Earth-architect.jp 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), while the claimed language is Japanese. Our system also found out that Earth-architect.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.
earth-architect.jp
Open Graph data is detected on the main page of Earth Architect. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: