adultsearch.com

adultsearch.com is SSL secured

Free website and domain report on adultsearch.com

Last Updated: 29th April, 2022 Update Now
Overview

Snoop Summary for adultsearch.com

This is a free and comprehensive report about adultsearch.com. The domain adultsearch.com is currently hosted on a server located in United States with the IP address 104.18.140.16, where the local currency is USD and English is the local language. Our records indicate that adultsearch.com is privately registered by Privacy service provided by Withheld for Privacy ehf. Adultsearch.com is expected to earn an estimated $225 USD per day from advertising revenue. The sale of adultsearch.com would possibly be worth $164,422 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Adultsearch.com is wildly popular with an estimated 53,258 daily unique visitors. This report was last updated 29th April, 2022.

About adultsearch.com

Site Preview:
Title: search
Description: United States , United States Sensual Massage, United States Erotic Services
Keywords and Tags: adult content, pornography, united states
Related Terms: 55 years old men and above from united states, critical mineral resources of the united states, dharmaraja united kingdon, smm panel united states of america, states abbreviations, united states coins, united states government, united states population policy, united states., western united states
Fav Icon:
Age: Over 27 years old
Domain Created: 22nd May, 1997
Domain Updated: 1st March, 2021
Domain Expires: 23rd May, 2029
Review

Snoop Score

4/5 (Excellent!)

Valuation

$164,422 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 19,812
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: 53,258
Monthly Visitors: 1,621,006
Yearly Visitors: 19,439,170
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $225 USD
Monthly Revenue: $6,855 USD
Yearly Revenue: $82,206 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: adultsearch.com 15
Domain Name: adultsearch 11
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.87 seconds
Load Time Comparison: Faster than 84% of sites

PageSpeed Insights

Avg. (All Categories) 72
Performance 95
Accessibility 75
Best Practices 83
SEO 83
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://adultsearch.com/
Updated: 29th April, 2022

1.34 seconds
First Contentful Paint (FCP)
88%
9%
3%

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

95

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 120 ms
Users could experience a delay when interacting with the page.
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://adultsearch.com/
http/1.1
0
50.63599999994
410
0
301
text/plain
https://adultsearch.com/
h2
51.00800000946
674.15200002142
28218
466808
200
text/html
Document
https://adultsearch.com/build/desktop.452aba62.css
h2
687.52500001574
821.31200001459
72779
438109
200
text/css
Stylesheet
https://adultsearch.com/images/as-redesign-desktop/brand.svg
h2
688.6340000201
745.01700000837
2453
4527
200
image/svg+xml
Image
https://adultsearch.com/images/icons/bw_round_facebook.svg
h2
718.14400001313
776.05800001766
1002
855
200
image/svg+xml
Image
https://adultsearch.com/images/icons/bw_round_instagram.svg
h2
718.38900001603
773.8079999981
1229
1442
200
image/svg+xml
Image
https://www.googletagmanager.com/gtag/js?id=UA-157599614-1
h2
718.59900001436
739.87799999304
39532
99937
200
application/javascript
Script
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
719.01400000206
771.37400000356
5618
13970
200
text/javascript
Script
https://adultsearch.com/build/runtime.420770e4.js
h2
719.26500002155
777.50399999786
1362
1505
200
application/javascript
Script
https://adultsearch.com/build/desktop.07984fe0.js
h2
719.49700001278
838.69299999787
580363
1923744
200
application/javascript
Script
https://adultsearch.com/images/as-redesign-desktop/icons/caret.svg
h2
863.12600001111
941.33600001805
830
481
200
image/svg+xml
Image
https://adultsearch.com/build/fonts/ProximaNova-Regular.bf9f5d50.otf
h2
887.1119999967
916.56500002136
41686
62892
200
application/font-sfnt
Font
https://adultsearch.com/build/fonts/ProximaNova-Semibold.f14eee64.otf
h2
887.27100001415
913.321
41352
63116
200
application/font-sfnt
Font
https://www.google-analytics.com/analytics.js
h2
1001.8520000158
1006.475000002
20631
50205
200
text/javascript
Script
data
1238.7980000058
1238.949999999
0
353
200
image/jpeg
Image
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=239211857&t=pageview&_s=1&dl=https%3A%2F%2Fadultsearch.com%2F&ul=en-us&de=UTF-8&dt=Find%20Escorts%2C%20Strip%20Clubs%2C%20Sex%20Shops%20%7C%20Adult%20Search%20Engine&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=804985940&gjid=627657225&cid=593411898.1651241511&tid=UA-157599614-1&_gid=96051669.1651241511&_r=1&gtm=2ou4r0&z=2140722539
h2
1309.8710000049
1313.5790000088
613
1
200
text/plain
XHR
https://adultsearch.com/cdn-cgi/rum?
h2
1328.9680000162
1351.0010000027
410
0
200
text/plain
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)
716.871
7.957
788.067
9.078
862.345
19.932
886.672
143.769
1030.485
11.444
1050.896
235.858
1286.867
17.049
1314.377
12.079
1328.443
21.064
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. Adultsearch.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Adultsearch.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Adultsearch.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Adultsearch.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 69 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Adultsearch.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://adultsearch.com/build/desktop.452aba62.css
72779
71002
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.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Adultsearch.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://adultsearch.com/
190
https://adultsearch.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Adultsearch.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 0 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://adultsearch.com/build/desktop.07984fe0.js
57
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://adultsearch.com/images/as-redesign-desktop/brand.svg
0
Avoids enormous network payloads — Total size was 819 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://adultsearch.com/build/desktop.07984fe0.js
580363
https://adultsearch.com/build/desktop.452aba62.css
72779
https://adultsearch.com/build/fonts/ProximaNova-Regular.bf9f5d50.otf
41686
https://adultsearch.com/build/fonts/ProximaNova-Semibold.f14eee64.otf
41352
https://www.googletagmanager.com/gtag/js?id=UA-157599614-1
39532
https://adultsearch.com/
28218
https://www.google-analytics.com/analytics.js
20631
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
5618
https://adultsearch.com/images/as-redesign-desktop/brand.svg
2453
https://adultsearch.com/build/runtime.420770e4.js
1362
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. Adultsearch.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.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://adultsearch.com/build/desktop.07984fe0.js
252.75
153.592
28.618
https://adultsearch.com/
202.98
13.059
1.587
Unattributable
51.862
3.03
0.162
Minimizes main-thread work — 0.6 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
206.277
Style & Layout
159.132
Other
91.607
Rendering
41.006
Parse HTML & CSS
40.608
Script Parsing & Compilation
33.331
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 — 16 requests • 819 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
838488
Script
5
647506
Font
2
83038
Stylesheet
1
72779
Document
1
28218
Image
4
5514
Other
3
1433
Media
0
0
Third-party
4
66394
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)
39532
0
21244
0
5618
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 — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00021535623651781
0.00017465123170836
9.389851167116E-5
9.389851167116E-5
9.389851167116E-5
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://adultsearch.com/build/desktop.07984fe0.js
1380
118
https://adultsearch.com/
380
72
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 adultsearch.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

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

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 130 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Adultsearch.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://adultsearch.com/build/desktop.452aba62.css
72779
120
Reduce unused JavaScript — Potential savings of 457 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://adultsearch.com/build/desktop.07984fe0.js
580363
468014

Other

Reduce initial server response time — Root document took 620 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://adultsearch.com/
624.138
Serve static assets with an efficient cache policy — 11 resources found
Adultsearch.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://adultsearch.com/build/fonts/ProximaNova-Regular.bf9f5d50.otf
0
41686
https://adultsearch.com/build/fonts/ProximaNova-Semibold.f14eee64.otf
0
41352
https://adultsearch.com/images/as-redesign-desktop/brand.svg
0
2453
https://adultsearch.com/images/icons/bw_round_instagram.svg
0
1229
https://adultsearch.com/images/icons/bw_round_facebook.svg
0
1002
https://adultsearch.com/images/as-redesign-desktop/icons/caret.svg
0
830
https://www.google-analytics.com/analytics.js
7200000
20631
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
https://adultsearch.com/build/desktop.07984fe0.js
432000000
580363
https://adultsearch.com/build/desktop.452aba62.css
432000000
72779
https://adultsearch.com/build/runtime.420770e4.js
432000000
1362
Avoid an excessive DOM size — 2,768 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
2768
Maximum DOM Depth
13
Maximum Child Elements
88
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://adultsearch.com/images/icons/bw_round_facebook.svg
https://adultsearch.com/images/icons/bw_round_instagram.svg
https://adultsearch.com/images/as-redesign-desktop/brand.svg
75

Accessibility

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

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

Contrast

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

Internationalization and localization

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
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 adultsearch.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.
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
Bootstrap
4.5.0
jQuery
3.5.1
jQuery UI
1.12.1
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.
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://adultsearch.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
High

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://adultsearch.com/build/desktop.07984fe0.js
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for adultsearch.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 adultsearch.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.
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.
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 adultsearch.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 adultsearch.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 81
Accessibility 81
Best Practices 75
SEO 93
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://adultsearch.com/m/location
Updated: 29th April, 2022

1.13 seconds
First Contentful Paint (FCP)
92%
5%
3%

0.01 seconds
First Input Delay (FID)
96%
2%
2%

81

Performance

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

Metrics

Speed Index — 3.2 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.3 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

First Meaningful Paint — 2.3 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://adultsearch.com/
http/1.1
0
51.850999996532
410
0
301
text/plain
https://adultsearch.com/
h2
52.158000005875
540.36499996437
1101
550
200
text/html
Document
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
552.51800001133
611.3989999867
5618
13970
200
text/javascript
Script
https://adultsearch.com/m/location
h2
554.94499998167
1222.2019999754
87112
2419446
200
text/html
Document
https://adultsearch.com/css/preloader.css
h2
1237.5079999911
1261.8829999701
1153
1624
200
text/css
Stylesheet
https://adultsearch.com/build/mobile.88123220.css
h2
1237.8189999727
1298.3999999706
52486
301041
200
text/css
Stylesheet
https://adultsearch.com/js/publisher/p.js?20180922
h2
1238.1109999842
1262.4540000106
1430
2899
200
application/javascript
Script
https://adultsearch.com/js/mobile/geo.js
h2
1238.2929999731
1283.6799999932
1926
4379
200
application/javascript
Script
https://adultsearch.com/images/as-redesign/brand2.svg
h2
1285.2209999692
1322.0250000013
2372
4649
200
image/svg+xml
Image
https://adultsearch.com/build/fonts/ProximaNova-Regular.bf9f5d50.otf
h2
1322.4749999936
1354.1710000136
41686
62892
200
application/font-sfnt
Font
https://adultsearch.com/promo/b?random=1651241539527&s=10094&u=https%3A//adultsearch.com/m/location&r=https%3A//adultsearch.com/
h2
1329.6069999924
1808.0709999776
1044
716
200
text/html
Document
data
1344.133000006
1344.2359999754
0
514
200
image/svg+xml
Image
https://adultsearch.com/build/fonts/ProximaNova-Semibold.f14eee64.otf
h2
1345.0900000171
1378.3369999728
41352
63116
200
application/font-sfnt
Font
https://www.googletagmanager.com/gtag/js?id=UA-157599614-1
h2
1413.6149999686
1427.3500000127
39532
99937
200
application/javascript
Script
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
1414.048000006
1476.2880000053
5618
13970
200
text/javascript
Script
https://adultsearch.com/build/runtime.420770e4.js
h2
1414.3499999773
1442.9349999991
1362
1505
200
application/javascript
Script
https://adultsearch.com/build/mobile.844c0050.js
h2
1414.6409999812
1494.8940000031
478107
1585242
200
application/javascript
Script
https://adultsearch.com/js/mobile/mobile.js
h2
1414.850000001
1449.0070000174
2422
5060
200
application/javascript
Script
https://adultsearch.com/js/preloader.js
h2
1415.6289999955
1441.6910000145
826
304
200
application/javascript
Script
https://adultsearch.com/promo/b?random=1651241539622&s=10072&u=https%3A//adultsearch.com/m/location&r=https%3A//adultsearch.com/
h2
1424.3799999822
1606.5959999687
1047
716
200
text/html
Document
https://www.google-analytics.com/analytics.js
h2
1463.4029999725
1468.480999989
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=419880026&t=pageview&_s=1&dl=https%3A%2F%2Fadultsearch.com%2Fm%2Flocation&ul=en-us&de=UTF-8&dt=Choose%20Your%20Location&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=1547525976&gjid=1893215083&cid=1470358397.1651241540&tid=UA-157599614-1&_gid=1669444054.1651241540&_r=1&gtm=2ou4r0&z=1972177933
h2
1499.3210000102
1504.0840000147
613
1
200
text/plain
XHR
data
1744.1610000096
1744.3130000029
0
353
200
image/jpeg
Image
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
1791.1409999942
1791.2979999674
5618
13970
200
text/javascript
Script
https://auburn9819.com/spot/21096.html
http/1.1
1796.1270000087
2258.153999981
589
378
200
text/html
Document
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
1817.9619999719
1818.0890000076
5618
13970
200
text/javascript
Script
https://auburn9819.com/spot/21110.html
http/1.1
1821.7270000023
2363.3740000078
887
913
200
text/html
Document
https://auburn9819.com/mad_history?h=adgroups&v=18633
http/1.1
2270.0099999784
2720.8279999904
495
42
200
image/gif
Image
https://auburn9819.com/user_history?v=7092028414039689743
http/1.1
2270.3319999855
2809.253000014
494
42
200
image/gif
Image
https://auburn9819.com/spot/22311.html
http/1.1
2273.4559999662
2498.3249999932
1103
1443
200
text/html
Document
https://auburn9819.com/mad_history?h=adgroups&v=19299
http/1.1
2376.4479999663
2728.5989999655
495
42
200
image/gif
Image
https://auburn9819.com/user_history?v=7092028413617004207
http/1.1
2376.8450000207
2796.4420000208
494
42
200
image/gif
Image
https://servedbyadbutler.com/adserve/;ID=173988;size=300x100;setID=361751;type=iframe;sw=360;sh=640;spr=2.625;kw=;pid=7638344;place=0;rnd=7638344;click=CLICK_MACRO_PLACEHOLDER
http/1.1
2380.5679999641
2426.9370000111
828
518
200
text/html
Document
https://servedbyadbutler.com/getad.img/;libID=911877
http/1.1
2437.7540000132
2515.0150000118
9852
9387
200
image/jpeg
Image
https://b.bcdn9854324.com/media-ba/YmFubmVycy9hZmYvY3JwL2FhYnVnaG9zaC82MTEzMi5qcGc.jpg
h2
2511.4699999685
2637.0749999769
29618
29277
200
image/jpeg
Image
https://auburn9819.com/mad_history?h=adgroups&v=21053
http/1.1
2511.7520000204
2802.3699999903
496
42
200
image/gif
Image
https://auburn9819.com/user_history?v=7092028413049706149
http/1.1
2512.8910000203
2802.5180000113
493
42
200
image/gif
Image
https://adultsearch.com/cdn-cgi/rum?
h2
2802.7349999757
2832.7569999965
410
0
200
text/plain
XHR
https://adultsearch.com/cdn-cgi/rum?
h2
2818.7320000143
2838.2269999711
410
0
200
text/plain
XHR
https://adultsearch.com/cdn-cgi/rum?
h2
2821.5009999694
2868.879000016
410
0
200
text/plain
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)
582.393
7.327
1267.211
7.399
1296.217
17.794
1339
9.418
1351.662
12.598
1364.362
12.606
1380.372
9.588
1399.412
14.389
1431.447
11.134
1442.646
5.939
1453.851
5.473
1464.035
5.636
1478.705
9.784
1489.731
11.511
1512.45
24.124
1620.796
171.322
1792.786
5.974
1818.573
10.137
1850.171
6.367
2299.761
6.382
2405.778
7.781
2468.424
6.629
2540.846
7.538
2849.32
5.258
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. Adultsearch.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Adultsearch.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Adultsearch.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Adultsearch.com should consider minifying JS files.
Efficiently encode images — Potential savings of 16 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://b.bcdn9854324.com/media-ba/YmFubmVycy9hZmYvY3JwL2FhYnVnaG9zaC82MTEzMi5qcGc.jpg
29277
16775
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Adultsearch.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 0 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://adultsearch.com/build/mobile.844c0050.js
51
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 826 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://adultsearch.com/build/mobile.844c0050.js
478107
https://adultsearch.com/m/location
87112
https://adultsearch.com/build/mobile.88123220.css
52486
https://adultsearch.com/build/fonts/ProximaNova-Regular.bf9f5d50.otf
41686
https://adultsearch.com/build/fonts/ProximaNova-Semibold.f14eee64.otf
41352
https://www.googletagmanager.com/gtag/js?id=UA-157599614-1
39532
https://b.bcdn9854324.com/media-ba/YmFubmVycy9hZmYvY3JwL2FhYnVnaG9zaC82MTEzMi5qcGc.jpg
29618
https://www.google-analytics.com/analytics.js
20631
https://servedbyadbutler.com/getad.img/;libID=911877
9852
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
5618
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Adultsearch.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.9 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://adultsearch.com/build/mobile.844c0050.js
741.068
532.692
109.224
Unattributable
495.016
11.716
0.604
https://adultsearch.com/m/location
454.368
20.608
10.252
https://www.google-analytics.com/analytics.js
101.828
91.168
3.628
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
93.936
67.44
7.7
https://www.googletagmanager.com/gtag/js?id=UA-157599614-1
90.632
80.864
6.776
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 — 38 requests • 826 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
38
846158
Script
12
568708
Document
8
93711
Font
2
83038
Stylesheet
2
53639
Image
9
44809
Other
5
2253
Media
0
0
Third-party
19
129092
Minimize third-party usage — Third-party code blocked the main thread for 40 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)
21244
36.816
39532
0
22472
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
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://adultsearch.com/build/mobile.844c0050.js
8031
685
https://www.google-analytics.com/analytics.js
4516
96
Unattributable
630
71
https://adultsearch.com/m/location
726
58
https://adultsearch.com/js/publisher/p.js?20180922
2160
50
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 adultsearch.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.0 s
The time taken for the first image or text on the page to be rendered.
Total Blocking Time — 360 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).

Other

Eliminate render-blocking resources — Potential savings of 300 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Adultsearch.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://adultsearch.com/build/mobile.88123220.css
52486
300
Reduce unused CSS — Potential savings of 50 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Adultsearch.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://adultsearch.com/build/mobile.88123220.css
52486
50998
Serve images in next-gen formats — Potential savings of 23 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://b.bcdn9854324.com/media-ba/YmFubmVycy9hZmYvY3JwL2FhYnVnaG9zaC82MTEzMi5qcGc.jpg
29277
23819.5
Minimize main-thread work — 2.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
848.628
Other
756.276
Parse HTML & CSS
285.164
Script Parsing & Compilation
167.612
Style & Layout
123.044
Rendering
63.14
Garbage Collection
40.32
First Contentful Paint (3G) — 3960 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Time to Interactive — 8.3 s
The time taken for the page to become fully interactive.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 375 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://adultsearch.com/build/mobile.844c0050.js
478107
383809
Reduce initial server response time — Root document took 670 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://adultsearch.com/m/location
668.252
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Adultsearch.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://adultsearch.com/
630
https://adultsearch.com/
480
https://adultsearch.com/m/location
0
Serve static assets with an efficient cache policy — 23 resources found
Adultsearch.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://adultsearch.com/build/fonts/ProximaNova-Regular.bf9f5d50.otf
0
41686
https://adultsearch.com/build/fonts/ProximaNova-Semibold.f14eee64.otf
0
41352
https://adultsearch.com/images/as-redesign/brand2.svg
0
2372
https://auburn9819.com/mad_history?h=adgroups&v=21053
0
496
https://auburn9819.com/mad_history?h=adgroups&v=18633
0
495
https://auburn9819.com/mad_history?h=adgroups&v=19299
0
495
https://auburn9819.com/user_history?v=7092028413617004207
0
494
https://auburn9819.com/user_history?v=7092028414039689743
0
494
https://auburn9819.com/user_history?v=7092028413049706149
0
493
https://www.google-analytics.com/analytics.js
7200000
20631
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
https://adultsearch.com/build/mobile.844c0050.js
432000000
478107
https://adultsearch.com/build/mobile.88123220.css
432000000
52486
https://adultsearch.com/js/mobile/mobile.js
432000000
2422
https://adultsearch.com/js/mobile/geo.js
432000000
1926
https://adultsearch.com/js/publisher/p.js?20180922
432000000
1430
https://adultsearch.com/build/runtime.420770e4.js
432000000
1362
https://adultsearch.com/css/preloader.css
432000000
1153
https://adultsearch.com/js/preloader.js
432000000
826
https://b.bcdn9854324.com/media-ba/YmFubmVycy9hZmYvY3JwL2FhYnVnaG9zaC82MTEzMi5qcGc.jpg
2592000000
29618
Avoid an excessive DOM size — 8,623 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
8623
Maximum DOM Depth
15
Maximum Child Elements
374
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://adultsearch.com/images/as-redesign/brand2.svg
81

Accessibility

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

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.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
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.

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

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

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

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

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 adultsearch.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

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.
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
Bootstrap
4.5.0
jQuery
3.5.1
jQuery UI
1.12.1
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.
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://adultsearch.com/
Allowed
Requests 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.
Source
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
High

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://adultsearch.com/build/mobile.844c0050.js
93

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for adultsearch.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 adultsearch.com on mobile screens.
Document uses legible font sizes — 87.42% 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
.footer__item-title
12.58%
11px
87.42%
≥ 12px
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.
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.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

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 adultsearch.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 adultsearch.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: 104.18.140.16
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: Yes
Name: Withheld for Privacy Purposes
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: Reykjavik
State: Capital Region
Post Code: 101
Email: 342e078ddd5a49eeb1a674818a0b2817.protect@withheldforprivacy.com
Phone: +354.4212434
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NameCheap, Inc. 104.16.100.56
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 14th July, 2021
Valid To: 13th July, 2022
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 16242690827878241129786005798126190591
Serial Number (Hex): 0C383A7CA2A1C488147D797DF8B97FFF
Valid From: 14th July, 2024
Valid To: 13th July, 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 : 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 : Jul 14 15:39:29.827 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D9:EA:A5:EB:DB:D2:C1:E6:5A:74:1A:
0A:91:93:44:9A:C6:ED:1D:FC:11:97:1B:FF:EC:04:B3:
53:03:CF:6E:08:02:20:7B:F7:E3:8B:7E:86:DB:A7:13:
DC:D8:56:46:14:3B:AA:89:6F:91:A5:C9:0D:D4:7E:51:
70:27:A5:63:EF:E9:D5
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 51:A3:B0:F5:FD:01:79:9C:56:6D:B8:37:78:8F:0C:A4:
7A:CC:1B:27:CB:F7:9E:88:42:9A:0D:FE:D4:8B:05:E5
Timestamp : Jul 14 15:39:29.919 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:54:EE:91:F2:B6:65:89:7E:82:DC:B0:F7:
BD:E6:A0:7E:63:95:C4:F9:15:7D:68:74:37:1A:3B:D8:
5E:AE:7F:9B:02:21:00:C4:E7:2B:F6:81:0E:33:5F:E6:
E0:58:AC:6D:B2:F7:39:F6:75:18:17:61:97:5E:56:BA:
E9:F9:87:EA:BC:4D:A0
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Jul 14 15:39:29.887 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:20:F9:37:93:75:19:11:7E:99:28:7C:55:
BC:A8:57:42:67:0F:67:47:8C:96:34:5A:45:B6:20:1F:
2C:16:33:5B:02:20:4D:EC:18:6E:2B:5E:FE:09:00:63:
4E:BD:76:16:E1:30:AE:01:3F:74:B8:80:45:93:90:8E:
3E:11:2A:69:7B:12
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.adultsearch.com
DNS:sni.cloudflaressl.com
DNS:adultsearch.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 29th April, 2022
Content-Type: text/html; charset=UTF-8
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate
Server: cloudflare
Connection: keep-alive
Vary: X-Forwarded-Proto
Pragma: no-cache
Set-Cookie: *
X-Varnish: 8980411
Age: 0
Via: 1.1 varnish (Varnish/5.2)
X-Varnish-Cache: MISS
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
CF-RAY: 7038a0ef7d4219bb-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 22nd May, 1997
Changed: 1st March, 2021
Expires: 23rd May, 2029
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
Nameservers: jill.ns.cloudflare.com
merlin.ns.cloudflare.com
Owner Name: Redacted for Privacy
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: Kalkofnsvegur 2
Owner Post Code: 101
Owner City: Reykjavik
Owner State: Capital Region
Owner Country: IS
Owner Phone: +354.4212434
Owner Email: d2088258fa9f40ae8270ca1383107a8d.protect@withheldforprivacy.com
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin Post Code: 101
Admin City: Reykjavik
Admin State: Capital Region
Admin Country: IS
Admin Phone: +354.4212434
Admin Email: d2088258fa9f40ae8270ca1383107a8d.protect@withheldforprivacy.com
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech Post Code: 101
Tech City: Reykjavik
Tech State: Capital Region
Tech Country: IS
Tech Phone: +354.4212434
Tech Email: d2088258fa9f40ae8270ca1383107a8d.protect@withheldforprivacy.com
Full Whois: Domain name: adultsearch.com
Registry Domain ID: 1625679_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2021-03-01T05:19:23.00Z
Creation Date: 1997-05-22T04:00:00.00Z
Registrar Registration Expiration Date: 2029-05-23T04:00:00.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.9854014545
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Redacted for Privacy
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: Kalkofnsvegur 2
Registrant City: Reykjavik
Registrant State/Province: Capital Region
Registrant Postal Code: 101
Registrant Country: IS
Registrant Phone: +354.4212434
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: d2088258fa9f40ae8270ca1383107a8d.protect@withheldforprivacy.com
Registry Admin ID:
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin City: Reykjavik
Admin State/Province: Capital Region
Admin Postal Code: 101
Admin Country: IS
Admin Phone: +354.4212434
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: d2088258fa9f40ae8270ca1383107a8d.protect@withheldforprivacy.com
Registry Tech ID:
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech City: Reykjavik
Tech State/Province: Capital Region
Tech Postal Code: 101
Tech Country: IS
Tech Phone: +354.4212434
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: d2088258fa9f40ae8270ca1383107a8d.protect@withheldforprivacy.com
Name Server: jill.ns.cloudflare.com
Name Server: merlin.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-04-28T14:52:41.02Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
jill.ns.cloudflare.com 172.64.32.122
merlin.ns.cloudflare.com 172.64.33.205
Related

Subdomains

Domain Subdomain
uk

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

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

Sites hosted on the same IP address