ntt.com

ntt.com is SSL secured

Free website and domain report on ntt.com

Last Updated: 6th September, 2020 Update Now
Overview

Snoop Summary for ntt.com

This is a free and comprehensive report about ntt.com. Ntt.com is expected to earn an estimated $1,333 USD per day from advertising revenue. The sale of ntt.com would possibly be worth $973,328 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Ntt.com receives an estimated 212,483 unique visitors every day - an insane amount of traffic! This report was last updated 6th September, 2020.

About ntt.com

Site Preview: ntt.com ntt.com
Title: NTT Communications
Description: NTTコミュニケーションズ オフィシャルサイト。企業情報、採用情報や個人向けサービス・法人向けサービス・個人事業・中小法人向けサービス情報を掲載しています。
Keywords and Tags: ict, internet services, ntt, ntt com, ntt communications, nttコミュニケーションズ, nttコム, ocn, イベント, インターネット, キャンペーン, ニュース, ホスティング, 電話
Related Terms: lowongan kerja bank ntt kupang, ntt docomo, ntt me
Fav Icon:
Age: Over 26 years old
Domain Created: 7th October, 1997
Domain Updated: 19th February, 2020
Domain Expires: 6th October, 2025
Review

Snoop Score

4/5 (Excellent!)

Valuation

$973,328 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 8,322
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 212,483
Monthly Visitors: 6,467,299
Yearly Visitors: 77,556,127
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1,333 USD
Monthly Revenue: $40,582 USD
Yearly Revenue: $486,659 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: ntt.com 7
Domain Name: ntt 3
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.73 seconds
Load Time Comparison: Faster than 55% of sites

PageSpeed Insights

Avg. (All Categories) 71
Performance 63
Accessibility 79
Best Practices 77
SEO 91
Progressive Web App 44
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.ntt.com/language-selector.html
Updated: 6th September, 2020

4.39 seconds
First Contentful Paint (FCP)
11%
43%
46%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
63

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ntt.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 2.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 2.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive ntt.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ntt.com/
0
708.63100001588
328
0
301
text/html
http://www.ntt.com/
709.04300000984
1131.1909999931
316
0
301
https://www.ntt.com/
1131.5900000045
1488.348999992
437
0
302
text/html
https://www.ntt.com/language-selector.html
1488.7549999985
2695.4670000123
1601
6373
200
text/html
Document
https://www.ntt.com/etc/designs/nttcom/cmn/css/MyFontsWebfontsKit.css
2717.9809999652
3081.3220000127
1298
3105
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/style.css
2718.366999994
2760.1019999711
3983
16597
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.css
2718.54599996
2943.8809999847
1711
4115
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/breadcrumb.css
2718.6859999783
2937.3889999697
1501
3280
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/colorbox.css
2719.1579999635
2819.6769999922
1598
4103
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/darktooltip/darktooltip.css
2719.4550000131
2930.2630000166
1944
8248
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
2719.9970000074
2726.9029999734
33674
93100
200
text/javascript
Script
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
2720.1749999658
2757.741999987
62148
228539
200
text/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.js
2720.3159999917
2943.0379999685
12590
52123
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.sweet-scroll.min.js
2720.634999976
2748.8630000153
3750
8306
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.cookie.js
2720.8049999899
2759.3819999602
1880
3254
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/jquery.colorbox.js
2721.137000015
2756.8719999981
9328
29323
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
2721.298999968
2755.1569999778
80281
79852
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/breadcrumb.js
2721.4709999971
2749.8630000046
3364
2938
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/site_search.js
2721.8339999672
2793.7549999915
4799
4372
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/plugin_setting.js
2722.0649999799
2798.0279999902
2529
2103
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/darktooltip/jquery.darktooltip.min.js
2722.202999983
2957.3779999628
1896
4664
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/css/selecter.css
2722.5639999961
2746.8529999605
1032
1518
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/lang_select.js
2722.7079999866
2798.4510000097
2045
1619
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/eloqua.js
2722.8769999929
2791.8799999752
819
551
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/marketo.js
2723.2409999706
2960.802000016
443
20
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/css/new_header.css
2723.387999984
2933.0619999673
1418
2951
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/css/new_header_d.css
2723.6149999662
2933.5759999813
3239
11440
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/js/new_d.js
2723.8270000089
2798.7779999967
6493
6065
200
application/javascript
Script
https://www.ntt.com/content/dam/nttcom/cmn/img/lgo-ntt.png
3013.0379999755
3166.1019999883
41150
40735
200
image/png
Image
https://www.ntt.com/etc/designs/nttcom/cmn/css/mq_tab.css
3083.6559999734
3168.2900000014
2400
7842
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/mq_mbl.css
3171.8439999968
3201.9929999951
1545
3167
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/print.css
3186.2679999904
3558.5570000112
1563
5533
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_reset.css
2770.1799999923
2804.077000008
1162
1318
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_common.css
2770.4490000033
3010.9299999895
5708
26821
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_header.css
2771.391999966
2999.0910000051
1228
2756
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_slidenavi.css
2771.8110000133
2984.5329999807
2688
9511
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_footer.css
2772.106999997
2803.6490000086
1581
4236
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_grid.css
2772.24999998
2990.6859999755
1306
3964
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_diamonds.css
2773.3170000138
3005.0620000111
1065
1236
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_component.css
2773.8039999967
2818.7789999647
9906
62739
200
text/css
Stylesheet
https://hello.myfonts.net/count/3008a0
3083.7969999993
3184.4629999832
339
0
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.cookie.js
3253.1019999878
3283.9169999934
1880
3254
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/84685d94-8066-4f36-9ee9-984794d74e85.woff2
3298.2450000127
3372.6989999996
18244
17932
200
application/octet-stream
Font
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/fdc080c5-29c7-468c-a8a2-beb3c96a769c.woff2
3299.7789999936
3392.3840000061
18424
18112
200
application/octet-stream
Font
https://www.ntt.com/etc/data/nttcom/ctrl/dc.txt
3378.1810000073
3893.8789999811
413
2
200
text/plain
XHR
https://img03.en25.com/i/elqCfg.min.js
3384.0629999759
3706.8020000006
2700
5943
200
application/x-javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/9edf3443-80c6-4de6-b582-122401f63ad4.woff2
3408.5659999982
3488.4939999902
26456
26144
200
application/octet-stream
Font
https://s1595868125.t.eloqua.com/visitor/v200/svrGP?pps=3&siteid=1595868125&ref2=elqNone&tzo=480&ms=627&optin=disabled
3711.5929999854
3736.8969999952
748
0
302
text/html
https://s1595868125.t.eloqua.com/visitor/v200/svrGP.aspx?pps=3&siteid=1595868125&ref2=elqNone&tzo=480&ms=627&optin=disabled&elqCookie=1
3737.5039999606
3826.2779999641
406
49
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
2748.696
10.456
2761.183
8.237
2866.767
5.379
3230.516
64.395
3329.781
94.576
3432.784
5.205
3442.302
7.575
3542.044
5.55
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 30 KiB
Images can slow down the page's load time. Ntt.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/content/dam/nttcom/cmn/img/lgo-ntt.png
40735
30551
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ntt.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ntt.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_component.css
9906
4143
Minify JavaScript — Potential savings of 39 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ntt.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
80281
31393
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.js
12590
5799
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/jquery.colorbox.js
9328
3242
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ntt.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 98 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
62148
55827
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
80281
44164
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 27 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/content/dam/nttcom/cmn/img/lgo-ntt.png
40735
27631
Enable text compression — Potential savings of 70 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
79852
61312
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/js/new_d.js
6065
4346
https://www.ntt.com/etc/designs/nttcom/cmn/js/site_search.js
4372
2763
https://www.ntt.com/etc/designs/nttcom/cmn/js/breadcrumb.js
2938
2057
https://www.ntt.com/etc/designs/nttcom/cmn/js/plugin_setting.js
2103
1474
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ntt.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 378 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
80281
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
62148
https://www.ntt.com/content/dam/nttcom/cmn/img/lgo-ntt.png
41150
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
33674
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/9edf3443-80c6-4de6-b582-122401f63ad4.woff2
26456
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/fdc080c5-29c7-468c-a8a2-beb3c96a769c.woff2
18424
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/84685d94-8066-4f36-9ee9-984794d74e85.woff2
18244
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.js
12590
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_component.css
9906
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/jquery.colorbox.js
9328
Uses efficient cache policy on static assets — 0 resources found
Ntt.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 60 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
60
Maximum DOM Depth
15
Maximum Child Elements
7
Avoid chaining critical requests — 36 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ntt.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
112.901
56.096
3.012
https://www.ntt.com/language-selector.html
53.663
3.973
1.176
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
85.697
Other
75.588
Style & Layout
63.79
Parse HTML & CSS
29.322
Script Parsing & Compilation
19.002
Rendering
11.296
Garbage Collection
2.435
Keep request counts low and transfer sizes small — 49 requests • 378 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
49
387357
Script
17
230619
Font
3
63124
Stylesheet
21
48215
Image
2
41556
Other
5
2242
Document
1
1601
Media
0
0
Third-party
6
100015
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
95822
0
3854
0
339
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00027340513089922
6.5487839083223E-5
6.0628781504187E-6
6.0628781504187E-6
2.5170793765276E-6
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Largest Contentful Paint — 2.3 s
The timing of the largest text or image that is painted.

Opportunities

Avoid multiple page redirects — Potential savings of 530 ms
Redirects can cause additional delays before the page can begin loading. Ntt.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://ntt.com/
0
http://www.ntt.com/
190
https://www.ntt.com/
190
https://www.ntt.com/language-selector.html
150

Metrics

First Contentful Paint — 2.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.6 s
The time taken for the page contents to be visibly populated.

Other

First Meaningful Paint — 2.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,710 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ntt.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.ntt.com/etc/designs/nttcom/cmn/css/MyFontsWebfontsKit.css
1298
70
https://www.ntt.com/etc/designs/nttcom/cmn/css/style.css
3983
150
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.css
1711
150
https://www.ntt.com/etc/designs/nttcom/cmn/css/breadcrumb.css
1501
150
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/colorbox.css
1598
150
https://www.ntt.com/etc/designs/nttcom/cmn/js/darktooltip/darktooltip.css
1944
150
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
33674
470
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
62148
590
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.js
12590
150
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.sweet-scroll.min.js
3750
70
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.cookie.js
1880
70
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/jquery.colorbox.js
9328
110
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
80281
350
https://www.ntt.com/etc/designs/nttcom/cmn/js/breadcrumb.js
3364
70
https://www.ntt.com/etc/designs/nttcom/cmn/js/site_search.js
4799
110
https://www.ntt.com/etc/designs/nttcom/cmn/js/plugin_setting.js
2529
70
https://www.ntt.com/etc/designs/nttcom/cmn/js/darktooltip/jquery.darktooltip.min.js
1896
70
https://www.ntt.com/etc/designs/nttcom/cmn/css/selecter.css
1032
70
https://www.ntt.com/etc/designs/nttcom/cmn/js/lang_select.js
2045
70
https://www.ntt.com/etc/designs/nttcom/cmn/js/eloqua.js
819
70
https://www.ntt.com/etc/designs/nttcom/cmn/js/marketo.js
443
70
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/css/new_header.css
1418
70
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/css/new_header_d.css
3239
70
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/js/new_d.js
6493
110
Reduce initial server response time — Root document took 1,210 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/84685d94-8066-4f36-9ee9-984794d74e85.woff2
74.453999986872
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/fdc080c5-29c7-468c-a8a2-beb3c96a769c.woff2
92.605000012554
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/9edf3443-80c6-4de6-b582-122401f63ad4.woff2
79.927999991924
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ntt.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ntt.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Ntt.com may provide relevant information that dialogue cannot, by using audio descriptions.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
77

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ntt.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.10.2
jQuery UI
1.10.4
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 2 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://ntt.com/
http://www.ntt.com/
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
1
High
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ntt.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ntt.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
44

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of ntt.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ntt.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 2 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://ntt.com/
http://www.ntt.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 67
Performance 43
Accessibility 79
Best Practices 77
SEO 92
Progressive Web App 46
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.ntt.com
Updated: 6th September, 2020

2.38 seconds
First Contentful Paint (FCP)
24%
60%
16%

0.05 seconds
First Input Delay (FID)
85%
11%
4%

Simulate loading on mobile
43

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ntt.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 70 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive ntt.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ntt.com/
0
330.22000000346
312
0
301
text/html
http://www.ntt.com/
331.10599999782
406.39100002591
319
0
301
https://www.ntt.com/
406.65199997602
701.1310000089
430
0
302
text/html
https://www.ntt.com/language-selector.html
701.68399997056
1352.4890000117
1601
6373
200
text/html
Document
https://www.ntt.com/etc/designs/nttcom/cmn/css/MyFontsWebfontsKit.css
1365.3560000239
1446.6450000182
1298
3105
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/style.css
1365.5429999926
1439.5369999693
3983
16597
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/mq_tab.css
1365.6520000077
1534.7649999894
2400
7842
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/mq_mbl.css
1365.9069999703
1393.945000018
1545
3167
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.css
1366.2679999834
1438.3670000243
1711
4115
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/breadcrumb.css
1366.5180000244
1463.9239999815
1501
3280
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/colorbox.css
1366.7380000115
1397.8350000107
1598
4103
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/darktooltip/darktooltip.css
1366.8799999868
1439.0780000249
1944
8248
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
1367.0769999735
1373.6270000227
33674
93100
200
text/javascript
Script
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
1367.3389999894
1377.4429999758
62161
228539
200
text/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.js
1367.6219999907
1442.733999982
12590
52123
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.sweet-scroll.min.js
1367.8589999909
1393.6129999929
3750
8306
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.cookie.js
1368.0199999944
1400.4999999888
1880
3254
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/jquery.colorbox.js
1368.1159999687
1445.905999979
9328
29323
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
1368.4069999726
1430.7799999951
80281
79852
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/breadcrumb.js
1368.5149999801
1393.2570000179
3364
2938
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/site_search.js
1368.627000018
1445.2370000072
4799
4372
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/plugin_setting.js
1368.8379999949
1500.1069999998
2529
2103
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/darktooltip/jquery.darktooltip.min.js
1369.1300000064
1492.7710000193
1896
4664
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/css/selecter.css
1369.4319999777
1459.3250000034
1032
1518
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/lang_select.js
1369.6449999698
1397.4080000189
2045
1619
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/eloqua.js
1369.7730000131
1449.2949999985
819
551
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/js/marketo.js
1370.0090000057
1447.2819999792
443
20
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/css/new_header.css
1370.3860000242
1495.3129999922
1418
2951
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/css/new_header_d.css
1370.523999969
1449.9250000226
3239
11440
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/js/new_d.js
1371.3049999787
1444.2130000098
6493
6065
200
application/javascript
Script
https://www.ntt.com/content/dam/nttcom/cmn/img/lgo-ntt.png
1518.6129999929
1655.9450000059
41150
40735
200
image/png
Image
https://www.ntt.com/etc/designs/nttcom/cmn/css/print.css
1536.0019999789
1649.3129999726
1563
5533
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_reset.css
1441.8530000257
1468.2049999828
1162
1318
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_common.css
1442.0919999829
1468.6430000002
5708
26821
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_header.css
1442.2519999789
1474.6540000197
1228
2756
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_slidenavi.css
1442.5150000025
1470.8559999708
2688
9511
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_footer.css
1443.2369999704
1470.467999985
1581
4236
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_grid.css
1443.3560000034
1517.3780000187
1306
3964
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_diamonds.css
1444.9840000016
1469.8179999832
1065
1236
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_component.css
1445.1220000046
1480.607000005
9906
62739
200
text/css
Stylesheet
https://hello.myfonts.net/count/3008a0
1448.2239999925
1477.8309999965
339
0
200
text/css
Stylesheet
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.cookie.js
1590.6030000187
1616.5349999792
1880
3254
200
application/javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/84685d94-8066-4f36-9ee9-984794d74e85.woff2
1627.582999994
1651.5079999808
18244
17932
200
application/octet-stream
Font
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/fdc080c5-29c7-468c-a8a2-beb3c96a769c.woff2
1628.0329999863
1651.9989999942
18424
18112
200
application/octet-stream
Font
https://www.ntt.com/etc/data/nttcom/ctrl/dc.txt
1677.6930000051
2440.5719999922
413
2
200
text/plain
XHR
https://img03.en25.com/i/elqCfg.min.js
1680.2150000003
2031.6660000244
2700
5943
200
application/x-javascript
Script
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/9edf3443-80c6-4de6-b582-122401f63ad4.woff2
1693.1360000162
1773.8290000125
26456
26144
200
application/octet-stream
Font
https://s1595868125.t.eloqua.com/visitor/v200/svrGP?pps=3&siteid=1595868125&ref2=elqNone&tzo=480&ms=437&optin=disabled
2035.8059999999
2058.956999972
733
0
302
text/html
https://s1595868125.t.eloqua.com/visitor/v200/svrGP.aspx?pps=3&siteid=1595868125&ref2=elqNone&tzo=480&ms=437&optin=disabled&elqCookie=1
2059.5750000211
2181.4219999942
406
49
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1386.803
8.216
1396.527
6.384
1568.447
54.155
1649.686
63.162
1721.369
5.737
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Ntt.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ntt.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ntt.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_component.css
9906
4143
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ntt.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 378 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
80281
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
62161
https://www.ntt.com/content/dam/nttcom/cmn/img/lgo-ntt.png
41150
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
33674
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/9edf3443-80c6-4de6-b582-122401f63ad4.woff2
26456
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/fdc080c5-29c7-468c-a8a2-beb3c96a769c.woff2
18424
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/84685d94-8066-4f36-9ee9-984794d74e85.woff2
18244
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.js
12590
https://www.ntt.com/etc/designs/nttcom/cmn/css/inc/_component.css
9906
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/jquery.colorbox.js
9328
Uses efficient cache policy on static assets — 0 resources found
Ntt.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 60 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
60
Maximum DOM Depth
15
Maximum Child Elements
7
Avoid chaining critical requests — 38 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ntt.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
316.372
191.916
10.272
https://www.ntt.com/language-selector.html
139.396
10.52
3.604
Unattributable
125.512
4.496
0.732
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
91.8
57.336
19.676
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
284.056
Other
213.212
Style & Layout
140.952
Parse HTML & CSS
92.932
Script Parsing & Compilation
67.544
Rendering
11.36
Keep request counts low and transfer sizes small — 49 requests • 378 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
49
387335
Script
17
230632
Font
3
63124
Stylesheet
21
48215
Image
2
41556
Other
5
2207
Document
1
1601
Media
0
0
Third-party
6
100013
Minimize third-party usage — Third-party code blocked the main thread for 100 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
95835
101.796
3839
0
339
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.cookie.js
9930
126
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
7560
108

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Opportunities

Minify JavaScript — Potential savings of 39 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ntt.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
80281
31393
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.js
12590
5799
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/jquery.colorbox.js
9328
3242
Remove unused JavaScript — Potential savings of 98 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
62161
55839
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
80281
44164
Serve images in next-gen formats — Potential savings of 27 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/content/dam/nttcom/cmn/img/lgo-ntt.png
40735
27631
Enable text compression — Potential savings of 70 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
79852
61312
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/js/new_d.js
6065
4346
https://www.ntt.com/etc/designs/nttcom/cmn/js/site_search.js
4372
2763
https://www.ntt.com/etc/designs/nttcom/cmn/js/breadcrumb.js
2938
2057
https://www.ntt.com/etc/designs/nttcom/cmn/js/plugin_setting.js
2103
1474
Preload key requests — Potential savings of 360 ms
Key requests can be preloaded by using '<link rel=preload>'. Ntt.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/84685d94-8066-4f36-9ee9-984794d74e85.woff2
360
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/fdc080c5-29c7-468c-a8a2-beb3c96a769c.woff2
300

Metrics

First Contentful Paint — 6.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 8.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 7.3 s
The timing of the largest text or image that is painted.
Time to Interactive — 7.7 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 6.9 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 6.9 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 13302 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 5,050 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ntt.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.ntt.com/etc/designs/nttcom/cmn/css/MyFontsWebfontsKit.css
1298
180
https://www.ntt.com/etc/designs/nttcom/cmn/css/style.css
3983
630
https://www.ntt.com/etc/designs/nttcom/cmn/css/mq_tab.css
2400
480
https://www.ntt.com/etc/designs/nttcom/cmn/css/mq_mbl.css
1545
480
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.css
1711
480
https://www.ntt.com/etc/designs/nttcom/cmn/css/breadcrumb.css
1501
480
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/colorbox.css
1598
180
https://www.ntt.com/etc/designs/nttcom/cmn/js/darktooltip/darktooltip.css
1944
180
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
33674
2130
https://ajax.googleapis.com/ajax/libs/jqueryui/1/jquery-ui.min.js
62161
2430
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.bxslider/jquery.bxslider.js
12590
780
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.sweet-scroll.min.js
3750
330
https://www.ntt.com/etc/designs/nttcom/cmn/js/jquery.cookie.js
1880
180
https://www.ntt.com/etc/designs/nttcom/cmn/js/colorbox/jquery.colorbox.js
9328
630
https://www.ntt.com/etc/designs/nttcom/cmn/js/common.js
80281
1680
https://www.ntt.com/etc/designs/nttcom/cmn/js/breadcrumb.js
3364
330
https://www.ntt.com/etc/designs/nttcom/cmn/js/site_search.js
4799
330
https://www.ntt.com/etc/designs/nttcom/cmn/js/plugin_setting.js
2529
180
https://www.ntt.com/etc/designs/nttcom/cmn/js/darktooltip/jquery.darktooltip.min.js
1896
180
https://www.ntt.com/etc/designs/nttcom/cmn/css/selecter.css
1032
180
https://www.ntt.com/etc/designs/nttcom/cmn/js/lang_select.js
2045
180
https://www.ntt.com/etc/designs/nttcom/cmn/js/eloqua.js
819
180
https://www.ntt.com/etc/designs/nttcom/cmn/js/marketo.js
443
180
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/css/new_header.css
1418
180
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/css/new_header_d.css
3239
330
https://www.ntt.com/etc/designs/nttcom/hq/jp/global_parts/js/new_d.js
6493
330
Reduce initial server response time — Root document took 650 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 1,740 ms
Redirects can cause additional delays before the page can begin loading. Ntt.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://ntt.com/
0
http://www.ntt.com/
630
https://www.ntt.com/
630
https://www.ntt.com/language-selector.html
480

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/84685d94-8066-4f36-9ee9-984794d74e85.woff2
23.924999986775
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/fdc080c5-29c7-468c-a8a2-beb3c96a769c.woff2
23.966000007931
https://www.ntt.com/etc/designs/nttcom/cmn/fonts/9edf3443-80c6-4de6-b582-122401f63ad4.woff2
80.692999996245
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ntt.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ntt.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Ntt.com may provide relevant information that dialogue cannot, by using audio descriptions.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
77

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ntt.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.10.2
jQuery UI
1.10.4
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 2 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://ntt.com/
http://www.ntt.com/
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
1
High
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ntt.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ntt.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
46

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of ntt.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ntt.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 2 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://ntt.com/
http://www.ntt.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 61.113.104.9
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Japan Network Information Center
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Japan Registry Services Co.,Ltd.(JPRS) 117.104.133.164
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 4.3/5 (2 reviews)
WOT Trustworthiness: 86/100
WOT Child Safety: 90/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.ntt.com
Issued By: DigiCert SHA2 Extended Validation Server CA
Valid From: 13th November, 2019
Valid To: 11th February, 2022
Subject: CN = www.ntt.com
O = NTT Communications Corporation
L = Chiyoda-ku
S = JP
Hash: 7483e4e3
Issuer: CN = DigiCert SHA2 Extended Validation Server CA
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 21112710239805507758226511674835020220
Serial Number (Hex): 0FE228FB6210E65437F6B271F1FD29BC
Valid From: 13th November, 2024
Valid To: 11th February, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:3D:D3:50:A5:D6:A0:AD:EE:F3:4A:60:0A:65:D3:21:D4:F8:F8:D6:0F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/sha2-ev-server-g2.crl

Full Name:
URI:http://crl4.digicert.com/sha2-ev-server-g2.crl

Certificate Policies: Policy: 2.16.840.1.114412.2.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.1

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2ExtendedValidationServerCA.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A4:B9:09:90:B4:18:58:14:87:BB:13:A2:CC:67:70:0A:
3C:35:98:04:F9:1B:DF:B8:E3:77:CD:0E:C8:0D:DC:10
Timestamp : Nov 13 08:58:51.279 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:89:C3:52:7D:05:59:93:73:4C:E9:24:
E7:C8:FA:B5:BF:D4:0E:85:D7:C6:2B:42:50:6F:4A:47:
71:32:AE:50:F3:02:21:00:CB:A5:E6:A3:A2:88:0D:BD:
3B:6C:5A:1A:07:80:C8:9D:57:45:76:74:F7:5F:7E:1C:
74:06:C2:74:54:E1:48:44
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 56:14:06:9A:2F:D7:C2:EC:D3:F5:E1:BD:44:B2:3E:C7:
46:76:B9:BC:99:11:5C:C0:EF:94:98:55:D6:89:D0:DD
Timestamp : Nov 13 08:58:51.501 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E4:5B:29:7D:A2:29:A5:07:61:29:BC:
7F:D4:22:21:4E:22:A6:F5:AA:DA:30:27:E1:8E:7D:78:
40:FD:DC:52:E3:02:21:00:B1:09:B0:2D:53:D9:EF:E7:
13:72:B6:D6:B7:9A:96:62:41:19:C1:B7:78:DE:85:28:
DA:1E:F7:3F:92:3A:45:EA
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : EE:4B:BD:B7:75:CE:60:BA:E1:42:69:1F:AB:E1:9E:66:
A3:0F:7E:5F:B0:72:D8:83:00:C4:7B:89:7A:A8:FD:CB
Timestamp : Nov 13 08:58:51.335 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:81:98:81:E8:54:93:89:D9:FF:7E:CD:
6D:20:BB:F2:5A:8C:1F:A8:CC:E8:52:6A:F0:A8:1B:A1:
FA:FE:08:C8:E9:02:20:68:48:6E:9E:6E:EA:FB:A1:73:
8B:7C:42:2A:B7:E4:A5:21:81:22:A6:09:86:9D:FD:4E:
BD:5F:0C:A8:EE:B7:21
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:au.query.ntt.com
DNS:br.query.ntt.com
DNS:cn.query.ntt.com
DNS:eu.query.ntt.com
DNS:hk.query.ntt.com
DNS:id.query.ntt.com
DNS:in.query.ntt.com
DNS:kr.query.ntt.com
DNS:my.query.ntt.com
DNS:ntt.com
DNS:ru.query.ntt.com
DNS:sg.query.ntt.com
DNS:th.query.ntt.com
DNS:tw.query.ntt.com
DNS:us.query.ntt.com
DNS:vn.query.ntt.com
DNS:www.au.ntt.com
DNS:www.br.ntt.com
DNS:www.cn.ntt.com
DNS:www.eu.ntt.com
DNS:www.glc.ntt.com
DNS:www.hk.ntt.com
DNS:www.id.ntt.com
DNS:www.in.ntt.com
DNS:www.kr.ntt.com
DNS:www.my.ntt.com
DNS:www.ru.ntt.com
DNS:www.sg.ntt.com
DNS:www.th.ntt.com
DNS:www.tw.ntt.com
DNS:www.us.ntt.com
DNS:www.vn.ntt.com
DNS:www.ntt.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
ntt.com. 61.113.104.9 IN 299

NS Records

Host Nameserver Class TTL
ntt.com. pns.ocn.ad.jp. IN 21599
ntt.com. ns-os001.ocn.ad.jp. IN 21599

MX Records

Priority Host Server Class TTL
10 ntt.com. cmcodfcs03.noc.ntt.com. IN 21599
10 ntt.com. cmcodfcs01.noc.ntt.com. IN 21599
10 ntt.com. cmcodfcs02.noc.ntt.com. IN 21599

SOA Records

Domain Name Primary NS Responsible Email TTL
ntt.com. pns.ocn.ad.jp. root.ntt.net. 21599

TXT Records

Host Value Class TTL
ntt.com. v=spf1 IN 599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: Apache
Content-Type: text/html; charset=UTF-8
Expires: 6th September, 2020
Cache-Control: max-age=0, no-cache, no-store
Date: 6th September, 2020
X-Powered-By: PHP/7.2.28
X-FRAME-OPTIONS: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Pragma: no-cache
Content-Length: 0
Connection: keep-alive

Whois Lookup

Created: 7th October, 1997
Changed: 19th February, 2020
Expires: 6th October, 2025
Registrar: Japan Registry Services Co.,Ltd.(JPRS)
Status: clientTransferProhibited
Nameservers: ns-os001.ocn.ad.jp
pns.ocn.ad.jp
Owner Name: NTT Communications Corporation
Owner Street: 3-1 otemachi 2-chome otemachi place west
Owner Post Code: 1008019
Owner City: Chiyoda-ku
Owner State: Tokyo
Owner Country: JP
Owner Phone: +99.99999999
Owner Email: domain-contact-pandk@NTT.COM
Admin Name: Hidehisa Maruyama
Admin Street: 3-1 otemachi 2-chome otemachi place west
Admin Post Code: 1008019
Admin City: Chiyoda-ku
Admin State: Tokyo
Admin Country: JP
Admin Phone: +36.7009450
Admin Email: domain-contact-pandk@NTT.COM
Tech Name: Hidehisa Maruyama
Tech Street: 3-1 otemachi 2-chome otemachi place west
Tech Post Code: 1008019
Tech City: Chiyoda-ku
Tech State: Tokyo
Tech Country: JP
Tech Phone: +36.7009450
Tech Email: domain-contact-pandk@NTT.COM
Full Whois: Domain Name: NTT.COM
Registry Domain ID: 533056_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.jprs.jp
Registrar URL: https://jprs.jp/registrar/
Updated Date: 2020-02-19T15:25:10Z
Creation Date: 1997-10-07T04:00:00Z
Registrar Registration Expiration Date: 2025-10-06T04:00:00Z
Registrar: Japan Registry Services Co.,Ltd.(JPRS)
Registrar IANA ID: 1485
Registrar Abuse Contact Email: gtld-abuse@jprs.jp
Registrar Abuse Contact Phone: +81.352158457
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: NTT Communications Corporation
Registrant Street: 3-1 otemachi 2-chome otemachi place west
Registrant City: Chiyoda-ku
Registrant State/Province: Tokyo
Registrant Postal Code: 1008019
Registrant Country: JP
Registrant Phone: +99.99999999
Registrant Email: domain-contact-pandk@NTT.COM
Registry Admin ID: Not Available From Registry
Admin Name: Hidehisa Maruyama
Admin Street: 3-1 otemachi 2-chome otemachi place west
Admin City: Chiyoda-ku
Admin State/Province: Tokyo
Admin Postal Code: 1008019
Admin Country: JP
Admin Phone: +36.7009450
Admin Email: domain-contact-pandk@NTT.COM
Registry Tech ID: Not Available From Registry
Tech Name: Hidehisa Maruyama
Tech Street: 3-1 otemachi 2-chome otemachi place west
Tech City: Chiyoda-ku
Tech State/Province: Tokyo
Tech Postal Code: 1008019
Tech Country: JP
Tech Phone: +36.7009450
Tech Email: domain-contact-pandk@NTT.COM
Name Server: NS-OS001.OCN.AD.JP
Name Server: PNS.OCN.AD.JP
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2020-09-06T03:08:32Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

JPRS WHOIS LEGAL DISCLAIMER:

The WHOIS service (the "Service") offered by Japan Registry Services Co.,Ltd. (JPRS) and the access to the records in the JPRS WHOIS database (the "Database") are provided for information purposes and query-based public access.

Neither JPRS nor any of its officers, directors, employees or agents makes any warranty as to the results to be obtained from use of the Service. JPRS specifically disclaims all warranties of any kind, whether express, implied or statutory, including, but not limited to, any warranties of title, non-infringement, merchantability or fitness for a particular purpose.
In no event shall JPRS nor anyone else involved in creating, supporting, producing or delivering the Service be liable to you for any lost profits or costs, even if JPRS or such person has been advised of the possibility of such damages.

JPRS allows you to use the Service only for lawful purposes and that, under no circumstances shall you use the Service to: (a) allow, enable or otherwise support the transmission by e-mail, telephone, postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of any registry operator or ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations.

By submitting the query you agree to abide by these terms and further agree that JPRS may take measures to limit the use of the Service in order to protect the privacy of its registrants or the integrity of the Database.

JPRS reserves the right to modify or change these terms at any time without prior or subsequent notification of any kind.

For further information, use 'whois -h whois.jprs.jp help'. To express Japanese output, add '/j' at the end of command, e.g. 'whois -h whois.jprs.jp xxx/j'.

Nameservers

Name IP Address
ns-os001.ocn.ad.jp 203.139.161.37
pns.ocn.ad.jp 203.139.160.19
Related

Subdomains

Domain Subdomain
eu
my
us

Similar Sites

Domain Valuation Snoop Score
$10 USD 1/5
$252,142 USD 3/5
$35,638 USD 2/5
$41,328 USD 2/5
$13,836 USD 3/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$3,705 USD 2/5
$7,844 USD 2/5
$10 USD 1/5

Sites hosted on the same IP address