phonemantra.com

phonemantra.com is SSL secured

Free website and domain report on phonemantra.com

Last Updated: 6th May, 2020 Update Now
Overview

Snoop Summary for phonemantra.com

This is a free and comprehensive report about phonemantra.com. The domain phonemantra.com is currently hosted on a server located in United States with the IP address 68.65.123.224, where USD is the local currency and the local language is English. Our records indicate that phonemantra.com is privately registered by Private Registration. Phonemantra.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If phonemantra.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). Phonemantra.com receives an estimated 478 unique visitors every day - a decent amount of traffic! This report was last updated 6th May, 2020.

About phonemantra.com

Site Preview: phonemantra.com phonemantra.com
Title: Latest Mobiles / Latest Smartphone Launches | New Mobiles | Technology News
Description:
Keywords and Tags: malicious sites, parked domain
Related Terms: 3g mobiles, andi mobiles, cdma mobiles., forfaits mobiles, imported mobiles, jivi mobiles, latest mobiles, mobiles, mobiles lesen, upcoming mobiles
Fav Icon:
Age: Over 7 years old
Domain Created: 22nd January, 2017
Domain Updated: 25th January, 2019
Domain Expires: 22nd January, 2022
Review

Snoop Score

2/5

Valuation

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

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,466,657
Alexa Reach: <0.0001%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Rank By Country

Country Alexa Rank
India Flag India 134,922

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 478
Monthly Visitors: 14,549
Yearly Visitors: 174,470
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
India Flag India Daily: 342
Monthly: 10,402
Yearly: 124,746
71.5%
Other Daily: 138
Monthly: 4,190
Yearly: 50,247
28.8%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $41 USD
Yearly Revenue: $497 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
India Flag India Daily: $1 USD
Monthly: $41 USD
Yearly: $497 USD
100%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: phonemantra.com 15
Domain Name: phonemantra 11
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.79 seconds
Load Time Comparison: Faster than 25% of sites

PageSpeed Insights

Avg. (All Categories) 76
Performance 89
Accessibility 86
Best Practices 77
SEO 80
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://phonemantra.com
Updated: 24th April, 2020

4.03 seconds
First Contentful Paint (FCP)
6%
50%
44%

0.06 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on desktop
89

Performance

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

Metrics

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
First CPU Idle — 1.0 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.

Other

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 phonemantra.com as laggy when the latency is higher than 0.05 seconds.
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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://phonemantra.com/
0
214.38899997156
240
0
301
text/html
https://phonemantra.com/
214.73000000697
577.10500003304
13552
61090
200
text/html
Document
https://phonemantra.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4
590.20500001498
890.95399994403
7956
53489
200
text/css
Stylesheet
https://phonemantra.com/wp-content/plugins/covid19-plugin-wp/assets/style.css?ver=2.2.0
590.43199999724
713.47900002729
626
426
200
text/css
Stylesheet
https://phonemantra.com/wp-content/plugins/social-warfare/css/style.min.css?ver=3.2.0
590.65799997188
933.54499991983
6454
46284
200
text/css
Stylesheet
https://phonemantra.com/wp-includes/css/dashicons.min.css?ver=5.4
590.89099999983
998.85600002017
28811
47558
200
text/css
Stylesheet
https://phonemantra.com/wp-content/plugins/td-composer/td-multi-purpose/style.css?ver=3328da2481dfce47ccb29fd8f8bc649a
591.12200001255
899.75099998992
9665
71765
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400%2C400italic%2C600%2C600italic%2C700%7CRoboto%3A300%2C400%2C400italic%2C500%2C500italic%2C700%2C900&ver=9.6.1&display=swap
591.3859999273
613.4440000169
2474
33336
200
text/css
Stylesheet
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
591.53299999889
1183.483999921
127964
1222000
200
text/css
Stylesheet
https://phonemantra.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
591.78200003225
991.68199999258
34120
96873
200
application/javascript
Script
https://phonemantra.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
592.00399997644
877.2459999891
4357
10056
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-96442620-1
592.4309999682
618.46699996386
30845
81636
200
application/javascript
Script
https://phonemantra.com/wp-content/uploads/2020/03/Phonemantra-Logo-1024x339-1.png
592.57099998649
1042.351000011
51654
51362
200
image/png
Image
https://phonemantra.com/wp-content/plugins/social-warfare/js/script.min.js?ver=3.2.0
625.78699993901
876.67699996382
4205
10232
200
application/javascript
Script
https://phonemantra.com/wp-content/themes/Newspaper/js/tagdiv_theme.min.js?ver=9.6.1
878.10700002592
1134.3989999732
53726
228414
200
application/javascript
Script
https://phonemantra.com/wp-includes/js/comment-reply.min.js?ver=5.4
1044.2429999821
1354.5109999832
1502
2420
200
application/javascript
Script
https://phonemantra.com/wp-includes/js/wp-embed.min.js?ver=5.4
1144.3560000043
1231.9940000307
1111
1434
200
application/javascript
Script
https://connect.facebook.net/en_US/fbevents.js
1256.8520000204
1275.8149999427
31568
128769
200
application/x-javascript
Script
1284.9249999272
1284.9639999913
0
121
200
image/png
Image
https://phonemantra.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?16
1287.0330000296
1462.2159999562
66795
122756
200
font/woff
Font
https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxK.woff2
1290.0039999513
1304.7439999646
16335
15736
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN7rgOUuhp.woff2
1291.4269999601
1295.0459999265
15655
15056
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4.woff2
1293.0789999664
1296.3359999703
16471
15872
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem8YaGs126MiZpBA-UFVZ0b.woff2
1301.8630000297
1305.3359999321
14979
14380
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem6YaGs126MiZpBA-UFUK0Zdc0.woff2
1306.8059999496
1309.9369999254
14378
13780
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
1317.1409999486
1320.9090000018
16415
15816
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOkCnqEu92Fr1Mu51xIIzI.woff2
1324.3629999924
1327.946000034
17923
17324
200
font/woff2
Font
1334.6439999295
1334.6819999861
0
138
200
image/png
Image
1334.872999927
1334.9089999683
0
114
200
image/png
Image
https://www.google-analytics.com/analytics.js
1363.5449999711
1368.4529999737
18794
45229
200
text/javascript
Script
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UNirkOUuhp.woff2
1372.5799999665
1375.6699999794
15479
14880
200
font/woff2
Font
https://connect.facebook.net/signals/config/220455392157207?v=2.9.15&r=stable
1433.4479999961
1496.0349999601
116836
457789
200
application/x-javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=281362690&t=pageview&_s=1&dl=https%3A%2F%2Fphonemantra.com%2F&ul=en-us&de=UTF-8&dt=Latest%20Mobiles%20%2F%20Latest%20Smartphone%20Launches%20%7C%20New%20Mobiles%20%7C%20Technology%20News&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=951516926&gjid=502824043&cid=1179776606.1587730379&tid=UA-96442620-1&_gid=1470479433.1587730379&_r=1&gtm=2ou4f0&z=1746148264
1563.2060000207
1631.8089999259
750
0
302
text/html
https://connect.facebook.net/signals/config/290348814895075?v=2.9.15&r=stable
1631.194000016
1716.7109999573
116187
457789
200
application/x-javascript
Script
https://www.facebook.com/tr/?id=220455392157207&ev=PageView&dl=https%3A%2F%2Fphonemantra.com%2F&rl=&if=false&ts=1587730379285&sw=800&sh=600&v=2.9.15&r=stable&ec=0&o=30&fbp=fb.1.1587730379283.1692468655&it=1587730379088&coo=false&rqm=GET
1631.4919999568
1648.7249999773
590
44
200
image/gif
Image
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-96442620-1&cid=1179776606.1587730379&jid=951516926&_gid=1470479433.1587730379&gjid=502824043&_v=j81&z=1746148264
1632.3619999457
1636.7029999383
653
35
200
image/gif
Image
https://www.facebook.com/tr/?id=290348814895075&ev=PageView&dl=https%3A%2F%2Fphonemantra.com%2F&rl=&if=false&ts=1587730379407&sw=800&sh=600&v=2.9.15&r=stable&a=wordpress-5.4-2.0.2&ec=0&o=30&fbp=fb.1.1587730379283.1692468655&it=1587730379088&coo=false&rqm=GET
1751.6609999584
1767.7109999349
441
44
200
image/gif
Image
https://phonemantra.com/wp-content/uploads/2020/04/Intel-5-534x390.jpg
1788.9449999202
2113.8929999433
67974
67681
200
image/jpeg
Image
https://phonemantra.com/wp-content/uploads/2020/04/Xiaomi-Watch-265x198.jpg
1806.6389999585
1898.5799999209
18203
17910
200
image/jpeg
Image
https://phonemantra.com/wp-content/uploads/2020/04/Samsung-smart-TVs-265x198.png
1827.8670000145
2152.3759999545
77004
76712
200
image/png
Image
https://phonemantra.com/wp-content/uploads/2020/04/Huawei-Mate-10-265x198.jpg
1842.5849999767
1961.8329999503
8397
8105
200
image/jpeg
Image
https://phonemantra.com/wp-content/uploads/2020/04/Oppo-Find-X2-Pro-265x198.jpg
1866.2440000335
2039.8339999374
16910
16617
200
image/jpeg
Image
https://phonemantra.com/wp-content/uploads/2020/04/Intel-5-150x150.jpg
1902.0470000105
1993.1660000002
9423
9131
200
image/jpeg
Image
https://phonemantra.com/wp-content/uploads/2020/04/Xiaomi-Watch-150x150.jpg
1943.4459999902
2036.9419999188
8639
8347
200
image/jpeg
Image
https://www.facebook.com/tr/
2135.2930000285
2137.4180000275
0
0
-1
Other
https://www.facebook.com/tr/
2254.8709999537
2261.2669999944
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)
599.79
7.24
1208.079
42.346
1250.469
28.288
1284.476
69.463
1370.604
10.109
1382.166
43.851
1434.178
20.005
1454.508
90.246
1544.804
6.795
1556.822
26.04
1585.856
29.313
1615.207
37.156
1758.268
14.268
1789.707
20.281
2150.774
6.177
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. Phonemantra.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Phonemantra.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 27 KB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Phonemantra.com should consider minifying CSS files.
URL Size (Bytes) Potential Savings (Bytes)
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
127964
27396
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Phonemantra.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 111 KB
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 Size (Bytes) Potential Savings (Bytes)
https://phonemantra.com/wp-content/uploads/2020/04/Samsung-smart-TVs-265x198.png
76712
66686
https://phonemantra.com/wp-content/uploads/2020/03/Phonemantra-Logo-1024x339-1.png
51362
28306
https://phonemantra.com/wp-content/uploads/2020/04/Intel-5-534x390.jpg
67681
18547
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.
Server response times are low (TTFB) — Root document took 360 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Phonemantra.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://phonemantra.com/
0
https://phonemantra.com/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Phonemantra.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 1,041 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
127964
https://connect.facebook.net/signals/config/220455392157207?v=2.9.15&r=stable
116836
https://connect.facebook.net/signals/config/290348814895075?v=2.9.15&r=stable
116187
https://phonemantra.com/wp-content/uploads/2020/04/Samsung-smart-TVs-265x198.png
77004
https://phonemantra.com/wp-content/uploads/2020/04/Intel-5-534x390.jpg
67974
https://phonemantra.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?16
66795
https://phonemantra.com/wp-content/themes/Newspaper/js/tagdiv_theme.min.js?ver=9.6.1
53726
https://phonemantra.com/wp-content/uploads/2020/03/Phonemantra-Logo-1024x339-1.png
51654
https://phonemantra.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
34120
https://connect.facebook.net/en_US/fbevents.js
31568
Avoids an excessive DOM size — 309 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
309
Maximum DOM Depth
20
Maximum Child Elements
13
Avoid chaining critical requests — 22 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Phonemantra.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)
Other
370.59
7.822
0.955
https://phonemantra.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
80.591
65.892
1.657
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
200.011
Style & Layout
192.097
Other
110.589
Parse HTML & CSS
57.142
Rendering
49.672
Script Parsing & Compilation
36.075
Garbage Collection
3.334
Keep request counts low and transfer sizes small — 46 requests • 1,041 KB
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
46
1066061
Script
11
413251
Image
14
259888
Font
9
194430
Stylesheet
7
183950
Document
1
13552
Other
4
990
Media
0
0
Third-party
23
446773
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 Size (Bytes) Main-Thread Blocking Time (Ms)
265622
0
30845
0
19544
0
653
0

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.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 1.0 s
The time taken for the primary content of the page to be rendered.
Speed Index — 1.8 s
The time taken for the page contents to be visibly populated.

Opportunities

Eliminate render-blocking resources — Potential savings of 300 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Phonemantra.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://phonemantra.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4
7956
110
https://phonemantra.com/wp-content/plugins/covid19-plugin-wp/assets/style.css?ver=2.2.0
626
150
https://phonemantra.com/wp-content/plugins/social-warfare/css/style.min.css?ver=3.2.0
6454
190
https://phonemantra.com/wp-includes/css/dashicons.min.css?ver=5.4
28811
390
https://phonemantra.com/wp-content/plugins/td-composer/td-multi-purpose/style.css?ver=3328da2481dfce47ccb29fd8f8bc649a
9665
230
https://fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400%2C400italic%2C600%2C600italic%2C700%7CRoboto%3A300%2C400%2C400italic%2C500%2C500italic%2C700%2C900&ver=9.6.1&display=swap
2474
230
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
127964
590
https://phonemantra.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
34120
350
https://phonemantra.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4357
70
Remove unused CSS — Potential savings of 150 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Phonemantra.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Size (Bytes) Potential Savings (Bytes)
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
127964
124364
https://phonemantra.com/wp-includes/css/dashicons.min.css?ver=5.4
28811
28811

Diagnostics

Serve static assets with an efficient cache policy — 4 resources found
Phonemantra.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) Size (Bytes)
https://connect.facebook.net/signals/config/220455392157207?v=2.9.15&r=stable
1200000
116836
https://connect.facebook.net/signals/config/290348814895075?v=2.9.15&r=stable
1200000
116187
https://connect.facebook.net/en_US/fbevents.js
1200000
31568
https://www.google-analytics.com/analytics.js
7200000
18794
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://phonemantra.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?16
175.18299992662
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of phonemantra.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.
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.
`[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-*]` 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.

Audio and video

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

Tables and lists

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

Names and labels

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

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.

Names and labels

Buttons do not 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.
Failing Elements
a
Links do not 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.

Contrast

Best practices

`[id]` attributes on the page are not unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other 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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
77

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
jQuery (Fast path)
WordPress
5.4
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.

Other

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
http://phonemantra.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 2 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
2
Medium
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.
URL Description
https://www.facebook.com/tr/
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector
https://www.facebook.com/tr/
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector
80

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for phonemantra.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 phonemantra.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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

Crawling and Indexing

Page is 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.
Blocking Directive 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.
50

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

Fast and reliable

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

PWA Optimized

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

Fast and reliable

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

Installable

Does not use HTTPS — 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
http://phonemantra.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

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) 72
Performance 54
Accessibility 94
Best Practices 77
SEO 82
Progressive Web App 52
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://phonemantra.com
Updated: 24th April, 2020

6.13 seconds
First Contentful Paint (FCP)
6%
17%
77%

0.25 seconds
First Input Delay (FID)
87%
10%
3%

Simulate loading on mobile
54

Performance

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

Other

Estimated Input Latency — 30 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 phonemantra.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 210 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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://phonemantra.com/
0
84.241000004113
228
0
301
text/html
https://phonemantra.com/
84.583000047132
176.1810000753
13552
61090
200
text/html
Document
https://phonemantra.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4
189.9530000519
281.82100004051
7956
53489
200
text/css
Stylesheet
https://phonemantra.com/wp-content/plugins/covid19-plugin-wp/assets/style.css?ver=2.2.0
190.3680000687
277.93199999724
626
426
200
text/css
Stylesheet
https://phonemantra.com/wp-content/plugins/social-warfare/css/style.min.css?ver=3.2.0
190.65400003456
282.34900010284
6454
46284
200
text/css
Stylesheet
https://phonemantra.com/wp-includes/css/dashicons.min.css?ver=5.4
191.25100004021
531.44400008023
28811
47558
200
text/css
Stylesheet
https://phonemantra.com/wp-content/plugins/td-composer/td-multi-purpose/style.css?ver=3328da2481dfce47ccb29fd8f8bc649a
191.45400007255
287.51900000498
9665
71765
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400%2C400italic%2C600%2C600italic%2C700%7CRoboto%3A300%2C400%2C400italic%2C500%2C500italic%2C700%2C900&ver=9.6.1&display=swap
191.61800004076
210.28700005263
2742
35010
200
text/css
Stylesheet
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
191.83800008614
810.71099999826
127964
1222000
200
text/css
Stylesheet
https://phonemantra.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
192.29300005827
446.44400000107
34120
96873
200
application/javascript
Script
https://phonemantra.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
192.57499999367
447.26200005971
4357
10056
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-96442620-1
193.01500008442
211.63500007242
30845
81636
200
application/javascript
Script
https://phonemantra.com/wp-content/uploads/2020/03/Phonemantra-Logo-1024x339-1.png
193.31900007091
444.08500008285
51654
51362
200
image/png
Image
https://phonemantra.com/wp-content/plugins/social-warfare/js/script.min.js?ver=3.2.0
221.25100006815
323.87800002471
4205
10232
200
application/javascript
Script
https://phonemantra.com/wp-content/themes/Newspaper/js/tagdiv_theme.min.js?ver=9.6.1
325.20200009458
589.08500010148
53726
228414
200
application/javascript
Script
https://phonemantra.com/wp-includes/js/comment-reply.min.js?ver=5.4
445.25900005829
537.653000094
1502
2420
200
application/javascript
Script
https://phonemantra.com/wp-includes/js/wp-embed.min.js?ver=5.4
538.78300008364
629.11800004076
1111
1434
200
application/javascript
Script
https://connect.facebook.net/en_US/fbevents.js
875.22799998987
895.03900008276
31568
128769
200
application/x-javascript
Script
905.43600008823
905.48200008925
0
121
200
image/png
Image
https://phonemantra.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?16
907.7100000577
1165.602000081
66795
122756
200
font/woff
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
909.98400002718
913.01200003363
11655
11056
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
918.45200001262
925.81200005952
9730
9132
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem6YaGs126MiZpBA-UFUK0Zdc1GAK6b.woff2
948.25900008436
952.16600003187
10326
9728
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
964.79900006671
969.0310000442
11619
11020
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
970.40500002913
973.82600000128
11615
11016
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
978.06300001685
981.86600010376
13278
12680
200
font/woff2
Font
990.07300008088
990.12400000356
0
138
200
image/png
Image
990.28100003488
990.32500002068
0
114
200
image/png
Image
https://www.google-analytics.com/analytics.js
1013.534000027
1017.7720000502
18794
45229
200
text/javascript
Script
https://connect.facebook.net/signals/config/220455392157207?v=2.9.15&r=stable
1047.6830000989
1075.0240000198
116155
457789
200
application/x-javascript
Script
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
1053.3340000547
1110.6110000983
9777
9180
200
font/woff2
Font
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=1771662787&t=pageview&_s=1&dl=https%3A%2F%2Fphonemantra.com%2F&ul=en-us&de=UTF-8&dt=Latest%20Mobiles%20%2F%20Latest%20Smartphone%20Launches%20%7C%20New%20Mobiles%20%7C%20Technology%20News&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAUAB~&jid=904836239&gjid=1137699391&cid=419687749.1587730393&tid=UA-96442620-1&_gid=292099439.1587730393&_r=1&gtm=2ou4f0&z=2086401626
1180.2790000802
1217.6040000049
749
0
302
text/html
https://connect.facebook.net/signals/config/290348814895075?v=2.9.15&r=stable
1215.1900000172
1351.6989999916
116835
457789
200
application/x-javascript
Script
https://www.facebook.com/tr/?id=220455392157207&ev=PageView&dl=https%3A%2F%2Fphonemantra.com%2F&rl=&if=false&ts=1587730392832&sw=412&sh=660&v=2.9.15&r=stable&ec=0&o=30&fbp=fb.1.1587730392831.439903053&it=1587730392666&coo=false&rqm=GET
1215.51800007
1231.8650000961
590
44
200
image/gif
Image
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-96442620-1&cid=419687749.1587730393&jid=904836239&_gid=292099439.1587730393&gjid=1137699391&_v=j81&z=2086401626
1217.8710000589
1222.0100000268
653
35
200
image/gif
Image
https://www.facebook.com/tr/?id=290348814895075&ev=PageView&dl=https%3A%2F%2Fphonemantra.com%2F&rl=&if=false&ts=1587730393006&sw=412&sh=660&v=2.9.15&r=stable&a=wordpress-5.4-2.0.2&ec=0&o=30&fbp=fb.1.1587730392831.439903053&it=1587730392666&coo=false&rqm=GET
1387.6330000348
1404.0190000087
441
44
200
image/gif
Image
https://phonemantra.com/wp-content/uploads/2020/04/Intel-5.jpg
1424.5959999971
1910.1810000138
209801
209507
200
image/jpeg
Image
https://phonemantra.com/wp-content/uploads/2020/04/Xiaomi-Watch-450x396.jpg
1442.2150000464
1690.258000046
66912
66619
200
image/jpeg
Image
https://phonemantra.com/wp-content/uploads/2020/04/Samsung-smart-TVs-530x396.png
1465.9400000237
1875.6480000447
298255
297962
200
image/png
Image
https://phonemantra.com/wp-content/uploads/2020/04/Huawei-Mate-10-530x396.jpg
1501.6349999933
1673.3960000565
21943
21650
200
image/jpeg
Image
https://phonemantra.com/wp-content/uploads/2020/04/Oppo-Find-X2-Pro-530x396.jpg
1542.2610000242
1867.5490000751
53690
53397
200
image/jpeg
Image
https://www.facebook.com/tr/
1719.3990000524
1721.6890000273
0
0
-1
Other
https://www.facebook.com/tr/
1890.9710000735
1893.4900000459
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)
202.135
6.501
212.088
6.251
838.055
36.712
874.81
26.838
901.825
5.106
907.238
104.571
1026.691
10.515
1037.267
15.022
1058.193
12.894
1071.111
22.899
1094.134
60.633
1159.488
5.513
1166.387
37.52
1208.871
30.173
1241.18
16.242
1398.386
12.647
1428.407
20.028
1737.479
6.006
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. Phonemantra.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Phonemantra.com should consider lazy-loading offscreen and hidden images.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Phonemantra.com should consider minifying JS files.
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.
Server response times are low (TTFB) — Root document took 90 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Phonemantra.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://phonemantra.com/
0
https://phonemantra.com/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Phonemantra.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 1,426 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://phonemantra.com/wp-content/uploads/2020/04/Samsung-smart-TVs-530x396.png
298255
https://phonemantra.com/wp-content/uploads/2020/04/Intel-5.jpg
209801
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
127964
https://connect.facebook.net/signals/config/290348814895075?v=2.9.15&r=stable
116835
https://connect.facebook.net/signals/config/220455392157207?v=2.9.15&r=stable
116155
https://phonemantra.com/wp-content/uploads/2020/04/Xiaomi-Watch-450x396.jpg
66912
https://phonemantra.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?16
66795
https://phonemantra.com/wp-content/themes/Newspaper/js/tagdiv_theme.min.js?ver=9.6.1
53726
https://phonemantra.com/wp-content/uploads/2020/04/Oppo-Find-X2-Pro-530x396.jpg
53690
https://phonemantra.com/wp-content/uploads/2020/03/Phonemantra-Logo-1024x339-1.png
51654
Avoids an excessive DOM size — 309 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
309
Maximum DOM Depth
20
Maximum Child Elements
13
Avoid chaining critical requests — 21 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Phonemantra.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)
Other
1557.74
26.876
3.7
https://phonemantra.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
302.508
263.6
7.092
https://www.google-analytics.com/analytics.js
147.888
85.24
5.164
https://connect.facebook.net/signals/config/220455392157207?v=2.9.15&r=stable
138.528
106.888
31.64
https://phonemantra.com/wp-content/themes/Newspaper/js/tagdiv_theme.min.js?ver=9.6.1
87.572
59.152
24
https://www.googletagmanager.com/gtag/js?id=UA-96442620-1
70.264
61.312
8.952
https://connect.facebook.net/signals/config/290348814895075?v=2.9.15&r=stable
62.392
29.776
30.708
Keep request counts low and transfer sizes small — 43 requests • 1,426 KB
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
43
1460699
Image
12
703939
Script
11
413218
Stylesheet
7
184218
Font
8
144795
Document
1
13552
Other
4
977
Media
0
0
Third-party
22
397372
Minimize third-party usage — Third-party code blocked the main thread for 70 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 Size (Bytes) Main-Thread Blocking Time (Ms)
265589
32.632
19543
32.524
30845
0
653
0

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.

Metrics

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 3.8 s
The time taken for the primary content of the page to be rendered.
Speed Index — 5.4 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 7.2 s
The time taken for the page to become fully interactive.
First CPU Idle — 6.4 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 150 ms
Users could experience a delay when interacting with the page.

Opportunities

Minify CSS — Potential savings of 27 KB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Phonemantra.com should consider minifying CSS files.
URL Size (Bytes) Potential Savings (Bytes)
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
127964
27396
Efficiently encode images — Potential savings of 84 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Size (Bytes) Potential Savings (Bytes)
https://phonemantra.com/wp-content/uploads/2020/04/Intel-5.jpg
209507
86045

Diagnostics

Minimize main-thread work — 2.5 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)
Style & Layout
772.76
Script Evaluation
734.264
Other
438.768
Rendering
211.088
Parse HTML & CSS
208.984
Script Parsing & Compilation
139.156

Opportunities

Eliminate render-blocking resources — Potential savings of 1,220 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Phonemantra.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://phonemantra.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4
7956
480
https://phonemantra.com/wp-content/plugins/covid19-plugin-wp/assets/style.css?ver=2.2.0
626
480
https://phonemantra.com/wp-content/plugins/social-warfare/css/style.min.css?ver=3.2.0
6454
780
https://phonemantra.com/wp-includes/css/dashicons.min.css?ver=5.4
28811
1680
https://phonemantra.com/wp-content/plugins/td-composer/td-multi-purpose/style.css?ver=3328da2481dfce47ccb29fd8f8bc649a
9665
930
https://fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400%2C400italic%2C600%2C600italic%2C700%7CRoboto%3A300%2C400%2C400italic%2C500%2C500italic%2C700%2C900&ver=9.6.1&display=swap
2742
780
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
127964
2430
https://phonemantra.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
34120
1380
https://phonemantra.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4357
330
Remove unused CSS — Potential savings of 149 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Phonemantra.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Size (Bytes) Potential Savings (Bytes)
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1
127964
123982
https://phonemantra.com/wp-includes/css/dashicons.min.css?ver=5.4
28811
28811
Serve images in next-gen formats — Potential savings of 451 KB
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 Size (Bytes) Potential Savings (Bytes)
https://phonemantra.com/wp-content/uploads/2020/04/Samsung-smart-TVs-530x396.png
297962
269728
https://phonemantra.com/wp-content/uploads/2020/04/Intel-5.jpg
209507
138863
https://phonemantra.com/wp-content/uploads/2020/03/Phonemantra-Logo-1024x339-1.png
51362
28306
https://phonemantra.com/wp-content/uploads/2020/04/Oppo-Find-X2-Pro-530x396.jpg
53397
12967
https://phonemantra.com/wp-content/uploads/2020/04/Huawei-Mate-10-530x396.jpg
21650
12152

Diagnostics

Serve static assets with an efficient cache policy — 4 resources found
Phonemantra.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) Size (Bytes)
https://connect.facebook.net/signals/config/290348814895075?v=2.9.15&r=stable
1200000
116835
https://connect.facebook.net/signals/config/220455392157207?v=2.9.15&r=stable
1200000
116155
https://connect.facebook.net/en_US/fbevents.js
1200000
31568
https://www.google-analytics.com/analytics.js
7200000
18794
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://phonemantra.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?16
257.89200002328

Other

First Contentful Paint (3G) — 8507 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of phonemantra.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.
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.
`[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-*]` 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.

Audio and video

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

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

Internationalization and localization

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

Best practices

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

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

Best practices

`[id]` attributes on the page are not unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
Failing Elements

Names and labels

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

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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
77

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
jQuery (Fast path)
WordPress
5.4
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.

Other

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
http://phonemantra.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 2 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
2
Medium
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.
URL Description
https://www.facebook.com/tr/
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector
https://www.facebook.com/tr/
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for phonemantra.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 phonemantra.com on mobile screens.
Document uses legible font sizes — 97.64% 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
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1:8543:22
.td-module-meta-info
2.22%
11px
https://phonemantra.com/wp-content/themes/Newspaper/style.css?ver=9.6.1:8583:21
.td-module-comments
0.13%
10px
Legible text
97.64%
≥ 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.
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.
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 — 89% 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
250x20
75x18

Content Best Practices

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

Crawling and Indexing

Page is 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.
Blocking Directive 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.
52

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

Fast and reliable

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

PWA Optimized

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

Fast and reliable

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

Installable

Does not use HTTPS — 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
http://phonemantra.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

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: 68.65.123.224
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Namecheap, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Private Registration
Organization:
Country: US
City: Denver
State: CO
Post Code: 80205
Email: PhoneMantra.com@NameBrightPrivacy.com
Phone: +1.7204960020
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Very Risky
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: phonemantra.com
Issued By: Sectigo RSA Domain Validation Secure Server CA
Valid From: 9th March, 2020
Valid To: 9th March, 2021
Subject: CN = phonemantra.com
Hash: 595c93ac
Issuer: CN = Sectigo RSA Domain Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 0xF36AB811745C8085B0EC2414E7C45BA7
Serial Number (Hex): F36AB811745C8085B0EC2414E7C45BA7
Valid From: 9th March, 2024
Valid To: 9th March, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Mar 9 15:37:32.177 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:CA:12:BE:B9:7E:39:4B:B5:6E:97:4B:
B6:48:E9:14:51:64:25:9A:10:76:02:3E:BE:81:95:02:
3F:C6:63:26:63:02:20:33:C1:C0:38:57:25:4F:FF:E6:
DB:69:6C:A9:00:F6:D0:78:86:92:BD:2C:1C:08:4E:34:
A7:E0:0D:91:03:73:69
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 : Mar 9 15:37:32.123 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:2A:70:67:A5:E4:FD:C5:2D:1D:D1:A0:90:
4E:E5:8A:FA:E7:FB:AE:40:A8:1D:08:15:4B:DE:7F:09:
DB:3F:64:09:02:20:22:2A:CF:FE:0C:56:C7:A2:72:F9:
08:7F:C0:26:D3:09:BD:02:8C:70:D3:C5:15:AD:C9:E5:
A2:00:61:07:59:50
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.phonemantra.com
DNS:phonemantra.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
phonemantra.com. 68.65.123.224 IN 1199

NS Records

Host Nameserver Class TTL
phonemantra.com. dns1.namecheaphosting.com. IN 21599
phonemantra.com. dns2.namecheaphosting.com. IN 21599

MX Records

Priority Host Server Class TTL
0 phonemantra.com. mail.phonemantra.com. IN 1199

SOA Records

Domain Name Primary NS Responsible Email TTL
phonemantra.com. dns1.namecheaphosting.com. cpanel.tech.namecheap.com. 21599

TXT Records

Host Value Class TTL
phonemantra.com. v=spf1 IN 1199

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 6th May, 2020
Server: Apache
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/7.2.30
Last-Modified: 5th May, 2020

Whois Lookup

Created: 22nd January, 2017
Changed: 25th January, 2019
Expires: 22nd January, 2022
Registrar: DropCatch.com 721 LLC
Status: clientTransferProhibited
Nameservers: dns1.namecheaphosting.com
dns2.namecheaphosting.com
Owner Name: Private Registration
Owner Street: 2635 Walnut Street
Owner Post Code: 80205
Owner City: Denver
Owner State: CO
Owner Country: US
Owner Phone: +1.7204960020
Owner Email: PhoneMantra.com@NameBrightPrivacy.com
Admin Name: Private Registration
Admin Street: 2635 Walnut Street
Admin Post Code: 80205
Admin City: Denver
Admin State: CO
Admin Country: US
Admin Phone: +1.7204960020
Admin Email: PhoneMantra.com@NameBrightPrivacy.com
Tech Name: Private Registration
Tech Street: 2635 Walnut Street
Tech Post Code: 80205
Tech City: Denver
Tech State: CO
Tech Country: US
Tech Phone: +1.7204960020
Tech Email: PhoneMantra.com@NameBrightPrivacy.com
Full Whois: Domain Name: PhoneMantra.com
Registry Domain ID: 2092128175_DOMAIN_COM-VRSN
Registrar WHOIS server: whois.NameBright.com
Registrar URL: http://www.NameBright.com
Updated Date: 2019-01-25T00:00:00.000Z
Creation Date: 2017-01-22T19:10:37.000Z
Registrar Registration Expiration Date: 2022-01-22T00:00:00.000Z
Registrar: DropCatch.com 721 LLC
Registrar IANA ID: 2201
Registrar Abuse Contact Email: abuse@NameBright.com
Registrar Abuse Contact Phone: +1.7204960020
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Private Registration
Registrant Organization:
Registrant Street: 2635 Walnut Street
Registrant City: Denver
Registrant State/Province: CO
Registrant Postal Code: 80205
Registrant Country: US
Registrant Phone: +1.7204960020
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: PhoneMantra.com@NameBrightPrivacy.com
Registry Admin ID: Not Available From Registry
Admin Name: Private Registration
Admin Organization:
Admin Street: 2635 Walnut Street
Admin City: Denver
Admin State/Province: CO
Admin Postal Code: 80205
Admin Country: US
Admin Phone: +1.7204960020
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: PhoneMantra.com@NameBrightPrivacy.com
Registry Tech ID: Not Available From Registry
Tech Name: Private Registration
Tech Organization:
Tech Street: 2635 Walnut Street
Tech City: Denver
Tech State/Province: CO
Tech Postal Code: 80205
Tech Country: US
Tech Phone: +1.7204960020
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: PhoneMantra.com@NameBrightPrivacy.com
Name Server: dns1.namecheaphosting.com
Name Server: dns2.namecheaphosting.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System:
http://wdprs.internic.net
>>> Last update of WHOIS database: 2020-05-06T03:11:25.356Z <<<

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

Nameservers

Name IP Address
dns1.namecheaphosting.com 156.154.132.200
dns2.namecheaphosting.com 156.154.133.200
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

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