13.8 sec in total
3.2 sec
10.2 sec
344 ms
Welcome to support.myjcom.jp homepage info - get ready to check Support Myjcom best content for Japan right away, or after learning these important things about support.myjcom.jp
お困りごとはJCOMサポート!J:COMが提供するサービスの総合サポートサイトです。各サービス別のサポート情報やよくあるご質問、接続・設定方法、各種お手続き、お問い合わせなどについてご案内します。
Visit support.myjcom.jpWe analyzed Support.myjcom.jp page load time and found that the first response time was 3.2 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
support.myjcom.jp performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value15.0 s
0/100
25%
Value15.1 s
1/100
10%
Value820 ms
36/100
30%
Value0.05
99/100
15%
Value18.6 s
3/100
10%
3220 ms
1360 ms
722 ms
372 ms
750 ms
Our browser made a total of 193 requests to load all elements on the main page. We found that 90% of them (173 requests) were addressed to the original Support.myjcom.jp, 8% (15 requests) were made to Myjcom.jp and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Support.myjcom.jp.
Page size can be reduced by 477.8 kB (62%)
769.3 kB
291.6 kB
In fact, the total size of Support.myjcom.jp main page is 769.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 291.7 kB which makes up the majority of the site volume.
Potential reduce by 58.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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 13% 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 58.7 kB or 83% of the original size.
Potential reduce by 31.9 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. Obviously, Support Myjcom needs image optimization as it can save up to 31.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 200.7 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 200.7 kB or 69% of the original size.
Potential reduce by 186.5 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. Support.myjcom.jp needs all CSS files to be minified and compressed as it can save up to 186.5 kB or 86% of the original size.
Number of requests can be reduced by 44 (23%)
191
147
The browser has sent 191 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support Myjcom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
support.myjcom.jp
3220 ms
contents.css
1360 ms
common.css
722 ms
base_other.css
372 ms
style_other.css
750 ms
support_top.css
583 ms
support_common.css
746 ms
support_index.css
724 ms
sup_app_banner1.css
787 ms
import.js
930 ms
common.js
923 ms
support_index_2.js
943 ms
support_common.js
949 ms
sup_app_banner1.js
996 ms
setStartPage.js
1137 ms
glNavi_accordion02.js
974 ms
login_js.php
529 ms
login_box.js
695 ms
footer.js
688 ms
s_code_utf-8.js
382 ms
jquery.js
655 ms
jquery_common.js
204 ms
webApi.js
220 ms
header_bg01.gif
172 ms
header_logo01.gif
259 ms
header_bt02.gif
205 ms
nav_service_o.png
256 ms
nav_price_o.png
199 ms
nav_campaign_o.png
258 ms
nav_tv_o.png
215 ms
nav_event_o.png
393 ms
nav_support_o.png
403 ms
nav_jcom_o.png
423 ms
title_001.gif
488 ms
shortcut_off.jpg
496 ms
sp.gif
499 ms
big_icon_001.png
588 ms
mask.png
602 ms
icon_bg_001.gif
637 ms
big_icon_002.png
693 ms
icon_bg_002.gif
710 ms
big_icon_003.png
721 ms
icon_bg_003.gif
774 ms
big_icon_005.png
799 ms
icon_bg_005.gif
841 ms
big_icon_004_2.png
895 ms
icon_bg_004.gif
917 ms
arrow_001_2.gif
934 ms
tv_title_001_off.gif
964 ms
tv_btn_001_off.gif
1063 ms
tv_title_002_off.gif
1063 ms
tv_btn_002_off.gif
1115 ms
tv_btn_003_off.gif
1126 ms
tv_title_003_off.gif
1147 ms
tv_btn_004_off.gif
1152 ms
tv_btn_005_off.gif
1216 ms
tv_title_004_off.gif
1250 ms
tv_btn_006_off.gif
1299 ms
cls_001_off.gif
1328 ms
arrow_002_2.gif
1351 ms
aside_ic05.gif
171 ms
aside_ic06.gif
172 ms
aside_ic07.gif
187 ms
com_ic03.gif
248 ms
footer_logo02.gif
303 ms
footer_copyright.gif
302 ms
footer_copyright_zaqu.gif
333 ms
com_ic05.gif
336 ms
footer_bg01.gif
352 ms
s_code_pc.js
904 ms
net_title_001_off.gif
1156 ms
net_btn_001_off.gif
1223 ms
net_btn_002_off.gif
1255 ms
net_btn_003_off.gif
1260 ms
net_btn_004_off.gif
1286 ms
net_title_002_off.gif
1290 ms
net_btn_005_off.gif
1192 ms
net_btn_006_off.gif
1228 ms
net_title_003_off.gif
1254 ms
net_btn_007_off.gif
1224 ms
net_btn_008_off.gif
1247 ms
net_title_004_off.gif
1239 ms
net_btn_009_off.gif
1208 ms
cls_002_off.gif
1235 ms
arrow_003_2.gif
1247 ms
phone_title_001_off.gif
1217 ms
phone_btn_001_off.gif
1217 ms
phone_btn_002_off.gif
1222 ms
phone_title_002_off.gif
1231 ms
phone_btn_003_off.gif
1244 ms
phone_btn_004_off.gif
1247 ms
phone_title_003_off.gif
1215 ms
phone_btn_005_off.gif
1201 ms
phone_btn_006_off.gif
1211 ms
phone_title_004_off.gif
1261 ms
gtm.js
60 ms
phone_btn_007_off.gif
1179 ms
cls_003_off.gif
1234 ms
analytics.js
5 ms
s64318535651545
43 ms
collect
13 ms
collect
16 ms
arrow_005.gif
1197 ms
mobile_title_001_off.gif
1184 ms
mobile_btn_001_off.gif
1201 ms
mobile_btn_002_off.gif
1285 ms
mobile_btn_003_off.gif
1228 ms
mobile_btn_004_off.gif
1264 ms
mobile_btn_005_off.gif
1214 ms
mobile_title_002_off.gif
1183 ms
mobile_btn_006_off.gif
1207 ms
mobile_btn_007_off.gif
1292 ms
mobile_btn_008_off.gif
1228 ms
mobile_title_003_off.gif
1252 ms
mobile_btn_009_off.gif
1207 ms
mobile_btn_010_off.gif
1197 ms
mobile_btn_011_off.gif
1218 ms
mobile_title_004_off.gif
1271 ms
mobile_btn_012_off.gif
1245 ms
cls_005_off.gif
1236 ms
arrow_004_2.gif
1209 ms
oth_title_001_off.gif
1208 ms
oth_btn_001_off.gif
1230 ms
oth_btn_002_off.gif
1263 ms
oth_btn_003_off.gif
1252 ms
oth_btn_004_off.gif
1224 ms
oth_btn_005_off.gif
1211 ms
oth_title_002_off.gif
1220 ms
oth_btn_006_off.gif
1234 ms
oth_btn_008_off.gif
1257 ms
oth_btn_007_off.gif
1259 ms
oth_title_003_off.gif
1204 ms
oth_btn_007_off.gif
1208 ms
cls_004_off.gif
1234 ms
sub_icon_001_off.gif
1231 ms
sub_icon_002_off.gif
1237 ms
sub_icon_003_off.gif
1239 ms
sub_icon_004_off.gif
1223 ms
sub_icon_005_2_off.gif
1212 ms
sub_icon_006_off.gif
1245 ms
title_002.gif
1226 ms
sup_sarch_btn.gif
1222 ms
no3.jpg
1226 ms
no1.jpg
1225 ms
no5.jpg
1215 ms
no2.jpg
1245 ms
no4.jpg
1231 ms
no6.jpg
1217 ms
faq_more.png
1208 ms
info_arrow.gif
1223 ms
info_btn_off.gif
1241 ms
info_btn_005_off.gif
1238 ms
title_005.gif
1229 ms
info_btn_003_off.gif
1205 ms
info_btn_004_off.gif
1194 ms
title_003.gif
1229 ms
contact_btn_001_off.gif
1250 ms
contact_btn_002_off.gif
1236 ms
contact_btn_003_off.gif
1224 ms
app_banner_1.gif
1189 ms
sup_bnr_001_off.gif
1180 ms
sup_bnr_002_off.gif
1234 ms
sup_bnr_007_off.gif
1256 ms
sup_bnr_008_off.gif
1237 ms
sup_bnr_006_off.gif
1216 ms
sup_bnr_003_off.gif
1174 ms
sup_top_btn_off.gif
1172 ms
floatbanner.png
1409 ms
btn_pageTopOther.gif
1273 ms
pixel.gif
1238 ms
icon_001.gif
1221 ms
line_topicPath.gif
1162 ms
aside_ic04.gif
1182 ms
sup_arrow_001.gif
1274 ms
sup_q.png
1284 ms
more_btn.gif
1248 ms
tab_001.gif
1237 ms
tab_002.gif
1201 ms
tab_003.gif
1237 ms
info_arrow_001.gif
1273 ms
sup_ptop_btn.gif
1273 ms
icon_blank.gif
1260 ms
icon_pdf.gif
1221 ms
icon_word.gif
1203 ms
icon_excel.gif
1244 ms
nav_service_h.png
1284 ms
nav_price_h.png
1251 ms
nav_campaign_h.png
1261 ms
nav_tv_h.png
1262 ms
nav_event_h.png
1215 ms
nav_support_h.png
1246 ms
nav_jcom_h.png
1265 ms
aside_ic26.gif
1263 ms
support.myjcom.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.
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.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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.
support.myjcom.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
Browser errors were logged to the console
Page has valid source maps
support.myjcom.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 Support.myjcom.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 Support.myjcom.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.
support.myjcom.jp
Open Graph description is not detected on the main page of Support Myjcom. 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: