xhamster.de

xhamster.de is SSL secured

Free website and domain report on xhamster.de

Last Updated: 12th May, 2023 Update Now
Overview

Snoop Summary for xhamster.de

This is a free and comprehensive report about xhamster.de. The domain xhamster.de is currently hosted on a server located in Canada with the IP address 104.247.82.114, where CAD is the local currency and the local language is English. Xhamster.de has the potential to be earning an estimated $5 USD per day from advertising revenue. If xhamster.de was to be sold it would possibly be worth $3,599 USD (based on the daily revenue potential of the website over a 24 month period). Xhamster.de receives an estimated 1,725 unique visitors every day - a large amount of traffic! This report was last updated 12th May, 2023.

About xhamster.de

Site Preview: xhamster.de xhamster.de
Title: xhamster.de
Description: This domain may be for sale!
Keywords and Tags: parked domain
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$3,599 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 441,075
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 8
Moz Page Authority: 18

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,725
Monthly Visitors: 52,504
Yearly Visitors: 629,625
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5 USD
Monthly Revenue: $150 USD
Yearly Revenue: $1,794 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: xhamster.de 11
Domain Name: xhamster 8
Extension (TLD): de 2

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 76
Performance 99
Accessibility 86
Best Practices 83
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://xhamster.de/
Updated: 11th December, 2022
Simulate loading on desktop
99

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
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://xhamster.de/
http/1.1
0
269.51100002043
6342
12747
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
274.90300009958
290.93600006308
54337
147323
200
text/javascript
Script
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
http/1.1
275.46500007156
295.9630000405
7460
7006
200
application/javascript
Script
http://xhamster.de/track.php?domain=xhamster.de&toggle=browserjs&uid=MTY3MDc3MjYyMy45Mjk0OmJhYjBjYzdhZTdhMjFmYjg4ZmNjYzA5ZjE2NzlkYmM1N2QwNzI0YmYyMWM5ZWJhYTFlMTE2NmQ0ZmIzMTdlNmU6NjM5NWY3OGZlMmU1NQ%3D%3D
http/1.1
372.67700000666
470.29399999883
608
0
200
text/html
XHR
http://xhamster.de/ls.php
http/1.1
472.83300000709
555.64700008836
861
0
201
text/javascript
XHR
https://partner.googleadservices.com/gampad/cookie.js?domain=xhamster.de&client=dp-teaminternet01_adult_3ph&product=SAS&callback=__sasCookie
h2
478.52200001944
486.81800009217
884
362
200
text/javascript
Script
http://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
http/1.1
484.23400009051
499.84300008509
11817
11375
200
image/png
Image
https://www.google.com/afs/ads?adtest=off&psid=6016880802&pcsa=false&channel=000002&client=dp-teaminternet01_adult_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2586203782542928&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003&format=r3%7Cs&nocache=8571670772624254&num=0&output=afd_ads&domain_name=xhamster.de&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1670772624255&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=791&frm=0&cl=493016327&uio=--&cont=tc&jsid=caf&jsv=493016327&rurl=http%3A%2F%2Fxhamster.de%2F&adbw=master-1%3A530
h2
491.76000000443
576.35800004937
2596
5585
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
585.43000009377
600.48400005326
54371
147274
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
h2
677.73400002625
683.40100010391
1186
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
677.97800002154
681.58900004346
1090
200
200
image/svg+xml
Image
http://xhamster.de/track.php?domain=xhamster.de&caf=1&toggle=answercheck&answer=yes&uid=MTY3MDc3MjYyMy45Mjk0OmJhYjBjYzdhZTdhMjFmYjg4ZmNjYzA5ZjE2NzlkYmM1N2QwNzI0YmYyMWM5ZWJhYTFlMTE2NmQ0ZmIzMTdlNmU6NjM5NWY3OGZlMmU1NQ%3D%3D
http/1.1
680.80100009684
869.29600010626
610
0
200
text/html
XHR
https://www.google.com/afs/gen_204?client=dp-teaminternet01_adult_3ph&output=uds_ads_only&zx=d08cny7hdkcm&aqid=kPeVY6ObE4WxmwSAzJDoAg&psid=6016880802&pbt=bs&adbx=410&adby=130&adbh=497&adbw=530&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-teaminternet01_adult_3ph&errv=493016327&csala=10%7C0%7C98%7C30%7C276&lle=0&llm=1000&ifv=1&usr=1
h2
2395.324000041
2413.8430000748
1184
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet01_adult_3ph&output=uds_ads_only&zx=b67i2jz059wy&aqid=kPeVY6ObE4WxmwSAzJDoAg&psid=6016880802&pbt=bv&adbx=410&adby=130&adbh=497&adbw=530&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-teaminternet01_adult_3ph&errv=493016327&csala=10%7C0%7C98%7C30%7C276&lle=0&llm=1000&ifv=1&usr=1
h2
2895.9090000717
2913.1350000389
822
0
204
text/html
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)
273.252
7.482
303.956
66.433
370.437
123.98
580.011
6.768
612.284
67.518
680.431
190.52
883.441
5.185
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. Xhamster.de should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Xhamster.de should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Xhamster.de should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Xhamster.de should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Xhamster.de 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
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
7006
5184
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 270 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)
http://xhamster.de/
270.505
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Xhamster.de should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Xhamster.de should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
0
Avoids enormous network payloads — Total size was 141 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js?pac=0
54371
http://www.google.com/adsense/domains/caf.js
54337
http://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
11817
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
7460
http://xhamster.de/
6342
https://www.google.com/afs/ads?adtest=off&psid=6016880802&pcsa=false&channel=000002&client=dp-teaminternet01_adult_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2586203782542928&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003&format=r3%7Cs&nocache=8571670772624254&num=0&output=afd_ads&domain_name=xhamster.de&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1670772624255&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=791&frm=0&cl=493016327&uio=--&cont=tc&jsid=caf&jsv=493016327&rurl=http%3A%2F%2Fxhamster.de%2F&adbw=master-1%3A530
2596
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
1186
https://www.google.com/afs/gen_204?client=dp-teaminternet01_adult_3ph&output=uds_ads_only&zx=d08cny7hdkcm&aqid=kPeVY6ObE4WxmwSAzJDoAg&psid=6016880802&pbt=bs&adbx=410&adby=130&adbh=497&adbw=530&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-teaminternet01_adult_3ph&errv=493016327&csala=10%7C0%7C98%7C30%7C276&lle=0&llm=1000&ifv=1&usr=1
1184
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
1090
https://partner.googleadservices.com/gampad/cookie.js?domain=xhamster.de&client=dp-teaminternet01_adult_3ph&product=SAS&callback=__sasCookie
884
Uses efficient cache policy on static assets — 4 resources found
Xhamster.de 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)
http://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
0
11817
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
0
7460
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
82800000
1186
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1090
Avoids an excessive DOM size — 33 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
33
Maximum DOM Depth
7
Maximum Child Elements
15
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Xhamster.de 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)
http://www.google.com/adsense/domains/caf.js
268.331
261.269
2.125
https://www.google.com/adsense/domains/caf.js?pac=0
129.342
103.186
2.088
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
99.793
99.562
0.134
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
488.158
Other
43.028
Style & Layout
9.26
Script Parsing & Compilation
7.99
Parse HTML & CSS
7.462
Rendering
7.352
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 14 requests • 141 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
14
144168
Script
4
117052
Image
5
16099
Document
2
8938
Other
3
2079
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
10
135747
Minimize third-party usage — Third-party code blocked the main thread for 160 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
113310
161.487
884
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 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)
http://www.google.com/adsense/domains/caf.js
588
191
https://www.google.com/adsense/domains/caf.js?pac=0
810
68
http://www.google.com/adsense/domains/caf.js
460
66
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
526
62
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xhamster.de 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 380 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Xhamster.de should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://www.google.com/adsense/domains/caf.js
54337
270
Reduce unused JavaScript — Potential savings of 63 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
54337
32658
https://www.google.com/adsense/domains/caf.js?pac=0
54371
31496
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of xhamster.de. 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<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 `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Xhamster.de 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

Names and labels

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

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 — 7 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://xhamster.de/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
Allowed
http://xhamster.de/track.php?domain=xhamster.de&toggle=browserjs&uid=MTY3MDc3MjYyMy45Mjk0OmJhYjBjYzdhZTdhMjFmYjg4ZmNjYzA5ZjE2NzlkYmM1N2QwNzI0YmYyMWM5ZWJhYTFlMTE2NmQ0ZmIzMTdlNmU6NjM5NWY3OGZlMmU1NQ%3D%3D
Allowed
http://xhamster.de/ls.php
Allowed
http://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
Allowed
http://xhamster.de/track.php?domain=xhamster.de&caf=1&toggle=answercheck&answer=yes&uid=MTY3MDc3MjYyMy45Mjk0OmJhYjBjYzdhZTdhMjFmYjg4ZmNjYzA5ZjE2NzlkYmM1N2QwNzI0YmYyMWM5ZWJhYTFlMTE2NmQ0ZmIzMTdlNmU6NjM5NWY3OGZlMmU1NQ%3D%3D
Allowed

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for xhamster.de. 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 xhamster.de 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.
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.
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 xhamster.de. 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 xhamster.de 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) 76
Performance 87
Accessibility 86
Best Practices 83
SEO 92
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://xhamster.de/
Updated: 11th December, 2022
Simulate loading on mobile
87

Performance

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

Metrics

Time to Interactive — 3.1 s
The time taken for the page to become fully interactive.
Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 40 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 130 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://xhamster.de/
http/1.1
0
250.24600001052
7349
16422
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
262.51999998931
275.76600003522
54333
147308
200
text/javascript
Script
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
http/1.1
262.72200001404
278.68600003421
7460
7006
200
application/javascript
Script
http://xhamster.de/track.php?domain=xhamster.de&toggle=browserjs&uid=MTY3MDc3MjY0My43ODgzOjdmODYxNmJjN2M1NTBjMWNlYjY1MjhiMWE1MjhmNzM0Y2QwOGNhODNkMzQzNDA5ZjA2OTBkMTliOWIzODdlZTY6NjM5NWY3YTNjMDcyMA%3D%3D
http/1.1
303.30799997319
360.36199994851
608
0
200
text/html
XHR
http://xhamster.de/ls.php
http/1.1
363.40799997561
447.18899996951
861
0
201
text/javascript
XHR
https://partner.googleadservices.com/gampad/cookie.js?domain=xhamster.de&client=dp-mobile-teaminternet02_adult_3ph&product=SAS&callback=__sasCookie
h2
371.2120000273
376.39500002842
883
362
200
text/javascript
Script
http://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
http/1.1
378.64999996964
416.32099996787
51288
50845
200
image/jpeg
Image
https://www.google.com/afs/ads?adtest=off&psid=3164365637&pcsa=false&channel=000002%2Cbucket009&client=dp-mobile-teaminternet02_adult_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2586203782542928&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=6871670772644002&num=0&output=afd_ads&domain_name=xhamster.de&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1670772644005&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=953&frm=0&cl=493016327&uio=-&cont=tc&jsid=caf&jsv=493016327&rurl=http%3A%2F%2Fxhamster.de%2F&adbw=master-1%3A360
h2
392.31499994639
463.18199997768
2547
5528
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
475.42699996848
499.40999993123
54378
147281
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
h2
541.53499996755
547.86299995612
1186
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
542.31699998491
548.77699993085
1194
444
200
image/svg+xml
Image
http://xhamster.de/track.php?domain=xhamster.de&caf=1&toggle=answercheck&answer=yes&uid=MTY3MDc3MjY0My43ODgzOjdmODYxNmJjN2M1NTBjMWNlYjY1MjhiMWE1MjhmNzM0Y2QwOGNhODNkMzQzNDA5ZjA2OTBkMTliOWIzODdlZTY6NjM5NWY3YTNjMDcyMA%3D%3D
http/1.1
545.71199999191
600.42899998371
610
0
200
text/html
XHR
https://www.google.com/afs/gen_204?client=dp-mobile-teaminternet02_adult_3ph&output=uds_ads_only&zx=i6torezcz5bl&aqid=pPeVY9vWA4O1mwSCxoeICw&psid=3164365637&pbt=bs&adbx=0&adby=133&adbh=450&adbw=360&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-mobile-teaminternet02_adult_3ph&errv=493016327&csala=16%7C0%7C90%7C40%7C112&lle=0&llm=1000&ifv=1&usr=1
h2
2132.9259999329
2153.6230000202
893
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-mobile-teaminternet02_adult_3ph&output=uds_ads_only&zx=wltqxharli5o&aqid=pPeVY9vWA4O1mwSCxoeICw&psid=3164365637&pbt=bv&adbx=0&adby=133&adbh=450&adbw=360&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-mobile-teaminternet02_adult_3ph&errv=493016327&csala=16%7C0%7C90%7C40%7C112&lle=0&llm=1000&ifv=1&usr=1
h2
2633.4679999854
2651.3859999832
531
0
204
text/html
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)
257.651
9.069
291.615
7.045
298.702
97.891
468.076
8.633
512.35
32.248
545.439
56.706
602.157
6.402
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. Xhamster.de should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Xhamster.de should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Xhamster.de should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Xhamster.de should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Xhamster.de 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 24 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)
http://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
50845
24799.85
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
7006
5184
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 250 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)
http://xhamster.de/
251.24
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Xhamster.de should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Xhamster.de 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 180 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js?pac=0
54378
http://www.google.com/adsense/domains/caf.js
54333
http://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
51288
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
7460
http://xhamster.de/
7349
https://www.google.com/afs/ads?adtest=off&psid=3164365637&pcsa=false&channel=000002%2Cbucket009&client=dp-mobile-teaminternet02_adult_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2586203782542928&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=6871670772644002&num=0&output=afd_ads&domain_name=xhamster.de&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1670772644005&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=953&frm=0&cl=493016327&uio=-&cont=tc&jsid=caf&jsv=493016327&rurl=http%3A%2F%2Fxhamster.de%2F&adbw=master-1%3A360
2547
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
1186
https://www.google.com/afs/gen_204?client=dp-mobile-teaminternet02_adult_3ph&output=uds_ads_only&zx=i6torezcz5bl&aqid=pPeVY9vWA4O1mwSCxoeICw&psid=3164365637&pbt=bs&adbx=0&adby=133&adbh=450&adbw=360&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-mobile-teaminternet02_adult_3ph&errv=493016327&csala=16%7C0%7C90%7C40%7C112&lle=0&llm=1000&ifv=1&usr=1
893
https://partner.googleadservices.com/gampad/cookie.js?domain=xhamster.de&client=dp-mobile-teaminternet02_adult_3ph&product=SAS&callback=__sasCookie
883
Avoids an excessive DOM size — 31 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
31
Maximum DOM Depth
6
Maximum Child Elements
18
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Xhamster.de 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.8 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)
http://www.google.com/adsense/domains/caf.js
319.184
271.564
11.236
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
243.768
242.228
0.932
http://xhamster.de/
186.796
113.588
11.604
https://www.google.com/adsense/domains/caf.js?pac=0
183.384
131.712
9.612
Unattributable
95.796
7.5
0
https://www.google.com/afs/ads?adtest=off&psid=3164365637&pcsa=false&channel=000002%2Cbucket009&client=dp-mobile-teaminternet02_adult_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2586203782542928&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=6871670772644002&num=0&output=afd_ads&domain_name=xhamster.de&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1670772644005&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=953&frm=0&cl=493016327&uio=-&cont=tc&jsid=caf&jsv=493016327&rurl=http%3A%2F%2Fxhamster.de%2F&adbw=master-1%3A360
65.384
8.124
7.308
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
778.18
Other
154.292
Style & Layout
61.164
Script Parsing & Compilation
41.104
Parse HTML & CSS
34.628
Rendering
29.312
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 14 requests • 180 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
14
184121
Script
4
117054
Image
5
55092
Document
2
9896
Other
3
2079
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
10
174693
Minimize third-party usage — Third-party code blocked the main thread for 200 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)
112682
203.308
883
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'.
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 — 3 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)
http://www.google.com/adsense/domains/caf.js
2056
227
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
1860
196
https://www.google.com/adsense/domains/caf.js?pac=0
3090
129
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xhamster.de 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.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.3 s
The timing of the largest text or image that is painted.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 63 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
54333
32863
https://www.google.com/adsense/domains/caf.js?pac=0
54378
31464
Serve static assets with an efficient cache policy — 4 resources found
Xhamster.de 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)
http://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
0
51288
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
0
7460
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
82800000
1186

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. Xhamster.de should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://www.google.com/adsense/domains/caf.js
54333
1080
First Contentful Paint (3G) — 5419.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of xhamster.de. 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<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 `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Xhamster.de 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

Names and labels

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

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 — 7 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://xhamster.de/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
Allowed
http://xhamster.de/track.php?domain=xhamster.de&toggle=browserjs&uid=MTY3MDc3MjY0My43ODgzOjdmODYxNmJjN2M1NTBjMWNlYjY1MjhiMWE1MjhmNzM0Y2QwOGNhODNkMzQzNDA5ZjA2OTBkMTliOWIzODdlZTY6NjM5NWY3YTNjMDcyMA%3D%3D
Allowed
http://xhamster.de/ls.php
Allowed
http://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
Allowed
http://xhamster.de/track.php?domain=xhamster.de&caf=1&toggle=answercheck&answer=yes&uid=MTY3MDc3MjY0My43ODgzOjdmODYxNmJjN2M1NTBjMWNlYjY1MjhiMWE1MjhmNzM0Y2QwOGNhODNkMzQzNDA5ZjA2OTBkMTliOWIzODdlZTY6NjM5NWY3YTNjMDcyMA%3D%3D
Allowed

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for xhamster.de. 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 xhamster.de on mobile screens.
Document uses legible font sizes — 90.59% 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
.si133
9.41%
10px
90.59%
≥ 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 xhamster.de. 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 xhamster.de 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.247.82.114
Continent: North America
Country: Canada
Canada Flag
Region:
City:
Longitude: -79.3716
Latitude: 43.6319
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
NEXT DIMENSION INC
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

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

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Apr 11 22:21:20.916 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C8:FE:71:81:36:C7:FE:A7:EB:1B:AE:
88:7D:F9:48:F5:B7:A6:2E:EA:4E:BD:69:8A:1B:6C:D4:
39:D5:48:0C:CD:02:20:38:BD:48:A6:C3:CF:38:BA:77:
B5:BB:C8:C9:EC:10:D2:00:83:31:45:C3:06:BA:A9:1F:
6F:66:1F:75:1D:E7:81
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Apr 11 22:21:20.948 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:1C:0E:68:AD:10:54:7F:4F:29:55:94:DA:
87:41:9D:48:B5:56:57:FA:D3:1C:6F:FE:DF:BB:41:3E:
02:B9:7C:7C:02:21:00:D6:3F:EB:16:27:89:C0:BC:05:
FB:01:38:51:44:A8:E0:60:DC:0F:2C:F7:61:2E:C1:30:
FD:B7:F6:02:F4:C7:15
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:xhamster.de
Technical

DNS Lookup

A Records

Host IP Address Class TTL
xhamster.de. 104.247.82.114 IN 600

NS Records

Host Nameserver Class TTL
xhamster.de. ns1.parkingcrew.net. IN 3600
xhamster.de. ns2.parkingcrew.net. IN 3600

MX Records

Priority Host Server Class TTL
5 xhamster.de. mail.h-email.net. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
xhamster.de. ns1.parkingcrew.net. hostmaster.xhamster.de. 10800

TXT Records

Host Value Class TTL
xhamster.de. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 12th May, 2023
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_msGrUEABgcSQ/EyIaPYPw1MgJo1R//MvbVO28SVRtia+rh1xv/cZG1v3fTvAiUx5xyb80ZOMGhlMOUCLnzEVeQ==
Accept-CH: ua-mobile
Accept-CH-Lifetime: 30
X-Domain: xhamster.de
X-Subdomain:

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1.parkingcrew.net
ns2.parkingcrew.net
Full Whois: % Restricted rights.
%
% Terms and Conditions of Use
%
% The above data may only be used within the scope of technical or
% administrative necessities of Internet operation or to remedy legal
% problems.
% The use for other purposes, in particular for advertising, is not permitted.
%
% The DENIC whois service on port 43 doesn't disclose any information concerning
% the domain holder, general request and abuse contact.
% This information can be obtained through use of our web-based whois service
% available at the DENIC website:
% http://www.denic.de/en/domains/whois-service/web-whois.html
%
%

Domain: xhamster.de
Nserver: ns1.parkingcrew.net
Nserver: ns2.parkingcrew.net
Status: connect
Changed: 2021-09-08T11:24:41+02:00

Nameservers

Name IP Address
ns1.parkingcrew.net 13.248.158.159
ns2.parkingcrew.net 76.223.21.9
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5