ghettogaggers.com

ghettogaggers.com is SSL secured

Free website and domain report on ghettogaggers.com

Last Updated: 1st October, 2022 Update Now
Overview

Snoop Summary for ghettogaggers.com

This is a free and comprehensive report about ghettogaggers.com. The domain ghettogaggers.com is currently hosted on a server located in Franklin, Michigan in United States with the IP address 64.59.126.209, where USD is the local currency and the local language is English. Our records indicate that ghettogaggers.com is privately registered by Jewella Privacy LLC Privacy ID# 11276558. Ghettogaggers.com has the potential to be earning an estimated $15 USD per day from advertising revenue. If ghettogaggers.com was to be sold it would possibly be worth $10,814 USD (based on the daily revenue potential of the website over a 24 month period). Ghettogaggers.com is very popular with an estimated 5,193 daily unique visitors. This report was last updated 1st October, 2022.

About ghettogaggers.com

Site Preview:
Title: Ghetto Gaggers: White Cocks Gagging Ebony Hoodrats
Description: Extreme hardcore face fucking, ebony hoodrats, ghetto double penetration, yellow discipline and interracial throat banging of the Ghetto Gaggers.
Keywords and Tags: adult content, anal, black, dp, extreme, fa, face fuck, face fucking, facial, figure whore, gag, ghetto, ghetto gaggers, ghettogaggers, ir, pornography, reverse interracial, rough sex, yd, yellow discipline
Related Terms: banging, cobblestone throat, discipline olistiche, ghetto confessions, ghetto hoochies, ms juicy ghetto gaggers, petticoat discipline, throat
Fav Icon:
Age: Over 19 years old
Domain Created: 5th August, 2004
Domain Updated: 21st June, 2022
Domain Expires: 5th August, 2023
Review

Snoop Score

3/5 (Great!)

Valuation

$10,814 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 108,015
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: 5,193
Monthly Visitors: 158,059
Yearly Visitors: 1,895,445
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $15 USD
Monthly Revenue: $450 USD
Yearly Revenue: $5,402 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: ghettogaggers.com 17
Domain Name: ghettogaggers 13
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.99 seconds
Load Time Comparison: Faster than 80% of sites

PageSpeed Insights

Avg. (All Categories) 76
Performance 98
Accessibility 79
Best Practices 83
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://tour5m.ghettogaggers.com/
Updated: 1st October, 2022

1.32 seconds
First Contentful Paint (FCP)
85%
10%
5%

0.00 seconds
First Input Delay (FID)
98%
1%
1%

98

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 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://ghettogaggers.com/
http/1.1
0
55.61200005468
399
0
301
text/html
https://tour5m.ghettogaggers.com/
http/1.1
55.920000071637
185.88800006546
5994
14461
200
text/html
Document
https://tour5m.ghettogaggers.com/css/zerogrid.css
http/1.1
194.18500002939
320.32400008757
946
2301
200
text/css
Stylesheet
https://tour5m.ghettogaggers.com/css/style.css
http/1.1
194.64800006244
320.73100004345
2111
5019
200
text/css
Stylesheet
https://tour5m.ghettogaggers.com/css/responsive.css
http/1.1
194.79700003285
277.70600002259
1086
3424
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Open+Sans
h2
194.95800009463
208.06900004391
1415
2835
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-165290228-1
h2
321.81900006253
340.46100010164
44070
111779
200
application/javascript
Script
https://tour5m.ghettogaggers.com/images/logo.png
http/1.1
322.94500002172
407.21000009216
24887
24516
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-M7PX67
h2
325.94800007064
346.64700005669
38354
96075
200
application/javascript
Script
https://fonts.gstatic.com/s/opensans/v34/memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQbjA.woff
h2
330.09400009178
333.85600009933
15894
14968
200
font/woff
Font
https://www.googletagmanager.com/gtag/js?id=G-PVRSX202HR&l=dataLayer&cx=c
h2
394.3750000326
432.00600007549
75800
214157
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
400.06200002972
404.5230000047
20450
49672
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j97&a=1804991460&t=pageview&_s=1&dl=https%3A%2F%2Ftour5m.ghettogaggers.com%2F&ul=en-us&de=UTF-8&dt=Ghetto%20Gaggers%20%C2%AE%20%3A%20Black%20Women%2C%20White%20Men%2C%20ROUGH%20SEX&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=48741208&gjid=663838365&cid=1376086601.1664601102&tid=UA-165290228-1&_gid=1260342187.1664601102&_r=1&gtm=2ou9s0&z=1614569601
h2
434.26000000909
438.06500011124
622
1
200
text/plain
XHR
https://analytics.google.com/g/collect?v=2&tid=G-PVRSX202HR&gtm=2oe9s0&_p=1804991460&_gaz=1&cid=1376086601.1664601102&ul=en-us&sr=800x600&_z=ccd.v9B&_s=1&sid=1664601102&sct=1&seg=0&dl=https%3A%2F%2Ftour5m.ghettogaggers.com%2F&dt=Ghetto%20Gaggers%20%C2%AE%20%3A%20Black%20Women%2C%20White%20Men%2C%20ROUGH%20SEX&en=page_view&_fv=1&_ss=1
505.71200007107
508.90600006096
0
0
-1
Ping
https://stats.g.doubleclick.net/g/collect?v=2&tid=G-PVRSX202HR&cid=1376086601.1664601102&gtm=2oe9s0&aip=1
506.74900005106
511.52900001034
0
0
-1
Ping
https://tour5m.ghettogaggers.com/images/bkg_pic_gg01.jpg
http/1.1
511.11600000877
623.0570001062
274762
274388
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
190.902
11.236
328.134
19.891
353.17
13.082
366.643
12.17
378.849
7.114
389.316
12.565
411.54
25.049
455.694
54.458
513.783
8.606
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

Properly size images
Images can slow down the page's load time. Ghettogaggers.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ghettogaggers.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ghettogaggers.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ghettogaggers.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ghettogaggers.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 137 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://tour5m.ghettogaggers.com/images/bkg_pic_gg01.jpg
274388
120665.05
https://tour5m.ghettogaggers.com/images/logo.png
24516
19351.4
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 130 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://tour5m.ghettogaggers.com/
130.961
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Ghettogaggers.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ghettogaggers.com/
190
https://tour5m.ghettogaggers.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ghettogaggers.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 495 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://tour5m.ghettogaggers.com/images/bkg_pic_gg01.jpg
274762
https://www.googletagmanager.com/gtag/js?id=G-PVRSX202HR&l=dataLayer&cx=c
75800
https://www.googletagmanager.com/gtag/js?id=UA-165290228-1
44070
https://www.googletagmanager.com/gtm.js?id=GTM-M7PX67
38354
https://tour5m.ghettogaggers.com/images/logo.png
24887
https://www.google-analytics.com/analytics.js
20450
https://fonts.gstatic.com/s/opensans/v34/memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQbjA.woff
15894
https://tour5m.ghettogaggers.com/
5994
https://tour5m.ghettogaggers.com/css/style.css
2111
https://fonts.googleapis.com/css?family=Open+Sans
1415
Uses efficient cache policy on static assets — 4 resources found
Ghettogaggers.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://www.google-analytics.com/analytics.js
7200000
20450
https://tour5m.ghettogaggers.com/css/style.css
2592000000
2111
https://tour5m.ghettogaggers.com/css/responsive.css
2592000000
1086
https://tour5m.ghettogaggers.com/css/zerogrid.css
2592000000
946
Avoids an excessive DOM size — 72 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
72
Maximum DOM Depth
D
13
Maximum Child Elements
22
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ghettogaggers.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.googletagmanager.com/gtag/js?id=G-PVRSX202HR&l=dataLayer&cx=c
64.545
59.787
3.227
https://tour5m.ghettogaggers.com/
54.977
4.054
1.665
Minimizes main-thread work — 0.2 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
124.81
Other
34.232
Style & Layout
26.246
Rendering
9.726
Script Parsing & Compilation
9.691
Parse HTML & CSS
3.374
Keep request counts low and transfer sizes small — 16 requests • 495 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
16
506790
Image
2
299649
Script
4
178674
Font
1
15894
Document
1
5994
Stylesheet
4
5558
Other
4
1021
Media
0
0
Third-party
9
196605
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
158224
0
21072
0
17309
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.
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.044511426319937
0.00016434725505647
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 — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.googletagmanager.com/gtag/js?id=G-PVRSX202HR&l=dataLayer&cx=c
1126
54
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 ghettogaggers.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.

Other

Eliminate render-blocking resources — Potential savings of 490 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ghettogaggers.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://tour5m.ghettogaggers.com/css/zerogrid.css
946
70
https://tour5m.ghettogaggers.com/css/style.css
2111
150
https://tour5m.ghettogaggers.com/css/responsive.css
1086
150
https://fonts.googleapis.com/css?family=Open+Sans
1415
230
Reduce unused JavaScript — Potential savings of 51 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-PVRSX202HR&l=dataLayer&cx=c
75800
28866
https://www.googletagmanager.com/gtm.js?id=GTM-M7PX67
38354
23471

Other

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://fonts.gstatic.com/s/opensans/v34/memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQbjA.woff
3.7620000075549
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://tour5m.ghettogaggers.com/images/logo.png
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ghettogaggers.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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have 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 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"]`
Ghettogaggers.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Manual Checks

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

Best Practices

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

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.
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://ghettogaggers.com/
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
100

SEO

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

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

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

Installable

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

PWA Optimized

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

Manual Checks

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

1.15 seconds
First Contentful Paint (FCP)
88%
7%
5%

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

85

Performance

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

Metrics

Speed Index — 3.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 120 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.049
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Ghettogaggers.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ghettogaggers.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ghettogaggers.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ghettogaggers.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ghettogaggers.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 150 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://tour5m.ghettogaggers.com/
146.163
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Ghettogaggers.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ghettogaggers.com/
630
https://tour5m.ghettogaggers.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ghettogaggers.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 492 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://tour5m.ghettogaggers.com/images/bkg_pic_gg01.jpg
274762
https://www.googletagmanager.com/gtag/js?id=G-PVRSX202HR&l=dataLayer&cx=c
75762
https://www.googletagmanager.com/gtag/js?id=UA-165290228-1
44070
https://www.googletagmanager.com/gtm.js?id=GTM-M7PX67
38353
https://tour5m.ghettogaggers.com/images/logo.png
24887
https://www.google-analytics.com/analytics.js
20451
https://fonts.gstatic.com/s/opensans/v34/memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVIUx6EQ.woff2
12468
https://tour5m.ghettogaggers.com/
5994
https://tour5m.ghettogaggers.com/css/style.css
2110
https://fonts.googleapis.com/css?family=Open+Sans
1410
Uses efficient cache policy on static assets — 4 resources found
Ghettogaggers.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://www.google-analytics.com/analytics.js
7200000
20451
https://tour5m.ghettogaggers.com/css/style.css
2592000000
2110
https://tour5m.ghettogaggers.com/css/responsive.css
2592000000
1087
https://tour5m.ghettogaggers.com/css/zerogrid.css
2592000000
946
Avoids an excessive DOM size — 72 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
72
Maximum DOM Depth
D
13
Maximum Child Elements
22
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ghettogaggers.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.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-PVRSX202HR&l=dataLayer&cx=c
285.684
262.692
15.528
https://tour5m.ghettogaggers.com/
237.276
17.544
7.164
https://www.googletagmanager.com/gtm.js?id=GTM-M7PX67
122.856
110.08
6.132
https://www.google-analytics.com/analytics.js
97.64
88.148
2.752
Unattributable
66.668
10.184
0.48
Minimizes main-thread work — 0.9 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
512.872
Other
139.704
Style & Layout
126.416
Script Parsing & Compilation
39.296
Rendering
29.76
Parse HTML & CSS
15.044
Keep request counts low and transfer sizes small — 16 requests • 492 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
16
503321
Image
2
299649
Script
4
178636
Font
1
12468
Document
1
5994
Stylesheet
4
5553
Other
4
1021
Media
0
0
Third-party
9
193136
Minimize third-party usage — Third-party code blocked the main thread for 240 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)
158185
206.924
21073
34.132
13878
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.
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.048922322591146
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.googletagmanager.com/gtag/js?id=G-PVRSX202HR&l=dataLayer&cx=c
4585
276
https://www.googletagmanager.com/gtm.js?id=GTM-M7PX67
3478
57
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 ghettogaggers.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.

Audits

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://ghettogaggers.com/
http/1.1
0
55.063999723643
399
0
301
text/html
https://tour5m.ghettogaggers.com/
http/1.1
55.399999953806
200.56799985468
5994
14461
200
text/html
Document
https://tour5m.ghettogaggers.com/css/zerogrid.css
http/1.1
210.87600011379
323.1159998104
946
2301
200
text/css
Stylesheet
https://tour5m.ghettogaggers.com/css/style.css
http/1.1
211.04499977082
285.29200004414
2110
5019
200
text/css
Stylesheet
https://tour5m.ghettogaggers.com/css/responsive.css
http/1.1
211.37099992484
322.09799997509
1087
3424
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Open+Sans
h2
211.72800008208
223.00900006667
1410
2827
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-165290228-1
h2
323.5369999893
354.78799976408
44070
111779
200
application/javascript
Script
https://tour5m.ghettogaggers.com/images/logo.png
http/1.1
324.40999988467
412.29100013152
24887
24516
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-M7PX67
h2
327.33599981293
349.21999974176
38353
96075
200
application/javascript
Script
https://fonts.gstatic.com/s/opensans/v34/memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVIUx6EQ.woff2
h2
332.9459996894
340.71299992502
12468
11540
200
font/woff2
Font
https://www.googletagmanager.com/gtag/js?id=G-PVRSX202HR&l=dataLayer&cx=c
h2
402.61300001293
429.80200005695
75762
214157
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
407.84400003031
413.57300011441
20451
49672
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j97&a=1934577435&t=pageview&_s=1&dl=https%3A%2F%2Ftour5m.ghettogaggers.com%2F&ul=en-us&de=UTF-8&dt=Ghetto%20Gaggers%20%C2%AE%20%3A%20Black%20Women%2C%20White%20Men%2C%20ROUGH%20SEX&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=1386380382&gjid=1342361059&cid=1962034270.1664601116&tid=UA-165290228-1&_gid=175879817.1664601116&_r=1&gtm=2ou9s0&z=1666153916
h2
441.79600011557
448.54199979454
622
1
200
text/plain
XHR
https://analytics.google.com/g/collect?v=2&tid=G-PVRSX202HR&gtm=2oe9s0&_p=1934577435&_gaz=1&cid=1962034270.1664601116&ul=en-us&sr=360x640&_z=ccd.v9B&_s=1&sid=1664601115&sct=1&seg=0&dl=https%3A%2F%2Ftour5m.ghettogaggers.com%2F&dt=Ghetto%20Gaggers%20%C2%AE%20%3A%20Black%20Women%2C%20White%20Men%2C%20ROUGH%20SEX&en=page_view&_fv=1&_ss=1
529.65199993923
533.5840000771
0
0
-1
Ping
https://stats.g.doubleclick.net/g/collect?v=2&tid=G-PVRSX202HR&cid=1962034270.1664601116&gtm=2oe9s0&aip=1
530.86999990046
536.43399989232
0
0
-1
Ping
https://tour5m.ghettogaggers.com/images/bkg_pic_gg01.jpg
http/1.1
536.23799979687
674.47899980471
274762
274388
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
204.955
12.186
329.58
23.172
357.694
13.998
372.871
9.726
383.095
8.374
395.263
14.245
420.597
23.003
465.519
69.003
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 3.0 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.5 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 3.2 s
The timing of the largest text or image that is painted.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 74 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-PVRSX202HR&l=dataLayer&cx=c
75762
30359
https://www.googletagmanager.com/gtm.js?id=GTM-M7PX67
38353
24380
https://www.googletagmanager.com/gtag/js?id=UA-165290228-1
44070
20600
Serve images in next-gen formats — Potential savings of 137 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://tour5m.ghettogaggers.com/images/bkg_pic_gg01.jpg
274388
120665.05
https://tour5m.ghettogaggers.com/images/logo.png
24516
19351.4

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 1,510 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ghettogaggers.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://tour5m.ghettogaggers.com/css/zerogrid.css
946
180
https://tour5m.ghettogaggers.com/css/style.css
2110
480
https://tour5m.ghettogaggers.com/css/responsive.css
1087
480
https://fonts.googleapis.com/css?family=Open+Sans
1410
780
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://fonts.gstatic.com/s/opensans/v34/memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVIUx6EQ.woff2
7.7670002356172
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://tour5m.ghettogaggers.com/images/logo.png
First Contentful Paint (3G) — 5820 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ghettogaggers.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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have 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 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"]`
Ghettogaggers.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ghettogaggers.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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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.
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://ghettogaggers.com/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://tour5m.ghettogaggers.com/images/logo.png
190 x 65
190 x 65
380 x 130

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
93

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ghettogaggers.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 ghettogaggers.com on mobile screens.
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
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

Document doesn't use legible font sizes — 3.28% 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
a, abbr, acronym, address, applet, article, aside, audio, b, blockquote, big, body, center, canvas, caption, cite, code, command, datalist, dd, del, details, dfn, dl, div, dt, em, embed, fieldset, figcaption, figure, font, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, html, i, iframe, img, ins, kbd, keygen, label, legend, li, meter, nav, object, ol, output, p, pre, progress, q, s, samp, section, small, span, source, strike, strong, sub, sup, table, tbody, tfoot, thead, th, tr, tdvideo, tt, u, ul, var
96.41%
11px
span.obfus
0.31%
0.00001px
3.28%
≥ 12px

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

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

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

Installable

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

PWA Optimized

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

Manual Checks

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

Server Location

Server IP Address: 64.59.126.209
Continent: North America
Country: United States
United States Flag
Region: Michigan
City: Franklin
Longitude: -83.2519
Latitude: 42.5219
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Mojohost
Registration

Domain Registrant

Private Registration: Yes
Name: Jewella Privacy - 2da9a
Organization: Jewella Privacy LLC Privacy ID# 11276558
Country: US
City: Harahan
State: LA
Post Code: 70123
Email: ghettogaggers.com@dnic.JewellaPrivacy.com
Phone: +1.5043550545
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: 38/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: tour5m.ghettogaggers.com
Issued By: R3
Valid From: 25th August, 2022
Valid To: 23rd November, 2022
Subject: CN = tour5m.ghettogaggers.com
Hash: e0ff6487
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x032A08B8358714FE6C2BF2C6E5568D5A3DDD
Serial Number (Hex): 032A08B8358714FE6C2BF2C6E5568D5A3DDD
Valid From: 25th August, 2024
Valid To: 23rd November, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Aug 25 21:27:54.430 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:E5:1D:17:26:F9:D9:CF:B8:E0:53:56:
DD:BA:55:DD:CF:D6:B9:19:C9:D5:F4:A1:5F:96:74:98:
D2:89:C4:5F:B3:02:20:78:C9:1A:72:08:2C:B7:05:07:
BC:06:DA:4C:13:C7:8B:99:25:46:38:9F:B1:8D:CF:6A:
30:10:31:8F:AC:A4:75
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Aug 25 21:27:54.443 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:47:23:A9:F7:59:F2:FA:A9:2F:48:64:4F:
2E:86:0C:D5:2F:9B:CC:9C:9C:65:FC:87:D8:6C:0B:BD:
09:D1:19:EA:02:20:40:4D:03:A8:46:27:C1:FE:9D:49:
BC:6A:F2:6A:A9:51:1A:14:E0:A1:07:80:7E:88:A3:5B:
E6:5F:66:B3:5F:2A
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:tour5m.ghettogaggers.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
ghettogaggers.com. 64.59.126.209 IN 60

NS Records

Host Nameserver Class TTL
ghettogaggers.com. ns2.mojohost.com. IN 60
ghettogaggers.com. ns1.mojohost.com. IN 60

MX Records

Priority Host Server Class TTL
10 ghettogaggers.com. mail.ghettogaggers.com. IN 60

SOA Records

Domain Name Primary NS Responsible Email TTL
ghettogaggers.com. ns1.mojohost.com. postmaster.mojohost.com. 60

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 1st October, 2022
Server: Apache
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/7.3.3
Vary: User-Agent,Accept-Encoding

Whois Lookup

Created: 5th August, 2004
Changed: 21st June, 2022
Expires: 5th August, 2023
Registrar: DNC Holdings, Inc
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
renewPeriod
Nameservers: ns1.mojohost.com
ns2.mojohost.com
Owner Name: Jewella Privacy - 2da9a
Owner Organization: Jewella Privacy LLC Privacy ID# 11276558
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: ghettogaggers.com@dnic.JewellaPrivacy.com
Admin Name: Jewella Privacy
Admin Organization: Jewella Privacy LLC Privacy ID# 11276558
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: ghettogaggers.com@dnic.JewellaPrivacy.com
Tech Name: Jewella Privacy
Tech Organization: Jewella Privacy LLC Privacy ID# 11276558
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: ghettogaggers.com@dnic.JewellaPrivacy.com
Full Whois:
Domain Name: GHETTOGAGGERS.COM
Registry Domain ID: 126493300_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.directnic.com
Registrar URL: http://www.directnic.com
Updated Date: 2022-06-21T02:21:33Z
Creation Date: 2004-08-05T01:10:26Z
Registrar Registration Expiration Date: 2023-08-05T01:10:26Z
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 - 2da9a
Registrant Organization: Jewella Privacy LLC Privacy ID# 11276558
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: ghettogaggers.com@dnic.JewellaPrivacy.com
Registry Admin ID: Not Available From Registry
Admin Name: Jewella Privacy
Admin Organization: Jewella Privacy LLC Privacy ID# 11276558
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: ghettogaggers.com@dnic.JewellaPrivacy.com
Registry Tech ID: Not Available From Registry
Tech Name: Jewella Privacy
Tech Organization: Jewella Privacy LLC Privacy ID# 11276558
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: ghettogaggers.com@dnic.JewellaPrivacy.com
Name Server: NS1.MOJOHOST.COM
Name Server: NS2.MOJOHOST.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net
>>> Last update of WHOIS database: 2022-09-30T19:11:38Z <<<


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
ns1.mojohost.com 64.59.64.2
ns2.mojohost.com 64.59.65.2
Related

Subdomains

Domain Subdomain
tour5m

Similar Sites

Domain Valuation Snoop Score
0/5
$9,826,869 USD 5/5
$10 USD
$10,835 USD 2/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$6,774 USD 3/5
$859 USD 2/5
$799 USD 2/5
$76,764 USD 3/5
$742 USD 2/5