9 sec in total
1.1 sec
6.6 sec
1.3 sec
Visit mobile-station.jp now to see the best up-to-date Mobile Station content for Japan and also check out these interesting facts you probably never knew about mobile-station.jp
携帯電話の乗り換えでお悩みなら当店で承ります!今ならソフトバンク携帯への乗り換え(NMP)でキャッシュバック最大50,000円!何でもお気軽にご相談下さい♪
Visit mobile-station.jpWe analyzed Mobile-station.jp page load time and found that the first response time was 1.1 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
mobile-station.jp performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value14.9 s
0/100
25%
Value14.0 s
1/100
10%
Value500 ms
58/100
30%
Value0.001
100/100
15%
Value11.8 s
17/100
10%
1104 ms
44 ms
672 ms
349 ms
346 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 80% of them (130 requests) were addressed to the original Mobile-station.jp, 6% (9 requests) were made to Apis.google.com and 2% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Mobile-station.jp.
Page size can be reduced by 590.7 kB (14%)
4.4 MB
3.8 MB
In fact, the total size of Mobile-station.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.7 MB which makes up the majority of the site volume.
Potential reduce by 41.5 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 41.5 kB or 76% of the original size.
Potential reduce by 161.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. Mobile Station images are well optimized though.
Potential reduce by 365.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 365.3 kB or 68% of the original size.
Potential reduce by 22.1 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. Mobile-station.jp needs all CSS files to be minified and compressed as it can save up to 22.1 kB or 84% of the original size.
Number of requests can be reduced by 44 (28%)
160
116
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Station. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
mobile-station.jp
1104 ms
css
44 ms
style.css
672 ms
als_demo.css
349 ms
ui.tabs.css
346 ms
jquery.min.js
59 ms
jquery.2.1.1.js
1084 ms
script.js
365 ms
top.js
693 ms
TweenMax.min.js
1211 ms
jquery.scrollmagic.js
1313 ms
jquery.min.js
1073 ms
jquery.easing.min.js
836 ms
slider.js
859 ms
jquery.als-1.7.min.js
1003 ms
slider03.js
1030 ms
selector.js
1170 ms
platform.js
55 ms
s_retargeting.js
522 ms
conversion.js
18 ms
fbevents.js
28 ms
logo01.png
279 ms
num1.png
279 ms
001.png
1108 ms
logo02.png
275 ms
btn.png
275 ms
24h.png
280 ms
freedial.png
419 ms
0034.png
421 ms
1.png
419 ms
f_item01.png
425 ms
f_item02.png
426 ms
f_item03.png
629 ms
f_item04.png
629 ms
f_item05.png
627 ms
f_item06.png
625 ms
f_item07.png
625 ms
f_item08.png
804 ms
f_item09.png
804 ms
f_item10.png
784 ms
thin_left_arrow.png
787 ms
thin_right_arrow.png
804 ms
0032.png
1118 ms
0033.png
957 ms
012.png
983 ms
item01.png
984 ms
item02.png
985 ms
item03.png
1127 ms
item04.png
1161 ms
item05.png
1162 ms
item06.png
1163 ms
item07.png
1274 ms
item08.png
1284 ms
item09.png
1298 ms
item10.png
1339 ms
item02_spec.png
1522 ms
analytics.js
65 ms
reason_title.png
1330 ms
widgets.js
8 ms
238 ms
237 ms
linkid.js
160 ms
sdk.js
147 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
176 ms
cb=gapi.loaded_0
169 ms
cb=gapi.loaded_1
234 ms
fastbutton
304 ms
reason_ttl01.png
1181 ms
reason_txt01.png
1183 ms
reason_ttl02.png
1201 ms
reason_txt02.png
1251 ms
collect
72 ms
collect
301 ms
reason_ttl03.png
1154 ms
178 ms
267 ms
xd_arbiter.php
96 ms
xd_arbiter.php
195 ms
reason_txt03.png
1208 ms
step_title.png
1206 ms
step_img.png
1395 ms
step_ttl01.png
1281 ms
step_txt01.png
1282 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
88 ms
postmessageRelay
170 ms
rs=AGLTcCNFg9Lxr6A_1qJE1FafaQPPaU_lFQ
71 ms
step_ttl02.png
1088 ms
step_txt02.png
1167 ms
step_ttl03.png
1172 ms
step_txt03.png
1259 ms
line.png
1262 ms
cb=gapi.loaded_0
43 ms
cb=gapi.loaded_1
49 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
43 ms
3193398744-postmessagerelay.js
54 ms
rpc:shindig_random.js
35 ms
cb=gapi.loaded_0
7 ms
3step.png
1111 ms
qaa_title.png
1172 ms
q1ttl_01
1169 ms
q1txt_01
1185 ms
q1ttl_02
1261 ms
jot.html
2 ms
q1txt_02
1112 ms
q1ttl_03
1092 ms
q1txt_03
1142 ms
q1ttl_04
1160 ms
q1txt_04
1059 ms
q2ttl_01
1129 ms
q2txt_01
1125 ms
q2ttl_02
1097 ms
q2txt_02
1130 ms
q3ttl_01
1149 ms
q3txt_01
1055 ms
q3ttl_02
1141 ms
q3txt_02
1129 ms
q3ttl_03
1099 ms
q3txt_03
1116 ms
q3ttl_04
1043 ms
q3txt_04
1049 ms
q4ttl_01
1136 ms
q4txt_01
1091 ms
q4ttl_02
1096 ms
q4txt_02
1098 ms
q4ttl_03
1055 ms
q4txt_03
1058 ms
q4ttl_04
1088 ms
q4txt_04
1093 ms
q4ttl_05
1096 ms
q4txt_05
1007 ms
q4ttl_06
1044 ms
q4txt_06
1033 ms
line.gif
1086 ms
pict1.png
1077 ms
pict2.png
1087 ms
pict3.png
1034 ms
pict4.png
1041 ms
009.png
1031 ms
009-1.jpg
1067 ms
009-2.jpg
1083 ms
009-3.jpg
1086 ms
009-4.jpg
1227 ms
009-5.jpg
1042 ms
inquiry_title.png
1030 ms
cpi.jpg
1055 ms
inquiry_img.png
1260 ms
001b.jpg
1449 ms
002a.png
1077 ms
bg.png
1388 ms
0035.png
1138 ms
012a.jpg
2204 ms
4.jpg
1104 ms
006d.jpg
1196 ms
006dbk02.png
1414 ms
007e.jpg
1223 ms
008c.jpg
1471 ms
inner_bk.png
1443 ms
009b.jpg
1453 ms
011d.jpg
1264 ms
confirm_btn.png
1430 ms
pagetop.png
1385 ms
pict1_o.png
1460 ms
mobile-station.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.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
mobile-station.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
Issues were logged in the Issues panel in Chrome Devtools
mobile-station.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile-station.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 Mobile-station.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.
mobile-station.jp
Open Graph description is not detected on the main page of Mobile Station. 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: