11.9 sec in total
499 ms
10.5 sec
880 ms
Visit e-earth.co.jp now to see the best up-to-date E Earth content and also check out these interesting facts you probably never knew about e-earth.co.jp
横浜市 不動産 横浜エリアの不動産仲介、不動産売買はセンチュリー21アース住販
Visit e-earth.co.jpWe analyzed E-earth.co.jp page load time and found that the first response time was 499 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
e-earth.co.jp performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value15.0 s
0/100
25%
Value15.4 s
1/100
10%
Value210 ms
89/100
30%
Value0.447
20/100
15%
Value12.6 s
14/100
10%
499 ms
6905 ms
836 ms
687 ms
66 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 77% of them (116 requests) were addressed to the original E-earth.co.jp, 16% (24 requests) were made to Sys.arcs.jp and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain E-earth.co.jp.
Page size can be reduced by 367.6 kB (17%)
2.2 MB
1.8 MB
In fact, the total size of E-earth.co.jp main page is 2.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. 35% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 79.8 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 79.8 kB or 82% of the original size.
Potential reduce by 109.6 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. E Earth images are well optimized though.
Potential reduce by 150.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 150.7 kB or 64% of the original size.
Potential reduce by 27.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. E-earth.co.jp needs all CSS files to be minified and compressed as it can save up to 27.5 kB or 84% of the original size.
Number of requests can be reduced by 28 (19%)
148
120
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Earth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
e-earth.co.jp
499 ms
www.e-earth.co.jp
6905 ms
base.css
836 ms
top.css
687 ms
jquery.min.js
66 ms
ajax_search.js
355 ms
searchindex.js
561 ms
rollover.js
380 ms
common.js
532 ms
common.css
179 ms
slide.html
182 ms
IMG_FILE_TOP1.jpg
895 ms
07901_0790100782.jpg
905 ms
IMG_FILE_TOP1.jpg
919 ms
07901_0790100780.jpg
917 ms
IMG_FILE_TOP1.jpg
938 ms
07901_0790100788.jpg
988 ms
page-bg.png
174 ms
header-bg.jpg
576 ms
header-tel.png
382 ms
logo.png
172 ms
header-mail.png
361 ms
navi-bg.png
355 ms
navi-bt1.png
518 ms
navi-bt2.png
528 ms
navi-bt3.png
719 ms
navi-bt4.png
775 ms
navi-bt5.png
864 ms
navi-bt6.png
699 ms
title1.png
1206 ms
search-navi1_on.png
867 ms
search-navi2.png
896 ms
search-navi3.png
978 ms
search-navi4.png
1049 ms
search-step1.png
1049 ms
search-type1_on.png
1102 ms
search-type2.png
1233 ms
search-type3.png
1245 ms
search-type4.png
1242 ms
search-type5.png
1285 ms
search-step2.png
1421 ms
search-member.png
1463 ms
search_arrow.png
1447 ms
freeword-title.png
1459 ms
freeword-bt.png
1506 ms
bklist-bg.jpg
1631 ms
ranking1.png
1644 ms
ranking2.png
1659 ms
ranking3.png
1678 ms
00078.png
1721 ms
00013.png
1790 ms
accordion.css
1647 ms
jquery-1.7.2.min.js
2465 ms
jquery.msAccordion.js
1704 ms
00001.png
1559 ms
02005.png
1633 ms
00044.png
1657 ms
IMG_FILE_TOP1.jpg
994 ms
IMG_FILE_TOP1.jpg
1008 ms
IMG_FILE_TOP1.jpg
1006 ms
07901_0790100775.jpg
1241 ms
07901_0790100778.jpg
1066 ms
IMG_FILE_TOP1.jpg
1065 ms
00048.png
1580 ms
00037.png
1579 ms
00002.png
1641 ms
07901_0790100784.jpg
1581 ms
IMG_FILE_TOP1.jpg
1421 ms
IMG_FILE_TOP1.jpg
1384 ms
IMG_FILE_TOP1.jpg
1432 ms
IMG_FILE_TOP1.jpg
1441 ms
IMG_FILE_TOP1.jpg
1586 ms
07901_0790100786.jpg
1902 ms
IMG_FILE_TOP1.jpg
1945 ms
00029.png
1587 ms
staff-demo.jpg
1577 ms
00077.png
1513 ms
00010.png
1528 ms
00027.png
1611 ms
noimage.jpg
2203 ms
00031.png
1508 ms
00059.png
1508 ms
00065.png
1631 ms
00098.png
1571 ms
00035.png
1533 ms
00006.png
1591 ms
toplist.jpg
3297 ms
topics-arrow.png
1234 ms
new.gif
1272 ms
member-bg.jpg
695 ms
title1.png
504 ms
slide1.jpg
1860 ms
title2.png
646 ms
slide2.jpg
1132 ms
title3.png
799 ms
slide3.jpg
1203 ms
07901_0000000096_image.jpg
1139 ms
07901_0000000097_image.jpg
558 ms
07901_0000000095_image.jpg
1035 ms
07901_0000000090_image.jpg
1146 ms
member-bt.png
718 ms
voice-board.jpg
915 ms
voice-board-bt.png
1098 ms
other-bt1.jpg
249 ms
other-bt2.jpg
255 ms
other-bt3.jpg
424 ms
other-bt4.jpg
628 ms
other-bt5.jpg
471 ms
other-bt6.jpg
479 ms
other-bt7.jpg
630 ms
other-bt8.jpg
655 ms
banner-mamber.jpg
697 ms
result-bg.jpg
805 ms
login-bt.png
816 ms
banner.png
1239 ms
man-catalog.jpg
902 ms
quick-bt.png
874 ms
shop-photo.jpg
1386 ms
arrow.png
1040 ms
shop-tel.png
1119 ms
shop-mail.png
1129 ms
idea-bg.png
1293 ms
idea-bt1.png
1325 ms
idea-bt2.png
1345 ms
idea-bt3.png
1144 ms
useful-bt1.png
1210 ms
useful-bt2.png
1287 ms
useful-bt3.png
1306 ms
useful-bt4.png
1322 ms
useful-bt5.png
1339 ms
search-bt1.png
1372 ms
search-bt2.png
1390 ms
search-bt3.png
2064 ms
side_view.js
1469 ms
search-bt4.png
2062 ms
search-bt5.png
2063 ms
banner-blog.jpg
2060 ms
banner-market.png
2037 ms
pagetop.png
2030 ms
footer-bg.jpg
1862 ms
footer-logo.png
1817 ms
gtm.js
46 ms
tag.js
20 ms
tag
28 ms
analytics.js
8 ms
pta.js
513 ms
659047916c322cd8_2131.js
479 ms
collect
4 ms
collect
51 ms
177b7b52.js
497 ms
e-earth.co.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-hidden="true"] elements contain focusable descendents
ARIA input 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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
e-earth.co.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
e-earth.co.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 E-earth.co.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 E-earth.co.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.
e-earth.co.jp
Open Graph description is not detected on the main page of E Earth. 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: