Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

rocks.com

rocks.com is SSL secured

Free website and domain report on rocks.com

Last Updated: 15th January, 2023 Update Now
Overview

Snoop Summary for rocks.com

This is a free and comprehensive report about rocks.com. Rocks.com is hosted in Germany on a server with an IP address of 64.190.63.111, where EUR is the local currency and the local language is German. Our records indicate that rocks.com is privately registered by Contact Privacy Inc. Customer 0142777537. Rocks.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If rocks.com was to be sold it would possibly be worth $762 USD (based on the daily revenue potential of the website over a 24 month period). Rocks.com receives an estimated 361 unique visitors every day - a decent amount of traffic! This report was last updated 15th January, 2023.

About rocks.com

Site Preview: rocks.com rocks.com
Title: Rocks
Description:
Keywords and Tags: content server
Related Terms: 3 types of rocks, painted rocks, red rocks, red rocks amphitheatre, red rocks concerts, red rocks schedule, rocks, snapper rocks, three types of rocks, types of rocks
Fav Icon:
Age: Over 26 years old
Domain Created: 18th March, 1997
Domain Updated: 18th March, 2022
Domain Expires: 19th March, 2023
Review

Snoop Score

1/5

Valuation

$762 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,555,083
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: 361
Monthly Visitors: 10,999
Yearly Visitors: 131,897
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $31 USD
Yearly Revenue: $376 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: rocks.com 9
Domain Name: rocks 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 75
Performance 100
Accessibility 70
Best Practices 92
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
100

Performance

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

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.5 s
The time taken for the page to become fully interactive.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.7 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 — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.5 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://rocks.com/
http/1.1
0
467.28500002064
7724
22208
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
475.7179999724
490.20500003826
54448
147553
200
text/javascript
Script
http://img.sedoparking.com/templates/bg/arrows.png
http/1.1
488.89899998903
546.80500004906
13196
12642
200
image/png
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=rocks.com&client=dp-sedo80_3ph&product=SAS&callback=__sasCookie
h2
539.78099999949
546.40800005291
882
358
200
text/javascript
Script
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=9330244380&channel=cl-255%2C%2Cexp-0051%2Cauxa-control-2%2C55397&client=dp-sedo80_3ph&r=m&hl=en&terms=Squirt%2CGems%2Cgem%20stone&type=3&uiopt=true&swp=as-drid-2616522800315416&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r3&nocache=6631673744941124&num=0&output=afd_ads&domain_name=rocks.com&v=3&bsl=8&pac=2&u_his=2&u_tz=-480&dt=1673744941126&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=925&frm=0&cl=500700135&uio=-&cont=rb-default&jsid=caf&jsv=500700135&rurl=http%3A%2F%2Frocks.com%2F&adbw=master-1%3A490
h2
553.98900003638
654.634000035
2602
5446
200
text/html
Document
http://rocks.com/search/tsc.php?200=MjA1OTcyNDA=&21=NjcuMjA1LjEzNy4xMjc=&681=MTY3Mzc0NDk0MDdkOTAyZTRhN2E4NDA0OGFkZmI4YWJmNWNlNWE4YmJh&crc=17c663adf15a4b33eee2fd833d2c9a0a2581875e&cv=1
http/1.1
555.92399998568
809.01299999095
200
0
200
text/html
XHR
https://www.google.com/adsense/domains/caf.js?pac=2
h2
677.25900001824
695.75299997814
54482
147504
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
750.06099999882
756.93499995396
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
750.24299998768
754.09800000489
1089
200
200
image/svg+xml
Image
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=dx5pduhqqbc0&aqid=LVLDY7DZC4b0owb2j4KIDw&psid=9330244380&pbt=bs&adbx=430&adby=134.625&adbh=551&adbw=490&adbah=178%2C178%2C178&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=500700135&csala=9%7C0%7C129%7C40%7C55&lle=0&llm=1000&ifv=1&usr=1
h2
2277.0360000432
2296.2759999791
1160
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=dm4ijncze342&aqid=LVLDY7DZC4b0owb2j4KIDw&psid=9330244380&pbt=bv&adbx=430&adby=134.625&adbh=551&adbw=490&adbah=178%2C178%2C178&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=500700135&csala=9%7C0%7C129%7C40%7C55&lle=0&llm=1000&ifv=1&usr=1
h2
2778.2829999924
2796.8610000098
798
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
471.593
11.488
487.824
6.83
519.606
9.161
529.047
28.396
565.66
6.234
661.971
13.766
710.452
36.812
748.653
7.665
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. Rocks.com 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. Rocks.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rocks.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rocks.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rocks.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rocks.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 63 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
54448
32948
https://www.google.com/adsense/domains/caf.js?pac=2
54482
31893
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 470 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://rocks.com/
468.277
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Rocks.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rocks.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
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://img.sedoparking.com/templates/bg/arrows.png
0
Avoids enormous network payloads — Total size was 135 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js?pac=2
54482
http://www.google.com/adsense/domains/caf.js
54448
http://img.sedoparking.com/templates/bg/arrows.png
13196
http://rocks.com/
7724
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=9330244380&channel=cl-255%2C%2Cexp-0051%2Cauxa-control-2%2C55397&client=dp-sedo80_3ph&r=m&hl=en&terms=Squirt%2CGems%2Cgem%20stone&type=3&uiopt=true&swp=as-drid-2616522800315416&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r3&nocache=6631673744941124&num=0&output=afd_ads&domain_name=rocks.com&v=3&bsl=8&pac=2&u_his=2&u_tz=-480&dt=1673744941126&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=925&frm=0&cl=500700135&uio=-&cont=rb-default&jsid=caf&jsv=500700135&rurl=http%3A%2F%2Frocks.com%2F&adbw=master-1%3A490
2602
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=dx5pduhqqbc0&aqid=LVLDY7DZC4b0owb2j4KIDw&psid=9330244380&pbt=bs&adbx=430&adby=134.625&adbh=551&adbw=490&adbah=178%2C178%2C178&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=500700135&csala=9%7C0%7C129%7C40%7C55&lle=0&llm=1000&ifv=1&usr=1
1160
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
1089
https://partner.googleadservices.com/gampad/cookie.js?domain=rocks.com&client=dp-sedo80_3ph&product=SAS&callback=__sasCookie
882
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=dm4ijncze342&aqid=LVLDY7DZC4b0owb2j4KIDw&psid=9330244380&pbt=bv&adbx=430&adby=134.625&adbh=551&adbw=490&adbah=178%2C178%2C178&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=500700135&csala=9%7C0%7C129%7C40%7C55&lle=0&llm=1000&ifv=1&usr=1
798
Uses efficient cache policy on static assets — 3 resources found
Rocks.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://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1089
http://img.sedoparking.com/templates/bg/arrows.png
604800000
13196
Avoids an excessive DOM size — 26 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
26
Maximum DOM Depth
Sedo Domain Parking
6
Maximum Child Elements
body
8
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rocks.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.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://rocks.com/
65.523
31.124
2.738
Minimizes main-thread work — 0.2 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
86.553
Other
42.746
Style & Layout
15.567
Rendering
14.371
Script Parsing & Compilation
11.545
Parse HTML & CSS
10.719
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 — 11 requests • 135 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
11
137769
Script
3
109812
Image
5
17431
Document
2
10326
Other
1
200
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
9
129845
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
113490
0
SHOW DETAILS
882
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 > div#container-content > div.container-content__left
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 > div#container-content > div.container-content__left
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
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 rocks.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.
70

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of rocks.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.
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"]`
Rocks.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
div#container-content > div#container-relatedlinks > div#rb-default > iframe#master-1

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
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 — 4 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://rocks.com/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://img.sedoparking.com/templates/bg/arrows.png
Allowed
http://rocks.com/search/tsc.php?200=MjA1OTcyNDA=&21=NjcuMjA1LjEzNy4xMjc=&681=MTY3Mzc0NDk0MDdkOTAyZTRhN2E4NDA0OGFkZmI4YWJmNWNlNWE4YmJh&crc=17c663adf15a4b33eee2fd833d2c9a0a2581875e&cv=1
Allowed
90

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Page is 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.
Blocking Directive Source
SHOW DETAILS

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of rocks.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 73
Performance 97
Accessibility 63
Best Practices 92
SEO 83
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
97

Performance

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

Metrics

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

Audits

First Meaningful Paint — 1.6 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://rocks.com/
http/1.1
0
331.74100000178
8529
27009
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
342.68399997381
354.25699996995
54440
147538
200
text/javascript
Script
https://partner.googleadservices.com/gampad/cookie.js?domain=rocks.com&client=dp-sedo80_3ph&product=SAS&callback=__sasCookie
h2
386.69199997094
392.72199996049
880
358
200
text/javascript
Script
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=7097983261&channel=cl-255%2Cexp-0050%2Cauxa-control-2%2C55397&client=dp-sedo80_3ph&r=m&hl=en&terms=Squirt%2CGems%2Cgem%20stone&type=3&uiopt=true&swp=as-drid-2616522800315416&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=6631673744958564&num=0&output=afd_ads&domain_name=rocks.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1673744958566&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=463&frm=0&cl=500700135&uio=-&cont=rb-default&jsid=caf&jsv=500700135&rurl=http%3A%2F%2Frocks.com%2F&adbw=master-1%3A0
h2
397.78899995144
487.63699998381
2619
5466
200
text/html
Document
http://rocks.com/search/tsc.php?200=MjA1OTcyNDA=&21=NjcuMjA1LjEzNy4xMjc=&681=MTY3Mzc0NDk1ODJiOGE3MmMyYjFjM2FjZTJhYWVhNjkwZTMzNmRkZDkx&crc=814ac3368c920613deb53365b2a8b28577f443af&cv=1
http/1.1
400.9129999904
737.27799998596
200
0
200
text/html
XHR
https://www.google.com/adsense/domains/caf.js?pac=0
h2
500.24599995231
514.52699996298
54482
147504
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%232a56c6
h2
564.44499996724
571.6769999708
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
564.64699999196
571.04199996684
1090
200
200
image/svg+xml
Image
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=9xo936i4e0w6&aqid=PlLDY86QJo70ogab4IzoCw&psid=7097983261&pbt=bs&adbx=0&adby=68.1875&adbh=572&adbw=360&adbah=155%2C195%2C195&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=500700135&csala=7%7C0%7C108%7C33%7C57&lle=0&llm=1000&ifv=1&usr=1
h2
2094.8469999712
2114.6749999607
893
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=8kfo0ypc7qbc&aqid=PlLDY86QJo70ogab4IzoCw&psid=7097983261&pbt=bv&adbx=0&adby=68.1875&adbh=572&adbw=360&adbah=155%2C195%2C195&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=500700135&csala=7%7C0%7C108%7C33%7C57&lle=0&llm=1000&ifv=1&usr=1
h2
2595.6230000011
2610.9549999819
531
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
339.03
10.557
353.153
6.364
374.466
7.969
382.462
22.34
495.063
8.808
530.642
37.329
569.537
6.96
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. Rocks.com 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. Rocks.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rocks.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rocks.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rocks.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rocks.com 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 330 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://rocks.com/
332.73
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Rocks.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rocks.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
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 122 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js?pac=0
54482
http://www.google.com/adsense/domains/caf.js
54440
http://rocks.com/
8529
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=7097983261&channel=cl-255%2Cexp-0050%2Cauxa-control-2%2C55397&client=dp-sedo80_3ph&r=m&hl=en&terms=Squirt%2CGems%2Cgem%20stone&type=3&uiopt=true&swp=as-drid-2616522800315416&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=6631673744958564&num=0&output=afd_ads&domain_name=rocks.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1673744958566&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=463&frm=0&cl=500700135&uio=-&cont=rb-default&jsid=caf&jsv=500700135&rurl=http%3A%2F%2Frocks.com%2F&adbw=master-1%3A0
2619
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%232a56c6
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
1090
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=9xo936i4e0w6&aqid=PlLDY86QJo70ogab4IzoCw&psid=7097983261&pbt=bs&adbx=0&adby=68.1875&adbh=572&adbw=360&adbah=155%2C195%2C195&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=500700135&csala=7%7C0%7C108%7C33%7C57&lle=0&llm=1000&ifv=1&usr=1
893
https://partner.googleadservices.com/gampad/cookie.js?domain=rocks.com&client=dp-sedo80_3ph&product=SAS&callback=__sasCookie
880
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=8kfo0ypc7qbc&aqid=PlLDY86QJo70ogab4IzoCw&psid=7097983261&pbt=bv&adbx=0&adby=68.1875&adbh=572&adbw=360&adbah=155%2C195%2C195&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=500700135&csala=7%7C0%7C108%7C33%7C57&lle=0&llm=1000&ifv=1&usr=1
531
http://rocks.com/search/tsc.php?200=MjA1OTcyNDA=&21=NjcuMjA1LjEzNy4xMjc=&681=MTY3Mzc0NDk1ODJiOGE3MmMyYjFjM2FjZTJhYWVhNjkwZTMzNmRkZDkx&crc=814ac3368c920613deb53365b2a8b28577f443af&cv=1
200
Uses efficient cache policy on static assets — 2 resources found
Rocks.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://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%232a56c6
82800000
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1090
Avoids an excessive DOM size — 26 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
26
Maximum DOM Depth
Sedo Domain Parking
7
Maximum Child Elements
body.onet
9
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rocks.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.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://rocks.com/
197.24
96.74
9.944
https://www.google.com/adsense/domains/caf.js?pac=0
194.312
144.172
11.552
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=7097983261&channel=cl-255%2Cexp-0050%2Cauxa-control-2%2C55397&client=dp-sedo80_3ph&r=m&hl=en&terms=Squirt%2CGems%2Cgem%20stone&type=3&uiopt=true&swp=as-drid-2616522800315416&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=6631673744958564&num=0&output=afd_ads&domain_name=rocks.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1673744958566&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=463&frm=0&cl=500700135&uio=-&cont=rb-default&jsid=caf&jsv=500700135&rurl=http%3A%2F%2Frocks.com%2F&adbw=master-1%3A0
102.812
8.848
6.808
http://www.google.com/adsense/domains/caf.js
64.664
47.34
10.676
Unattributable
60.928
6.78
0
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
307.952
Other
148.988
Style & Layout
58.928
Parse HTML & CSS
43.492
Script Parsing & Compilation
39.44
Rendering
26.084
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 — 10 requests • 122 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
10
124852
Script
3
109802
Document
2
11148
Image
4
3702
Other
1
200
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
8
116123
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
112965
48.324
SHOW DETAILS
880
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
This webpage was generated by the domain owner using Sedo Domain Parking. Discl…
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
This webpage was generated by the domain owner using Sedo Domain Parking. Discl…
0.08897705078125
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)
https://www.google.com/adsense/domains/caf.js?pac=0
2682
149
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 rocks.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

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

Other

Reduce unused JavaScript — Potential savings of 63 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
54440
32946
https://www.google.com/adsense/domains/caf.js?pac=0
54482
31885
First Contentful Paint (3G) — 3102 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
63

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of rocks.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Rocks.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
rocks.com
This webpage was generated by the domain owner using Sedo Domain Parking. Discl…
Sedo Domain Parking
Privacy Policy

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
div#container-content > div#container-relatedlinks > div#rb-default > iframe#master-1

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
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 — 3 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://rocks.com/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://rocks.com/search/tsc.php?200=MjA1OTcyNDA=&21=NjcuMjA1LjEzNy4xMjc=&681=MTY3Mzc0NDk1ODJiOGE3MmMyYjFjM2FjZTJhYWVhNjkwZTMzNmRkZDkx&crc=814ac3368c920613deb53365b2a8b28577f443af&cv=1
Allowed
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for rocks.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 rocks.com on mobile screens.
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Page is 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.
Blocking Directive Source
SHOW DETAILS

Mobile Friendly

Document doesn't use legible font sizes — 8.89% 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
.content-disclaimer, .content-privacy-policy, .content-imprint, .content-contact-us
89.58%
9px
SHOW DETAILS
.si133
1.53%
11px
SHOW DETAILS
8.89%
≥ 12px

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of rocks.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 64.190.63.111
Continent: Europe
Country: Germany
Germany Flag
Region:
City:
Longitude: 9.491
Latitude: 51.2993
Currencies: EUR
Languages: German

Web Hosting Provider

Registration

Domain Registrant

Private Registration: Yes
Name: Contact Privacy Inc. Customer 0142777537
Organization: Contact Privacy Inc. Customer 0142777537
Country: CA
City: Toronto
State: ON
Post Code: M6K 3M1
Email: rocks.com@contactprivacy.com
Phone: +1.4165385457
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
TUCOWS, INC. 199.16.172.52
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: rocks.com
Issued By: Encryption Everywhere DV TLS CA - G1
Valid From: 11th October, 2022
Valid To: 11th October, 2023
Subject: CN = rocks.com
Hash: bc3b026b
Issuer: CN = Encryption Everywhere DV TLS CA - G1
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 7840546856216111316567972297514299779
Serial Number (Hex): 05E608CE3F2B8EF0BA46EA5DDA6A3183
Valid From: 11th October, 2024
Valid To: 11th October, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:55:74:4F:B2:72:4F:F5:60:BA:50:D1:D7:E6:51:5C:9A:01:87:1A:D7
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
CPS: http://www.digicert.com/CPS
Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/EncryptionEverywhereDVTLSCA-G1.crt
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Oct 11 14:49:24.041 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A2:C7:A5:5D:1A:77:13:57:AA:91:58:
7B:7F:58:3F:73:61:CB:C3:E1:77:E0:3A:3B:88:B4:41:
83:D1:91:BD:3F:02:21:00:B3:F4:15:89:90:1D:30:19:
3D:C3:8F:A0:3A:0A:71:1F:AF:AE:35:A2:5E:42:38:13:
D9:05:38:95:DC:11:4A:CB
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Oct 11 14:49:24.102 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:F7:6A:19:B1:3F:D0:7E:1C:D1:AB:4A:
73:2D:88:98:DE:E1:70:85:E6:A0:5E:C8:78:21:42:BA:
34:CD:10:19:88:02:20:59:C8:B5:4C:35:AF:88:95:62:
3E:AD:86:1C:8E:81:D0:64:73:FD:D8:13:0E:D4:E8:8E:
78:A4:45:7B:3A:A4:A2
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Oct 11 14:49:24.039 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:95:15:B8:4E:85:A6:7E:1D:F3:48:FA:
79:B5:CA:35:DF:ED:D7:F6:08:EF:5D:54:66:10:A6:EF:
DE:6B:34:7B:86:02:20:34:B3:F3:E3:43:BD:22:EE:27:
04:DB:EE:70:0C:4E:7A:A1:06:D0:D7:B9:4D:BF:37:2E:
46:1C:39:BA:C6:A4:C6
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:rocks.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
rocks.com. 64.190.63.111 IN 300

NS Records

Host Nameserver Class TTL
rocks.com. ns1.sedoparking.com. IN 21600
rocks.com. ns2.sedoparking.com. IN 21600

MX Records

Priority Host Server Class TTL
0 rocks.com. localhost. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
rocks.com. ns1.sedoparking.com. hostmaster.sedo.de. 21600

TXT Records

Host Value Class TTL
rocks.com. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 403 Forbidden
date: 15th January, 2023
content-type: text/html
server: NginX
content-length: 552
vary: Accept-Encoding

Whois Lookup

Created: 18th March, 1997
Changed: 18th March, 2022
Expires: 19th March, 2023
Registrar: TUCOWS, INC.
Status: clientTransferProhibited
clientUpdateProhibited
Nameservers: ns1.sedoparking.com
ns2.sedoparking.com
Owner Name: Contact Privacy Inc. Customer 0142777537
Owner Organization: Contact Privacy Inc. Customer 0142777537
Owner Street: 96 Mowat Ave
Owner Post Code: M6K 3M1
Owner City: Toronto
Owner State: ON
Owner Country: CA
Owner Phone: +1.4165385457
Owner Email: rocks.com@contactprivacy.com
Admin Name: Contact Privacy Inc. Customer 0142777537
Admin Organization: Contact Privacy Inc. Customer 0142777537
Admin Street: 96 Mowat Ave
Admin Post Code: M6K 3M1
Admin City: Toronto
Admin State: ON
Admin Country: CA
Admin Phone: +1.4165385457
Admin Email: rocks.com@contactprivacy.com
Tech Name: Contact Privacy Inc. Customer 0142777537
Tech Organization: Contact Privacy Inc. Customer 0142777537
Tech Street: 96 Mowat Ave
Tech Post Code: M6K 3M1
Tech City: Toronto
Tech State: ON
Tech Country: CA
Tech Phone: +1.4165385457
Tech Email: rocks.com@contactprivacy.com
Full Whois: Domain Name: ROCKS.COM
Registry Domain ID: 639279_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://tucowsdomains.com
Updated Date: 2022-03-18T09:32:05
Creation Date: 1997-03-18T05:00:00
Registrar Registration Expiration Date: 2023-03-19T04:00:00
Registrar: TUCOWS, INC.
Registrar IANA ID: 69
Reseller: Hover
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID:
Registrant Name: Contact Privacy Inc. Customer 0142777537
Registrant Organization: Contact Privacy Inc. Customer 0142777537
Registrant Street: 96 Mowat Ave
Registrant City: Toronto
Registrant State/Province: ON
Registrant Postal Code: M6K 3M1
Registrant Country: CA
Registrant Phone: +1.4165385457
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: rocks.com@contactprivacy.com
Registry Admin ID:
Admin Name: Contact Privacy Inc. Customer 0142777537
Admin Organization: Contact Privacy Inc. Customer 0142777537
Admin Street: 96 Mowat Ave
Admin City: Toronto
Admin State/Province: ON
Admin Postal Code: M6K 3M1
Admin Country: CA
Admin Phone: +1.4165385457
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: rocks.com@contactprivacy.com
Registry Tech ID:
Tech Name: Contact Privacy Inc. Customer 0142777537
Tech Organization: Contact Privacy Inc. Customer 0142777537
Tech Street: 96 Mowat Ave
Tech City: Toronto
Tech State/Province: ON
Tech Postal Code: M6K 3M1
Tech Country: CA
Tech Phone: +1.4165385457
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: rocks.com@contactprivacy.com
Name Server: ns1.sedoparking.com
Name Server: ns2.sedoparking.com
DNSSEC: unsigned
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
URL of the ICANN WHOIS Data Problem Reporting System: https://icann.org/wicf
>>> Last update of WHOIS database: 2023-01-15T01:08:57Z <<<

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

Registration Service Provider:
Hover, help@hover.com
+1.8667316556
https://help.hover.com


The Data in the Tucows Registrar WHOIS database is provided to you by Tucows
for information purposes only, and may be used to assist you in obtaining
information about or related to a domain name's registration record.

Tucows makes this information available "as is," and does not guarantee its
accuracy.

By submitting a WHOIS query, 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 any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited without the prior written consent of Tucows.

Tucows reserves the right to terminate your access to the Tucows WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this
policy.

Tucows reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.
View Raw Whois

Nameservers

Name IP Address
ns1.sedoparking.com 91.195.241.8
ns2.sedoparking.com 34.211.188.210
Related

Subdomains

Domain Subdomain
xossip.rocks.com
xossip

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
rocks.cafe
0/5
rocks.lol
0/5
rocks.markets
0/5
rocks.nl
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
kat.ph
$14,007 USD 3/5
mp3juices.com
$1,102 USD 2/5
serialz.to
$942 USD 1/5
tnpsc.com
$691 USD 2/5
Love W3 Snoop?
Update Now

Recently Updated

filmyfair.com
ipaagal.com
moviesraja.com
flixvid.net
zooskool.com
lifereport.net
iasbs.ac.ir
nangmak.com
playmag.ir
renevi.com

Recently Viewed

wunlive.com
susanhoakart.com
svlw.ch
floridabarexam.org
gommepoint.com
westmannreviews.com
svdpseattle.org
fisioterapiarubiera.com
fluidev.net
4walls.com