6.2 sec in total
297 ms
5.4 sec
500 ms
Click here to check amazing I X content. Otherwise, check out these important facts you probably never knew about i-x.cc
1都3県で不動産売買をご検討されているお客様は、新宿にある株式会社イクスにぜひご相談ください。弊社では、お客様本位の住みやすさや、資産価値の向上を考えて、コンサルタントサービスをご提供しております。ご不満やご要望も含めてお気軽にご相談ください。
Visit i-x.ccWe analyzed I-x.cc page load time and found that the first response time was 297 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
i-x.cc performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value24.8 s
0/100
25%
Value11.6 s
4/100
10%
Value1,260 ms
19/100
30%
Value0.174
69/100
15%
Value15.4 s
7/100
10%
297 ms
596 ms
288 ms
666 ms
172 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 78% of them (84 requests) were addressed to the original I-x.cc, 14% (15 requests) were made to Lab3cdn.ielove.jp and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Cdn.img-asp.jp.
Page size can be reduced by 116.7 kB (5%)
2.4 MB
2.3 MB
In fact, the total size of I-x.cc main page is 2.4 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. 60% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 73.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. This page needs HTML code to be minified as it can gain 32.8 kB, which is 38% 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 73.9 kB or 86% of the original size.
Potential reduce by 42.7 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. I X images are well optimized though.
Potential reduce by 50 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 28 (27%)
104
76
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I X. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
i-x.cc
297 ms
i-x.cc
596 ms
www.i-x.cc
288 ms
www.i-x.cc
666 ms
ui-meiriyo.css
172 ms
common.css
334 ms
onecolumn-footer.css
443 ms
onecolumn-header.css
451 ms
aside.css
458 ms
jquery.jscrollpane.css
472 ms
slick.css
479 ms
jquery.mCustomScrollbar.css
497 ms
pattern3.css
604 ms
jquery-1.8.2.min.js
201 ms
common_library.js
205 ms
jquery.jscrollpane.min.js
207 ms
jquery.mousewheel.js
208 ms
jquery.page-scroller-306.js
210 ms
onecolumn.js
212 ms
jquerypngfix.js
208 ms
slick.min.js
210 ms
jquery.lazyload.js
211 ms
url_define.js
618 ms
widgets.js
91 ms
common.js
213 ms
default.js
213 ms
mainslider.js
213 ms
jquery-ui.min.js
213 ms
jquery.mousewheel.min.js
213 ms
jquery.mCustomScrollbar.js
213 ms
gtm.js
127 ms
analytics.js
75 ms
fbds.js
39 ms
43644_1_0_0_2.jpg
1417 ms
logo.jpg
150 ms
tel.jpg
175 ms
img_bg-his.png
175 ms
img_bg-fav.png
165 ms
img-nav-home.jpg
162 ms
img-nav-area_search.jpg
159 ms
img-nav-line_search.jpg
298 ms
img-nav-company.jpg
306 ms
img-nav-contact.jpg
309 ms
img_main-dot.jpg
315 ms
img_kodawari01.jpg
1095 ms
img_kodawari02.jpg
1109 ms
img_mainsearch-area.png
601 ms
img_mainsearch-line.png
739 ms
img_mainsearch-map.png
749 ms
img_btn-freesearch.png
475 ms
img_ttl-pickup.png
637 ms
img_btn-pickup01.jpg
758 ms
img_btn-pickup02.jpg
941 ms
img_btn-pickup03.jpg
892 ms
img_btn-pickup04.jpg
910 ms
img_btn-pickup05.jpg
912 ms
img_ttl-info-1.png
1043 ms
img_btn-info.png
1066 ms
img_ttl-contmenu.png
1067 ms
bt_side_staff.jpg
1092 ms
bt_side_customer.jpg
1190 ms
bt_side_spot.jpg
1215 ms
bt_side_accessmap.jpg
1216 ms
bt_side_contact.jpg
1242 ms
img_ttl-staff.png
1256 ms
img_ttl-company.png
1272 ms
img_btn-contact.png
1344 ms
43644_2_0_0_2.jpg
2601 ms
clearfix.gif
1351 ms
img_bg-pickup.jpg
1351 ms
img_bg-info1.jpg
1380 ms
collect
18 ms
collect
28 ms
1282 ms
js
41 ms
img_info-arrow.jpg
1282 ms
img_bg-new.jpg
1342 ms
img_bg-contmenu.jpg
1357 ms
img_bg-staff.jpg
1359 ms
img_bg-company.jpg
1387 ms
img_pcicon-phone.png
1301 ms
img_pcicon-mail.png
1349 ms
img_sub-dot.jpg
1354 ms
img-nav-home_on.jpg
1207 ms
img-nav-area_search_on.jpg
1112 ms
img-nav-line_search_on.jpg
1129 ms
img-nav-company_on.jpg
1026 ms
img-nav-contact_on.jpg
1056 ms
img_mainsearch-area_on.png
1066 ms
img_mainsearch-line_on.png
946 ms
img_mainsearch-map_on.png
1108 ms
img_btn-freesearch_on.png
1013 ms
img_btn-pickup01_on.jpg
992 ms
img_btn-pickup02_on.jpg
913 ms
img_btn-pickup03_on.jpg
918 ms
img_btn-pickup04_on.jpg
928 ms
img_btn-pickup05_on.jpg
1000 ms
img_btn-info_on.png
1007 ms
bt_side_staff_on.jpg
1000 ms
bt_side_customer_on.jpg
941 ms
bt_side_spot_on.jpg
930 ms
bt_side_accessmap_on.jpg
953 ms
bt_side_contact_on.jpg
1007 ms
img_btn-contact_on.png
1010 ms
loading.gif
981 ms
img_mainbg-slide01.jpg
1371 ms
img_mainbg-slide02.jpg
1519 ms
img_mainhalf-dot.jpg
956 ms
i-x.cc 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.
i-x.cc 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
i-x.cc SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-x.cc 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 I-x.cc 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.
i-x.cc
Open Graph data is detected on the main page of I X. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: