8 sec in total
602 ms
7 sec
321 ms
Click here to check amazing Y Mobile content for Japan. Otherwise, check out these important facts you probably never knew about ymobile.jp
【公式】ワイモバイル(Y!mobile)、家族で980円(税抜)からご利用可能なiPhone、Android スマートフォン、SIMの料金・サービスをご紹介します。
Visit ymobile.jpWe analyzed Ymobile.jp page load time and found that the first response time was 602 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ymobile.jp performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value25.3 s
0/100
25%
Value11.4 s
5/100
10%
Value4,420 ms
0/100
30%
Value0.149
76/100
15%
Value20.3 s
2/100
10%
602 ms
1096 ms
794 ms
227 ms
222 ms
Our browser made a total of 244 requests to load all elements on the main page. We found that 15% of them (36 requests) were addressed to the original Ymobile.jp, 46% (112 requests) were made to Cdn.ymobile.jp and 2% (6 requests) were made to Cast-cs-j.adtdp.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cdn.ymobile.jp.
Page size can be reduced by 642.1 kB (19%)
3.4 MB
2.8 MB
In fact, the total size of Ymobile.jp main page is 3.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 2.6 MB which makes up the majority of the site volume.
Potential reduce by 65.7 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 65.7 kB or 79% of the original size.
Potential reduce by 84.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. Y Mobile images are well optimized though.
Potential reduce by 364.5 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 364.5 kB or 65% of the original size.
Potential reduce by 127.2 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. Ymobile.jp needs all CSS files to be minified and compressed as it can save up to 127.2 kB or 86% of the original size.
Number of requests can be reduced by 96 (42%)
227
131
The browser has sent 227 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Y Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and as a result speed up the page load time.
ymobile.jp
602 ms
www.ymobile.jp
1096 ms
index.html
794 ms
jquery.js
227 ms
opacity-rollover2.1.js
222 ms
smoothrollover.js
222 ms
popup.js
414 ms
jquery.cookie.js
222 ms
jquery.min.js
1385 ms
top_tab.js
400 ms
ojs
556 ms
basic.css
766 ms
jquery.bxslider.css
572 ms
top.css
568 ms
jquery.easing.1.3.js
195 ms
jquery.bxslider.js
203 ms
top_script.js
198 ms
menu_link.js
4 ms
logo_ymobile.gif
43 ms
logo_ymobile.gif
41 ms
btn_search.gif
41 ms
icon_plan.gif
43 ms
icon_lineup.gif
42 ms
img_lineup_403sh.png
43 ms
img_lineup_404sh.png
44 ms
img_lineup03.png
45 ms
img_lineup04.png
45 ms
img_lineup05.png
46 ms
img_lineup06.png
48 ms
icon_service.gif
49 ms
icon_support.gif
48 ms
logo_ymobile_s.gif
50 ms
logo_ymobile.gif
210 ms
top_imp_opera.png
215 ms
topimp_ym.jpg
267 ms
gakuwari_960_300.jpg
285 ms
banner_newlineup.jpg
361 ms
topimp_pocketwifi.jpg
866 ms
topimp_hikari.jpg
400 ms
banner_superkomikomi.jpg
525 ms
topimp_05.jpg
659 ms
toppick_cp_index.gif
517 ms
toppick_cp_link.gif
656 ms
toppick_data_double.png
816 ms
setotoku.png
823 ms
cp_newphone.png
878 ms
toppick_03.gif
822 ms
top_imp_opera_sp.png
933 ms
sp_topimp_ym.jpg
877 ms
gakuwari_640_300.jpg
1136 ms
sp_banner_newlineup.jpg
945 ms
sp_topimp_pocketwifi.jpg
1089 ms
sp_topimp_hikari.jpg
1087 ms
sp_banner_superkomikom.jpg
1089 ms
gtm.js
86 ms
tag.js
29 ms
ojs2
335 ms
sp_topimp_05.jpg
1119 ms
sp_toppick_nibai.png
1145 ms
setotoku.png
1249 ms
cp_newphone.png
1249 ms
sp_toppick_03.gif
1248 ms
navi_plan.gif
1278 ms
navi_lineup.gif
1280 ms
navi_service.gif
1340 ms
navi_area.gif
1435 ms
navi_shop.gif
1434 ms
navi_store.gif
1438 ms
navi_campaign.gif
1471 ms
navi_support.gif
1467 ms
index_priceplan.png
1527 ms
tag
11 ms
10aa37b4d3ee86e8b1950c8636dd1047ec7f0a2f.js
30 ms
conversion_async.js
17 ms
analytics.js
18 ms
2000004205-img-2d
702 ms
DIGITALICE_REC.js
691 ms
conversion.js
42 ms
70 ms
ec.js
29 ms
s_retargeting.js
350 ms
collect
9 ms
collect
64 ms
plan_s.gif
1474 ms
plan_m.gif
1460 ms
50 ms
plan_l.gif
1417 ms
ga-audiences
19 ms
sp_plan_image.png
1425 ms
index_lineup_sp.png
1342 ms
lb
6 ms
lineup_404sh.png
1465 ms
lineup_403sh.png
1341 ms
lineup_nexus5x.png
1348 ms
fbds.js
116 ms
icon_onlinestore.png
278 ms
icon_myymobile.png
285 ms
icon_cp.png
284 ms
icon_biz.png
284 ms
navi_nonactive.gif
283 ms
icon_plan.png
261 ms
icon_lineup.png
359 ms
icon_service.png
493 ms
icon_area.png
492 ms
icon_shop.png
494 ms
icon_support.png
491 ms
icon_sp.png
494 ms
icon_wifi.png
585 ms
icon_phs.png
680 ms
link_icon.png
681 ms
icon_link.png
680 ms
service_icon1.png
678 ms
service_icon2.png
666 ms
service_icon3.png
754 ms
news.gif
859 ms
icon_link_top.gif
884 ms
sns_index.png
885 ms
link_icon.gif
885 ms
link_faq.png
883 ms
link_contact.png
952 ms
lineup_503hw.png
1212 ms
sp.html
893 ms
mone.e24fc5864d1_1267.js
106 ms
d.js
450 ms
conversion_async.js
75 ms
blade_track_jp.js
368 ms
slider_left2.png
833 ms
slider_right2.png
863 ms
lineup_nexus6.png
1079 ms
lineup_digno_c.png
1073 ms
lineup_spray.png
1229 ms
index_service.png
1233 ms
60 ms
413 ms
mileage.png
1186 ms
lineup_smartphone.jpg
1183 ms
lineup_smartphone.jpg
1249 ms
44 ms
43 ms
ymobile.js
68 ms
segmentation.js
15 ms
tc.min.js
106 ms
m.js
42 ms
22 ms
29 ms
lineup_wifi.jpg
1152 ms
cnt
307 ms
redirect.js
8 ms
cnt
379 ms
beacon.html
10 ms
lineup_wifi.jpg
1297 ms
pre
366 ms
popin_read-min.js
43 ms
ca.html
57 ms
lineup_phone.jpg
1161 ms
lineup_phone.jpg
1166 ms
recommend1.gif
1160 ms
pixel
63 ms
Pug
48 ms
cx
69 ms
adb.gif
36 ms
1
74 ms
cs
370 ms
sync
53 ms
demconf.jpg
35 ms
tap.php
41 ms
recomend1.gif
1138 ms
recommend2.gif
1387 ms
360947.gif
40 ms
cm
46 ms
pixel.gif
46 ms
cm
40 ms
xrefid.xgi
39 ms
pixel
45 ms
41 ms
cx
43 ms
recomend2.gif
1269 ms
cm
36 ms
mapuid
38 ms
sd
33 ms
cookie_enabled_get.html
354 ms
cm
22 ms
17 ms
cx
27 ms
362378.gif
20 ms
xrefid.xgi
16 ms
lr.gif
14 ms
combo
156 ms
pixel.gif
12 ms
simulation_288_68_02.gif
1264 ms
simulation_308_68_02.gif
1177 ms
recommend5.gif
1179 ms
recomend5.gif
1166 ms
bnr_compare_288x68.png
1327 ms
cast-mark-j.adtdp.com
185 ms
bnr_compare_308x68.png
1272 ms
pb.html
78 ms
bnr_hikari_308x68.jpg
1188 ms
151002_fute2_TOP.png
1201 ms
news_list.gif
1257 ms
pixel
18 ms
299 ms
610 ms
303 ms
rss.gif
1227 ms
news_list.gif
1322 ms
mark
315 ms
bl_track.cgi
360 ms
rss.gif
1270 ms
sns_facebook.png
1187 ms
sns_twitter.png
1192 ms
sns_google.png
1251 ms
sns_line.png
1227 ms
sns_instagram.png
1324 ms
150 ms
sync
357 ms
allcsync.js
411 ms
sns_youtube2.png
1406 ms
sns_youtube2.png
1192 ms
search.gif
1000 ms
banner_cp.png
999 ms
banner_mm.png
977 ms
banner_cmgallery.gif
977 ms
banner4.jpg
826 ms
share_facebook.gif
823 ms
share_twitter.gif
824 ms
share_googleplus.gif
824 ms
share.gif
801 ms
totop.gif
766 ms
adstir
171 ms
sync.ad
443 ms
cookiesync
338 ms
300 ms
s.kau.li
334 ms
pixel
14 ms
xrost
171 ms
158 ms
mediba
167 ms
compass
184 ms
sd
8 ms
sync
6 ms
gcs
352 ms
rep
149 ms
3 ms
ymobile.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
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.
ymobile.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
General
Impact
Issue
Detected JavaScript libraries
ymobile.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
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 Ymobile.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 Ymobile.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.
ymobile.jp
Open Graph description is not detected on the main page of Y Mobile. 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: