docs.com

docs.com may not be SSL secured

Free website and domain report on docs.com

Last Updated: 8th August, 2021 Update Now
Overview

Snoop Summary for docs.com

This is a free and comprehensive report about docs.com. Docs.com is hosted in Washington, Virginia in United States on a server with an IP address of 20.49.104.24, where the local currency is USD and English is the local language. Docs.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If docs.com was to be sold it would possibly be worth $1,004 USD (based on the daily revenue potential of the website over a 24 month period). Docs.com receives an estimated 478 unique visitors every day - a decent amount of traffic! This report was last updated 8th August, 2021.

About docs.com

Site Preview: docs.com docs.com
Title: Docs Inc.
Description: Offers Soapware, an electronic medical record system for patient records. Includes support and newsletter.
Keywords and Tags: technical information
Related Terms: docs, docs jpa gov my, google docs, post docs, read the docs, sync docs
Fav Icon:
Age: Over 29 years old
Domain Created: 7th March, 1995
Domain Updated: 5th February, 2021
Domain Expires: 8th March, 2022
Review

Snoop Score

1/5

Valuation

$1,004 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,487,594
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: 478
Monthly Visitors: 14,547
Yearly Visitors: 174,453
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $41 USD
Yearly Revenue: $497 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: docs.com 8
Domain Name: docs 4
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.61 seconds
Load Time Comparison: Faster than 32% of sites

PageSpeed Insights

Avg. (All Categories) 80
Performance 78
Accessibility 98
Best Practices 87
SEO 100
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://docs.microsoft.com/en-us/
Updated: 8th August, 2021

1.33 seconds
First Contentful Paint (FCP)
83%
9%
8%

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

Simulate loading on desktop
78

Performance

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

Metrics

Time to Interactive — 1.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 40 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

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Docs.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Docs.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 3 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Docs.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://docs.microsoft.com/static/third-party/jsll/4.3.4/jsll-4.js
20377
3101
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 219 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
198074
119804
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
143727
79241
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
62488
24962
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 100 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://docs.microsoft.com/en-us/
98.112
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.
Remove duplicate modules in JavaScript bundles — Potential savings of 18 KiB
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Source Transfer Size (Bytes) Potential Savings (Bytes)
node_modules/@microsoft/applicationinsights-core-js
5907
node_modules/@microsoft/applicationinsights-dependencies-js
4483
node_modules/@microsoft/applicationinsights-analytics-js
3543
node_modules/@microsoft/applicationinsights-common
2924
Other
1359
Avoid serving legacy JavaScript to modern browsers — Potential savings of 26 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
18825
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
7866
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 1,217 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
382702
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
198899
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
144551
https://docs.microsoft.com/static/third-party/SegoeUIWeb/1.01.206/SegoeUI-Roman-VF_web.woff2
119174
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
70148
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
63310
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
54904
https://docs.microsoft.com/en-us/
50424
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
32182
https://docs.microsoft.com/en-us/media/home-and-directory/docs-and-friends-selfie-stick.png?branch=master
20517
Avoids an excessive DOM size — 572 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
572
Maximum DOM Depth
20
Maximum Child Elements
g
68
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Docs.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 — 5 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
at-request-start
Mark
955.45
at-library-loaded
Mark
957.869
at-request-succeeded
Mark
1391.128
at-content-rendering-start
Mark
1394.666
at-content-rendering-succeeded
Mark
1398.532
JavaScript execution time — 0.2 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://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
148.793
78.75
33.506
https://docs.microsoft.com/en-us/
148.77
62.333
1.887
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
73.79
61.285
2.062
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
67.553
2.279
1.13
Unattributable
61.617
2.938
0.151
Minimizes main-thread work — 0.6 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
276.611
Style & Layout
120.369
Other
100.741
Script Parsing & Compilation
50.702
Parse HTML & CSS
40.754
Rendering
21.994
Keep request counts low and transfer sizes small — 31 requests • 1,217 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
31
1246093
Script
11
547655
Image
8
439696
Font
2
132554
Stylesheet
1
70148
Document
1
50424
Other
8
5616
Media
0
0
Third-party
8
91252
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)
20969
0
12915
0
716
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
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'.
Avoid long main-thread tasks — 1 long task 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://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
1820
133
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

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.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://docs.com/
http/1.1
0
89.833999983966
380
0
301
text/html
https://docs.com/
http/1.1
90.498000005027
267.80599998892
281
0
301
text/html
https://docs.microsoft.com/
http/1.1
268.42599999509
590.30799998436
1242
0
301
https://docs.microsoft.com/en-us/
h2
591.01800000644
688.13199998112
50424
126805
200
text/html
Document
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
h2
708.73300000676
851.95399998338
70148
493155
200
text/css
Stylesheet
https://wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js
h2
709.09699998447
827.06199999666
13539
52715
200
application/javascript
Script
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
h2
710.11899999576
827.83100000233
54904
179518
200
text/javascript
Script
https://docs.microsoft.com/static/third-party/jsll/4.3.4/jsll-4.js
h2
710.7079999987
799.54899998847
20377
65764
200
application/x-javascript
Script
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
h2
710.90999999433
757.89899998927
4764
10063
200
application/javascript
Script
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/global/93ae22c4.at-config.js
h2
711.09500000603
790.7300000079
4576
11299
200
application/javascript
Script
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
h2
711.301000003
870.91299999156
32182
93986
200
application/x-javascript
Script
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
h2
711.70899999561
823.99999999325
382702
1668388
200
application/javascript
Script
https://docs.microsoft.com/en-us/media/home-and-directory/docs-and-friends-selfie-stick.png?branch=master
h2
916.52199998498
964.83099999023
20517
19693
200
image/png
Image
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
h2
974.62399999495
1015.4920000059
63310
62488
200
image/png
Image
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
h2
1097.8529999848
1156.9009999803
198899
198074
200
image/png
Image
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
h2
1098.0390000041
1184.1919999861
144551
143727
200
image/png
Image
https://docs.microsoft.com/en-us/media/home-and-directory/startups-icon.svg?branch=master
h2
1098.1859999883
1125.6419999991
1837
3075
200
image/svg+xml
Image
https://docs.microsoft.com/en-us/media/home-and-directory/students-icon.svg?branch=master
h2
1098.5069999879
1123.1379999954
5632
12587
200
image/svg+xml
Image
https://docs.microsoft.com/en-us/media/home-and-directory/learn-tv-icon.svg?branch=master
h2
1098.6409999896
1124.8719999858
4078
9697
200
image/svg+xml
Image
https://target.microsoft.com/rest/v1/delivery?client=microsoftmscompoc&sessionId=daa1460fac1b42e28e0dcc4e620261e1&version=2.4.0
h2
973.55399999651
1379.3249999871
552
223
200
application/json
XHR
data
1111.8940000015
1112.546999997
0
36843
200
image/svg+xml
Image
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/docons.66501339.woff2
h2
1123.8019999873
1148.7029999844
13380
12568
200
application/font-woff2
Font
https://docs.microsoft.com/static/third-party/SegoeUIWeb/1.01.206/SegoeUI-Roman-VF_web.woff2
h2
1127.0739999891
1187.7939999977
119174
118288
200
application/octet-stream
Font
https://web.vortex.data.microsoft.com/collect/v1/t.js?ver=%272.1%27&name=%27Ms.Webi.PageView%27&time=%272021-08-08T22%3A40%3A30.937Z%27&os=%27MacOS%27&appId=%27JS%3ADocs%27&-ver=%271.0%27&-impressionGuid=%27ca9be0b0-539a-4d9e-88d6-0cdaaf46cebd%27&-pageName=%279ef1269a-9151-6be5-4abe-8a06e1936746%27&-uri=%27https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2F%27&-market=%27en-us%27&-pageType=%27welcome%27&-resHeight=600&-resWidth=800&-pageTags=%27%7B%22author%22%3A%22wibjorn%22%2C%22depotname%22%3A%22MSDN.DocsCoreContent%22%2C%22document_version_independent_id%22%3A%22568a65ba-5905-2775-c30c-f5412d9c68c3%22%2C%22gitcommit%22%3A%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDocsRoot%2Fblob%2F867645739294541e3efb97b2b7e8f70b23ae5299%2FDocsCoreContent%2Findex.yml%22%2C%22pgtop%22%3A%22hub-page%22%2C%22translationtype%22%3A%22HT%22%2C%22giturl%22%3A%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDocsRoot%2Fblob%2Flive%2FDocsCoreContent%2Findex.yml%22%2C%22publishtime%22%3A%222021-01-19%2010%3A50%20PM%22%2C%22contentlocale%22%3A%22en-us%22%2C%22highContrast%22%3A%22false%22%2C%22metaTags%22%3A%7B%7D%7D%27&-behavior=0&*baseType=%27Ms.Content.PageView%27&*cookieEnabled=true&*isJs=true&*title=%27Developer%20tools%2C%20technical%20documentation%20and%20coding%20examples%20%7C%20Microsoft%20Docs%27&*isLoggedIn=false&*flashInstalled=false&ext-javascript-ver=%271.1%27&ext-javascript-libVer=%274.3.4%27&ext-javascript-domain=%27docs.microsoft.com%27&ext-javascript-userConsent=true&$mscomCookies=false
http/1.1
1227.3749999877
1502.2989999852
966
281
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1228.9809999929
1234.1739999829
20323
49389
200
text/javascript
Script
https://w.usabilla.com/cd99660205c0.js?lv=1
h2
1274.4470000034
1293.7349999847
12915
54091
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j92&aip=1&a=1604324926&t=pageview&_s=1&dl=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2F&ul=en-us&de=UTF-8&dt=Developer%20tools%2C%20technical%20documentation%20and%20coding%20examples%20%7C%20Microsoft%20Docs&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAEABAAAAAC~&jid=1708440743&gjid=937199643&cid=566405345.1628462431&tid=UA-62780441-21&_gid=1643021191.1628462431&_r=1&_slc=1&cd2=off&cd3=Welcome&z=1957751752
h2
1354.8500000034
1382.7199999942
646
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j92&tid=UA-62780441-21&cid=566405345.1628462431&jid=1708440743&gjid=937199643&_gid=1643021191.1628462431&_u=YEBAAEAAAAAAAC~&z=950689237
h2
1399.2689999868
1403.0930000008
716
1
200
text/plain
XHR
https://web.vortex.data.microsoft.com/collect/v1/t.js?ver=%272.1%27&name=%27Ms.Webi.ContentUpdate%27&time=%272021-08-08T22%3A40%3A31.247Z%27&os=%27MacOS%27&appId=%27JS%3ADocs%27&-ver=%271.0%27&-impressionGuid=%27ca9be0b0-539a-4d9e-88d6-0cdaaf46cebd%27&-pageName=%279ef1269a-9151-6be5-4abe-8a06e1936746%27&-uri=%27https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2F%27&-market=%27en-us%27&-pageTags=%27%7B%22author%22%3A%22wibjorn%22%2C%22depotname%22%3A%22MSDN.DocsCoreContent%22%2C%22document_version_independent_id%22%3A%22568a65ba-5905-2775-c30c-f5412d9c68c3%22%2C%22gitcommit%22%3A%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDocsRoot%2Fblob%2F867645739294541e3efb97b2b7e8f70b23ae5299%2FDocsCoreContent%2Findex.yml%22%2C%22pgtop%22%3A%22hub-page%22%2C%22translationtype%22%3A%22HT%22%2C%22giturl%22%3A%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDocsRoot%2Fblob%2Flive%2FDocsCoreContent%2Findex.yml%22%2C%22publishtime%22%3A%222021-01-19%2010%3A50%20PM%22%2C%22contentlocale%22%3A%22en-us%22%2C%22highContrast%22%3A%22false%22%2C%22metaTags%22%3A%7B%7D%2C%22timing%22%3A%22%7B%5C%22first-paint%5C%22%3A1264.6349999995437%2C%5C%22first-contentful-paint%5C%22%3A1264.6349999995437%2C%5C%22navigationStart%5C%22%3A1628462429712%2C%5C%22unloadEventStart%5C%22%3A0%2C%5C%22unloadEventEnd%5C%22%3A0%2C%5C%22redirectStart%5C%22%3A0%2C%5C%22redirectEnd%5C%22%3A0%2C%5C%22fetchStart%5C%22%3A1628462430304%2C%5C%22domainLookupStart%5C%22%3A1628462430304%2C%5C%22domainLookupEnd%5C%22%3A1628462430304%2C%5C%22connectStart%5C%22%3A1628462430304%2C%5C%22connectEnd%5C%22%3A1628462430304%2C%5C%22secureConnectionStart%5C%22%3A0%2C%5C%22requestStart%5C%22%3A1628462430304%2C%5C%22responseStart%5C%22%3A1628462430402%2C%5C%22responseEnd%5C%22%3A1628462430402%2C%5C%22domLoading%5C%22%3A1628462430407%2C%5C%22domInteractive%5C%22%3A1628462430816%2C%5C%22domContentLoadedEventStart%5C%22%3A1628462430817%2C%5C%22domContentLoadedEventEnd%5C%22%3A1628462430951%2C%5C%22domComplete%5C%22%3A1628462431218%2C%5C%22loadEventStart%5C%22%3A1628462431218%2C%5C%22loadEventEnd%5C%22%3A1628462431236%7D%22%7D%27&-pageHeight=2190&-vpHeight=940&-vpWidth=1350&-behavior=0&-vScrollOffset=0&-hScrollOffset=0&-contentVer=%272.0%27&-content=%27%5B%5D%27&*baseType=%27Ms.Content.ContentUpdate%27&*title=%27Developer%20tools%2C%20technical%20documentation%20and%20coding%20examples%20%7C%20Microsoft%20Docs%27&*cookieEnabled=true&*isJs=true&*isDomComplete=true&*isLoggedIn=false&*pageLoadTime=1506&ext-javascript-ver=%271.1%27&ext-javascript-libVer=%274.3.4%27&ext-javascript-domain=%27docs.microsoft.com%27&ext-javascript-msfpc=%27GUID%3D0659f8fc2ba3453b9cb5f791e432c77c%26HASH%3D0659%26LV%3D202108%26V%3D4%26LU%3D1628462431182%27&ext-javascript-userConsent=true&$mscomCookies=false
http/1.1
1535.9069999831
1840.7920000027
407
45
200
application/javascript
Script
https://c1.microsoft.com/c.gif?DI=4050&did=1&t=
http/1.1
1536.2889999815
1567.9630000086
712
0
302
https://c.bing.com/c.gif?DI=4050&did=1&t=&ctsa=mr&CtsSyncId=B4049DAD90DB4359883B0AF3CFC7EB0D&RedC=c1.microsoft.com&MXFR=25CD6F23370168910DE07FAE33016E20
http/1.1
1568.2459999807
1591.8200000015
1087
0
302
https://c1.microsoft.com/c.gif?DI=4050&did=1&t=&ctsa=mr&CtsSyncId=B4049DAD90DB4359883B0AF3CFC7EB0D&MUID=25CD6F23370168910DE07FAE33016E20
h2
1592.187000002
1706.5599999914
872
42
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)
698.578
10.161
860.769
23.301
885.116
37.26
923.317
56.776
980.431
265.642
1268.339
12.286
1282.957
7.141
1290.449
43.745
1337.032
24.615
1386.412
17.162
1405.848
8.921
1511.488
19.026
1537.061
5.664
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Speed Index — 1.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.4 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.

Opportunities

Properly size images — Potential savings of 329 KiB
Images can slow down the page's load time. Docs.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
198074
156935
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
143727
113886
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
62488
49510
https://docs.microsoft.com/en-us/media/home-and-directory/docs-and-friends-selfie-stick.png?branch=master
19693
16129
Reduce unused CSS — Potential savings of 65 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Docs.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
70148
66311
Reduce unused JavaScript — Potential savings of 346 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://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
382702
311251
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
54904
43503
Avoid multiple page redirects — Potential savings of 570 ms
Redirects can cause additional delays before the page can begin loading. Docs.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://docs.com/
190
https://docs.com/
150
https://docs.microsoft.com/
230
https://docs.microsoft.com/en-us/
0
Preload key requests — Potential savings of 430 ms
Key requests can be preloaded by using '<link rel=preload>'. Docs.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/docons.66501339.woff2
430
https://docs.microsoft.com/static/third-party/SegoeUIWeb/1.01.206/SegoeUI-Roman-VF_web.woff2
190

Metrics

First Contentful Paint — 1.8 s
The time taken for the first image or text on the page to be rendered.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 1,160 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Docs.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://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
70148
350
https://wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js
13539
310
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
54904
470
https://docs.microsoft.com/static/third-party/jsll/4.3.4/jsll-4.js
20377
270
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
4764
150
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/global/93ae22c4.at-config.js
4576
150
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
32182
310
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
382702
830

Diagnostics

Serve static assets with an efficient cache policy — 15 resources found
Docs.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
58000
63310
https://docs.microsoft.com/en-us/media/home-and-directory/learn-tv-icon.svg?branch=master
315000
4078
https://docs.microsoft.com/en-us/media/home-and-directory/students-icon.svg?branch=master
467000
5632
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
494000
144551
https://docs.microsoft.com/en-us/media/home-and-directory/startups-icon.svg?branch=master
1073000
1837
https://docs.microsoft.com/en-us/media/home-and-directory/docs-and-friends-selfie-stick.png?branch=master
1206000
20517
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
1242000
198899
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
1800000
54904
https://www.google-analytics.com/analytics.js
7200000
20323
https://wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js
43200000
13539
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
172139000
70148
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
219270000
4764
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/docons.66501339.woff2
219310000
13380
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
421920000
382702
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/global/93ae22c4.at-config.js
572860000
4576
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://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/docons.66501339.woff2
24.900999997044
https://docs.microsoft.com/static/third-party/SegoeUIWeb/1.01.206/SegoeUI-Roman-VF_web.woff2
60.720000008587
Avoid `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.
Source
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of docs.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.
Heading elements appear 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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Docs.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

Some elements have 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.
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.
87

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

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
core-js
core-js-global@3.16.0
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
https://js.monitor.azure.com/scripts/c/ms.jsll-3.1.4.min.js.map
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js.map
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request 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 Request Resolution
http://docs.com/
Allowed

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for docs.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 docs.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.
Document has 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.
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.

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.
36

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 docs.com. This includes details about web app manifests.

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 docs.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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.
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) 76
Performance 52
Accessibility 98
Best Practices 87
SEO 99
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://docs.microsoft.com/en-us/
Updated: 8th August, 2021

2.47 seconds
First Contentful Paint (FCP)
63%
19%
18%

0.01 seconds
First Input Delay (FID)
95%
3%
2%

Simulate loading on mobile
52

Performance

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

Metrics

Total Blocking Time — 40 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

Opportunities

Properly size images
Images can slow down the page's load time. Docs.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Docs.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Docs.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 3 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Docs.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://docs.microsoft.com/static/third-party/jsll/4.3.4/jsll-4.js
20377
3101
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 420 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://docs.microsoft.com/en-us/
419.102
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.
Remove duplicate modules in JavaScript bundles — Potential savings of 18 KiB
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Source Transfer Size (Bytes) Potential Savings (Bytes)
node_modules/@microsoft/applicationinsights-core-js
5907
node_modules/@microsoft/applicationinsights-dependencies-js
4483
node_modules/@microsoft/applicationinsights-analytics-js
3543
node_modules/@microsoft/applicationinsights-common
2924
Other
1359
Avoid serving legacy JavaScript to modern browsers — Potential savings of 26 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
18825
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
7866
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 1,217 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
382702
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
198899
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
144552
https://docs.microsoft.com/static/third-party/SegoeUIWeb/1.01.206/SegoeUI-Roman-VF_web.woff2
119174
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
70148
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
63312
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
54904
https://docs.microsoft.com/en-us/
50450
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
32182
https://docs.microsoft.com/en-us/media/home-and-directory/docs-and-friends-selfie-stick.png?branch=master
20517
Avoids an excessive DOM size — 544 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
544
Maximum DOM Depth
20
Maximum Child Elements
g
68
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Docs.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 — 5 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
at-request-start
Mark
1047.821
at-library-loaded
Mark
1050.647
at-request-succeeded
Mark
1490.144
at-content-rendering-start
Mark
1495.464
at-content-rendering-succeeded
Mark
1499.966
Keep request counts low and transfer sizes small — 31 requests • 1,217 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
31
1246119
Script
11
547656
Image
8
439699
Font
2
132554
Stylesheet
1
70148
Document
1
50450
Other
8
5612
Media
0
0
Third-party
8
91261
Minimize third-party usage — Third-party code blocked the main thread for 90 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)
20969
91.636
12916
0
716
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
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'.
Avoid long main-thread tasks — 5 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://wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js
6450
766
https://www.google-analytics.com/analytics.js
8446
102
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
3450
97
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
7996
79
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
7216
60
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

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.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://docs.com/
http/1.1
0
42.058999999426
395
0
301
text/html
https://docs.com/
http/1.1
42.727999971248
165.13099998701
274
0
301
text/html
https://docs.microsoft.com/
http/1.1
165.90399993584
289.74399995059
1231
0
301
https://docs.microsoft.com/en-us/
h2
290.53200001363
708.63699994516
50450
126805
200
text/html
Document
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
h2
729.01899996214
933.48100001458
70148
493155
200
text/css
Stylesheet
https://wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js
h2
729.4019999681
760.70400001481
13539
52715
200
application/javascript
Script
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
h2
729.5869999798
840.85999999661
54904
179518
200
text/javascript
Script
https://docs.microsoft.com/static/third-party/jsll/4.3.4/jsll-4.js
h2
729.86999992281
757.05100002233
20377
65764
200
application/x-javascript
Script
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
h2
730.09999992792
830.86600003298
4764
10063
200
application/javascript
Script
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/global/93ae22c4.at-config.js
h2
730.28899997007
759.61700000335
4576
11299
200
application/javascript
Script
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
h2
730.41099996772
765.54299995769
32182
93986
200
application/x-javascript
Script
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
h2
730.76900001615
797.63099993579
382702
1668388
200
application/javascript
Script
https://docs.microsoft.com/en-us/media/home-and-directory/docs-and-friends-selfie-stick.png?branch=master
h2
877.68799997866
913.30299992114
20517
19693
200
image/png
Image
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
h2
915.2339999564
943.60200001393
63312
62488
200
image/png
Image
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
h2
936.95699993987
967.42400003131
198899
198074
200
image/png
Image
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
h2
962.65400003176
1181.8770000245
144552
143727
200
image/png
Image
https://docs.microsoft.com/en-us/media/home-and-directory/startups-icon.svg?branch=master
h2
1204.1879999451
1229.4710000278
1837
3075
200
image/svg+xml
Image
https://docs.microsoft.com/en-us/media/home-and-directory/students-icon.svg?branch=master
h2
1204.3739999644
1228.6760000279
5632
12587
200
image/svg+xml
Image
https://docs.microsoft.com/en-us/media/home-and-directory/learn-tv-icon.svg?branch=master
h2
1204.5709999511
1230.0479999976
4078
9697
200
image/svg+xml
Image
https://target.microsoft.com/rest/v1/delivery?client=microsoftmscompoc&sessionId=dd7e290d2c7f456ba49f5c08fcd7a21a&version=2.4.0
h2
1060.6039999984
1431.4839999424
551
223
200
application/json
XHR
data
1218.8989999704
1219.5069999434
0
36843
200
image/svg+xml
Image
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/docons.66501339.woff2
h2
1229.3409999693
1255.9109999565
13380
12568
200
application/font-woff2
Font
https://docs.microsoft.com/static/third-party/SegoeUIWeb/1.01.206/SegoeUI-Roman-VF_web.woff2
h2
1234.211999923
1263.3640000131
119174
118288
200
application/octet-stream
Font
https://web.vortex.data.microsoft.com/collect/v1/t.js?ver=%272.1%27&name=%27Ms.Webi.PageView%27&time=%272021-08-08T22%3A40%3A51.107Z%27&os=%27Android%27&appId=%27JS%3ADocs%27&-ver=%271.0%27&-impressionGuid=%27fa661e48-bcc4-4697-8b61-d27089e51a3f%27&-pageName=%279ef1269a-9151-6be5-4abe-8a06e1936746%27&-uri=%27https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2F%27&-market=%27en-us%27&-pageType=%27welcome%27&-resHeight=640&-resWidth=360&-pageTags=%27%7B%22author%22%3A%22wibjorn%22%2C%22depotname%22%3A%22MSDN.DocsCoreContent%22%2C%22document_version_independent_id%22%3A%22568a65ba-5905-2775-c30c-f5412d9c68c3%22%2C%22gitcommit%22%3A%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDocsRoot%2Fblob%2F867645739294541e3efb97b2b7e8f70b23ae5299%2FDocsCoreContent%2Findex.yml%22%2C%22pgtop%22%3A%22hub-page%22%2C%22translationtype%22%3A%22HT%22%2C%22giturl%22%3A%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDocsRoot%2Fblob%2Flive%2FDocsCoreContent%2Findex.yml%22%2C%22publishtime%22%3A%222021-01-19%2010%3A50%20PM%22%2C%22contentlocale%22%3A%22en-us%22%2C%22highContrast%22%3A%22false%22%2C%22metaTags%22%3A%7B%7D%7D%27&-behavior=0&*baseType=%27Ms.Content.PageView%27&*cookieEnabled=true&*isJs=true&*title=%27Developer%20tools%2C%20technical%20documentation%20and%20coding%20examples%20%7C%20Microsoft%20Docs%27&*isLoggedIn=false&*flashInstalled=false&ext-javascript-ver=%271.1%27&ext-javascript-libVer=%274.3.4%27&ext-javascript-domain=%27docs.microsoft.com%27&ext-javascript-userConsent=true&$mscomCookies=false
http/1.1
1334.7379999468
1588.1880000234
966
281
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1337.0359999826
1341.7369999224
20323
49389
200
text/javascript
Script
https://w.usabilla.com/cd99660205c0.js?lv=1
h2
1389.6989999339
1410.7879999792
12916
54091
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j92&aip=1&a=831741687&t=pageview&_s=1&dl=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2F&ul=en-us&de=UTF-8&dt=Developer%20tools%2C%20technical%20documentation%20and%20coding%20examples%20%7C%20Microsoft%20Docs&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAEABAAAAAC~&jid=598822082&gjid=2044519895&cid=896419957.1628462451&tid=UA-62780441-21&_gid=2138676272.1628462451&_r=1&_slc=1&cd2=off&cd3=Welcome&z=1545655903
h2
1465.8959999215
1474.2289999267
646
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j92&tid=UA-62780441-21&cid=896419957.1628462451&jid=598822082&gjid=2044519895&_gid=2138676272.1628462451&_u=YEBAAEAAAAAAAC~&z=860183250
h2
1501.8319999799
1506.0560000129
716
1
200
text/plain
XHR
https://web.vortex.data.microsoft.com/collect/v1/t.js?ver=%272.1%27&name=%27Ms.Webi.ContentUpdate%27&time=%272021-08-08T22%3A40%3A51.394Z%27&os=%27Android%27&appId=%27JS%3ADocs%27&-ver=%271.0%27&-impressionGuid=%27fa661e48-bcc4-4697-8b61-d27089e51a3f%27&-pageName=%279ef1269a-9151-6be5-4abe-8a06e1936746%27&-uri=%27https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2F%27&-market=%27en-us%27&-pageTags=%27%7B%22author%22%3A%22wibjorn%22%2C%22depotname%22%3A%22MSDN.DocsCoreContent%22%2C%22document_version_independent_id%22%3A%22568a65ba-5905-2775-c30c-f5412d9c68c3%22%2C%22gitcommit%22%3A%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDocsRoot%2Fblob%2F867645739294541e3efb97b2b7e8f70b23ae5299%2FDocsCoreContent%2Findex.yml%22%2C%22pgtop%22%3A%22hub-page%22%2C%22translationtype%22%3A%22HT%22%2C%22giturl%22%3A%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDocsRoot%2Fblob%2Flive%2FDocsCoreContent%2Findex.yml%22%2C%22publishtime%22%3A%222021-01-19%2010%3A50%20PM%22%2C%22contentlocale%22%3A%22en-us%22%2C%22highContrast%22%3A%22false%22%2C%22metaTags%22%3A%7B%7D%2C%22timing%22%3A%22%7B%5C%22first-paint%5C%22%3A1363.565000006929%2C%5C%22first-contentful-paint%5C%22%3A1363.565000006929%2C%5C%22navigationStart%5C%22%3A1628462449774%2C%5C%22unloadEventStart%5C%22%3A0%2C%5C%22unloadEventEnd%5C%22%3A0%2C%5C%22redirectStart%5C%22%3A0%2C%5C%22redirectEnd%5C%22%3A0%2C%5C%22fetchStart%5C%22%3A1628462450066%2C%5C%22domainLookupStart%5C%22%3A1628462450066%2C%5C%22domainLookupEnd%5C%22%3A1628462450066%2C%5C%22connectStart%5C%22%3A1628462450066%2C%5C%22connectEnd%5C%22%3A1628462450066%2C%5C%22secureConnectionStart%5C%22%3A0%2C%5C%22requestStart%5C%22%3A1628462450066%2C%5C%22responseStart%5C%22%3A1628462450485%2C%5C%22responseEnd%5C%22%3A1628462450485%2C%5C%22domLoading%5C%22%3A1628462450493%2C%5C%22domInteractive%5C%22%3A1628462450986%2C%5C%22domContentLoadedEventStart%5C%22%3A1628462450986%2C%5C%22domContentLoadedEventEnd%5C%22%3A1628462451116%2C%5C%22domComplete%5C%22%3A1628462451368%2C%5C%22loadEventStart%5C%22%3A1628462451368%2C%5C%22loadEventEnd%5C%22%3A1628462451387%7D%22%7D%27&-pageHeight=3667&-vpHeight=640&-vpWidth=360&-behavior=0&-vScrollOffset=0&-hScrollOffset=0&-contentVer=%272.0%27&-content=%27%5B%5D%27&*baseType=%27Ms.Content.ContentUpdate%27&*title=%27Developer%20tools%2C%20technical%20documentation%20and%20coding%20examples%20%7C%20Microsoft%20Docs%27&*cookieEnabled=true&*isJs=true&*isDomComplete=true&*isLoggedIn=false&*pageLoadTime=1594&ext-javascript-ver=%271.1%27&ext-javascript-libVer=%274.3.4%27&ext-javascript-domain=%27docs.microsoft.com%27&ext-javascript-msfpc=%27GUID%3Decea50fb8e5846cfab20203a904d720a%26HASH%3Decea%26LV%3D202108%26V%3D4%26LU%3D1628462451337%27&ext-javascript-userConsent=true&$mscomCookies=false
http/1.1
1620.4819999402
1914.313999936
407
45
200
application/javascript
Script
https://c1.microsoft.com/c.gif?DI=4050&did=1&t=
http/1.1
1621.7879999895
1687.4270000262
712
0
302
https://c.bing.com/c.gif?DI=4050&did=1&t=&ctsa=mr&CtsSyncId=8CD1D6DF88D64ACAA6500EE744F93078&RedC=c1.microsoft.com&MXFR=1AD466732DF66197140876FE29F667E4
http/1.1
1687.7979999408
1710.5290000327
1087
0
302
https://c1.microsoft.com/c.gif?DI=4050&did=1&t=&ctsa=mr&CtsSyncId=8CD1D6DF88D64ACAA6500EE744F93078&MUID=1AD466732DF66197140876FE29F667E4
h2
1710.8139999909
1741.626999923
872
42
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)
722.632
9.153
944.649
24.265
970.329
383.133
1353.488
11.06
1382.825
15.118
1399.523
12.718
1412.603
8.147
1423.637
51.109
1475.171
11.634
1487.145
19.838
1515.121
7.237
1600.728
20.066
1623.062
6.091
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Reduce unused CSS — Potential savings of 65 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Docs.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
70148
66742

Diagnostics

Reduce JavaScript execution time — 1.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://docs.microsoft.com/en-us/
590.344
207.272
6.972
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
570.792
341.896
169.096
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
325.344
14.512
6.932
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
306.968
293.212
8.936
Unattributable
273.8
13.084
0.84
https://www.google-analytics.com/analytics.js
219.84
107.08
6.008
https://w.usabilla.com/cd99660205c0.js?lv=1
118.908
94.416
11.86
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
97.06
0
0
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
65.796
51.124
14.672
Minimize main-thread work — 2.6 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
1166.044
Style & Layout
532.892
Other
329.092
Parse HTML & CSS
256.892
Script Parsing & Compilation
246.856
Rendering
105.192

Metrics

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

Other

Max Potential First Input Delay — 430 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 7.7 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 15646.5 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,320 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Docs.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://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
70148
1980
https://wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js
13539
1230
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
54904
1980
https://docs.microsoft.com/static/third-party/jsll/4.3.4/jsll-4.js
20377
1230
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
4764
630
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/global/93ae22c4.at-config.js
4576
630
https://docs.microsoft.com/static/third-party/adobe-target/at-js/2.4.0-cname/at.js
32182
1530
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
382702
4530
Reduce unused JavaScript — Potential savings of 347 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://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
382702
312302
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
54904
43503
Serve images in next-gen formats — Potential savings of 219 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
198074
119804
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
143727
79241
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
62488
24962
Avoid multiple page redirects — Potential savings of 1,890 ms
Redirects can cause additional delays before the page can begin loading. Docs.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://docs.com/
630
https://docs.com/
480
https://docs.microsoft.com/
780
https://docs.microsoft.com/en-us/
0
Preload key requests — Potential savings of 2,580 ms
Key requests can be preloaded by using '<link rel=preload>'. Docs.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/docons.66501339.woff2
2580
https://docs.microsoft.com/static/third-party/SegoeUIWeb/1.01.206/SegoeUI-Roman-VF_web.woff2
1230

Diagnostics

Serve static assets with an efficient cache policy — 15 resources found
Docs.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://docs.microsoft.com/en-us/media/home-and-directory/learn-tv-icon.svg?branch=master
279000
4078
https://docs.microsoft.com/en-us/media/home-and-directory/students-icon.svg?branch=master
447000
5632
https://docs.microsoft.com/en-us/media/home-and-directory/startups-icon.svg?branch=master
1053000
1837
https://docs.microsoft.com/en-us/media/home-and-directory/docs-and-friends-selfie-stick.png?branch=master
1186000
20517
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learn-tv-2x.png?branch=master
1195000
144552
https://docs.microsoft.com/en-us/media/home-and-directory/featured-certifications-2x.png?branch=master
1222000
198899
https://docs.microsoft.com/en-us/media/home-and-directory/featured-learning-paths-2x.png?branch=master
1420000
63312
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
1800000
54904
https://www.google-analytics.com/analytics.js
7200000
20323
https://wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js
43200000
13539
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/e6141ec8.site-ltr.css
128095000
70148
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
219250000
4764
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/docons.66501339.woff2
219289000
13380
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
421900000
382702
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/global/93ae22c4.at-config.js
574386000
4576
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://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/styles/docons.66501339.woff2
26.56999998726
https://docs.microsoft.com/static/third-party/SegoeUIWeb/1.01.206/SegoeUI-Roman-VF_web.woff2
29.152000090107
Avoid `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.
Source
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of docs.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.
Heading elements appear 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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Docs.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

Some elements have 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.
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.
87

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

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
core-js
core-js-global@3.16.0
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://js.monitor.azure.com/scripts/c/ms.jsll-3.min.js
https://js.monitor.azure.com/scripts/c/ms.jsll-3.1.4.min.js.map
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/81889e74.index-docs.js.map
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js
https://docs.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/2c6911d0.index-polyfills.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request 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 Request Resolution
http://docs.com/
Allowed

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
99

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for docs.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 docs.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

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.
Document has 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.
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.

Mobile Friendly

Tap targets are not sized appropriately — 97% 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.
Tap Target Size Overlapping Target
27x19

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.
42

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 docs.com. This includes details about web app manifests.

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 docs.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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.
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: 20.49.104.24
Continent: North America
Country: United States
United States Flag
Region: Virginia
City: Washington
Longitude: -78.1539
Latitude: 38.7095
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Microsoft Corporation
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
MarkMonitor, Inc. 172.64.148.104
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 94/100
WOT Child Safety: 94/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
docs.com. 23.101.203.117 IN 3599
docs.com. 20.49.104.24 IN 3599

NS Records

Host Nameserver Class TTL
docs.com. ns1-06.azure-dns.com. IN 21599
docs.com. ns2-06.azure-dns.net. IN 21599
docs.com. ns3-06.azure-dns.org. IN 21599
docs.com. ns4-06.azure-dns.info. IN 21599

SOA Records

Domain Name Primary NS Responsible Email TTL
docs.com. ns1-06.azure-dns.com. azuredns-hostmaster.microsoft.com. 3599

TXT Records

Host Value Class TTL
docs.com. developerrewrite.azurewebsites.net IN 3599
docs.com. 7C4223EA776C08BC9E07CE3DFECA00C4B83BA5A298A78151231F01B7FE31BBA8 IN 3599

HTTP Response Headers

Whois Lookup

Created: 7th March, 1995
Changed: 5th February, 2021
Expires: 8th March, 2022
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
serverUpdateProhibited
serverTransferProhibited
serverDeleteProhibited
Nameservers: ns1-06.azure-dns.com
ns2-06.azure-dns.net
ns3-06.azure-dns.org
ns4-06.azure-dns.info
Owner Name: Domain Administrator
Owner Organization: Microsoft Corporation
Owner Street: One Microsoft Way,
Owner Post Code: 98052
Owner City: Redmond
Owner State: WA
Owner Country: US
Owner Phone: +1.4258828080
Owner Email: domains@microsoft.com
Admin Name: Domain Administrator
Admin Organization: Microsoft Corporation
Admin Street: One Microsoft Way,
Admin Post Code: 98052
Admin City: Redmond
Admin State: WA
Admin Country: US
Admin Phone: +1.4258828080
Admin Email: domains@microsoft.com
Tech Name: MSN Hostmaster
Tech Organization: Microsoft Corporation
Tech Street: One Microsoft Way,
Tech Post Code: 98052
Tech City: Redmond
Tech State: WA
Tech Country: US
Tech Phone: +1.4258828080
Tech Email: msnhst@microsoft.com
Full Whois: Domain Name: docs.com
Registry Domain ID: 57052_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2021-02-05T02:30:28-0800
Creation Date: 1995-03-07T21:00:00-0800
Registrar Registration Expiration Date: 2022-03-08T00:00:00-0800
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895770
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited)
Domain Status: serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited)
Domain Status: serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited)
Registry Registrant ID:
Registrant Name: Domain Administrator
Registrant Organization: Microsoft Corporation
Registrant Street: One Microsoft Way,
Registrant City: Redmond
Registrant State/Province: WA
Registrant Postal Code: 98052
Registrant Country: US
Registrant Phone: +1.4258828080
Registrant Phone Ext:
Registrant Fax: +1.4259367329
Registrant Fax Ext:
Registrant Email: domains@microsoft.com
Registry Admin ID:
Admin Name: Domain Administrator
Admin Organization: Microsoft Corporation
Admin Street: One Microsoft Way,
Admin City: Redmond
Admin State/Province: WA
Admin Postal Code: 98052
Admin Country: US
Admin Phone: +1.4258828080
Admin Phone Ext:
Admin Fax: +1.4259367329
Admin Fax Ext:
Admin Email: domains@microsoft.com
Registry Tech ID:
Tech Name: MSN Hostmaster
Tech Organization: Microsoft Corporation
Tech Street: One Microsoft Way,
Tech City: Redmond
Tech State/Province: WA
Tech Postal Code: 98052
Tech Country: US
Tech Phone: +1.4258828080
Tech Phone Ext:
Tech Fax: +1.4259367329
Tech Fax Ext:
Tech Email: msnhst@microsoft.com
Name Server: ns2-06.azure-dns.net
Name Server: ns4-06.azure-dns.info
Name Server: ns1-06.azure-dns.com
Name Server: ns3-06.azure-dns.org
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-08-08T15:40:26-0700 <<<

For more information on WHOIS status codes, please visit:
https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
(1) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
(2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

MarkMonitor reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220

Nameservers

Name IP Address
ns1-06.azure-dns.com 13.107.236.6
ns2-06.azure-dns.net 150.171.21.6
ns3-06.azure-dns.org 204.14.183.6
ns4-06.azure-dns.info 208.84.5.6
Related

Subdomains

Domain Subdomain
google
oogle

Similar Sites

Domain Valuation Snoop Score
0/5
$1,040 USD 1/5
0/5
$10 USD 1/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address