6.8 sec in total
569 ms
5.8 sec
345 ms
Click here to check amazing Faq Nttdocomo content for Japan. Otherwise, check out these important facts you probably never knew about faq.nttdocomo.co.jp
Visit faq.nttdocomo.co.jpWe analyzed Faq.nttdocomo.co.jp page load time and found that the first response time was 569 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
faq.nttdocomo.co.jp performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value16.4 s
0/100
25%
Value10.1 s
9/100
10%
Value1,040 ms
25/100
30%
Value0.878
3/100
15%
Value16.2 s
6/100
10%
569 ms
865 ms
342 ms
1054 ms
537 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that all of those requests were addressed to Faq.nttdocomo.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Faq.nttdocomo.co.jp.
Page size can be reduced by 387.5 kB (80%)
484.3 kB
96.8 kB
In fact, the total size of Faq.nttdocomo.co.jp main page is 484.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. 15% of websites need less resources to load. CSS take 307.5 kB which makes up the majority of the site volume.
Potential reduce by 24.8 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 7.1 kB, which is 24% 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 24.8 kB or 83% of the original size.
Potential reduce by 3.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. Obviously, Faq Nttdocomo needs image optimization as it can save up to 3.7 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 88.9 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 88.9 kB or 64% of the original size.
Potential reduce by 270.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. Faq.nttdocomo.co.jp needs all CSS files to be minified and compressed as it can save up to 270.1 kB or 88% of the original size.
Number of requests can be reduced by 72 (73%)
98
26
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faq Nttdocomo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
faq.nttdocomo.co.jp
569 ms
865 ms
common.css
342 ms
main.css
1054 ms
header.css
537 ms
footer.css
367 ms
layout.css
364 ms
screen.css
1344 ms
top.css
547 ms
screen.css
549 ms
localnav.css
596 ms
common_new.js
890 ms
ecl.js
908 ms
initcompletion.js
732 ms
complete.js
790 ms
common.js
917 ms
roll_over.js
983 ms
popup.js
1073 ms
font.css
1090 ms
popup.css
743 ms
clearfix.css
813 ms
common.css
682 ms
main.css
1061 ms
header.css
733 ms
localnav.css
741 ms
footer.css
818 ms
layout.css
860 ms
header.html
198 ms
footer.html
182 ms
bg_body.gif
187 ms
bg_contentswrap_gray.gif
188 ms
bg_contentswrap.gif
175 ms
partition_breadcrumb.gif
184 ms
bg_h2.jpg
346 ms
bg_boxArea_line.gif
360 ms
bg_boxArea_bottom.gif
375 ms
bg_boxArea_top.gif
365 ms
bg_boxArea_h2line.gif
372 ms
bg_boxArea_line.gif
371 ms
bg_boxArea_bottom180.gif
519 ms
bg_boxArea_top180.gif
538 ms
bg_boxArea_h2line_short.gif
545 ms
bg_li_li.gif
554 ms
bg_li_a.gif
555 ms
arrow_li_li_a.gif
564 ms
icon_pc2.gif
689 ms
blet_popup.gif
718 ms
line_leftcol145.gif
724 ms
icon_tel2.gif
739 ms
arrow_right.gif
737 ms
bg_boxArea_line.gif
753 ms
bg_boxArea_bottom.gif
859 ms
bg_boxArea_top.gif
896 ms
bg_boxArea_h2line.gif
904 ms
arrow_left_normal.gif
919 ms
arrow_right_normal.gif
920 ms
blet_close.gif
944 ms
icon_q.gif
1029 ms
icon_a.gif
1076 ms
line_leftcol.gif
1082 ms
spec_tooltip.gif
1101 ms
arrow_top_normal.gif
1102 ms
slogan.gif
1027 ms
jQuery1.10.2.min.js
1260 ms
rollover_default_over.min.js
1107 ms
icon_footer_link_s.png
192 ms
background_base.gif
198 ms
header_logo.gif
183 ms
bg_font.gif
187 ms
header_font_txt.gif
185 ms
font_small_off.gif
173 ms
font_middle_on.gif
183 ms
font_big_off.gif
343 ms
header_nav_info_default.gif
360 ms
header_nav_faq_default.gif
361 ms
header_nav_contact_default.gif
368 ms
header_nav_ir_default.gif
369 ms
header_nav_shop_default.gif
385 ms
btn_online_shop.gif
513 ms
bg_gn.gif
538 ms
header_menu_home_default.gif
542 ms
header_menu_product_default.gif
550 ms
header_menu_service_default.gif
550 ms
header_menu_charge_default.gif
574 ms
header_menu_area_default.gif
683 ms
header_menu_support_current.gif
713 ms
header_menu_mydocomo_default.gif
720 ms
header_nav_info_over.gif
732 ms
header_nav_faq_over.gif
734 ms
header_nav_contact_over.gif
764 ms
header_nav_ir_over.gif
854 ms
header_nav_shop_over.gif
891 ms
header_menu_home_over.gif
899 ms
header_menu_product_over.gif
912 ms
header_menu_service_over.gif
916 ms
header_menu_charge_over.gif
955 ms
header_menu_area_over.gif
1021 ms
header_menu_mydocomo_over.gif
1069 ms
font_small_on.gif
193 ms
font_middle_off.gif
180 ms
font_big_on.gif
184 ms
layoutPrint.css
195 ms
print_new.css
196 ms
faq.nttdocomo.co.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
Links do not have a discernible name
faq.nttdocomo.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
General
Impact
Issue
Detected JavaScript libraries
faq.nttdocomo.co.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
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faq.nttdocomo.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 Faq.nttdocomo.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
faq.nttdocomo.co.jp
Open Graph description is not detected on the main page of Faq Nttdocomo. 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: