Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

betrayal.io

betrayal.io is SSL secured

Free website and domain report on betrayal.io

Last Updated: 29th February, 2024
Overview

Snoop Summary for betrayal.io

This is a free and comprehensive report about betrayal.io. Our records indicate that betrayal.io is privately registered by Privacy service provided by Withheld for Privacy ehf. Betrayal.io has the potential to be earning an estimated $10 USD per day from advertising revenue. If betrayal.io was to be sold it would possibly be worth $7,105 USD (based on the daily revenue potential of the website over a 24 month period). Betrayal.io receives an estimated 3,410 unique visitors every day - a large amount of traffic! This report was last updated 29th February, 2024.

About betrayal.io

Site Preview: betrayal.io betrayal.io
Title: Betrayal.io - Play Online!
Description: Play Betrayal.io - An online multiplayer mystery game for 6 to 12 players! Betray your teammates as the betrayer, or work together as a team to win as crew members! Coming soon to PC, iOS and Android.
Keywords and Tags: games
Related Terms: betrayal and beyond
Fav Icon:
Age: Over 3 years old
Domain Created: 9th March, 2020
Domain Updated: 8th September, 2023
Domain Expires: 9th March, 2024
Review

Snoop Score

2/5

Valuation

$7,105 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 180,020
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: 3,410
Monthly Visitors: 103,790
Yearly Visitors: 1,244,650
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $10 USD
Monthly Revenue: $296 USD
Yearly Revenue: $3,547 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: betrayal.io 11
Domain Name: betrayal 8
Extension (TLD): io 2
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 74
Performance 98
Accessibility 66
Best Practices 83
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://betrayal.io/
Updated: 7th August, 2022

1.74 seconds
First Contentful Paint (FCP)
77%
16%
7%

0.05 seconds
First Input Delay (FID)
86%
7%
7%

Simulate loading on desktop
98

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Speed Index — 0.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 20 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 — 1.2 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 — 90 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://betrayal.io/
http/1.1
0
67.150999966543
708
0
301
text/plain
https://betrayal.io/
h2
67.502999969292
173.43399999663
2042
3198
200
text/html
Document
https://betrayal.io/asset/app.css?a28241c
h2
181.53399997391
256.28999999026
3446
14510
200
text/css
Stylesheet
https://betrayal.io/asset/app.js?17e9a4a
h2
181.84600002132
244.89199998789
50784
157381
200
application/javascript
Script
https://betrayal.io/asset/build/UnityLoader.js?60abe18
h2
182.51399998553
433.69699997129
86175
159436
200
application/javascript
Script
https://static.xsolla.com/embed/paystation/1.0.7/widget.min.js
http/1.1
189.39399998635
2190.7950000023
59630
170167
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
h2
189.51300001936
226.52600001311
72953
201961
200
application/javascript
Script
https://betrayal.io/asset/image/loading-pattern.png
h2
288.47799997311
378.58899997082
7994
7189
200
image/png
Image
https://betrayal.io/asset/image/loading-character.png
h2
288.8919999823
352.58399997838
552475
551671
200
image/png
Image
https://betrayal.io/asset/image/logo-betrayal.png
h2
289.44299998693
403.49200001219
112685
111879
200
image/png
Image
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
h2
289.92399998242
345.74899997097
33921
33112
200
application/octet-stream
Font
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
h2
290.10099999141
337.99199998612
29533
28712
200
application/octet-stream
Font
https://betrayal.io/build/webgl
h2
493.96300001536
529.26199999638
1047
561
200
application/json
XHR
https://www.google-analytics.com/g/collect?v=2&tid=G-FYRV7C0YPZ&gtm=2oe830&_p=1872470426&_z=ccd.v9B&cid=154307394.1659885286&ul=en-us&sr=800x600&_s=1&sid=1659885286&sct=1&seg=0&dl=https%3A%2F%2Fbetrayal.io%2F&dt=Betrayal.io%20-%20Play%20Online!&en=page_view&_fv=1&_nsi=1&_ss=1&_ee=1
546.86299996683
553.43600001652
0
0
-1
Ping
https://betrayal.io/asset/build/webgl.wasm.framework.unityweb?f738804
h2
559.17399999453
605.83999997471
128853
736508
200
application/wasm
XHR
https://betrayal.io/asset/build/webgl.data.unityweb?5b0c341
559.01399999857
1098.4099999769
0
0
-1
XHR
blob:https://betrayal.io/750bcb8b-537d-4d2d-a133-3dbcb98987a9
blob
618.55800001649
620.17399998149
0
264
200
text/javascript
Other
blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7
blob
661.58099996392
663.73099997872
0
736508
200
application/javascript
Script
https://betrayal.io/asset/build/webgl.wasm.code.unityweb?fb8639f
755.91700000223
1675.4770000116
0
0
-1
Fetch
https://betrayal.io/asset/build/webgl.wasm.code.unityweb?fb8639f
1676.3959999662
2684.4179999898
0
0
-1
Fetch
https://secure.xsolla.com/favicon.ico
http/1.1
2192.0730000129
3788.9030000078
3328
32988
200
image/x-icon
Image
https://cdn.xsolla.net/img/favicon.ico
h2
2192.212999973
2326.7350000096
1190
1406
200
image/x-icon
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)
206.004
10.342
286.522
28.227
314.761
9.147
327.334
16.855
370.693
17.781
433.697
10.643
469.73
48.007
517.875
6.736
524.73
15.233
542.397
34.202
635.388
11.253
656.894
33.624
692.513
93.71
2220.919
16.273
2247.513
23.347
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Betrayal.io should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Betrayal.io should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Betrayal.io should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Betrayal.io should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Betrayal.io should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Betrayal.io should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 110 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://betrayal.io/
106.925
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Betrayal.io should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://betrayal.io/
190
https://betrayal.io/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Betrayal.io 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 7 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://betrayal.io/asset/app.js?17e9a4a
7273
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://betrayal.io/asset/image/loading-character.png
0
Avoids enormous network payloads — Total size was 1,120 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://betrayal.io/asset/image/loading-character.png
552475
https://betrayal.io/asset/build/webgl.wasm.framework.unityweb?f738804
128853
https://betrayal.io/asset/image/logo-betrayal.png
112685
https://betrayal.io/asset/build/UnityLoader.js?60abe18
86175
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
72953
https://static.xsolla.com/embed/paystation/1.0.7/widget.min.js
59630
https://betrayal.io/asset/app.js?17e9a4a
50784
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
33921
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
29533
https://betrayal.io/asset/image/loading-pattern.png
7994
Avoids an excessive DOM size — 22 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
22
Maximum DOM Depth
div.home-loading > div.home-loading-inner > span.loading-bar-wrapper > span.loading-bar
5
Maximum Child Elements
body.home
11
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Betrayal.io 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://betrayal.io/asset/build/UnityLoader.js?60abe18
125.778
106.855
2.571
https://betrayal.io/
88.064
7.285
1.463
blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7
70.352
0.246
64.989
Unattributable
60.552
5.869
0.192
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
53.733
48.361
2.865
Minimizes main-thread work — 0.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
216.279
Script Parsing & Compilation
76.684
Other
73.035
Rendering
48.935
Garbage Collection
24.498
Style & Layout
15.783
Parse HTML & CSS
2.879
Keep request counts low and transfer sizes small — 20 requests • 1,120 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
20
1146764
Image
5
677672
Script
4
269542
Other
7
130608
Font
2
63454
Stylesheet
1
3446
Document
1
2042
Media
0
0
Third-party
5
137101
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
72953
0
SHOW DETAILS
0
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
body.home > div.home-loading > div.home-loading-character
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
body.home > div.home-loading > div.home-loading-character
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
© END GAME INTERACTIVE 2022
6.1917520357237E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 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)
blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7
1031.0238876343
94
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 betrayal.io on mobile screens.

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

Reduce unused JavaScript — Potential savings of 170 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://betrayal.io/asset/build/UnityLoader.js?60abe18
86175
70228
https://static.xsolla.com/embed/paystation/1.0.7/widget.min.js
59630
41326
https://betrayal.io/asset/app.js?17e9a4a
50784
32555
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
72953
30244
Serve images in next-gen formats — Potential savings of 579 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://betrayal.io/asset/image/loading-character.png
551671
514192.65
https://betrayal.io/asset/image/logo-betrayal.png
111879
78763.95

Other

Serve static assets with an efficient cache policy — 8 resources found
Betrayal.io 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://betrayal.io/asset/image/loading-character.png
14400000
552475
https://betrayal.io/asset/image/logo-betrayal.png
14400000
112685
https://betrayal.io/asset/build/UnityLoader.js?60abe18
14400000
86175
https://betrayal.io/asset/app.js?17e9a4a
14400000
50784
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
14400000
33921
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
14400000
29533
https://betrayal.io/asset/image/loading-pattern.png
14400000
7994
https://betrayal.io/asset/app.css?a28241c
14400000
3446
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://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
55.824999988545
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
47.890999994706
Registers an `unload` listener
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.
Source
SHOW DETAILS
66

Accessibility

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

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

Audio and video

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

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements
head > meta

Navigation

Some elements have 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.
Failing Elements
body.home > div.canvas-container > canvas##canvas

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 betrayal.io 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 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://betrayal.io/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
SHOW DETAILS
abort("both async and sync fetching of the wasm failed") at Error at jsStackTrace (blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:136675) at Object.stackTrace (blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:136846) at Object.onAbort (https://betrayal.io/asset/build/UnityLoader.js?60abe18:4:11199) at abort (blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:735494) at getBinary (blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:144470) at blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:144834
SHOW DETAILS
both async and sync fetching of the wasm failed
SHOW DETAILS
failed to asynchronously prepare wasm: abort("both async and sync fetching of the wasm failed") at Error at jsStackTrace (blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:136675) at Object.stackTrace (blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:136846) at Object.onAbort (https://betrayal.io/asset/build/UnityLoader.js?60abe18:4:11199) at abort (blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:735494) at getBinary (blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:144470) at blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7:8:144834
SHOW DETAILS
Failed to load resource: net::ERR_CONNECTION_FAILED
SHOW DETAILS
Failed to load resource: net::ERR_CONNECTION_FAILED
SHOW DETAILS
Failed to load resource: net::ERR_CONNECTION_FAILED
SHOW DETAILS
falling back to ArrayBuffer instantiation
SHOW DETAILS
wasm streaming compile failed: TypeError: Failed to fetch
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
blob:https://betrayal.io/1ad6390c-1719-4882-9102-1a4cd5fc5fd7
https://static.xsolla.com/embed/paystation/1.0.7/widget.min.js
https://static.xsolla.com/embed/paystation/1.0.7/widget.min.js.map
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for betrayal.io. 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 betrayal.io 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 betrayal.io. 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 betrayal.io 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) 69
Performance 65
Accessibility 66
Best Practices 92
SEO 91
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://betrayal.io/mobile
Updated: 7th August, 2022

1.24 seconds
First Contentful Paint (FCP)
86%
8%
6%

0.02 seconds
First Input Delay (FID)
93%
5%
2%

Simulate loading on mobile
65

Performance

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

Metrics

Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Betrayal.io 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://betrayal.io/asset/app.css?a28241c
3452
150
Properly size images
Images can slow down the page's load time. Betrayal.io should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Betrayal.io should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Betrayal.io should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Betrayal.io should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Betrayal.io 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
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 30 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://betrayal.io/mobile
32.375
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Betrayal.io 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)
https://betrayal.io/asset/image/logo-betrayal.png
0
Avoids enormous network payloads — Total size was 1,209 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://betrayal.io/asset/image/loading-character.png
552480
https://betrayal.io/asset/image/logo-betrayal.png
112681
https://betrayal.io/asset/image/logo-betrayal.png
112681
https://betrayal.io/asset/build/UnityLoader.js?60abe18
86175
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
73030
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
72953
https://betrayal.io/asset/app.js?17e9a4a
50785
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
33928
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
33928
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
29534
Avoids an excessive DOM size — 12 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
12
Maximum DOM Depth
Discord
5
Maximum Child Elements
body.home
4
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Betrayal.io should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.5 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://betrayal.io/mobile
267.72
14.332
8.048
https://betrayal.io/asset/build/UnityLoader.js?60abe18
189.04
176.356
9.884
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
178.464
154.488
14.536
Unattributable
139.124
10.228
0.488
https://betrayal.io/asset/app.js?17e9a4a
129.748
115.12
9.156
Minimizes main-thread work — 0.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
481.796
Other
224.688
Rendering
120.46
Style & Layout
46.816
Script Parsing & Compilation
42.908
Parse HTML & CSS
14.248
Keep request counts low and transfer sizes small — 23 requests • 1,209 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
23
1237555
Image
8
816754
Script
5
282943
Font
4
126924
Stylesheet
2
6904
Document
2
3309
Other
2
721
Media
0
0
Third-party
4
145983
Minimize third-party usage — Third-party code blocked the main thread for 50 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)
SHOW DETAILS
145983
51.576
SHOW DETAILS
0
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
body.home > div.home-mobile > div.home-mobile-wrapper > div.home-mobile-logo
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
body.home > div.home-mobile > div.home-mobile-wrapper > div.home-mobile-logo
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://betrayal.io/asset/build/UnityLoader.js?60abe18
4275
195
https://betrayal.io/asset/app.js?17e9a4a
3210
130
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
4172
103
https://betrayal.io/mobile
651
85
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
4110
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 betrayal.io on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://betrayal.io/
http/1.1
0
37.756999954581
721
0
301
text/plain
https://betrayal.io/
h2
38.147000013851
71.023000054993
2042
3198
200
text/html
Document
https://betrayal.io/asset/app.css?a28241c
h2
81.344000063837
106.02800000925
3452
14510
200
text/css
Stylesheet
https://betrayal.io/asset/app.js?17e9a4a
h2
81.664000055753
115.29500002507
50785
157381
200
application/javascript
Script
https://betrayal.io/asset/build/UnityLoader.js?60abe18
h2
81.770000047982
110.78800004907
86175
159436
200
application/javascript
Script
https://static.xsolla.com/embed/paystation/1.0.7/widget.min.js
80.080999992788
261.3030000357
0
0
-1
Script
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
h2
84.496999974363
114.43600000348
72953
201961
200
application/javascript
Script
https://betrayal.io/asset/image/loading-pattern.png
h2
109.8639999982
134.07300005201
8001
7189
200
image/png
Image
https://betrayal.io/asset/image/loading-character.png
h2
111.40900000464
149.63999995962
552480
551671
200
image/png
Image
https://betrayal.io/asset/image/logo-betrayal.png
h2
111.68199998792
184.79199998546
112681
111879
200
image/png
Image
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
h2
111.80199997034
144.88400006667
33928
33112
200
application/octet-stream
Font
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
h2
111.90300004091
135.55200002156
29534
28712
200
application/octet-stream
Font
https://betrayal.io/mobile
h2
226.27500002272
257.6569999801
1267
1540
200
text/html
Document
https://betrayal.io/asset/app.css?a28241c
h2
269.21900000889
269.34600004461
3452
14510
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
h2
269.86700005364
316.5179999778
73030
201961
200
application/javascript
Script
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
h2
274.23400001135
274.35600000899
29534
28712
200
application/octet-stream
Font
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
h2
274.39999999478
274.46600003168
33928
33112
200
application/octet-stream
Font
https://betrayal.io/asset/image/loading-pattern.png
h2
274.63500003796
274.76499998011
8001
7189
200
image/png
Image
https://betrayal.io/asset/image/loading-pattern.png
h2
274.83500004746
274.90299998317
8001
7189
200
image/png
Image
https://betrayal.io/asset/image/logo-betrayal.png
h2
275.15600004699
275.26100003161
112681
111879
200
image/png
Image
https://betrayal.io/asset/image/mobile-app-store.png
h2
276.61199995782
306.99000007007
4988
4186
200
image/png
Image
https://betrayal.io/asset/image/mobile-play-store.png
h2
276.92099998239
340.30799998436
9921
9124
200
image/png
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-FYRV7C0YPZ&gtm=2oe830&_p=119894098&_z=ccd.v9B&cid=1921629320.1659885307&ul=en-us&sr=360x640&_s=1&sid=1659885307&sct=1&seg=0&dl=https%3A%2F%2Fbetrayal.io%2Fmobile&dr=https%3A%2F%2Fbetrayal.io%2F&dt=Betrayal.io%20-%20Play%20Online!&en=page_view&_fv=1&_nsi=1&_ss=1&_ee=1
374.55099995714
377.52900004853
0
0
-1
Ping
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)
100.263
8.889
134.226
8.434
145.734
5.734
157.003
32.41
202.709
48.663
256.382
21.187
286.854
11.616
358.638
15.6
375.947
25.722
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.5 s
The time taken for the page to become fully interactive.
Total Blocking Time — 280 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).

Audits

Max Potential First Input Delay — 200 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.8 s
The time taken for the primary content of the page to be rendered.

Metrics

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

Other

Reduce unused JavaScript — Potential savings of 140 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://betrayal.io/asset/build/UnityLoader.js?60abe18
86175
78662
https://betrayal.io/asset/app.js?17e9a4a
50785
34229
https://www.googletagmanager.com/gtag/js?id=G-FYRV7C0YPZ
72953
30290
Avoid multiple page redirects — Potential savings of 3,210 ms
Redirects can cause additional delays before the page can begin loading. Betrayal.io should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://betrayal.io/
630
https://betrayal.io/
2580
https://betrayal.io/mobile
0
Serve static assets with an efficient cache policy — 16 resources found
Betrayal.io 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://betrayal.io/asset/image/loading-character.png
14400000
552480
https://betrayal.io/asset/image/logo-betrayal.png
14400000
112681
https://betrayal.io/asset/image/logo-betrayal.png
14400000
112681
https://betrayal.io/asset/build/UnityLoader.js?60abe18
14400000
86175
https://betrayal.io/asset/app.js?17e9a4a
14400000
50785
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
14400000
33928
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
14400000
33928
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
14400000
29534
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
14400000
29534
https://betrayal.io/asset/image/mobile-play-store.png
14400000
9921
https://betrayal.io/asset/image/loading-pattern.png
14400000
8001
https://betrayal.io/asset/image/loading-pattern.png
14400000
8001
https://betrayal.io/asset/image/loading-pattern.png
14400000
8001
https://betrayal.io/asset/image/mobile-app-store.png
14400000
4988
https://betrayal.io/asset/app.css?a28241c
14400000
3452
https://betrayal.io/asset/app.css?a28241c
14400000
3452
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://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
33.082000096329
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
23.648999980651
https://betrayal.io/asset/fonts/yangpro-regular-webfont.woff2
0.12199999764562
https://betrayal.io/asset/fonts/yangpro-bold-webfont.woff2
0.066000036895275
First Contentful Paint (3G) — 5655 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
66

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Contrast

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

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

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

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements
head > meta

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 betrayal.io 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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

SEO

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

Content Best Practices

Document does not have 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.

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 betrayal.io. 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 betrayal.io 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.21.45.245
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: REDACTED FOR PRIVACY
State: Capital Region
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NameCheap, Inc. 104.16.99.56
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: betrayal.io
Issued By: GTS CA 1P5
Valid From: 29th January, 2024
Valid To: 28th April, 2024
Subject: CN = betrayal.io
Hash: f91e8220
Issuer: CN = GTS CA 1P5
O = Google Trust Services LLC
S = US
Version: 2
Serial Number: 0xE34FA717AE246504112B49D065D64725
Serial Number (Hex): E34FA717AE246504112B49D065D64725
Valid From: 29th January, 2024
Valid To: 28th April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:D5:FC:9E:0D:DF:1E:CA:DD:08:97:97:6E:2B:C5:5F:C5:2B:F5:EC:B8
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crls.pki.goog/gts1p5/kEu9ioQF6Gw.crl
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.11129.2.5.3
Authority Information Access: OCSP - URI:http://ocsp.pki.goog/s/gts1p5/osEjGA5mvxg
CA Issuers - URI:http://pki.goog/repo/certs/gts1p5.der
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
Timestamp : Jan 29 19:30:51.806 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:27:31:01:A8:58:F2:0C:9A:9C:78:4B:75:
92:19:8D:CF:9A:26:D1:AC:F1:57:85:2A:93:FB:B5:68:
7E:E0:5E:B9:02:21:00:A5:F1:BB:E9:40:D0:A9:02:77:
1B:69:67:07:4F:97:BE:98:95:68:78:89:57:8D:F9:97:
31:A4:E4:FA:49:F3:64
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DA:B6:BF:6B:3F:B5:B6:22:9F:9B:C2:BB:5C:6B:E8:70:
91:71:6C:BB:51:84:85:34:BD:A4:3D:30:48:D7:FB:AB
Timestamp : Jan 29 19:30:51.821 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E6:45:88:B9:1A:EB:2E:1A:48:B8:87:
1E:36:7F:44:9C:D9:B0:9A:1D:DC:5A:42:B2:5E:70:54:
17:85:68:C5:5E:02:21:00:87:F6:C6:21:31:5C:3D:6C:
E1:02:37:3C:C1:AC:BD:FE:58:BD:2A:ED:FE:FC:03:CF:
B5:DA:09:00:A3:1F:88:47
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.betrayal.io
DNS:betrayal.io
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/2 200
date: 29th February, 2024
content-type: text/html; charset=UTF-8
cache-control: no-cache
server: cloudflare
set-cookie: *
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=w38xuM2JTBW9v1Ue9wiBOPPcyQ8SOglcG9bIPsAT8FlHRxac8rcVLBJ36n2oiInRITGg2wN0XtIqVZSThqZi3pnuNTDe3KoIQ4IYlHx%2F38mNSxgXlLALXki2%2BdCF4g%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
cf-ray: 85cff607ce3681a3-IAD
alt-svc: h3=":443"; ma=86400

Whois Lookup

Created: 9th March, 2020
Changed: 8th September, 2023
Expires: 9th March, 2024
Registrar: NameCheap, Inc.
Status: clientTransferProhibited
Nameservers: cash.ns.cloudflare.com
sharon.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: Capital Region
Owner Country: IS
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: betrayal.io
Registry Domain ID: da7426ba3779469b9b704d85b0c5eb30-DONUTS
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: https://www.namecheap.com/
Updated Date: 2023-08-09T05:59:32Z
Creation Date: 2020-09-03T06:19:33Z
Registry Expiry Date: 2024-09-03T06:19:33Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.9854014545
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Capital Region
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: IS
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: sharon.ns.cloudflare.com
Name Server: cash.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-02-29T09:43:07Z <<<

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

Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
View Raw Whois

Nameservers

Name IP Address
cash.ns.cloudflare.com 108.162.193.81
sharon.ns.cloudflare.com 172.64.32.221
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Love W3 Snoop?
Update Now

betrayal.io Infographic

betrayal.io by the numbers infographic

Recently Updated

ddrmovies.blog
africa.com
youtube.com
onlyflings.com
hdmoviezone.net
findtutors.co.uk
mit-blog.de
dev-insider.de
jointpaindoctor.in
slowroads.io

Recently Viewed

wwbinhinsi.com
wwbinhindi.com
vstartek.com
josepika.com
matamsa.org
romaselectroengineering.com
dskjewelry.com
adamvaughan.org
adventurestomachupicchu.com
dynamixo.com