queensnake.com

queensnake.com is SSL secured

Free website and domain report on queensnake.com

Last Updated: 27th July, 2022 Update Now
Overview

Snoop Summary for queensnake.com

This is a free and comprehensive report about queensnake.com. The domain queensnake.com is currently hosted on a server located in Netherlands with the IP address 82.192.87.148, where the local currency is EUR and Dutch is the local language. Our records indicate that queensnake.com is privately registered by Whois Privacy Corp.. Queensnake.com has the potential to be earning an estimated $7 USD per day from advertising revenue. If queensnake.com was to be sold it would possibly be worth $5,126 USD (based on the daily revenue potential of the website over a 24 month period). Queensnake.com is quite popular with an estimated 2,459 daily unique visitors. This report was last updated 27th July, 2022.

About queensnake.com

Site Preview:
Title: Queensnake.com - Welcome
Description: queensnake.com offers exclusive and unusual BDSM content with true masochistic girls, unique self-torments, lesbian and first-person-view maledom actions.
Keywords and Tags: adult content, pornography
Related Terms: maledom, torments, unusual
Fav Icon:
Age: Over 20 years old
Domain Created: 24th January, 2004
Domain Updated: 14th December, 2018
Domain Expires: 24th January, 2024
Review

Snoop Score

3/5 (Great!)

Valuation

$5,126 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 218,412
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: 2,459
Monthly Visitors: 74,844
Yearly Visitors: 897,535
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $7 USD
Monthly Revenue: $213 USD
Yearly Revenue: $2,558 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: queensnake.com 14
Domain Name: queensnake 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.15 seconds
Load Time Comparison: Faster than 72% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 88
Accessibility 71
Best Practices 83
SEO 91
PWA 78
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://queensnake.com/
Updated: 27th July, 2022

2.61 seconds
First Contentful Paint (FCP)
61%
23%
16%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

88

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 80 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://queensnake.com/
http/1.1
0
328.86799995322
301
0
301
text/html
https://queensnake.com/
http/1.1
329.38699994702
1409.4429999823
9085
8537
200
text/html
Document
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
h2
1432.4849999975
1666.6449999902
85748
267194
200
application/javascript
Script
https://www.google.com/recaptcha/api.js
h2
1433.5029999493
1463.7569999322
1147
850
200
text/javascript
Script
https://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
h2
1433.6509999121
1646.6769999824
16602
67181
200
application/javascript
Script
https://cdn.queensnake.com/js/js.cookie.js?v=20210812-1125
h2
1433.8179999031
1779.383999994
2242
3676
200
application/javascript
Script
https://cdn.queensnake.com/js/qsmisc.js?v=20210812-1125
h2
1433.9669999899
1659.2389999423
2087
3527
200
application/javascript
Script
https://cdn.queensnake.com/js/qscaptcha.js?v=20210812-1125
h2
1440.1719999732
1828.7969999947
1020
1577
200
application/javascript
Script
https://cdn.queensnake.com/js/qsgestures.js?v=20210812-1125
h2
1441.9219999108
1616.6619999567
1288
2157
200
application/javascript
Script
https://cdn.queensnake.com/js/qsstore.js?v=20210812-1125
h2
1442.9079999682
1627.5059999898
2731
7901
200
application/javascript
Script
https://cdn.queensnake.com/js/qswebpush.js?v=20210812-1125
h2
1443.1929999264
1917.4959999509
1954
3862
200
application/javascript
Script
https://cdn.queensnake.com/js/plyr/plyr.css?v=20210812-1125
h2
1443.3880000142
1629.4279999565
5932
24875
200
text/css
Stylesheet
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
h2
1443.5860000085
1673.398999963
79062
303802
200
application/javascript
Script
https://cdn.queensnake.com/js/hint.css-2.6.0/hint.css?v=20210812-1125
h2
1444.6749999188
1610.6379999546
3677
15226
200
text/css
Stylesheet
https://cdn.queensnake.com/skins/qs/qs-cdn-20210812-1125.css
h2
1444.9569999706
1658.3039999241
16950
114218
200
text/css
Stylesheet
https://cdn.queensnake.com/skins/qs/custom/custom-cdn-20210812-1125.css
h2
1445.3839999624
1621.1219999241
957
0
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
h2
1832.7349999454
1867.3129999079
42372
108465
200
application/javascript
Script
https://cdn.queensnake.com/skins/qs/notification.png
h2
1892.0919999946
2088.4859999642
3588
2921
200
image/png
Image
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
h2
1920.8729999373
1939.5939999959
154126
387107
200
text/javascript
Script
https://cdn.queensnake.com/skins/qs/blog.png
h2
1982.24199994
2049.4450000115
3183
2544
200
image/png
Image
https://cdn.queensnake.com/skins/qs/twitter.png
h2
1982.4350000126
2211.4909999073
4255
3616
200
image/png
Image
https://cdn.queensnake.com/skins/qs/tumblr.png
h2
1985.0330000045
2097.4219999043
3237
2598
200
image/png
Image
https://cdn.queensnake.com/skins/qs/custom/background.jpg?v=20210812-1125
h2
2005.2429999923
2124.4449999649
197329
196687
200
image/jpeg
Image
https://cdn.queensnake.com/skins/qs/custom/headerLogo.jpg?v=20210812-1125
h2
2006.7789999302
2066.7999999132
30586
29945
200
image/jpeg
Image
https://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
h2
2013.3559999522
2232.9989999998
476731
476089
200
image/jpeg
Image
https://www.google-analytics.com/analytics.js
h2
2123.7379999366
2134.0159999672
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1699167770&t=pageview&_s=1&dl=https%3A%2F%2Fqueensnake.com%2F&ul=en-us&de=UTF-8&dt=Queensnake.com%20-%20Welcome&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=2064756985&gjid=1329039010&cid=82910822.1658917623&tid=UA-8354274-4&_gid=1827179442.1658917623&_r=1&gtm=2ou7p0&z=1843268588
h2
2383.3509999095
2391.1499999231
613
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-8354274-4&cid=82910822.1658917623&jid=2064756985&gjid=1329039010&_gid=1827179442.1658917623&_u=YEBAAUAAAAAAAC~&z=889484802
h2
2397.4589999998
2403.6619999679
685
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1473.029
26.351
1671.118
7.458
1737.29
39.846
1777.435
16.162
1973.374
79.305
2052.714
43.65
2096.478
11.539
2108.23
32.207
2146.999
28.796
2176.483
22.365
2199.156
27.684
2234.781
7.377
2253.537
35.999
2289.555
60.361
2353.956
37.117
2391.239
45.087
2910.65
5.079
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Queensnake.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Queensnake.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Queensnake.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn.queensnake.com/skins/qs/qs-cdn-20210812-1125.css
16950
2856
Minify JavaScript — Potential savings of 84 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Queensnake.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
85748
41809
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
79062
37920
https://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
16602
6004
Reduce unused CSS — Potential savings of 15 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Queensnake.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://cdn.queensnake.com/skins/qs/qs-cdn-20210812-1125.css
16950
15485
Efficiently encode images — Potential savings of 67 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
476089
68576
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://queensnake.com/
8537
5490
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Queensnake.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://queensnake.com/
190
https://queensnake.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Queensnake.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 6 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://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
6451
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
43
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
0
Avoids enormous network payloads — Total size was 1,141 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
476731
https://cdn.queensnake.com/skins/qs/custom/background.jpg?v=20210812-1125
197329
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
154126
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
85748
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
79062
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
42372
https://cdn.queensnake.com/skins/qs/custom/headerLogo.jpg?v=20210812-1125
30586
https://www.google-analytics.com/analytics.js
20631
https://cdn.queensnake.com/skins/qs/qs-cdn-20210812-1125.css
16950
https://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
16602
Uses efficient cache policy on static assets — 1 resource found
Queensnake.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20631
Avoids an excessive DOM size — 64 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
64
Maximum DOM Depth
8
Maximum Child Elements
9
Avoid chaining critical requests — 13 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Queensnake.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://queensnake.com/
226.004
29.463
2.714
Unattributable
90.516
9.638
0.154
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
72.313
56.113
6.085
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
66.331
59.969
2.886
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
61.739
49.677
8.418
Minimizes main-thread work — 0.6 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
292.291
Other
128.495
Rendering
95.848
Style & Layout
41.393
Parse HTML & CSS
31.482
Script Parsing & Compilation
30.022
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 28 requests • 1,141 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
28
1168119
Image
7
718909
Script
13
411010
Stylesheet
4
27516
Document
1
9085
Other
3
1599
Media
0
0
Font
0
0
Third-party
6
219574
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)
154126
0
42372
0
21244
0
1147
0
685
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
1246
79
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
1186
60
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of queensnake.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 570 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Queensnake.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://cdn.queensnake.com/js/plyr/plyr.css?v=20210812-1125
5932
230
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
85748
80
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
79062
120
Reduce unused JavaScript — Potential savings of 257 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
154126
121337
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
79062
65325
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
85748
56099
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
42372
20639
Serve images in next-gen formats — Potential savings of 406 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://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
476089
286069.95
https://cdn.queensnake.com/skins/qs/custom/background.jpg?v=20210812-1125
196687
118189.45
https://cdn.queensnake.com/skins/qs/custom/headerLogo.jpg?v=20210812-1125
29945
11117.85

Other

Reduce initial server response time — Root document took 1,080 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://queensnake.com/
1081.048
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://cdn.queensnake.com/skins/qs/notification.png
https://cdn.queensnake.com/skins/qs/blog.png
https://cdn.queensnake.com/skins/qs/twitter.png
https://cdn.queensnake.com/skins/qs/tumblr.png
71

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Internationalization and localization

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.1.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
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://queensnake.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
Medium
91

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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

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

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers 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.
Sets 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
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 queensnake.com on mobile screens.
Provides 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.

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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) 73
Performance 56
Accessibility 71
Best Practices 83
SEO 77
PWA 80
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://queensnake.com/
Updated: 27th July, 2022

3.80 seconds
First Contentful Paint (FCP)
44%
21%
35%

0.01 seconds
First Input Delay (FID)
98%
2%
0%

56

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. Queensnake.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Queensnake.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Queensnake.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn.queensnake.com/skins/qs/qs-cdn-20210812-1125.css
16950
2856
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://queensnake.com/
8537
5490
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Queensnake.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://queensnake.com/
630
https://queensnake.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Queensnake.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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
0
Avoids enormous network payloads — Total size was 1,141 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
476730
https://cdn.queensnake.com/skins/qs/custom/background.jpg?v=20210812-1125
197329
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
154126
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
85713
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
79062
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
42369
https://cdn.queensnake.com/skins/qs/custom/headerLogo.jpg?v=20210812-1125
30586
https://www.google-analytics.com/analytics.js
20631
https://cdn.queensnake.com/skins/qs/qs-cdn-20210812-1125.css
16950
https://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
16570
Uses efficient cache policy on static assets — 1 resource found
Queensnake.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20631
Avoids an excessive DOM size — 64 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
64
Maximum DOM Depth
8
Maximum Child Elements
9
Avoid chaining critical requests — 13 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Queensnake.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.7 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://queensnake.com/
290.392
38.5
9.268
Unattributable
212.984
19.824
0.66
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
195.992
157.096
18.952
https://www.google-analytics.com/analytics.js
167.772
152.98
4.576
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
144.336
103.816
27.248
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
124.828
102.204
15.552
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
73.248
33.112
20.276
Minimizes main-thread work — 1.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
655.512
Other
323.536
Script Parsing & Compilation
105.352
Style & Layout
96.24
Parse HTML & CSS
48.208
Rendering
39.848
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 28 requests • 1,141 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
28
1168017
Image
7
718908
Script
13
410942
Stylesheet
4
27484
Document
1
9085
Other
3
1598
Media
0
0
Font
0
0
Third-party
6
219571
Minimize third-party usage — Third-party code blocked the main thread for 150 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21244
94
154126
47.856
42369
9.224
1147
0
685
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 10 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google-analytics.com/analytics.js
3765
154
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
4988
140
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
3158
106
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
3608
87
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
5408
73
https://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
4208
70
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
3695
70
https://queensnake.com/
1110
68
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
2611
61
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
2558
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of queensnake.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://queensnake.com/
http/1.1
0
328.70099996217
300
0
301
text/html
https://queensnake.com/
http/1.1
329.1629999876
1381.8989999127
9085
8537
200
text/html
Document
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
h2
1394.2849999294
1640.611999901
85713
267194
200
application/javascript
Script
https://www.google.com/recaptcha/api.js
h2
1394.5839998778
1401.3729998842
1147
850
200
text/javascript
Script
https://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
h2
1395.1789999846
1635.4970000684
16570
67181
200
application/javascript
Script
https://cdn.queensnake.com/js/js.cookie.js?v=20210812-1125
h2
1395.8689998835
1588.5939998552
2244
3676
200
application/javascript
Script
https://cdn.queensnake.com/js/qsmisc.js?v=20210812-1125
h2
1396.2520000059
1587.2110000346
2087
3527
200
application/javascript
Script
https://cdn.queensnake.com/js/qscaptcha.js?v=20210812-1125
h2
1396.4879999403
1613.5929999873
1020
1577
200
application/javascript
Script
https://cdn.queensnake.com/js/qsgestures.js?v=20210812-1125
h2
1396.9399998896
1593.9789998811
1288
2157
200
application/javascript
Script
https://cdn.queensnake.com/js/qsstore.js?v=20210812-1125
h2
1397.3959998693
1609.5169999171
2731
7901
200
application/javascript
Script
https://cdn.queensnake.com/js/qswebpush.js?v=20210812-1125
h2
1397.7900000755
1625.3519998863
1954
3862
200
application/javascript
Script
https://cdn.queensnake.com/js/plyr/plyr.css?v=20210812-1125
h2
1397.9410000611
1588.1189999636
5932
24875
200
text/css
Stylesheet
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
h2
1398.3439998701
1654.4460000005
79062
303802
200
application/javascript
Script
https://cdn.queensnake.com/js/hint.css-2.6.0/hint.css?v=20210812-1125
h2
1398.6710000318
1594.9729999993
3645
15226
200
text/css
Stylesheet
https://cdn.queensnake.com/skins/qs/qs-cdn-20210812-1125.css
h2
1399.0849999245
1647.7769999765
16950
114218
200
text/css
Stylesheet
https://cdn.queensnake.com/skins/qs/custom/custom-cdn-20210812-1125.css
h2
1399.3939999491
1613.0190000404
957
0
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
h2
1656.278999988
1686.1779999454
42369
108465
200
application/javascript
Script
https://cdn.queensnake.com/skins/qs/notification.png
h2
1703.8650000468
1743.3430000674
3588
2921
200
image/png
Image
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
h2
1727.9590000398
1739.2390000168
154126
387107
200
text/javascript
Script
https://cdn.queensnake.com/skins/qs/blog.png
h2
1729.1500000283
2055.352000054
3183
2544
200
image/png
Image
https://cdn.queensnake.com/skins/qs/twitter.png
h2
1730.1109998953
1943.7369999941
4255
3616
200
image/png
Image
https://cdn.queensnake.com/skins/qs/tumblr.png
h2
1731.4440000337
1760.2059999481
3237
2598
200
image/png
Image
https://cdn.queensnake.com/skins/qs/custom/background.jpg?v=20210812-1125
h2
1740.3279999271
1845.1809999533
197329
196687
200
image/jpeg
Image
https://cdn.queensnake.com/skins/qs/custom/headerLogo.jpg?v=20210812-1125
h2
1740.557000041
1825.7079999894
30586
29945
200
image/jpeg
Image
https://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
h2
1741.2719998974
1855.0919999834
476730
476089
200
image/jpeg
Image
https://www.google-analytics.com/analytics.js
h2
1823.3330000658
1828.8499999326
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1759406003&t=pageview&_s=1&dl=https%3A%2F%2Fqueensnake.com%2F&ul=en-us&de=UTF-8&dt=Queensnake.com%20-%20Welcome&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=1771665128&gjid=1657782470&cid=1087880678.1658917649&tid=UA-8354274-4&_gid=1911310969.1658917649&_r=1&gtm=2ou7p0&z=1554026767
h2
1917.1269999351
1921.1399999913
613
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-8354274-4&cid=1087880678.1658917649&jid=1771665128&gjid=1657782470&_gid=1911310969.1658917649&_u=YEBAAUAAAAAAAC~&z=713224771
h2
1927.3870000616
1932.7859999612
685
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1415.989
16.921
1685.193
26.563
1713.153
17.475
1733.192
18.312
1751.564
21.689
1773.277
18.66
1792.314
5.451
1797.807
17.503
1820.343
13.354
1837.696
15.194
1857.429
34.898
1908.729
38.381
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

Time to Interactive — 5.3 s
The time taken for the page to become fully interactive.
Speed Index — 4.7 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 310 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 — 150 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.5 s
The time taken for the primary content of the page to be rendered.

Other

Minify JavaScript — Potential savings of 84 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Queensnake.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
85713
41792
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
79062
37920
https://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
16570
5993
Reduce unused CSS — Potential savings of 15 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Queensnake.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://cdn.queensnake.com/skins/qs/qs-cdn-20210812-1125.css
16950
15464
Efficiently encode images — Potential savings of 67 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
476089
68576
Avoid serving legacy JavaScript to modern browsers — Potential savings of 6 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://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
6438
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
43

Metrics

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

Other

Eliminate render-blocking resources — Potential savings of 2,350 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Queensnake.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://cdn.queensnake.com/js/plyr/plyr.css?v=20210812-1125
5932
780
https://cdn.queensnake.com/js/hint.css-2.6.0/hint.css?v=20210812-1125
3645
150
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
85713
450
https://cdn.queensnake.com/js/sweetalert.js?v=20210812-1125
16570
300
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
79062
600
Reduce unused JavaScript — Potential savings of 257 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/5JGZgxkKwe0uOXDdUvSaNtk_/recaptcha__en.js
154126
121337
https://cdn.queensnake.com/js/plyr/plyr.js?v=20210812-1125
79062
65325
https://cdn.queensnake.com/js/jquery-3.1.1.js?v=20210812-1125
85713
56076
https://www.googletagmanager.com/gtag/js?id=UA-8354274-4
42369
20637
Serve images in next-gen formats — Potential savings of 406 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://cdn.queensnake.com/skins/qs/custom/welcome.jpg?v=20210812-1125
476089
286069.95
https://cdn.queensnake.com/skins/qs/custom/background.jpg?v=20210812-1125
196687
118189.45
https://cdn.queensnake.com/skins/qs/custom/headerLogo.jpg?v=20210812-1125
29945
11117.85
Reduce initial server response time — Root document took 1,050 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://queensnake.com/
1053.727
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://cdn.queensnake.com/skins/qs/notification.png
https://cdn.queensnake.com/skins/qs/blog.png
https://cdn.queensnake.com/skins/qs/twitter.png
https://cdn.queensnake.com/skins/qs/tumblr.png
First Contentful Paint (3G) — 6797 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
71

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Internationalization and localization

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.1.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
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://queensnake.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
Medium
77

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Mobile Friendly

Document doesn't use legible font sizes — 2.29% 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
.commonWrapper
70.60%
11.2px
.cookieConsent span:first-child
17.94%
10.5px
.footerCopyright div
9.14%
10.5px
.unreadNotifications div
0.02%
5.6px
0.02%
< 12px
2.29%
≥ 12px
Tap targets are not sized appropriately — 7% 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
32x16
FAQ
25x16
1
11x11
11x11
11x11
46x16
78x16
62x16
76x16
29x16

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

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

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers 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.
Sets 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
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 queensnake.com on mobile screens.
Provides 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.

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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: 82.192.87.148
Continent: Europe
Country: Netherlands
Netherlands Flag
Region:
City:
Longitude: 4.8995
Latitude: 52.3824
Currencies: EUR
Languages: Dutch

Web Hosting Provider

Name IP Address
LeaseWeb Netherlands B.V.
Registration

Domain Registrant

Private Registration: Yes
Name: Domain Admin
Organization: Whois Privacy Corp.
Country: BS
City: Nassau
State: New Providence
Post Code:
Email: queensnake.com-owner@customers.whoisprivacycorp.com
Phone: +1.5163872248
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Internet Domain Service BS Corp. 172.67.37.162
Security

Visitor Safety

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

SSL/TLS Certificate

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

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Jun 14 22:05:03.220 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:9E:4F:D9:91:E3:EE:25:27:04:DE:BC:
23:4A:AF:F2:A8:F3:30:5A:20:1B:21:C1:0A:96:D2:0F:
29:68:E4:AE:20:02:20:7A:6A:69:17:3F:78:78:AC:D3:
F7:5F:83:6C:6A:88:AF:E3:EE:A4:E1:91:EA:1F:0C:82:
18:6B:54:5D:3A:93:62
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Jun 14 22:05:03.271 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:82:8B:83:47:55:F1:A3:D6:AA:45:49:
5F:8D:6C:5D:7A:01:C6:A7:A7:A2:F8:FF:8E:C1:39:7E:
31:77:D5:55:1B:02:21:00:A3:BF:F2:08:60:94:AD:8D:
10:75:73:37:FA:BB:5D:F3:39:77:3A:D7:96:51:DA:F8:
D5:5E:35:21:F6:E6:CA:9E
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:queensnake.me
DNS:queensnake.net
DNS:queensnake.xyz
DNS:queensnakebdsm.com
DNS:www.queensnake.com
DNS:queensnake.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
queensnake.com. 82.192.87.148 IN 3600

NS Records

Host Nameserver Class TTL
queensnake.com. ns.queensect.com. IN 14400
queensnake.com. ns.queensnake.com. IN 14400

MX Records

Priority Host Server Class TTL
1 queensnake.com. ASPMX.L.GOOGLE.com. IN 14400
5 queensnake.com. ALT2.ASPMX.L.GOOGLE.com. IN 14400
10 queensnake.com. ASPMX3.GOOGLEMAIL.com. IN 14400
10 queensnake.com. ASPMX2.GOOGLEMAIL.com. IN 14400
5 queensnake.com. ALT1.ASPMX.L.GOOGLE.com. IN 14400

SOA Records

Domain Name Primary NS Responsible Email TTL
queensnake.com. ns.queensect.com. admin.queensnake.com. 14400

TXT Records

Host Value Class TTL
queensnake.com. v=spf1 IN 14400
queensnake.com. google-site-verification=_iRd4ClzI-z5eaeKZW3K0xQOSYzAmesDLaj2T50k24Y IN 14400

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 27th July, 2022
Server: Apache
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate
Content-Type: text/html; charset=UTF-8
Set-Cookie: *
Pragma: no-cache
Access-Control-Allow-Origin: https://queensnake.com
Access-Control-Allow-Credentials: true

Whois Lookup

Created: 24th January, 2004
Changed: 14th December, 2018
Expires: 24th January, 2024
Registrar: Internet Domain Service BS Corp.
Status: clientTransferProhibited
Nameservers: ns.queensect.com
ns.queensnake.com
Owner Name: Domain Admin
Owner Organization: Whois Privacy Corp.
Owner Street: Ocean Centre, Montagu Foreshore, East Bay Street
Owner City: Nassau
Owner State: New Providence
Owner Country: BS
Owner Phone: +1.5163872248
Owner Email: queensnake.com-owner@customers.whoisprivacycorp.com
Admin Name: Domain Admin
Admin Organization: Whois Privacy Corp.
Admin Street: Ocean Centre, Montagu Foreshore, East Bay Street
Admin City: Nassau
Admin State: New Providence
Admin Country: BS
Admin Phone: +1.5163872248
Admin Email: queensnake.com-admin@customers.whoisprivacycorp.com
Tech Name: Domain Admin
Tech Organization: Whois Privacy Corp.
Tech Street: Ocean Centre, Montagu Foreshore, East Bay Street
Tech City: Nassau
Tech State: New Providence
Tech Country: BS
Tech Phone: +1.5163872248
Tech Email: queensnake.com-tech@customers.whoisprivacycorp.com
Full Whois: Domain Name: QUEENSNAKE.COM
Registry Domain ID: 110527189_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.internet.bs
Registrar URL: http://www.internetbs.net
Updated Date: 2018-12-14T04:36:37Z
Creation Date: 2004-01-24T19:22:58Z
Registrar Registration Expiration Date: 2024-01-24T19:22:58Z
Registrar: Internet Domain Service BS Corp.
Registrar IANA ID: 2487
Registrar Abuse Contact Email: abuse@internet.bs
Registrar Abuse Contact Phone: +1.5163015301
Reseller:
Domain Status: clientTransferProhibited - http://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not disclosed
Registrant Name: Domain Admin
Registrant Organization: Whois Privacy Corp.
Registrant Street: Ocean Centre, Montagu Foreshore, East Bay Street
Registrant City: Nassau
Registrant State/Province: New Providence
Registrant Postal Code:
Registrant Country: BS
Registrant Phone: +1.5163872248
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: queensnake.com-owner@customers.whoisprivacycorp.com
Registry Admin ID: Not disclosed
Admin Name: Domain Admin
Admin Organization: Whois Privacy Corp.
Admin Street: Ocean Centre, Montagu Foreshore, East Bay Street
Admin City: Nassau
Admin State/Province: New Providence
Admin Postal Code:
Admin Country: BS
Admin Phone: +1.5163872248
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: queensnake.com-admin@customers.whoisprivacycorp.com
Registry Tech ID: Not disclosed
Tech Name: Domain Admin
Tech Organization: Whois Privacy Corp.
Tech Street: Ocean Centre, Montagu Foreshore, East Bay Street
Tech City: Nassau
Tech State/Province: New Providence
Tech Postal Code:
Tech Country: BS
Tech Phone: +1.5163872248
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: queensnake.com-tech@customers.whoisprivacycorp.com
Name Server: ns.queensect.com
Name Server: ns.queensnake.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-07-27T10:26:18Z <<<


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


Nameservers

Name IP Address
ns.queensect.com 95.211.121.212
ns.queensnake.com 82.192.87.148
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address