shemaleroulette.com

shemaleroulette.com is SSL secured

Free website and domain report on shemaleroulette.com

Last Updated: 18th November, 2024
Overview

Snoop Summary for shemaleroulette.com

This is a free and comprehensive report about shemaleroulette.com. The domain shemaleroulette.com is currently hosted on a server located in France with the IP address 51.81.226.88, where the local currency is EUR and French is the local language. Our records indicate that shemaleroulette.com is privately registered by Account Privacy. Shemaleroulette.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If shemaleroulette.com was to be sold it would possibly be worth $882 USD (based on the daily revenue potential of the website over a 24 month period). Shemaleroulette.com is somewhat popular with an estimated 419 daily unique visitors. This report was last updated 18th November, 2024.

About shemaleroulette.com

Site Preview:
Title: Shemale Roulette - Shemale Chat, Shemale Webcams
Description: Free video chat with random shemales and trannies from all over the world on Shemale Roulette. Watch live shemale webcams right now!
Keywords and Tags: pornography
Related Terms: free shemale video, sexx roulette, shemale asian, shemale flirts, shemale fuck chick, shemale fuck man, shemale gangbang, shemale hot, shemale pornstars, shemale sexkontakt
Fav Icon:
Age: Over 14 years old
Domain Created: 20th February, 2010
Domain Updated: 4th May, 2024
Domain Expires: 20th February, 2025
Review

Snoop Score

2/5

Valuation

$882 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,510,594
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: 419
Monthly Visitors: 12,753
Yearly Visitors: 152,935
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $36 USD
Yearly Revenue: $436 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: shemaleroulette.com 19
Domain Name: shemaleroulette 15
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.75 seconds
Load Time Comparison: Faster than 89% of sites

PageSpeed Insights

Avg. (All Categories) 78
Performance 81
Accessibility 93
Best Practices 92
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.shemaleroulette.com/
Updated: 20th December, 2022

1.30 seconds
First Contentful Paint (FCP)
90%
7%
3%

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

81

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for shemaleroulette.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 — 2.0 s
The time taken for the page to become fully interactive.
Total Blocking Time — 60 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.6 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 0.6 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://shemaleroulette.com/
http/1.1
0
181.30199983716
308
0
301
text/html
https://www.shemaleroulette.com/
http/1.1
181.69599957764
628.70199978352
2562
6514
200
text/html
Document
https://www.shemaleroulette.com/style/style.css
http/1.1
636.02199964225
1048.3010001481
2377
8408
200
text/css
Stylesheet
https://www.shemaleroulette.com/shemale_chat.js
http/1.1
636.35599985719
901.41499973834
729
992
200
application/javascript
Script
https://www.cammedia.com/shemaleroulette/chat.js
h2
1055.1189994439
1273.1369994581
3495
9151
200
text/html
Script
https://www.shemaleroulette.com/images/bg_gradient.gif
http/1.1
1059.9589999765
1463.4710000828
6481
6202
200
image/gif
Image
https://www.shemaleroulette.com/images/top_bg.jpg
http/1.1
1060.2789996192
1675.2840001136
180070
179787
200
image/jpeg
Image
https://www.shemaleroulette.com/images/logo_shemaleroulette.png
http/1.1
1060.4379996657
1298.7259998918
8575
8296
200
image/png
Image
https://www.shemaleroulette.com/images/btn2.png
http/1.1
1060.521999374
1500.9079994634
5767
5488
200
image/png
Image
https://www.shemaleroulette.com/images/btn.png
http/1.1
1060.6039995328
1450.0349992886
6844
6565
200
image/png
Image
https://www.shemaleroulette.com/images/footer.gif
http/1.1
1060.7150001451
1501.3489993289
343
68
200
image/gif
Image
https://www.shemaleroulette.com/images/bottom_menu.gif
http/1.1
1060.8099997044
1453.0379995704
450
174
200
image/gif
Image
https://www.shemaleroulette.com/images/logo_shemale.png
http/1.1
1060.899999924
1462.7099996433
9682
9403
200
image/png
Image
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/
h2
1282.2159994394
2133.4649994969
12308
54569
200
text/html
Document
https://www2.cammedia.com/_themes/chat_app.min.css
h2
2145.5899998546
2244.9070001021
34194
162836
200
text/css
Stylesheet
https://www2.cammedia.com/_themes/white/theme.css
h2
2146.1239997298
2185.2439995855
2454
7300
200
text/css
Stylesheet
https://www2.cammedia.com/_themes/__logos/shemaleroulette.png
h2
2149.4539994746
2371.1049994454
3674
3247
200
image/png
Image
https://www2.cammedia.com/_themes/__images/trophy.svg
h2
2149.6930001304
2186.6969997063
1842
2828
200
image/svg+xml
Image
https://www2.cammedia.com/_themes/__images/crown_sm.svg
h2
2149.844000116
2242.5839994103
1779
3860
200
image/svg+xml
Image
https://www2.cammedia.com/_themes/__images/dice.svg
h2
2150.0419992954
2225.5259994417
2080
8052
200
image/svg+xml
Image
https://www2.cammedia.com/_themes/__images/slots.svg
h2
2150.2059996128
2229.3400000781
4407
13935
200
image/svg+xml
Image
https://www2.cammedia.com/_themes/__templates/shemaleroulette.css
h2
2149.2809997872
2363.086999394
1262
2573
200
text/css
Stylesheet
https://www2.cammedia.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
2150.3649996594
2168.672000058
4293
12332
200
application/javascript
Script
https://www2.cammedia.com/_themes/__images/loading.gif
h2
2261.1790001392
2305.2770001814
9129
8698
200
image/gif
Image
https://www2.cammedia.com/_themes/__images/header/ico_flags.gif
h2
2262.2480001301
2291.7909994721
2426
1997
200
image/gif
Image
https://www2.cammedia.com/_themes/__fonts/fontawesome-webfont.woff2?v=4.3.0
h2
2266.2119995803
2424.9419998378
57058
56780
200
application/octet-stream
Font
https://www2.cammedia.com/_js/application.min.js
h2
2373.7659994513
2476.2349994853
230963
777493
200
application/javascript
Script
https://www2.cammedia.com/_js/lang.php?lang=en&site=ShemaleRoulette
h2
2374.2570001632
2568.4039993212
6702
17663
200
text/javascript
Script
https://www2.cammedia.com/_ajax/get_roomslist.php?rt=Public
h2
2710.0160000846
2783.6899999529
2034
18600
200
text/html
XHR
https://www2.cammedia.com/_themes/__images/user/ico_genders.svg
h2
2735.0429994985
2774.3020001799
23867
257669
200
image/svg+xml
Image
https://www.shemaleroulette.com/images/background.jpg
http/1.1
2739.120000042
3498.9289995283
117300
117017
200
image/jpeg
Image
https://www2.cammedia.com/_themes/__audio/tip1.wav
h2
2831.9229995832
3158.7359998375
583088
582752
206
audio/x-wav
Media
https://www2.cammedia.com/_themes/__audio/pvt.wav
h2
2832.5169999152
3140.7840000466
247676
247340
206
audio/x-wav
Media
https://www2.cammedia.com/_themes/__audio/gift.wav
h2
2833.2039993256
3187.8969995305
539550
539214
206
audio/x-wav
Media
https://www2.cammedia.com/_themes/__audio/king.wav
h2
2833.8379999623
3233.0639995635
726324
725988
206
audio/x-wav
Media
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)
632.848
9.922
1059.265
39.356
1276.136
5.513
1677.107
8.538
2137.842
10.122
2152.659
10.666
2163.7
62.606
2247.584
9.207
2256.866
17.581
2369.16
6.405
2426.631
11.756
2572.498
12.009
2584.52
177.515
2762.101
59.713
2823.309
8.78
2835.072
36.108
2874.897
12.542
2888.326
20.312
2914.484
41.467
2957.529
19.393
2979.125
7.176
3001.508
56.325
3057.893
5.436
3118.095
46.12
3207.791
51.345
3259.16
5.896
3307.083
45.809
3420.956
6.442
3438.674
44.137
3533.115
47.717
3581.214
38.841
3629.877
47.308
3715.92
23.734
3759.28
5.458
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources — Potential savings of 70 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Shemaleroulette.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://www.shemaleroulette.com/style/style.css
2377
70
Properly size images
Images can slow down the page's load time. Shemaleroulette.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Shemaleroulette.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Shemaleroulette.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Shemaleroulette.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 28 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Shemaleroulette.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://www2.cammedia.com/_themes/chat_app.min.css
34194
28575
Reduce unused JavaScript — Potential savings of 148 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://www2.cammedia.com/_js/application.min.js
230963
152029
Efficiently encode images — Potential savings of 91 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.shemaleroulette.com/images/top_bg.jpg
179787
93123
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 450 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://www.shemaleroulette.com/
448
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Shemaleroulette.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://shemaleroulette.com/
190
https://www.shemaleroulette.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Shemaleroulette.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://www2.cammedia.com/_js/application.min.js
70
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids an excessive DOM size — 55 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
55
Maximum DOM Depth
5
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. Shemaleroulette.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://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/
635.341
1.251
1.041
https://www2.cammedia.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
181.922
119.215
0.546
https://www2.cammedia.com/_js/application.min.js
109.701
89.779
16.568
https://www.shemaleroulette.com/
102.131
3.976
1.385
Unattributable
83.403
2.317
0
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)
Rendering
484.024
Style & Layout
225.86
Script Evaluation
224.899
Other
151.705
Parse HTML & CSS
24.72
Script Parsing & Compilation
20.416
Garbage Collection
6.353
Keep request counts low and transfer sizes small — 35 requests • 2,775 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
35
2842093
Media
4
2096638
Image
17
384716
Script
5
246182
Font
1
57058
Stylesheet
4
40287
Document
2
14870
Other
2
2342
Third-party
22
2500605
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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 — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.90675708403972
0.10774824183251
0.055375038739223
0.04845315889682
0.048255390901322
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www2.cammedia.com/_js/application.min.js
2220
178
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 shemaleroulette.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

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

Audits

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

Other

Serve images in next-gen formats — Potential savings of 200 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://www.shemaleroulette.com/images/top_bg.jpg
179787
145661
https://www.shemaleroulette.com/images/background.jpg
117017
59544.3
Avoid enormous network payloads — Total size was 2,775 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www2.cammedia.com/_themes/__audio/king.wav
726324
https://www2.cammedia.com/_themes/__audio/tip1.wav
583088
https://www2.cammedia.com/_themes/__audio/gift.wav
539550
https://www2.cammedia.com/_themes/__audio/pvt.wav
247676
https://www2.cammedia.com/_js/application.min.js
230963
https://www.shemaleroulette.com/images/top_bg.jpg
180070
https://www.shemaleroulette.com/images/background.jpg
117300
https://www2.cammedia.com/_themes/__fonts/fontawesome-webfont.woff2?v=4.3.0
57058
https://www2.cammedia.com/_themes/chat_app.min.css
34194
https://www2.cammedia.com/_themes/__images/user/ico_genders.svg
23867

Metrics

Cumulative Layout Shift — 0.81
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Serve static assets with an efficient cache policy — 31 resources found
Shemaleroulette.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://www2.cammedia.com/_themes/__audio/king.wav
0
726324
https://www2.cammedia.com/_themes/__audio/tip1.wav
0
583088
https://www2.cammedia.com/_themes/__audio/gift.wav
0
539550
https://www2.cammedia.com/_themes/__audio/pvt.wav
0
247676
https://www.shemaleroulette.com/images/top_bg.jpg
0
180070
https://www.shemaleroulette.com/images/background.jpg
0
117300
https://www2.cammedia.com/_themes/__fonts/fontawesome-webfont.woff2?v=4.3.0
0
57058
https://www.shemaleroulette.com/images/logo_shemale.png
0
9682
https://www.shemaleroulette.com/images/logo_shemaleroulette.png
0
8575
https://www.shemaleroulette.com/images/btn.png
0
6844
https://www2.cammedia.com/_js/lang.php?lang=en&site=ShemaleRoulette
0
6702
https://www.shemaleroulette.com/images/bg_gradient.gif
0
6481
https://www.shemaleroulette.com/images/btn2.png
0
5767
https://www.cammedia.com/shemaleroulette/chat.js
0
3495
https://www.shemaleroulette.com/style/style.css
0
2377
https://www.shemaleroulette.com/shemale_chat.js
0
729
https://www.shemaleroulette.com/images/bottom_menu.gif
0
450
https://www.shemaleroulette.com/images/footer.gif
0
343
https://www2.cammedia.com/_js/application.min.js
14400000
230963
https://www2.cammedia.com/_themes/chat_app.min.css
14400000
34194
https://www2.cammedia.com/_themes/__images/user/ico_genders.svg
14400000
23867
https://www2.cammedia.com/_themes/__images/loading.gif
14400000
9129
https://www2.cammedia.com/_themes/__images/slots.svg
14400000
4407
https://www2.cammedia.com/_themes/__logos/shemaleroulette.png
14400000
3674
https://www2.cammedia.com/_themes/white/theme.css
14400000
2454
https://www2.cammedia.com/_themes/__images/header/ico_flags.gif
14400000
2426
https://www2.cammedia.com/_themes/__images/dice.svg
14400000
2080
https://www2.cammedia.com/_themes/__images/trophy.svg
14400000
1842
https://www2.cammedia.com/_themes/__images/crown_sm.svg
14400000
1779
https://www2.cammedia.com/_themes/__templates/shemaleroulette.css
14400000
1262
https://www2.cammedia.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4293
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www2.cammedia.com/_themes/__fonts/fontawesome-webfont.woff2?v=4.3.0
158.73000025749
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
93

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

Audio and video

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

Internationalization and localization

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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://shemaleroulette.com/
Allowed

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://www2.cammedia.com/_js/application.min.js
100

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of shemaleroulette.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 shemaleroulette.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) 77
Performance 73
Accessibility 93
Best Practices 92
SEO 95
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.shemaleroulette.com/
Updated: 20th December, 2022

1.36 seconds
First Contentful Paint (FCP)
88%
8%
4%

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

73

Performance

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

Metrics

First Contentful Paint — 1.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.8 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 1.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://shemaleroulette.com/
http/1.1
0
188.96599998698
323
0
301
text/html
https://www.shemaleroulette.com/
http/1.1
189.3680000212
439.09200001508
2562
6514
200
text/html
Document
https://www.shemaleroulette.com/style/style.css
http/1.1
450.47400007024
825.35300008021
2377
8408
200
text/css
Stylesheet
https://www.shemaleroulette.com/shemale_chat.js
http/1.1
451.45999989472
841.81799995713
729
992
200
application/javascript
Script
https://www.shemaleroulette.com/images/bg_gradient.gif
http/1.1
834.19999992475
1085.9189999755
6481
6202
200
image/gif
Image
https://www.shemaleroulette.com/images/top_bg.jpg
http/1.1
834.37000005506
1503.4729999024
180070
179787
200
image/jpeg
Image
https://www.shemaleroulette.com/images/logo_shemaleroulette.png
http/1.1
834.44899995811
1083.7870000396
8575
8296
200
image/png
Image
https://www.shemaleroulette.com/images/btn2.png
http/1.1
834.52300005592
1234.2779999599
5767
5488
200
image/png
Image
https://www.shemaleroulette.com/images/btn.png
http/1.1
834.60900001228
1074.8620000668
6844
6565
200
image/png
Image
https://www.cammedia.com/shemaleroulette/chat.js
h2
861.63800000213
1057.3770001065
3495
9151
200
text/html
Script
https://www.shemaleroulette.com/images/footer.gif
http/1.1
861.74400011078
1085.6639998965
343
68
200
image/gif
Image
https://www.shemaleroulette.com/images/bottom_menu.gif
http/1.1
861.81799997576
1233.2679999527
450
174
200
image/gif
Image
https://www.shemaleroulette.com/images/logo_shemale.png
http/1.1
873.86199994944
1264.5429999102
9682
9403
200
image/png
Image
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
h2
1078.404000029
1431.4039999153
12032
52979
200
text/html
Document
https://www2.cammedia.com/_themes/chat_app_mobile.min.css
h2
1444.2910000216
1500.6609999109
36340
173413
200
text/css
Stylesheet
https://www2.cammedia.com/_themes/white/theme.css
h2
1444.3969998974
1480.9970001224
2454
7300
200
text/css
Stylesheet
https://www2.cammedia.com/_themes/__logos/shemaleroulette.png
h2
1448.5480000731
1614.8419999518
3674
3247
200
image/png
Image
https://www2.cammedia.com/_themes/__images/trophy.svg?v=1
h2
1448.6430000979
1528.5449998919
1736
2828
200
image/svg+xml
Image
https://www2.cammedia.com/_themes/__images/crown_sm.svg
h2
1448.7270000391
1481.7480000202
1779
3860
200
image/svg+xml
Image
https://www2.cammedia.com/_themes/__images/dice.svg
h2
1448.8069999497
1485.4900001083
2080
8052
200
image/svg+xml
Image
https://www2.cammedia.com/_themes/__images/slots.svg
h2
1448.8919998985
1502.7749999426
4407
13935
200
image/svg+xml
Image
https://www2.cammedia.com/_themes/__templates/shemaleroulette.css
h2
1448.3560000081
1642.5050001126
1262
2573
200
text/css
Stylesheet
https://www2.cammedia.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
1448.9680000115
1473.081999924
4293
12332
200
application/javascript
Script
https://www2.cammedia.com/_themes/__images/loading.gif
h2
1548.2369998936
1586.1060000025
9129
8698
200
image/gif
Image
https://www2.cammedia.com/_js/mobile_application.min.js
h2
1655.1890000701
1722.3549999762
242127
797185
200
application/javascript
Script
https://www2.cammedia.com/_js/lang.php?lang=en&site=ShemaleRoulette
h2
1656.3190000597
1762.4619998969
6702
17663
200
text/javascript
Script
https://www2.cammedia.com/_themes/__images/header/ico_flags.gif
h2
1885.6550001074
1920.4440000467
2424
1997
200
image/gif
Image
https://www2.cammedia.com/_themes/__fonts/fontawesome-webfont.woff2?v=4.3.0
h2
1886.47700008
2013.4179999586
57058
56780
200
application/octet-stream
Font
https://www2.cammedia.com/_ajax/get_roomslist.php?rt=Public
h2
1932.7539999504
2007.3039999697
2026
18597
200
text/html
XHR
https://www2.cammedia.com/_themes/__images/user/ico_genders.svg
h2
1953.361999942
2002.0169999916
23867
257669
200
image/svg+xml
Image
https://www.shemaleroulette.com/images/background.jpg
http/1.1
1960.228000069
2432.6120000333
117300
117017
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
444.08
14.584
458.935
6.908
831.187
18.447
857.337
15.688
873.07
22.056
1061.789
20.544
1082.352
11.51
1099.134
5.506
1435.803
10.775
1450.922
6.446
1458.046
58.596
1526.711
9.676
1543.246
8.25
1592.79
38.128
1647.5
6.889
1777.379
202.058
1979.475
68.245
2051.058
47.542
2102.243
10.202
2112.531
22.7
2137.649
30.817
2178.949
10.149
2230.641
19.144
2257.458
11.399
2273.16
13.824
2289.845
17.875
2312.078
13.634
2330.924
19.081
2359.664
10.811
2374.774
19.265
2411.119
5.185
2429.645
14.129
2450.613
11.146
2470.047
24.797
2498.3
11.466
2521.09
16.057
2538.769
7.031
2605.007
7.302
2624.33
14.794
2654.953
6.46
2672.253
12.631
2690.59
15.019
2754.981
6.336
2773.654
6.281
2791.931
5.116
2837.038
23.561
2876.322
14.552
2934.819
8.828
2963.327
15.924
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources — Potential savings of 120 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Shemaleroulette.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://www.shemaleroulette.com/style/style.css
2377
180
Properly size images
Images can slow down the page's load time. Shemaleroulette.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Shemaleroulette.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Shemaleroulette.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Shemaleroulette.com should consider minifying JS files.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
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)
https://www.shemaleroulette.com/
250.718
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Shemaleroulette.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://shemaleroulette.com/
630
https://www.shemaleroulette.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Shemaleroulette.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://www2.cammedia.com/_js/mobile_application.min.js
87
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 741 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www2.cammedia.com/_js/mobile_application.min.js
242127
https://www.shemaleroulette.com/images/top_bg.jpg
180070
https://www.shemaleroulette.com/images/background.jpg
117300
https://www2.cammedia.com/_themes/__fonts/fontawesome-webfont.woff2?v=4.3.0
57058
https://www2.cammedia.com/_themes/chat_app_mobile.min.css
36340
https://www2.cammedia.com/_themes/__images/user/ico_genders.svg
23867
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
12032
https://www.shemaleroulette.com/images/logo_shemale.png
9682
https://www2.cammedia.com/_themes/__images/loading.gif
9129
https://www.shemaleroulette.com/images/logo_shemaleroulette.png
8575
Avoids an excessive DOM size — 55 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
55
Maximum DOM Depth
5
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. Shemaleroulette.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 — 1.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
2189.036
6.764
4.5
https://www.shemaleroulette.com/
731.36
13.596
30.32
https://www2.cammedia.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
611.428
474.064
2.004
https://www2.cammedia.com/_js/mobile_application.min.js
516.724
407.876
71.844
Unattributable
412.628
7.172
0
https://www.cammedia.com/shemaleroulette/chat.js
90.84
87.98
1.136
https://www2.cammedia.com/_themes/chat_app_mobile.min.css
51.42
0.168
0
Keep request counts low and transfer sizes small — 31 requests • 741 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
31
758388
Image
17
384608
Script
5
257346
Font
1
57058
Stylesheet
4
42433
Document
2
14594
Other
2
2349
Media
0
0
Third-party
18
416885
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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.
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 — 12 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://www2.cammedia.com/_js/mobile_application.min.js
7408
404
https://www.shemaleroulette.com/
819
153
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
972
136
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
702
117
Unattributable
1108
95
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
1244
94
https://www.cammedia.com/shemaleroulette/chat.js
2550
82
https://www.shemaleroulette.com/
1523
63
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
3546
62
https://www.shemaleroulette.com/
1428
58
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
1338
58
https://www2.cammedia.com/shemaleroulette/tsr/chat.html?page_url=https%3A//www.shemaleroulette.com/&device=mobile&version=mobile
3929
50
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 shemaleroulette.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

Time to Interactive — 6.8 s
The time taken for the page to become fully interactive.
Speed Index — 5.1 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 220 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

Reduce unused CSS — Potential savings of 29 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Shemaleroulette.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://www2.cammedia.com/_themes/chat_app_mobile.min.css
36340
29417
Efficiently encode images — Potential savings of 91 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.shemaleroulette.com/images/top_bg.jpg
179787
93123
First Contentful Paint (3G) — 3420 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Cumulative Layout Shift — 0.672
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

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

Other

Reduce unused JavaScript — Potential savings of 158 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://www2.cammedia.com/_js/mobile_application.min.js
242127
161546
Serve images in next-gen formats — Potential savings of 200 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://www.shemaleroulette.com/images/top_bg.jpg
179787
145661
https://www.shemaleroulette.com/images/background.jpg
117017
59544.3
Serve static assets with an efficient cache policy — 27 resources found
Shemaleroulette.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.shemaleroulette.com/images/top_bg.jpg
0
180070
https://www.shemaleroulette.com/images/background.jpg
0
117300
https://www2.cammedia.com/_themes/__fonts/fontawesome-webfont.woff2?v=4.3.0
0
57058
https://www.shemaleroulette.com/images/logo_shemale.png
0
9682
https://www.shemaleroulette.com/images/logo_shemaleroulette.png
0
8575
https://www.shemaleroulette.com/images/btn.png
0
6844
https://www2.cammedia.com/_js/lang.php?lang=en&site=ShemaleRoulette
0
6702
https://www.shemaleroulette.com/images/bg_gradient.gif
0
6481
https://www.shemaleroulette.com/images/btn2.png
0
5767
https://www.cammedia.com/shemaleroulette/chat.js
0
3495
https://www.shemaleroulette.com/style/style.css
0
2377
https://www2.cammedia.com/_themes/__images/trophy.svg?v=1
0
1736
https://www.shemaleroulette.com/shemale_chat.js
0
729
https://www.shemaleroulette.com/images/bottom_menu.gif
0
450
https://www.shemaleroulette.com/images/footer.gif
0
343
https://www2.cammedia.com/_js/mobile_application.min.js
14400000
242127
https://www2.cammedia.com/_themes/chat_app_mobile.min.css
14400000
36340
https://www2.cammedia.com/_themes/__images/user/ico_genders.svg
14400000
23867
https://www2.cammedia.com/_themes/__images/loading.gif
14400000
9129
https://www2.cammedia.com/_themes/__images/slots.svg
14400000
4407
https://www2.cammedia.com/_themes/__logos/shemaleroulette.png
14400000
3674
https://www2.cammedia.com/_themes/white/theme.css
14400000
2454
https://www2.cammedia.com/_themes/__images/header/ico_flags.gif
14400000
2424
https://www2.cammedia.com/_themes/__images/dice.svg
14400000
2080
https://www2.cammedia.com/_themes/__images/crown_sm.svg
14400000
1779
https://www2.cammedia.com/_themes/__templates/shemaleroulette.css
14400000
1262
https://www2.cammedia.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4293
Minimize main-thread work — 4.7 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)
Rendering
1822.708
Style & Layout
1012.484
Script Evaluation
1005.412
Other
614.888
Script Parsing & Compilation
112.236
Parse HTML & CSS
90.332
Garbage Collection
3.584
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www2.cammedia.com/_themes/__fonts/fontawesome-webfont.woff2?v=4.3.0
126.94099987857
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
93

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

Audio and video

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

Internationalization and localization

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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://shemaleroulette.com/
Allowed

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://www2.cammedia.com/_js/mobile_application.min.js
95

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for shemaleroulette.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 shemaleroulette.com on mobile screens.
Document uses legible font sizes — 98.74% 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
div#shemale_c_rules ol
0.97%
11px
div#shemale_c_footer p#shemale_copyright
0.15%
11px
#btn_getPaid, #btn_getTokens
0.08%
11px
.button, .button-red, .button-girly
0.03%
11px
#btn_register
0.03%
11px
.fa
0.00%
11px
98.74%
≥ 12px

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 50% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
147x30
129x30
95x30

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 shemaleroulette.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 shemaleroulette.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: 51.81.226.88
Continent: Europe
Country: France
France Flag
Region:
City:
Longitude: 2.3387
Latitude: 48.8582
Currencies: EUR
Languages: French

Web Hosting Provider

Name IP Address
NetTuner Corp., dba Webmasters.com
Registration

Domain Registrant

Private Registration: Yes
Name: Private Registration
Organization: Account Privacy
Country: US
City: Tampa
State: FL
Post Code: 33611
Email: proxy.shemaleroulette.com@accountprivacy.com
Phone: +1.8138378000
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NET TUNER CORP. DBA WEBMASTERS.COM 209.216.87.14
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: shemaleroulette.com
Issued By: R10
Valid From: 25th September, 2024
Valid To: 24th December, 2024
Subject: CN = shemaleroulette.com
Hash: 6de9e0b1
Issuer: CN = R10
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03D8C79552D6774834E0DCE388542B89BA42
Serial Number (Hex): 03D8C79552D6774834E0DCE388542B89BA42
Valid From: 25th September, 2024
Valid To: 24th December, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
Timestamp : Sep 25 09:33:07.437 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:8F:74:2E:81:03:40:A8:80:BD:7F:81:
B9:DD:80:2B:D7:8B:E3:EB:72:57:60:66:9F:DC:B6:9A:
34:E8:14:8B:1A:02:21:00:9D:81:34:91:03:E1:6B:4D:
02:1F:B8:4C:62:74:E0:23:E1:7B:F2:5A:FE:4D:6A:24:
69:AF:E6:89:50:08:4B:39
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
Timestamp : Sep 25 09:33:07.429 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:FF:A9:5A:33:CE:7B:7E:52:FC:FD:A9:
71:72:81:45:28:42:F3:90:1D:85:05:04:C3:4B:95:A5:
8A:F8:0A:0F:62:02:20:4C:FF:B5:6A:BC:80:41:1E:29:
8E:0D:F4:41:5C:FA:CD:45:56:6E:9A:52:0E:5A:C7:C2:
C9:DB:62:13:16:C9:E1
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.shemaleroulette.com
DNS:shemaleroulette.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
shemaleroulette.com. 51.81.226.88 IN 21600

NS Records

Host Nameserver Class TTL
shemaleroulette.com. dns3.webmasters.com. IN 21600
shemaleroulette.com. dns4.webmasters.com. IN 21600
shemaleroulette.com. dns1.webmasters.com. IN 21600
shemaleroulette.com. dns2.webmasters.com. IN 21600

MX Records

Priority Host Server Class TTL
10 shemaleroulette.com. mail.shemaleroulette.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
shemaleroulette.com. ns302.webmasters.com. admin.webmasters.com. 21600

TXT Records

Host Value Class TTL
shemaleroulette.com. v=spf1 IN 21600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 18th November, 2024
Server: Apache/2.4.38 (Debian)
Content-Type: text/html; charset=UTF-8

Whois Lookup

Created: 20th February, 2010
Changed: 4th May, 2024
Expires: 20th February, 2025
Registrar: NET TUNER CORP. DBA WEBMASTERS.COM
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
Nameservers: dns1.webmasters.com
dns2.webmasters.com
dns3.webmasters.com
dns4.webmasters.com
Owner Name: Private Registration
Owner Organization: Account Privacy
Owner Street: 4465 W. Gandy Blvd., Suite 801
Owner Post Code: 33611
Owner City: Tampa
Owner State: FL
Owner Country: US
Owner Phone: +1.8138378000
Owner Email: proxy.shemaleroulette.com@accountprivacy.com
Admin Name: Private Registration
Admin Organization: Account Privacy
Admin Street: 4465 W. Gandy Blvd., Suite 801
Admin Post Code: 33611
Admin City: Tampa
Admin State: FL
Admin Country: US
Admin Phone: +1.8138378000
Admin Email: proxy.shemaleroulette.com@accountprivacy.com
Tech Name: Private Registration
Tech Organization: Account Privacy
Tech Street: 4465 W. Gandy Blvd., Suite 801
Tech Post Code: 33611
Tech City: Tampa
Tech State: FL
Tech Country: US
Tech Phone: +1.8138378000
Tech Email: proxy.shemaleroulette.com@accountprivacy.com
Full Whois: NOTICE AND TERMS OF USE: The data in WEBMASTERS.COM's WHOIS database is provided for
information purposes only, and its accuracy is not guaranteed. By submitting a WHOIS
query, you agree to abide by the following terms of use: You agree that you may use this
Data only for lawful purposes and that under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via e-mail, telephone, or fax; or (2) enable high volume,
automated, electronic processes for the purpose of re-transmitting the WHOIS data.

Domain Name: SHEMALEROULETTE.COM
Registry Domain ID: 8076_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.webmasters.com
Registrar URL: http://www.webmasters.com
Updated Date: 2022-29-04T19:00:21Z
Creation Date: 2010-02-20T00:00:00Z
Registrar Registration Expiration Date: 2025-02-20T11:59:59Z
Registrar: NET TUNER CORP. DBA WEBMASTERS.COM
Registrar IANA ID: 634
Registrar Abuse Contact Email: abuse@webmasters.com
Registrar Abuse Contact Phone: +1.8138378000
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID:
Registrant Name: Private Registration
Registrant Organization: Account Privacy
Registrant Street: 4465 W. Gandy Blvd., Suite 801
Registrant City: Tampa
Registrant State/Province: FL
Registrant Postal Code: 33611
Registrant Country: US
Registrant Phone: +1.8138378000
Registrant Phone Ext:
Registrant Fax: FAX: +1.8138378900
Registrant Fax Ext:
Registrant Email: proxy.shemaleroulette.com@accountprivacy.com
Registry Admin ID:
Admin Name: Private Registration
Admin Organization: Account Privacy
Admin Street: 4465 W. Gandy Blvd., Suite 801
Admin City: Tampa
Admin State/Province: FL
Admin Postal Code: 33611
Admin Country: US
Admin Phone: +1.8138378000
Admin Phone Ext:
Admin Fax: FAX: +1.8138378900
Admin Fax Ext:
Admin Email: proxy.shemaleroulette.com@accountprivacy.com
Registry Tech ID:
Tech Name: Private Registration
Tech Organization: Account Privacy
Tech Street: 4465 W. Gandy Blvd., Suite 801
Tech City: Tampa
Tech State/Province: FL
Tech Postal Code: 33611
Tech Country: US
Tech Phone: +1.8138378000
Tech Phone Ext:
Tech Fax: FAX: +1.8138378900
Tech Fax Ext:
Tech Email: proxy.shemaleroulette.com@accountprivacy.com
Nameserver: DNS110.WEBMASTERS.COM
Nameserver: DNS111.WEBMASTERS.COM
Nameserver: DNS112.WEBMASTERS.COM
Nameserver: DNS120.WEBMASTERS.COM
DNSSEC: Unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of whois database: 2024-11-18T13:06:14Z <<<

To prevent fraudulent transfers, the above domain name has been LOCKED at the registry
level. Any request to transfer this domain name to a different owner or registrar will
require a signed, notarized authorization letter which will be verified by telephone
with the current registrant prior to approval.

-----------------------------------------------------------------------------
Get a free domain name with hosting at WEBMASTERS.COM for only $9.95 a month!
-----------------------------------------------------------------------------

Nameservers

Name IP Address
dns1.webmasters.com 51.81.90.59
dns2.webmasters.com 209.216.86.8
dns3.webmasters.com 209.216.88.8
dns4.webmasters.com 51.81.250.19
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address