waptap.com

waptap.com is SSL secured

Free website and domain report on waptap.com

Last Updated: 29th November, 2022 Update Now
Overview

Snoop Summary for waptap.com

This is a free and comprehensive report about waptap.com. Waptap.com is hosted in United States on a server with an IP address of 104.26.13.200, where the local currency is USD and English is the local language. Waptap.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If waptap.com was to be sold it would possibly be worth $1,000 USD (based on the daily revenue potential of the website over a 24 month period). Waptap.com is somewhat popular with an estimated 476 daily unique visitors. This report was last updated 29th November, 2022.

About waptap.com

Site Preview:
Title: Waptap - Freedom to be yourself!
Description: A social network of unrestricted creativity.
Keywords and Tags: nudity
Related Terms: unrestricted
Fav Icon:
Age: Over 7 years old
Domain Created: 2nd October, 2016
Domain Updated: 5th August, 2022
Domain Expires: 2nd October, 2027
Review

Snoop Score

1/5

Valuation

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

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,490,178
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 476
Monthly Visitors: 14,488
Yearly Visitors: 173,740
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

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

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

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

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 88
Performance 97
Accessibility 97
Best Practices 92
SEO 100
PWA 56
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://waptap.com/
Updated: 29th November, 2022

0.77 seconds
First Contentful Paint (FCP)
96%
2%
2%

0.00 seconds
First Input Delay (FID)
98%
2%
0%

97

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 150 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).
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
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://waptap.com/
http/1.1
0
150.79700003844
714
0
301
text/plain
https://waptap.com/
h2
151.18300006725
350.30500008725
9532
36192
200
text/html
Document
https://waptap.com/static/logo-3c17f86ff839b6d9c21d8bae29211db9.png
h2
366.9050000608
549.53399999067
46954
46010
200
image/webp
Image
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
h2
367.20500001684
413.86400000192
77387
220361
200
application/javascript
Script
https://waptap.com/app-ba4d1dde422b5cde931b.js
h2
393.04700004868
548.96600008942
30493
93558
200
application/javascript
Script
https://waptap.com/framework-c7703072d26e29cfa5cd.js
h2
393.43100006226
550.21400004625
46876
140679
200
application/javascript
Script
https://waptap.com/webpack-runtime-32310838aab478d0d78b.js
h2
393.53400003165
507.37200002186
3155
5030
200
application/javascript
Script
data
402.57200004999
402.78700005729
0
3005
200
image/svg+xml
Image
https://cdn.rollbar.com/rollbarjs/refs/tags/v2.25.0/rollbar.min.js
http/1.1
796.11700004898
858.63600007724
24073
78200
200
application/javascript
Script
https://waptap.com/page-data/app-data.json
h2
805.14300009236
957.55699998699
845
50
200
application/json
XHR
https://waptap.com/page-data/index/page-data.json
h2
805.30200002249
957.19200000167
902
130
200
application/json
XHR
https://www.google-analytics.com/g/collect?v=2&tid=G-TTCPCWJVXV&gtm=2oeb90&_p=790447288&cid=903786051.1669748434&ul=en-us&sr=800x600&uaa=x86&uab=&uafvl=&uamb=0&uam=&uap=macOS&uapv=10.15.7&uaw=0&_s=1&sid=1669748434&sct=1&seg=0&dl=https%3A%2F%2Fwaptap.com%2F&dt=Waptap%20-%20Freedom%20to%20be%20yourself!&en=scroll&_fv=1&_nsi=1&_ss=1&epn.percent_scrolled=90
1059.5600000815
1098.3220000053
0
0
-1
Ping
https://waptap.com/5d07935b989b486f66f2541be9923343b4d1925d-cc8f6414c8070b2a375e.js
h2
1083.7770000799
1258.9360000566
6990
16886
200
application/javascript
Script
https://waptap.com/component---src-pages-index-tsx-2ebbfdb7f42d5420e41e.js
h2
1089.6740000462
1259.3380000908
2390
3182
200
application/javascript
Script
https://waptap.com/page-data/sq/d/3267286006.json
h2
1089.9080000818
1259.5539999893
911
170
200
application/json
XHR
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)
362.355
26.245
388.879
15.508
404.397
73.837
478.336
21.58
499.977
17.691
519.487
60.721
580.826
16.817
599.268
16.107
615.971
49.114
666.79
36.275
703.732
106.235
811.156
67.957
879.971
109.178
990.48
82.687
1073.177
5.58
1080.238
12.093
1092.418
14.214
1287.547
11.942
1304.561
43.973
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Waptap.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 39 KiB
Images can slow down the page's load time. Waptap.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://waptap.com/static/logo-3c17f86ff839b6d9c21d8bae29211db9.png
46010
40328
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Waptap.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Waptap.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Waptap.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Waptap.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 50 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://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
77387
29396
https://waptap.com/framework-c7703072d26e29cfa5cd.js
46876
21296
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 200 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://waptap.com/
200.115
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Waptap.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://waptap.com/
190
https://waptap.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Waptap.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 — Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://cdn.rollbar.com/rollbarjs/refs/tags/v2.25.0/rollbar.min.js
6236
https://waptap.com/5d07935b989b486f66f2541be9923343b4d1925d-cc8f6414c8070b2a375e.js
69
https://waptap.com/app-ba4d1dde422b5cde931b.js
54
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://waptap.com/static/logo-3c17f86ff839b6d9c21d8bae29211db9.png
0
Avoids enormous network payloads — Total size was 245 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
77387
https://waptap.com/static/logo-3c17f86ff839b6d9c21d8bae29211db9.png
46954
https://waptap.com/framework-c7703072d26e29cfa5cd.js
46876
https://waptap.com/app-ba4d1dde422b5cde931b.js
30493
https://cdn.rollbar.com/rollbarjs/refs/tags/v2.25.0/rollbar.min.js
24073
https://waptap.com/
9532
https://waptap.com/5d07935b989b486f66f2541be9923343b4d1925d-cc8f6414c8070b2a375e.js
6990
https://waptap.com/webpack-runtime-32310838aab478d0d78b.js
3155
https://waptap.com/component---src-pages-index-tsx-2ebbfdb7f42d5420e41e.js
2390
https://waptap.com/page-data/sq/d/3267286006.json
911
Uses efficient cache policy on static assets — 0 resources found
Waptap.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 33 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
33
Maximum DOM Depth
11
Maximum Child Elements
9
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Waptap.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 — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
onInitialClientRender
Mark
1352.154
JavaScript execution time — 0.5 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/gtag/js?id=G-TTCPCWJVXV
267.459
254.004
7.368
https://waptap.com/
169.83
6.204
1.764
https://waptap.com/framework-c7703072d26e29cfa5cd.js
162.39
104.232
57.542
Unattributable
148.349
5.32
0
https://waptap.com/app-ba4d1dde422b5cde931b.js
55.195
49.989
2.274
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
440.067
Other
174.039
Script Parsing & Compilation
71.744
Style & Layout
62.598
Rendering
58.876
Parse HTML & CSS
14.667
Garbage Collection
5.566
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 14 requests • 245 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
14
251222
Script
7
191364
Image
1
46954
Document
1
9532
Other
5
3372
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
3
101460
Minimize third-party usage — Third-party code blocked the main thread for 100 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
77387
95.844
24073
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
838
109
https://waptap.com/framework-c7703072d26e29cfa5cd.js
620
106
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
947
83
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
770
68
Unattributable
230
61
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.
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 waptap.com on mobile screens.
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.

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

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
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.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Gatsby
core-js
core-js-global@3.22.8
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://waptap.com/
Allowed
100

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

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

PWA

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

Installable

Web app manifest and service worker 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.

PWA Optimized

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

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
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) 81
Performance 66
Accessibility 97
Best Practices 83
SEO 97
PWA 60
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://waptap.com/
Updated: 29th November, 2022

0.84 seconds
First Contentful Paint (FCP)
94%
4%
2%

0.02 seconds
First Input Delay (FID)
98%
2%
0%

66

Performance

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

Metrics

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

Audits

First Meaningful Paint — 2.2 s
The time taken for the primary content of the page to be rendered.
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://waptap.com/
http/1.1
0
60.745000373572
701
0
301
text/plain
https://waptap.com/
h2
61.157000251114
146.88100013882
9772
36666
200
text/html
Document
https://ajax.cloudflare.com/cdn-cgi/scripts/04b3eb47/cloudflare-static/mirage2.min.js
h2
165.14300042763
200.04600007087
12784
38536
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
h2
178.16300038248
233.54400042444
77378
220361
200
application/javascript
Script
https://waptap.com/app-ba4d1dde422b5cde931b.js
h2
199.80900036171
290.12600006536
30500
93558
200
application/javascript
Script
https://waptap.com/framework-c7703072d26e29cfa5cd.js
h2
200.7450000383
292.68600000069
46876
140679
200
application/javascript
Script
https://waptap.com/webpack-runtime-32310838aab478d0d78b.js
h2
200.83400001749
293.08800026774
3138
5030
200
application/javascript
Script
data
206.74100005999
206.97100041434
0
3005
200
image/svg+xml
Image
https://waptap.com/static/logo-3c17f86ff839b6d9c21d8bae29211db9.png
h2
338.31100026146
394.85500007868
46954
46010
200
image/webp
Image
https://cdn.rollbar.com/rollbarjs/refs/tags/v2.25.0/rollbar.min.js
http/1.1
535.88100010529
661.41699999571
24004
78200
200
application/javascript
Script
https://waptap.com/page-data/app-data.json
h2
541.64100019261
621.89000006765
839
50
200
application/json
XHR
https://waptap.com/page-data/index/page-data.json
h2
541.78600013256
633.53300001472
898
130
200
application/json
XHR
https://www.google-analytics.com/g/collect?v=2&tid=G-TTCPCWJVXV&gtm=2oeb90&_p=542194378&cid=625023670.1669748454&ul=en-us&sr=360x640&uaa=&uab=&uafvl=&uamb=1&uam=Moto%20G4&uap=Android&uapv=6.0&uaw=0&_s=1&sid=1669748454&sct=1&seg=0&dl=https%3A%2F%2Fwaptap.com%2F&dt=Waptap%20-%20Freedom%20to%20be%20yourself!&en=scroll&_fv=1&_nsi=1&_ss=1&epn.percent_scrolled=90
572.88500014693
593.24300009757
0
0
-1
Ping
https://waptap.com/5d07935b989b486f66f2541be9923343b4d1925d-cc8f6414c8070b2a375e.js
h2
638.25400033966
679.76700002328
6990
16886
200
application/javascript
Script
https://waptap.com/component---src-pages-index-tsx-2ebbfdb7f42d5420e41e.js
h2
638.38400039822
677.29300027713
2373
3182
200
application/javascript
Script
https://waptap.com/page-data/sq/d/3267286006.json
h2
639.51300038025
742.0169999823
911
170
200
application/json
XHR
https://api.rollbar.com/api/1/item/
h2
879.97900042683
942.73800030351
577
100
200
application/json
XHR
https://api.rollbar.com/api/1/item/
http/1.1
822.68900005147
879.18000016361
387
0
204
Preflight
https://api.rollbar.com/api/1/item/
h2
895.37000004202
1008.0010001548
577
100
200
application/json
XHR
https://api.rollbar.com/api/1/item/
h2
856.43300041556
894.75700026378
374
0
204
Preflight
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)
152.603
29.565
182.537
10.164
193.133
6.23
204.822
32.419
237.3
23.034
264.961
21.475
288.385
48.427
339.524
8.431
347.983
9.167
357.164
12.985
370.25
14.161
384.544
29.044
416.402
52.586
469.004
14.233
484.825
10.87
495.735
46.235
545.691
31.394
577.094
11.439
669.448
11.23
696.403
7.041
750.96
95.326
846.323
13.057
861.42
8.251
869.709
5.455
949.272
11.052
1010.69
5.3
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Waptap.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 7 KiB
Images can slow down the page's load time. Waptap.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://waptap.com/static/logo-3c17f86ff839b6d9c21d8bae29211db9.png
46010
6857
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Waptap.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Waptap.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Waptap.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Waptap.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 29 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://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
77378
29393
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 90 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://waptap.com/
86.719
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Waptap.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://waptap.com/
630
https://waptap.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Waptap.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 — Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://cdn.rollbar.com/rollbarjs/refs/tags/v2.25.0/rollbar.min.js
6218
https://waptap.com/5d07935b989b486f66f2541be9923343b4d1925d-cc8f6414c8070b2a375e.js
69
https://waptap.com/app-ba4d1dde422b5cde931b.js
54
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 260 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
77378
https://waptap.com/static/logo-3c17f86ff839b6d9c21d8bae29211db9.png
46954
https://waptap.com/framework-c7703072d26e29cfa5cd.js
46876
https://waptap.com/app-ba4d1dde422b5cde931b.js
30500
https://cdn.rollbar.com/rollbarjs/refs/tags/v2.25.0/rollbar.min.js
24004
https://ajax.cloudflare.com/cdn-cgi/scripts/04b3eb47/cloudflare-static/mirage2.min.js
12784
https://waptap.com/
9772
https://waptap.com/5d07935b989b486f66f2541be9923343b4d1925d-cc8f6414c8070b2a375e.js
6990
https://waptap.com/webpack-runtime-32310838aab478d0d78b.js
3138
https://waptap.com/component---src-pages-index-tsx-2ebbfdb7f42d5420e41e.js
2373
Uses efficient cache policy on static assets — 1 resource found
Waptap.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://ajax.cloudflare.com/cdn-cgi/scripts/04b3eb47/cloudflare-static/mirage2.min.js
172800000
12784
Avoids an excessive DOM size — 33 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
33
Maximum DOM Depth
11
Maximum Child Elements
9
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Waptap.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 — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
onInitialClientRender
Mark
861.259
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 19 requests • 260 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
19
266033
Script
8
204043
Image
1
46954
Document
1
9772
Other
9
5264
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
8
116081
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.2811279296875
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 13 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://waptap.com/framework-c7703072d26e29cfa5cd.js
3853
381
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
3174
210
https://waptap.com/app-ba4d1dde422b5cde931b.js
1828
185
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
3384
126
https://waptap.com/
1110
118
https://www.googletagmanager.com/gtag/js?id=G-TTCPCWJVXV
3058
116
https://ajax.cloudflare.com/cdn-cgi/scripts/04b3eb47/cloudflare-static/mirage2.min.js
2244
97
Unattributable
630
92
https://ajax.cloudflare.com/cdn-cgi/scripts/04b3eb47/cloudflare-static/mirage2.min.js
2158
86
https://waptap.com/
1269
65
Unattributable
774
57
https://waptap.com/
831
57
Unattributable
722
52
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.
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 waptap.com on mobile screens.
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.

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.1 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.1 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 3.1 s
The timing of the largest text or image that is painted.

Other

Reduce JavaScript execution time — 1.5 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/gtag/js?id=G-TTCPCWJVXV
506.916
405.64
54.132
https://waptap.com/framework-c7703072d26e29cfa5cd.js
436.396
394.764
39.864
https://waptap.com/
381.94
61.832
8.636
Unattributable
370.612
6.848
0
https://waptap.com/app-ba4d1dde422b5cde931b.js
305.992
282.452
8.784
https://ajax.cloudflare.com/cdn-cgi/scripts/04b3eb47/cloudflare-static/mirage2.min.js
297.332
154.392
3.524
https://cdn.rollbar.com/rollbarjs/refs/tags/v2.25.0/rollbar.min.js
83.332
67.992
6.228
https://waptap.com/5d07935b989b486f66f2541be9923343b4d1925d-cc8f6414c8070b2a375e.js
54.096
12.752
2.168
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)
Script Evaluation
1406.716
Other
463.804
Style & Layout
217.92
Rendering
158.824
Script Parsing & Compilation
124.928
Garbage Collection
44.94
Parse HTML & CSS
41.924
First Contentful Paint (3G) — 3894 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Total Blocking Time — 620 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.281
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

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

Other

Reduce the impact of third-party code — Third-party code blocked the main thread for 330 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)
77378
248.004
12784
82.676
25919
0
0
0
97

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
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.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Gatsby
core-js
core-js-global@3.22.8
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://waptap.com/
Allowed

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
Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at sa (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:49199) at xi (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:122492) at bs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109796) at vs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109724) at gs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109587) at ls (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:104719) at S (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138192) at MessagePort.T (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138724)
Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at sa (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:49199) at xi (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:122492) at bs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109796) at vs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109724) at gs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109587) at ls (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:104719) at S (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138192) at MessagePort.T (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138724)
Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at sa (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:49199) at xi (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:122492) at bs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109796) at vs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109724) at gs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109587) at ls (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:104719) at S (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138192) at MessagePort.T (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138724)
Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at sa (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:49199) at xi (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:122492) at bs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109796) at vs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109724) at gs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109587) at ls (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:104719) at S (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138192) at MessagePort.T (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138724)
Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at sa (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:49199) at xi (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:122492) at bs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109796) at vs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109724) at gs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109587) at ls (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:104719) at S (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138192) at MessagePort.T (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138724)
Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at xi (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:122178) at bs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109796) at vs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109724) at gs (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:109587) at as (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:106394) at ls (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:104946) at S (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138192) at MessagePort.T (https://waptap.com/framework-c7703072d26e29cfa5cd.js:1:138724)
97

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for waptap.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 waptap.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 75% 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
FAQ
28x16
34x16

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

PWA

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

Installable

Web app manifest and service worker 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.

PWA Optimized

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

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
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: 104.26.13.200
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
Cloudflare, Inc.
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
DNC Holdings, Inc 104.143.9.80
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: waptap.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 9th February, 2022
Valid To: 9th February, 2023
Subject: CN = waptap.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 9765f2ed
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 11383232998426762663663652944154856256
Serial Number (Hex): 089054B7CCB87CC9D8F1C5E3ACBA0B40
Valid From: 9th February, 2024
Valid To: 9th February, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Feb 9 02:32:00.090 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C9:5E:B4:BA:D4:6A:5A:28:A6:4D:28:
36:1A:A6:07:16:4B:BE:63:0F:52:E8:2D:D6:0A:31:CD:
C2:40:01:A9:84:02:21:00:91:81:C5:75:90:2E:61:5F:
01:7D:0A:62:D2:C4:E5:C7:A4:B1:CD:46:A3:46:E5:C2:
0D:38:CF:F4:72:47:C3:9D
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Feb 9 02:32:00.074 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:27:32:9E:B8:A0:08:3B:B1:9F:D7:15:D9:
A5:64:3A:E4:C2:9D:0B:73:9D:17:15:21:49:BB:B4:88:
BC:D0:5C:61:02:21:00:D0:F2:70:4A:D7:24:1E:F7:9B:
CF:21:26:BF:2C:AE:5C:9A:41:A2:70:42:6C:2B:A6:D9:
79:AA:50:92:09:89:E6
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Feb 9 02:32:00.114 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:9F:D4:21:D5:FB:80:2F:9A:16:F9:12:
34:37:70:A2:FE:59:08:BC:2E:74:03:7E:18:BC:99:C8:
4F:32:F9:BE:A8:02:21:00:F4:E5:34:41:28:D3:26:BB:
E7:4F:11:6F:F6:F7:16:F4:7A:88:29:BB:5A:0E:1D:ED:
4F:5A:E2:FA:54:83:B6:93
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:waptap.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 29th November, 2022
Content-Type: text/html; charset=utf-8
Cache-Control: public, max-age=0, must-revalidate
Server: cloudflare
Connection: keep-alive
Access-Control-Allow-Origin: *
Link: <https://www.googletagmanager.com>; rel="preconnect"
referrer-policy: strict-origin-when-cross-origin
x-content-type-options: nosniff
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=LnO3LxLwDxaI992f%2F5yFGf1bIB1lhzvYJavdijxZtU4hEjAN0AZusgoq52vYfyxo3najSHN4245xDE%2FWlmmOJqLYb%2B4Jz5AYtcV%2BSQOY81O9RkA8DIeK1hIJdgHX"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Vary: Accept-Encoding
CF-Cache-Status: DYNAMIC
CF-RAY: 771d9604cc30f051-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 2nd October, 2016
Changed: 5th August, 2022
Expires: 2nd October, 2027
Registrar: DNC Holdings, Inc
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
renewPeriod
Nameservers: guss.ns.cloudflare.com
jamie.ns.cloudflare.com
Owner Name: Jewella Privacy - ea055
Owner Organization: Jewella Privacy LLC Privacy ID# 14718053
Owner Street: 5860 Citrus Blvd, Suite D, #172
Owner Post Code: 70123
Owner City: Harahan
Owner State: LA
Owner Country: US
Owner Phone: +1.5043550545
Owner Email: waptap.com@dnic.JewellaPrivacy.com
Admin Name: Jewella Privacy
Admin Organization: Jewella Privacy LLC Privacy ID# 14718053
Admin Street: 5860 Citrus Blvd, Suite D, #172
Admin Post Code: 70123
Admin City: Harahan
Admin State: LA
Admin Country: US
Admin Phone: +1.5043550545
Admin Email: waptap.com@dnic.JewellaPrivacy.com
Tech Name: Jewella Privacy
Tech Organization: Jewella Privacy LLC Privacy ID# 14718053
Tech Street: 5860 Citrus Blvd, Suite D, #172
Tech Post Code: 70123
Tech City: Harahan
Tech State: LA
Tech Country: US
Tech Phone: +1.5043550545
Tech Email: waptap.com@dnic.JewellaPrivacy.com
Full Whois:
Domain Name: WAPTAP.COM
Registry Domain ID: 2063230808_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.directnic.com
Registrar URL: http://www.directnic.com
Updated Date: 2022-08-05T04:52:19Z
Creation Date: 2016-10-02T13:18:17Z
Registrar Registration Expiration Date: 2027-10-02T13:18:17Z
Registrar: DNC Holdings, Inc
Registrar IANA ID: 291
Registrar Abuse Contact Email: abuse@directnic.com
Registrar Abuse Contact Phone: +1.8778569598
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: renewPeriod (https://www.icann.org/epp#renewPeriod)
Registry Registrant ID: Not Available From Registry
Registrant Name: Jewella Privacy - ea055
Registrant Organization: Jewella Privacy LLC Privacy ID# 14718053
Registrant Street: 5860 Citrus Blvd, Suite D, #172
Registrant City: Harahan
Registrant State/Province: LA
Registrant Postal Code: 70123
Registrant Country: US
Registrant Phone: +1.5043550545
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: waptap.com@dnic.JewellaPrivacy.com
Registry Admin ID: Not Available From Registry
Admin Name: Jewella Privacy
Admin Organization: Jewella Privacy LLC Privacy ID# 14718053
Admin Street: 5860 Citrus Blvd, Suite D, #172
Admin City: Harahan
Admin State/Province: LA
Admin Postal Code: 70123
Admin Country: US
Admin Phone: +1.5043550545
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: waptap.com@dnic.JewellaPrivacy.com
Registry Tech ID: Not Available From Registry
Tech Name: Jewella Privacy
Tech Organization: Jewella Privacy LLC Privacy ID# 14718053
Tech Street: 5860 Citrus Blvd, Suite D, #172
Tech City: Harahan
Tech State/Province: LA
Tech Postal Code: 70123
Tech Country: US
Tech Phone: +1.5043550545
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: waptap.com@dnic.JewellaPrivacy.com
Name Server: GUSS.NS.CLOUDFLARE.COM
Name Server: JAMIE.NS.CLOUDFLARE.COM
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net
>>> Last update of WHOIS database: 2022-11-29T07:00:26Z <<<


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



The compilation, repackaging, dissemination, or other use of this WHOIS
data is expressly prohibited without the prior written consent of
The Producers, Inc.

The Producers reserves the right to terminate your access to its WHOIS
database in its sole discretion, including without limitation, for
excessive querying of the database or for failure to otherwise abide by
this policy.

The Producers reserves the right to modify these terms at any time.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY.
LACK OF A DOMAIN RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.


Nameservers

Name IP Address
guss.ns.cloudflare.com 172.64.33.172
jamie.ns.cloudflare.com 172.64.32.168
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address