9.7 sec in total
598 ms
7.7 sec
1.4 sec
Welcome to iida.jp homepage info - get ready to check Iida best content right away, or after learning these important things about iida.jp
auのスマートフォン(スマホ)・携帯電話・モバイルのページ。製品ラインアップ、キャンペーン、サービス、ご利用料金、サポート情報をご紹介します。
Visit iida.jpWe analyzed Iida.jp page load time and found that the first response time was 598 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
iida.jp performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value20.5 s
0/100
25%
Value24.5 s
0/100
10%
Value18,960 ms
0/100
30%
Value0.352
31/100
15%
Value46.4 s
0/100
10%
598 ms
843 ms
334 ms
345 ms
352 ms
Our browser made a total of 180 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Iida.jp, 67% (121 requests) were made to Au.kddi.com and 5% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Au.kddi.com.
Page size can be reduced by 477.8 kB (11%)
4.4 MB
3.9 MB
In fact, the total size of Iida.jp main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 55.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 55.4 kB or 78% of the original size.
Potential reduce by 48.8 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. Iida images are well optimized though.
Potential reduce by 343.3 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 343.3 kB or 75% of the original size.
Potential reduce by 30.3 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. Iida.jp needs all CSS files to be minified and compressed as it can save up to 30.3 kB or 78% of the original size.
Number of requests can be reduced by 61 (37%)
164
103
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iida. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
iida.jp
598 ms
843 ms
import.css
334 ms
common.css
345 ms
style.css
352 ms
jquery-1.7.min.js
1264 ms
html5shiv-printshiv.js
735 ms
common.js
1150 ms
jquery.easing.js
498 ms
jquery.color-2.1.2.min.js
678 ms
pgwbrowser.min.js
696 ms
fadeIn.js
666 ms
global.js
831 ms
main.js
848 ms
s_code_au.js
1274 ms
header.css
590 ms
footer.css
669 ms
0000020470-img-7b
749 ms
sdk.js
146 ms
gnav_bg_01.gif
239 ms
gnav_logo.gif
237 ms
gnav_mobile_cur.png
242 ms
gnav_bg_02.gif
243 ms
gnav_mobile_product_cur.gif
239 ms
gnav_mobile_charge.gif
385 ms
gnav_mobile_service.gif
387 ms
gnav_mobile_area.gif
388 ms
gnav_mobile_campaign.gif
388 ms
gnav_internet.png
599 ms
gnav_content.png
600 ms
gnav_auwallet.png
660 ms
gnav_electricity_02.png
656 ms
gnav_support.png
678 ms
gnav_onlineshop.png
676 ms
gnav_english.gif
659 ms
gnav_inquiry.gif
674 ms
gnav_sitemap.gif
782 ms
gnav_ip.gif
810 ms
gnav_bg_05.gif
800 ms
gnav_search.png
810 ms
search_tool_n1.js
783 ms
gnav_shop_search.gif
786 ms
gnav_information.png
780 ms
icn_breadcrumb.gif
922 ms
widgets.js
190 ms
title.png
840 ms
navi-menu01.png
846 ms
navi-menu02.png
873 ms
navi-menu03.png
880 ms
btn_facebook.png
884 ms
navi_bg.png
1000 ms
title-subnabi2.png
1002 ms
btn_close.png
1013 ms
icon01.png
1045 ms
icon02.png
1069 ms
icon03.png
1071 ms
icon04.png
1048 ms
icon05.png
1049 ms
icon06.png
1064 ms
icon07.png
1097 ms
icon08.png
1110 ms
so.js
661 ms
navi_arrow.png
988 ms
navi_title_lifestyle2.png
1066 ms
navi_lifestyle01.png
1357 ms
navi_lifestyle02.png
1361 ms
firstevent
86 ms
navi_lifestyle03.png
913 ms
navi_lifestyle04.png
1140 ms
90 ms
message_photo.jpg
2032 ms
103 ms
s2965352458879
94 ms
sub-title.png
1082 ms
title02.png
1098 ms
title_catch.png
1092 ms
btn_about.png
1141 ms
btn_about_arrow.png
1140 ms
btn_style.png
1156 ms
xd_arbiter.php
95 ms
xd_arbiter.php
182 ms
btn_style_arrow.png
1057 ms
gallery-title.png
1136 ms
i_search_assist_n1.js
355 ms
ac.css
343 ms
top-gallery-photo01.jpg
1972 ms
top-gallery-photo02.jpg
1480 ms
top-gallery-photo03.jpg
1369 ms
point.png
1264 ms
top-gallery-photo04.jpg
1338 ms
top-gallery-photo05.jpg
1819 ms
top-gallery-photo06.jpg
1902 ms
top-gallery-photo07.jpg
1865 ms
top-gallery-photo08.jpg
1643 ms
top-gallery-photo09.jpg
1969 ms
top-gallery-photo10.jpg
2485 ms
top-gallery-photo11.jpg
2175 ms
top-gallery-photo12.jpg
1983 ms
js
267 ms
top-gallery-photo13.jpg
1873 ms
top-gallery-photo14.jpg
2015 ms
top-gallery-photo15.jpg
2103 ms
top-gallery-photo16.jpg
2493 ms
top-gallery-photo17.jpg
2492 ms
top-gallery-photo18.jpg
2244 ms
top-gallery-photo19.jpg
2308 ms
top-gallery-photo20.jpg
2276 ms
top-gallery-photo21.jpg
3201 ms
v3
323 ms
ActivityServer.bs
77 ms
img
395 ms
top-gallery-photo22.jpg
3076 ms
a777ddbed156ff03_1318.js
9 ms
top-gallery-photo23.jpg
2455 ms
conversion.js
204 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
216 ms
top-gallery-photo24.jpg
2248 ms
title-subnabi.png
2204 ms
footer-banner01.png
3024 ms
banner-casa.png
2372 ms
ftr_bg.png
2373 ms
119 ms
footer-banner02.png
2367 ms
like.php
111 ms
footer-banner03.png
2497 ms
footer-banner04.png
2481 ms
40 ms
94 ms
combo
173 ms
footer-banner05.png
2501 ms
ftr_fb.png
2608 ms
141 ms
146 ms
U9rHIpG5ERY.js
274 ms
LVx-xkvaJ0b.png
276 ms
146 ms
icn_bullet.png
2530 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
92 ms
pb.html
47 ms
33 ms
pix
334 ms
pixel
37 ms
329 ms
39 ms
60 ms
38 ms
46 ms
59 ms
icn_bullet_s.png
2435 ms
38 ms
634 ms
309 ms
31 ms
28 ms
34 ms
42 ms
38 ms
jot
121 ms
icn_blank_m.gif
2451 ms
like.php
62 ms
gnav_footer_logo.gif
2393 ms
icn_blank_s.gif
2395 ms
163 ms
pixel
16 ms
gnav_footer_copyright_v2.gif
2075 ms
gnav_mobile_charge_on.gif
2066 ms
gnav_mobile_service_on.gif
2036 ms
gnav_mobile_area_on.gif
2088 ms
gnav_mobile_campaign_on.gif
2019 ms
gnav_internet_on.png
2036 ms
gnav_content_on.png
1948 ms
gnav_auwallet_on.png
1904 ms
gnav_electricity_02_on.png
1854 ms
gnav_support_on.png
1837 ms
gnav_onlineshop_on.png
1757 ms
dest4.html
21 ms
rep
163 ms
pixel
45 ms
ibs:dpid=416&dpuuid=TA219cc7d3-eb72-11e5-bc17-00163ebe92e0
19 ms
ibs:dpid=470&dpuuid=3630835439297028772
13 ms
iida.jp accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
iida.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
iida.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 Iida.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 Iida.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.
iida.jp
Open Graph data is detected on the main page of Iida. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: