11.2 sec in total
559 ms
10.3 sec
305 ms
Visit irios.co.jp now to see the best up-to-date Irios content for Japan and also check out these interesting facts you probably never knew about irios.co.jp
【東京・大阪】出店をご検討中のテナント様、空室等でお困りのビルオーナー様等、テナント様もオーナー様も店舗物件の事なら賃貸も売買もテナント物件専門不動産のイリオスがサポート致します。
Visit irios.co.jpWe analyzed Irios.co.jp page load time and found that the first response time was 559 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
irios.co.jp performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value18.2 s
0/100
25%
Value18.2 s
0/100
10%
Value300 ms
79/100
30%
Value0.658
9/100
15%
Value20.7 s
2/100
10%
559 ms
916 ms
818 ms
362 ms
375 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 63% of them (56 requests) were addressed to the original Irios.co.jp, 21% (19 requests) were made to Iri-search.net and 2% (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 Irios.co.jp.
Page size can be reduced by 338.8 kB (13%)
2.6 MB
2.2 MB
In fact, the total size of Irios.co.jp main page is 2.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. 35% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 27.4 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 27.4 kB or 74% of the original size.
Potential reduce by 80.4 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. Irios images are well optimized though.
Potential reduce by 170.2 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 170.2 kB or 65% of the original size.
Potential reduce by 60.8 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. Irios.co.jp needs all CSS files to be minified and compressed as it can save up to 60.8 kB or 82% of the original size.
Number of requests can be reduced by 35 (41%)
86
51
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Irios. 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 6 to 1 for CSS and as a result speed up the page load time.
irios.co.jp
559 ms
www.irios.co.jp
916 ms
common.css
818 ms
top.css
362 ms
main.js
375 ms
mootools.js
918 ms
highlights.js
376 ms
external.js
704 ms
jquery-1.8.2.min.js
1357 ms
jquery.cookie.js
712 ms
jquery.fontsize.js
1209 ms
search.js
1070 ms
common_tb.css
1275 ms
common_sp.css
1711 ms
jquery.flickslide.js
1576 ms
origin.js
1561 ms
jquery.slides.min.js
1608 ms
slides.js
1489 ms
slides.css
1513 ms
analytics.js
6 ms
collect
12 ms
background_st.png
316 ms
header-title2.png
515 ms
header-serch-btn.jpg
345 ms
header-english.jpg
344 ms
logo.png
524 ms
btn_menu.png
347 ms
btn_menu_close.png
633 ms
showcase-img_itengo.png
3567 ms
showcase-img_leasing.png
4012 ms
showcase-img_owner.png
6929 ms
showcase-img_kensaku.png
1889 ms
showcase-img_shin-urayasu.png
3690 ms
showcase-img_ebisu-minami.png
4224 ms
showcase-img_shinbashi.png
4940 ms
showcase-img_ebisu.png
6661 ms
img_top-company.png
4744 ms
img_top-kensaku.png
4690 ms
img_top-osusume.png
5860 ms
img_top-contact.png
5417 ms
bnr_home.png
5226 ms
bnr_irisearch-osusume.png
5569 ms
bnr_risemall.png
5878 ms
bnr_fb.png
5916 ms
bnr_info.png
5899 ms
bnr_recruit.png
6389 ms
bnr_group.png
6204 ms
get_adobe_reader.gif
6211 ms
sdk.js
108 ms
gtm.js
103 ms
1268 ms
header-serch.jpg
6135 ms
header-font.jpg
6593 ms
bg_navi_arrow.png
6438 ms
icon05.gif
6466 ms
icon02_st.jpg
6614 ms
icon04_st.gif
6792 ms
icon07_st.jpg
6780 ms
background-footernavi.jpg
6861 ms
footer.jpg
6903 ms
conversion_async.js
30 ms
tag.js
29 ms
84 ms
tag
18 ms
46 ms
xd_arbiter.php
66 ms
xd_arbiter.php
129 ms
41 ms
jquery-1.8.2.min.js
5 ms
common.js
307 ms
bnr.css
347 ms
www.iri-search.net
1846 ms
access1.gif
306 ms
access2.gif
323 ms
access3.gif
337 ms
bnr_ebisu-minami.png
3864 ms
region.gif
309 ms
search1.gif
466 ms
search2.gif
489 ms
search3.gif
496 ms
h3_main-area1.gif
345 ms
h3_main-area2.gif
351 ms
h3_main-area3.gif
637 ms
h3_main-area4.gif
646 ms
bnr_osusume.png
953 ms
bnr_irima.png
1072 ms
bnr_gyakuinuki.png
1112 ms
bnr_ebisu.png
1176 ms
ya.js
361 ms
irios.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-*] 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
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>).
irios.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
irios.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Irios.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 Irios.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.
irios.co.jp
Open Graph data is detected on the main page of Irios. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: