airtel.com

airtel.com is SSL secured

Free website and domain report on airtel.com

Last Updated: 29th July, 2022 Update Now
Overview

Snoop Summary for airtel.com

This is a free and comprehensive report about airtel.com. Airtel.com is hosted in India on a server with an IP address of 125.16.74.25, where INR is the local currency and the local language is English. Airtel.com is expected to earn an estimated $20 USD per day from advertising revenue. The sale of airtel.com would possibly be worth $14,509 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Airtel.com is very popular with an estimated 6,969 daily unique visitors. This report was last updated 29th July, 2022.

About airtel.com

Site Preview: airtel.com airtel.com
Title: airtel global presence
Description:
Keywords and Tags: airtel, airtel bd recharge offer, airtel bd sim offer, airtel idoc, internet services, warid customer care number bangladesh
Related Terms: airtel 345 recharge, airtel cheat, airtel faf code 2017, airtel fancy numbers, airtel free browsing, airtel next gen store, airtel office in usa, find my airtel sim number, is airtel gsm or cdma
Fav Icon:
Age: Over 14 years old
Domain Created: 13th February, 2010
Domain Updated: 31st January, 2017
Domain Expires: 13th February, 2026
Review

Snoop Score

3/5 (Great!)

Valuation

$14,509 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 60,827
Alexa Reach:
SEMrush Rank (US): 180,340
SEMrush Authority Score: 60
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 9,797 0
Traffic: 8,485 0
Cost: $890 USD $0 USD
Traffic

Visitors

Daily Visitors: 6,969
Monthly Visitors: 212,114
Yearly Visitors: 2,543,685
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $20 USD
Monthly Revenue: $605 USD
Yearly Revenue: $7,250 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 507,110
Referring Domains: 4,429
Referring IPs: 3,851
Airtel.com has 507,110 backlinks according to SEMrush. 96% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve airtel.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of airtel.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://www.sitejabber.com/reviews/airtel.com
Target: http://airtel.com/

2
Source: http://waplog.net/en-ban-noreason/html/stat/2917/operators
Target: http://www.mg.airtel.com/

3
Source: http://waplog.net/en-ban-noreason/html/stat/2917/operators/%7B%7D
Target: http://www.mg.airtel.com/

4
Source: https://mergr.com/emerging-capital-partners-acquires-airtel-gabon
Target: http://www.africa.airtel.com/

5
Source: https://www.digitaltrends.com/social-media/facebook-express-wi-fi-india/
Target: https://www.airtel.com/

Top Ranking Keywords (US)

1
Keyword: airtel
Ranked Page: https://www.airtel.com/

2
Keyword: airtel bd sim offer
Ranked Page: https://www.bd.airtel.com/en/personal/prepaid-postpaid/prepaid/prepaid-new-sim-offer

3
Keyword: warid customer care number bangladesh
Ranked Page: https://www.bd.airtel.com/en/personal/roaming/inbound-roaming

4
Keyword: airtel bd recharge offer
Ranked Page: https://www.bd.airtel.com/en/personal/offers

5
Keyword: airtel idoc
Ranked Page: https://i-docnorth.airtel.com/i-DOC/logout.aspx

Domain Analysis

Value Length
Domain: airtel.com 10
Domain Name: airtel 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.06 seconds
Load Time Comparison: Faster than 40% of sites

PageSpeed Insights

Avg. (All Categories) 63
Performance 82
Accessibility 80
Best Practices 67
SEO 70
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.airtel.com/
Updated: 11th May, 2021

3.40 seconds
First Contentful Paint (FCP)
18%
51%
31%

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

Simulate loading on desktop
82

Performance

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

Metrics

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

Other

First CPU Idle — 0.8 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive airtel.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://airtel.com/
http/1.1
0
860.11499981396
256
0
301
text/html
http://www.airtel.com/
http/1.1
860.91299983673
1373.2139999047
295
0
301
https://www.airtel.com/
h2
1374.0199999884
3278.7899998948
5061
11505
200
text/html
Document
https://www.airtel.com/common/style.css
h2
3298.9659998566
3720.0479998719
1423
4797
200
text/css
Stylesheet
https://www.airtel.com/Scripts/swfobject_modified.js
h2
3299.2429998703
3723.7909999676
5732
21696
200
application/javascript
Script
https://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
http/1.1
3299.751999788
3390.5799998902
1113
744
200
application/javascript
Script
https://www.adobe.com/images/shared/download_buttons/get_flash_player.gif
h2
3721.6959998477
3825.740999775
2087
1720
200
image/gif
Image
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
h2
3745.0779997744
3895.4209999647
51853
207040
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
h2
3747.1029998269
3793.4569998179
67019
289737
200
application/javascript
Script
https://www.airtel.com/common/world_map.png
h2
3750.50799991
4543.4139999561
10211
9870
200
image/png
Image
https://www.airtel.com/common/logo-bg.jpg
h2
3750.9889998473
4689.5669999067
4174
3833
200
image/jpeg
Image
https://www.airtel.com/common/Image-23.png
h2
3751.7539998516
4302.8669999912
259106
258762
200
image/png
Image
https://www.airtel.com/common/list1-icon.png
h2
3752.2449998651
4458.8009999134
538
200
200
image/png
Image
https://www.airtel.com/common/Image-16.png
h2
3752.6599999983
4053.6189998966
14292
13950
200
image/png
Image
https://www.airtel.com/common/Image-17.png
h2
3752.873999998
4093.110999791
5719
5378
200
image/png
Image
https://www.airtel.com/common/ronniabasicreg-webfont.woff
h2
3753.2789998222
4770.2769997995
29162
28808
200
application/font-woff
Font
https://www.googletagmanager.com/gtag/js?id=G-L722EHW79W&l=dataLayer&cx=c
h2
3852.2729999386
3882.8799999319
46873
120200
200
application/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-L722EHW79W&gtm=2oe4s0&_p=1854163510&sr=800x600&ul=en-us&cid=425876843.1620719676&_s=1&dl=https%3A%2F%2Fwww.airtel.com%2F&dt=airtel%20global%20presence&sid=1620719675&sct=1&seg=0&en=page_view&_fv=1&_nsi=1&_ss=1
3929.7149998602
3936.2309998833
0
0
-1
Other
https://c.go-mpulse.net/api/config.json?key=QTS83-A6PUQ-WYVS7-HTZNP-4SG6K&d=www.airtel.com&t=5402399&v=1.632.0&if=&sl=0&si=mm2ozhpj6x9-qsxnb0&plugins=AK,ConfigOverride,Continuity,PageParams,IFrameDelay,AutoXHR,SPA,Angular,Backbone,Ember,History,RT,CrossDomain,BW,PaintTiming,NavigationTiming,ResourceTiming,Memory,CACHE_RELOAD,Errors,TPAnalytics,UserTiming,Akamai,LOGN&acao=&ak.ai=616536
http/1.1
3979.8169999849
4375.9649998974
878
1146
200
application/json
XHR
https://173e250e.akstat.io/
4831.4379998483
4833.8979999535
0
0
-1
Other
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)
3319.347
10.868
3334.59
5.401
3762.444
23.917
3786.382
20.962
3807.889
13.974
3847.986
21.618
3870.82
31.277
3931.406
39.919
3985.342
27.632
4808.265
25.445
4840.628
7.849
4860.258
9.004
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Airtel.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Airtel.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Airtel.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 2 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Airtel.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.airtel.com/Scripts/swfobject_modified.js
5732
2329
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Airtel.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 49 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://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
51853
29279
https://www.googletagmanager.com/gtag/js?id=G-L722EHW79W&l=dataLayer&cx=c
46873
20787
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 261 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.airtel.com/common/Image-23.png
258762
255464
https://www.airtel.com/common/Image-16.png
13950
11628
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Airtel.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.airtel.com/common/Image-23.png
0

Diagnostics

Avoids enormous network payloads — Total size was 494 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.airtel.com/common/Image-23.png
259106
https://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
67019
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
51853
https://www.googletagmanager.com/gtag/js?id=G-L722EHW79W&l=dataLayer&cx=c
46873
https://www.airtel.com/common/ronniabasicreg-webfont.woff
29162
https://www.airtel.com/common/Image-16.png
14292
https://www.airtel.com/common/world_map.png
10211
https://www.airtel.com/Scripts/swfobject_modified.js
5732
https://www.airtel.com/common/Image-17.png
5719
https://www.airtel.com/
5061
Avoids an excessive DOM size — 105 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
105
Maximum DOM Depth
11
Maximum Child Elements
15
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Airtel.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.airtel.com/
88.676
29.727
2.963
https://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
73.22
61.19
7.444
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
54.026
41.968
4.823
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
177.219
Other
52.354
Style & Layout
33.793
Script Parsing & Compilation
20.927
Rendering
12.966
Parse HTML & CSS
10.136
Keep request counts low and transfer sizes small — 20 requests • 494 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
20
505792
Image
7
296127
Script
5
172590
Font
1
29162
Document
1
5061
Other
5
1429
Stylesheet
1
1423
Media
0
0
Third-party
8
169823
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)
113892
0
52731
0
1113
0
0
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 — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00027428421329131
0.00024434521203631
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

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

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 240 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Airtel.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://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
1113
230
Avoid multiple page redirects — Potential savings of 380 ms
Redirects can cause additional delays before the page can begin loading. Airtel.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://airtel.com/
190
http://www.airtel.com/
190
https://www.airtel.com/
0

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Airtel.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://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
0
1113
https://www.adobe.com/images/shared/download_buttons/get_flash_player.gif
84000
2087
https://www.airtel.com/Scripts/swfobject_modified.js
18827000
5732
https://www.airtel.com/common/style.css
62997000
1423
https://www.airtel.com/common/ronniabasicreg-webfont.woff
125382000
29162
https://www.airtel.com/common/Image-16.png
327389000
14292
https://www.airtel.com/common/Image-17.png
327450000
5719
https://www.airtel.com/common/world_map.png
336931000
10211
https://www.airtel.com/common/list1-icon.png
371410000
538
https://www.airtel.com/common/logo-bg.jpg
511540000
4174
https://www.airtel.com/common/Image-23.png
522159000
259106
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
604800000
51853

Metrics

Speed Index — 3.0 s
The time taken for the page contents to be visibly populated.

Opportunities

Reduce initial server response time — Root document took 1,910 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://www.airtel.com/
1905.767

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.airtel.com/common/ronniabasicreg-webfont.woff
1016.9979999773
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
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.adobe.com/images/shared/download_buttons/get_flash_player.gif
80

Accessibility

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

Navigation

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

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`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.

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 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"]`
Airtel.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Navigation

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

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

Names and labels

`<object>` elements do not 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.
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.
67

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that airtel.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.

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

Avoids `unload` event listeners
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.
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
SWFObject
boomerang.js
1.632.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 3 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://airtel.com/
Allowed
http://www.airtel.com/
Allowed
http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif
Automatically upgraded to HTTPS

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Charset declaration is missing or occurs too late in the HTML
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

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
ReferenceError: _satellite is not defined at https://www.airtel.com/:173:36
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
70

SEO

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

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.

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

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of airtel.com on mobile screens.

Crawling and Indexing

Links are not 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.

Content Best Practices

Document uses plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Element source

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

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

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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of airtel.com on mobile screens.
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) 54
Performance 68
Accessibility 58
Best Practices 60
SEO 67
Progressive Web App 17
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.airtel.com
Updated: 11th May, 2021

1.85 seconds
First Contentful Paint (FCP)
36%
53%
11%

0.24 seconds
First Input Delay (FID)
8%
87%
5%

Simulate loading on mobile
68

Performance

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

Metrics

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

Other

Max Potential First Input Delay — 120 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 20 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive airtel.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://airtel.com/
http/1.1
0
853.50099999778
256
0
301
text/html
http://www.airtel.com/
http/1.1
854.14599999785
1005.9849999961
296
0
301
https://www.airtel.com/
h2
1006.6059999954
2006.9629999998
5202
11550
200
text/html
Document
https://www.airtel.com/common/style.css
h2
2027.8809999945
2133.7619999977
1422
4797
200
text/css
Stylesheet
https://www.airtel.com/Scripts/swfobject_modified.js
h2
2028.2709999956
2097.3159999994
5733
21696
200
application/javascript
Script
https://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
http/1.1
2029.0269999969
2178.0309999958
1113
744
200
application/javascript
Script
https://www.adobe.com/images/shared/download_buttons/get_flash_player.gif
h2
2135.838999995
2193.5779999985
2088
1720
200
image/gif
Image
http://airtel.com/M-airtelcom/index.html
http/1.1
2143.3319999996
2446.6689999972
266
0
301
text/html
http://www.airtel.com/M-airtelcom/index.html
http/1.1
2447.1659999981
2512.3989999993
317
0
301
https://www.airtel.com/M-airtelcom/index.html
h2
2513.1279999987
3518.0149999942
4199
8452
200
text/html
Document
https://www.airtel.com/M-airtelcom/common/ronniabasicreg-webfont.woff
h2
3526.5959999961
3873.0139999971
29162
28808
200
application/font-woff
Font
https://www.airtel.com/M-airtelcom/common/style.css
h2
3531.5530000007
3675.2909999996
1170
2767
200
text/css
Stylesheet
https://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
http/1.1
3531.836999995
3678.4359999947
1113
744
200
application/javascript
Script
https://www.airtel.com/M-airtelcom/common/img.gif
h2
3679.9329999994
4104.6459999998
63482
63140
200
image/gif
Image
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
h2
3692.237999996
3723.3169999963
51853
207040
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
h2
3694.8039999988
3743.8789999942
67019
289737
200
application/javascript
Script
https://www.airtel.com/M-airtelcom/common/world_map.png
h2
3696.2219999987
4066.3249999998
10211
9870
200
image/png
Image
https://www.airtel.com/M-airtelcom/common/logo-bg.jpg
h2
3696.4559999979
4002.0089999962
4174
3833
200
image/jpeg
Image
https://www.airtel.com/M-airtelcom/common/Image-23.png
h2
3696.6790000006
4570.4819999955
259106
258762
200
image/png
Image
https://www.airtel.com/M-airtelcom/common/list1-icon.png
h2
3697.0609999989
4018.5299999939
538
200
200
image/png
Image
https://www.airtel.com/M-airtelcom/common/Image-16.png
h2
3697.5199999943
4199.443999998
181513
181169
200
image/png
Image
https://c.go-mpulse.net/api/config.json?key=QTS83-A6PUQ-WYVS7-HTZNP-4SG6K&d=www.airtel.com&t=5402399&v=1.632.0&if=&sl=0&si=ot5v0jv4asl-qsxnbo&plugins=AK,ConfigOverride,Continuity,PageParams,IFrameDelay,AutoXHR,SPA,Angular,Backbone,Ember,History,RT,CrossDomain,BW,PaintTiming,NavigationTiming,ResourceTiming,Memory,CACHE_RELOAD,Errors,TPAnalytics,UserTiming,Akamai,LOGN&acao=&ak.ai=616536
http/1.1
3756.0209999938
4151.7889999959
876
1146
200
application/json
XHR
https://www.googletagmanager.com/gtag/js?id=G-L722EHW79W&l=dataLayer&cx=c
h2
3794.0600000002
3808.4139999992
46873
120200
200
application/javascript
Script
https://stats.g.doubleclick.net/dc.js
h2
3796.6019999949
3800.5379999959
17723
46068
200
text/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-L722EHW79W&gtm=2oe4s0&_p=1685550857&sr=360x640&ul=en-us&cid=1319131993.1620719700&_s=1&dl=https%3A%2F%2Fwww.airtel.com%2FM-airtelcom%2Findex.html&dt=airtel%20global%20presence&sid=1620719699&sct=1&seg=0&en=page_view&_fv=1&_nsi=1&_ss=1
3874.4499999957
3879.9779999972
0
0
-1
Other
https://173e2516.akstat.io/
4595.2009999965
4601.5509999997
0
0
-1
Other
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)
2042.973
8.979
2167.891
5.24
3552.914
8.401
3711.898
15.516
3727.433
12.715
3766.2
18.509
3796.636
16.389
3813.462
29.325
3848.802
30.615
3884.185
25.411
4605.041
13.269
4622.325
5.788
4628.369
5.356
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Airtel.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Airtel.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Airtel.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Airtel.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Airtel.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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.
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
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
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.

Diagnostics

Avoids enormous network payloads — Total size was 738 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.airtel.com/M-airtelcom/common/Image-23.png
259106
https://www.airtel.com/M-airtelcom/common/Image-16.png
181513
https://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
67019
https://www.airtel.com/M-airtelcom/common/img.gif
63482
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
51853
https://www.googletagmanager.com/gtag/js?id=G-L722EHW79W&l=dataLayer&cx=c
46873
https://www.airtel.com/M-airtelcom/common/ronniabasicreg-webfont.woff
29162
https://stats.g.doubleclick.net/dc.js
17723
https://www.airtel.com/M-airtelcom/common/world_map.png
10211
https://www.airtel.com/Scripts/swfobject_modified.js
5733
Avoids an excessive DOM size — 61 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
61
Maximum DOM Depth
7
Maximum Child Elements
15
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Airtel.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.7 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://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
253.916
208.512
27.532
https://www.airtel.com/M-airtelcom/index.html
202.268
48.612
9.68
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
136.296
109.232
15.992
Unattributable
124.828
3.944
0.572
https://stats.g.doubleclick.net/dc.js
122.46
115.344
5.22
https://www.googletagmanager.com/gtag/js?id=G-L722EHW79W&l=dataLayer&cx=c
106.744
90.712
11.908
https://www.airtel.com/M-airtelcom/index.html#
60.604
42.516
4.336
Minimizes main-thread work — 1.1 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
640.488
Other
217.86
Script Parsing & Compilation
82.744
Style & Layout
59.796
Parse HTML & CSS
30.68
Rendering
25.072
Garbage Collection
4.564
Keep request counts low and transfer sizes small — 26 requests • 738 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
26
755705
Image
7
521112
Script
7
191427
Font
1
29162
Document
2
9401
Stylesheet
2
2592
Other
7
2011
Media
0
0
Third-party
10
188658
Minimize third-party usage — Third-party code blocked the main thread for 160 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)
113892
92.712
17723
64.988
52729
1.852
2226
0
0
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
img
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 — 7 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://stats.g.doubleclick.net/dc.js
5705
122
https://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
4508
117
https://www.googletagmanager.com/gtag/js?id=G-L722EHW79W&l=dataLayer&cx=c
5525
102
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
4292
74
https://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
4442
66
https://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
2700
62
https://www.googletagmanager.com/gtm.js?id=GTM-L6QJ
5627
53
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.

Metrics

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 4.4 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 5.6 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 5.4 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 2.8 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5312 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 240 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Airtel.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://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
1113
180
Remove unused JavaScript — Potential savings of 49 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://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
51853
29123
https://www.googletagmanager.com/gtag/js?id=G-L722EHW79W&l=dataLayer&cx=c
46873
20787
Preload key requests — Potential savings of 510 ms
Key requests can be preloaded by using '<link rel=preload>'. Airtel.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://www.airtel.com/M-airtelcom/common/style.css
510
Preload Largest Contentful Paint image — Potential savings of 360 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.airtel.com/M-airtelcom/common/img.gif
360

Metrics

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

Opportunities

Serve images in next-gen formats — Potential savings of 424 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.airtel.com/M-airtelcom/common/Image-23.png
258762
255464
https://www.airtel.com/M-airtelcom/common/Image-16.png
181169
178691
Reduce initial server response time — Root document took 1,010 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://www.airtel.com/M-airtelcom/index.html
1005.885
Avoid multiple page redirects — Potential savings of 2,340 ms
Redirects can cause additional delays before the page can begin loading. Airtel.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://airtel.com/
630
http://www.airtel.com/
630
https://www.airtel.com/
480
http://airtel.com/M-airtelcom/index.html
180
http://www.airtel.com/M-airtelcom/index.html
420
https://www.airtel.com/M-airtelcom/index.html
0

Diagnostics

Serve static assets with an efficient cache policy — 15 resources found
Airtel.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://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
0
1113
https://s3.amazonaws.com/searchdiscovery-satellite-production/7f4f507b059aa0b92e47c370242bd176d12a111f/satelliteLib-ee9fa188e6c905c33df5c26f5843db7c7c178b3b.js
0
1113
https://www.adobe.com/images/shared/download_buttons/get_flash_player.gif
854000
2088
https://stats.g.doubleclick.net/dc.js
7200000
17723
https://www.airtel.com/Scripts/swfobject_modified.js
18884000
5733
https://www.airtel.com/common/style.css
62994000
1422
https://www.airtel.com/M-airtelcom/common/style.css
86355000
1170
https://www.airtel.com/M-airtelcom/common/img.gif
123775000
63482
https://www.airtel.com/M-airtelcom/common/Image-23.png
179398000
259106
https://www.airtel.com/M-airtelcom/common/list1-icon.png
203399000
538
https://www.airtel.com/M-airtelcom/common/logo-bg.jpg
229441000
4174
https://www.airtel.com/M-airtelcom/common/world_map.png
318015000
10211
https://www.airtel.com/M-airtelcom/common/Image-16.png
347026000
181513
https://www.airtel.com/M-airtelcom/common/ronniabasicreg-webfont.woff
574099000
29162
https://s.go-mpulse.net/boomerang/QTS83-A6PUQ-WYVS7-HTZNP-4SG6K
604800000
51853
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.airtel.com/M-airtelcom/common/ronniabasicreg-webfont.woff
346.41800000099
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
58

Accessibility

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

Navigation

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

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`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.
`<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.

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 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"]`
Airtel.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Navigation

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

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that airtel.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.

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

Audits

Avoids `unload` event listeners
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.
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
boomerang.js
1.632.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 5 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://airtel.com/
Allowed
http://www.airtel.com/
Allowed
http://airtel.com/M-airtelcom/index.html
Allowed
http://www.airtel.com/M-airtelcom/index.html
Allowed
http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif
Automatically upgraded to HTTPS

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.airtel.com/M-airtelcom/common/img.gif
300 x 320
300 x 320
600 x 640

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Charset declaration is missing or occurs too late in the HTML
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

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
ReferenceError: _satellite is not defined at https://www.airtel.com/M-airtelcom/index.html:88:32
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
67

SEO

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

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

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of airtel.com on mobile screens.
Document doesn't use 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 not 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

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

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

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

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
Content is not 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of airtel.com on mobile screens.
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: 125.16.74.25
Continent: Asia
Country: India
India Flag
Region:
City:
Longitude: 77
Latitude: 20
Currencies: INR
Languages: English
Hindi
Tamil

Web Hosting Provider

Name IP Address
BHARTI-CELLUAR-LTD
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
Net 4 India Limited
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: airtel.in
Issued By: R3
Valid From: 30th April, 2021
Valid To: 29th July, 2021
Subject: CN = airtel.in
Hash: 31573e4f
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04D4F567139CDD34AB042ECEA5676D031D42
Serial Number (Hex): 04D4F567139CDD34AB042ECEA5676D031D42
Valid From: 30th April, 2024
Valid To: 29th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Apr 30 12:29:30.543 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:AC:DC:2A:5F:86:76:95:0E:B5:CD:75:
87:C5:F8:1B:DD:C9:70:28:B7:F4:14:94:E2:33:AF:78:
94:E8:D9:5F:27:02:21:00:CC:86:75:CC:40:79:4E:16:
D2:58:6A:35:21:3E:C4:2A:84:08:55:8E:15:09:80:8A:
33:6C:71:EB:BF:B6:B2:0F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Apr 30 12:29:30.528 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:23:EC:6D:DF:4E:1A:6B:94:58:A3:6F:84:
74:EA:1E:89:93:79:12:2F:E1:50:13:C4:96:C9:86:99:
48:EF:FA:4E:02:21:00:DE:9E:38:95:CE:0C:31:70:AC:
46:3C:C4:C9:CC:27:16:83:28:F9:75:99:E0:80:6D:9D:
65:12:D3:93:9F:77:14
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:assets-uat.bsbportal.com
DNS:assets.airtel.in
DNS:business.airtel.in
DNS:cdn.smartapi.airtel.in
DNS:ebpp.airtelworld.com
DNS:livestream.airtel.com
DNS:m.airtel.in
DNS:nwexp.airtel.com
DNS:opennetwork.airtel.in
DNS:videokyc-feature.airtelbank.com
DNS:videokyc.airtelbank.com
DNS:www.airtel.com
DNS:www.airtel.in
DNS:www.bharti.com
DNS:www.bhartihexacom.in
DNS:airtel.in
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Content-Type: text/html
Date: 19th May, 2021
Content-Length: 8160
Last-Modified: 7th May, 2021
ETag: "6094eaf0-1fe0"
Accept-Ranges: bytes
Connection: keep-alive

Whois Lookup

Created: 13th February, 2010
Changed: 31st January, 2017
Expires: 13th February, 2026
Registrar: Net 4 India Limited
Status: ok
Nameservers: aaadel.mantraonline.com
dnsdel.mantraonline.com
Full Whois: Domain Name: AIRTEL.COM
Registry Domain ID: 1585335172_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.net4domains.com
Registrar URL: http://www.net4.in
Updated Date: 2017-01-31T12:13:21Z
Creation Date: 2010-02-13T19:54:48Z
Registry Expiry Date: 2026-02-13T19:54:48Z
Registrar: Net 4 India Limited
Registrar IANA ID: 1007
Registrar Abuse Contact Email: abuse@net4.com
Registrar Abuse Contact Phone: +91.1204989000
Domain Status: ok https://icann.org/epp#ok
Name Server: AAADEL.MANTRAONLINE.COM
Name Server: DNSDEL.MANTRAONLINE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-05-19T02:43:54Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may 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 of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

Nameservers

Name IP Address
aaadel.mantraonline.com 202.56.230.6
dnsdel.mantraonline.com 202.56.230.5
Related

Subdomains

Domain Subdomain
africa
bd
hive
webmail

Similar Sites

Domain Valuation Snoop Score
0/5
$7,558,664 USD 4/5
0/5
$576 USD 1/5
$14,157 USD 2/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