rockptx.com

rockptx.com is SSL secured

Free website and domain report on rockptx.com

Last Updated: 4th April, 2023 Update Now
Overview

Snoop Summary for rockptx.com

This is a free and comprehensive report about rockptx.com. The domain rockptx.com is currently hosted on a server located in United States with the IP address 65.60.38.10, where USD is the local currency and the local language is English. Our records indicate that rockptx.com is privately registered by Whois Privacy Protection Service, Inc.. If rockptx.com was to be sold it would possibly be worth $414 USD (based on the daily revenue potential of the website over a 24 month period). Rockptx.com receives an estimated 194 unique visitors every day - a decent amount of traffic! This report was last updated 4th April, 2023.

About rockptx.com

Site Preview: rockptx.com rockptx.com
Title: rockPTX | a resource for mineralogy and petrology
Description:
Keywords and Tags: blogs, wiki
Related Terms: mineralogy, mineralogy database
Fav Icon:
Age: Over 9 years old
Domain Created: 1st April, 2015
Domain Updated: 27th March, 2023
Domain Expires: 1st April, 2024
Review

Snoop Score

1/5

Valuation

$414 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,541,465
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 21
Moz Page Authority: 24

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 194
Monthly Visitors: 5,905
Yearly Visitors: 70,810
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $17 USD
Yearly Revenue: $202 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: rockptx.com 11
Domain Name: rockptx 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 76
Performance 85
Accessibility 74
Best Practices 85
SEO 82
Progressive Web App 52
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
85

Performance

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

Metrics

Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive rockptx.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://rockptx.com/
0
380.39200007915
420
0
301
text/html
https://rockptx.com/
380.88000006974
807.10899992846
599
0
301
text/html
https://www.rockptx.com/
807.46900010854
1274.8370000627
14156
43194
200
text/html
Document
https://www.rockptx.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4.2
1297.4870000035
1533.8900000788
7811
53593
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/css/smpl-shortcodes.css?ver=5.4.2
1297.8330000769
1530.6909999344
5930
43782
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/plugins/twenty20/assets/css/twenty20.css?ver=1.5.6
1298.133000033
1449.9429999851
1660
6753
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/skeleton-960.css?ver=2.1.1
1298.6620001029
1402.2330001462
1747
7695
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/superfish.css?ver=2.1.1
1298.9580000285
1404.4770000037
1061
1447
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/themes/smpl-skeleton/style.css?ver=5.4.2
1299.1110000294
1473.6180000473
8396
34053
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/themes/smpl-skeleton/custom.css?ver=2.1.1
1299.3499999866
1339.3810000271
630
208
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/tablepress-combined.min.css?ver=74
1299.469999969
1452.5969999377
3017
10668
200
text/css
Stylesheet
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
1299.6529999655
1444.1540001426
33517
96873
200
application/javascript
Script
https://www.rockptx.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
1299.8760000337
1447.1150001045
4486
10056
200
application/javascript
Script
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/js/smpl-shortcodes.js?ver=1
1300.0239999965
1399.6709999628
1220
1354
200
application/javascript
Script
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
1566.4699999616
1802.4659999646
315262
314654
200
image/jpeg
Image
https://www.rockptx.com/wp-content/uploads/2015/11/gyroid-260x260-150x150.jpg
1567.0350000728
1610.4530000594
9503
9078
200
image/jpeg
Image
https://ads.greengeeks.com/Green_22.png
1567.211000016
1745.7370001357
27459
26877
200
image/png
Image
https://www.rockptx.com/wp-content/plugins/twenty20/assets/js/jquery.twenty20.js?ver=1.5.6
1532.0699999575
1572.2410001326
1315
2466
200
application/javascript
Script
https://www.rockptx.com/wp-content/plugins/twenty20/assets/js/jquery.event.move.js?ver=1.5.6
1535.2700001094
1572.9050000664
2349
5421
200
application/javascript
Script
https://www.rockptx.com/wp-content/themes/smpl-skeleton/javascripts/superfish.js?ver=2.1.1
1565.6010000966
1604.4050001074
2106
4206
200
application/javascript
Script
https://www.rockptx.com/wp-content/themes/smpl-skeleton/javascripts/custom.js?ver=2.1.1
1565.7820000779
1610.9899999574
834
800
200
application/javascript
Script
https://www.rockptx.com/wp-includes/js/wp-embed.min.js?ver=5.4.2
1566.0679999273
1603.340000147
1149
1434
200
application/javascript
Script
https://www.rockptx.com/wp-includes/js/wp-emoji-release.min.js?ver=5.4.2
1567.6929999609
1615.8479999285
4758
13901
200
application/javascript
Script
https://www.rockptx.com/wp-content/themes/smpl-skeleton/images/border_top.png
1573.8079999574
1612.9550000187
512
90
200
image/png
Image
https://s.w.org/images/core/emoji/12.0.0-1/svg/1f642.svg
1666.3500000723
1683.5280000232
727
525
200
image/svg+xml
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)
1311.631
11.038
1326.963
46.027
1567.657
32.01
1599.682
18.022
1643.729
42.079
1689.167
8.645
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 48 KB
Images can slow down the page's load time. Rockptx.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
314654
49494
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rockptx.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rockptx.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rockptx.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rockptx.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 14 KB
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.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
33517
14267
Efficiently encode images — Potential savings of 57 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
314654
58542
Serve images in next-gen formats — Potential savings of 182 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
314654
165860
https://ads.greengeeks.com/Green_22.png
26877
20791
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rockptx.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.

Diagnostics

Avoids enormous network payloads — Total size was 440 KB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
315262
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
33517
https://ads.greengeeks.com/Green_22.png
27459
https://www.rockptx.com/
14156
https://www.rockptx.com/wp-content/uploads/2015/11/gyroid-260x260-150x150.jpg
9503
https://www.rockptx.com/wp-content/themes/smpl-skeleton/style.css?ver=5.4.2
8396
https://www.rockptx.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4.2
7811
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/css/smpl-shortcodes.css?ver=5.4.2
5930
https://www.rockptx.com/wp-includes/js/wp-emoji-release.min.js?ver=5.4.2
4758
https://www.rockptx.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4486
Avoids an excessive DOM size — 201 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
201
Maximum DOM Depth
11
Maximum Child Elements
19
Avoid chaining critical requests — 16 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rockptx.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.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.rockptx.com/
96.04
45.248
2.956
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
58.822
48.257
1.777
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
107.382
Other
44.164
Style & Layout
24.22
Parse HTML & CSS
18.525
Script Parsing & Compilation
8.742
Rendering
8.442
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 — 25 requests • 440 KB
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
25
450624
Image
5
353463
Script
9
51734
Stylesheet
8
30252
Document
1
14156
Other
2
1019
Media
0
0
Font
0
0
Third-party
2
28186
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)
727
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — No elements found
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.

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 — 1.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.7 s
The timing of the largest text or image that is painted.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 790 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Rockptx.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.rockptx.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4.2
7811
110
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/css/smpl-shortcodes.css?ver=5.4.2
5930
150
https://www.rockptx.com/wp-content/plugins/twenty20/assets/css/twenty20.css?ver=1.5.6
1660
150
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/skeleton-960.css?ver=2.1.1
1747
150
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/superfish.css?ver=2.1.1
1061
150
https://www.rockptx.com/wp-content/themes/smpl-skeleton/style.css?ver=5.4.2
8396
190
https://www.rockptx.com/wp-content/themes/smpl-skeleton/custom.css?ver=2.1.1
630
70
https://www.rockptx.com/wp-content/tablepress-combined.min.css?ver=74
3017
70
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
33517
150
https://www.rockptx.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4486
70
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/js/smpl-shortcodes.js?ver=1
1220
70
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Rockptx.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://rockptx.com/
0
https://rockptx.com/
190
https://www.rockptx.com/
150

Diagnostics

Serve static assets with an efficient cache policy — 21 resources found
Rockptx.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.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
3600000
315262
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
3600000
33517
https://www.rockptx.com/wp-content/uploads/2015/11/gyroid-260x260-150x150.jpg
3600000
9503
https://www.rockptx.com/wp-content/themes/smpl-skeleton/style.css?ver=5.4.2
3600000
8396
https://www.rockptx.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4.2
3600000
7811
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/css/smpl-shortcodes.css?ver=5.4.2
3600000
5930
https://www.rockptx.com/wp-includes/js/wp-emoji-release.min.js?ver=5.4.2
3600000
4758
https://www.rockptx.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
3600000
4486
https://www.rockptx.com/wp-content/tablepress-combined.min.css?ver=74
3600000
3017
https://www.rockptx.com/wp-content/plugins/twenty20/assets/js/jquery.event.move.js?ver=1.5.6
3600000
2349
https://www.rockptx.com/wp-content/themes/smpl-skeleton/javascripts/superfish.js?ver=2.1.1
3600000
2106
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/skeleton-960.css?ver=2.1.1
3600000
1747
https://www.rockptx.com/wp-content/plugins/twenty20/assets/css/twenty20.css?ver=1.5.6
3600000
1660
https://www.rockptx.com/wp-content/plugins/twenty20/assets/js/jquery.twenty20.js?ver=1.5.6
3600000
1315
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/js/smpl-shortcodes.js?ver=1
3600000
1220
https://www.rockptx.com/wp-includes/js/wp-embed.min.js?ver=5.4.2
3600000
1149
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/superfish.css?ver=2.1.1
3600000
1061
https://www.rockptx.com/wp-content/themes/smpl-skeleton/javascripts/custom.js?ver=2.1.1
3600000
834
https://www.rockptx.com/wp-content/themes/smpl-skeleton/custom.css?ver=2.1.1
3600000
630
https://www.rockptx.com/wp-content/themes/smpl-skeleton/images/border_top.png
3600000
512
https://ads.greengeeks.com/Green_22.png
604800000
27459
74

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of rockptx.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.
`[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.
`[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-*]` 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 `[alt]` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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"]`
Rockptx.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Rockptx.com may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

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

Best practices

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

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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.
Displays images with appropriate size
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
WordPress
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.

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
http://rockptx.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 4 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
4
Medium
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for rockptx.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 rockptx.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.
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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

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

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of rockptx.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 rockptx.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

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
http://rockptx.com/
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.
Web app manifest does not 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.
View Data

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) 69
Performance 61
Accessibility 74
Best Practices 77
SEO 80
Progressive Web App 54
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
61

Performance

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

Metrics

Total Blocking Time — 50 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

Other

First CPU Idle — 3.6 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive rockptx.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://rockptx.com/
0
315.71300001815
394
0
301
text/html
https://rockptx.com/
316.02999998722
657.05599996727
398
0
301
text/html
https://www.rockptx.com/
657.38999994937
1043.8819999108
13984
43191
200
text/html
Document
https://www.rockptx.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4.2
1058.9919999475
1099.264999968
7630
53593
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/css/smpl-shortcodes.css?ver=5.4.2
1059.2519999482
1098.6509999493
5749
43782
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/plugins/twenty20/assets/css/twenty20.css?ver=1.5.6
1059.4669999555
1108.5689999163
1479
6753
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/skeleton-960.css?ver=2.1.1
1059.8039999604
1170.6019999692
1747
7695
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/superfish.css?ver=2.1.1
1060.3999999585
1165.7339999219
1061
1447
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/themes/smpl-skeleton/style.css?ver=5.4.2
1060.6820000103
1166.1339999409
8396
34053
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/themes/smpl-skeleton/custom.css?ver=2.1.1
1061.0040000174
1169.603999937
811
208
200
text/css
Stylesheet
https://www.rockptx.com/wp-content/tablepress-combined.min.css?ver=74
1061.2749999855
1159.9500000011
3198
10668
200
text/css
Stylesheet
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
1061.478999909
1199.0389999701
33517
96873
200
application/javascript
Script
https://www.rockptx.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
1061.6499999305
1170.158999972
4486
10056
200
application/javascript
Script
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/js/smpl-shortcodes.js?ver=1
1061.8319999194
1166.5289999219
1220
1354
200
application/javascript
Script
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
1231.1539999209
1461.7119999602
315262
314654
200
image/jpeg
Image
https://www.rockptx.com/wp-content/uploads/2015/11/gyroid-260x260-150x150.jpg
1231.472000014
1276.0239999043
9503
9078
200
image/jpeg
Image
https://ads.greengeeks.com/Green_22.png
1231.599999941
1467.3479999183
27459
26877
200
image/png
Image
https://www.rockptx.com/wp-content/plugins/twenty20/assets/js/jquery.twenty20.js?ver=1.5.6
1171.7959999805
1209.6259999089
1315
2466
200
application/javascript
Script
https://www.rockptx.com/wp-content/plugins/twenty20/assets/js/jquery.event.move.js?ver=1.5.6
1206.2029999215
1245.2649999177
2349
5421
200
application/javascript
Script
https://www.rockptx.com/wp-content/themes/smpl-skeleton/javascripts/superfish.js?ver=2.1.1
1230.6760000065
1268.9339999342
2106
4206
200
application/javascript
Script
https://www.rockptx.com/wp-content/themes/smpl-skeleton/javascripts/custom.js?ver=2.1.1
1230.8349999366
1269.4449999835
834
800
200
application/javascript
Script
https://www.rockptx.com/wp-includes/js/wp-embed.min.js?ver=5.4.2
1230.9670000104
1270.1419999357
1149
1434
200
application/javascript
Script
https://www.rockptx.com/wp-includes/js/wp-emoji-release.min.js?ver=5.4.2
1231.7489999114
1267.715999973
4758
13901
200
application/javascript
Script
https://www.rockptx.com/wp-content/themes/smpl-skeleton/images/border_top.png
1237.1109999949
1272.1540000057
512
90
200
image/png
Image
https://s.w.org/images/core/emoji/12.0.0-1/svg/1f642.svg
1279.4439999852
1295.8439999493
727
525
200
image/svg+xml
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)
1074.598
8.84
1086.113
47.753
1234.282
27.333
1261.629
14.14
1302.499
41.231
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Rockptx.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rockptx.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rockptx.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rockptx.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rockptx.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
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 390 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rockptx.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.

Diagnostics

Avoids enormous network payloads — Total size was 439 KB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
315262
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
33517
https://ads.greengeeks.com/Green_22.png
27459
https://www.rockptx.com/
13984
https://www.rockptx.com/wp-content/uploads/2015/11/gyroid-260x260-150x150.jpg
9503
https://www.rockptx.com/wp-content/themes/smpl-skeleton/style.css?ver=5.4.2
8396
https://www.rockptx.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4.2
7630
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/css/smpl-shortcodes.css?ver=5.4.2
5749
https://www.rockptx.com/wp-includes/js/wp-emoji-release.min.js?ver=5.4.2
4758
https://www.rockptx.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4486
Avoids an excessive DOM size — 201 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
201
Maximum DOM Depth
11
Maximum Child Elements
19
Avoid chaining critical requests — 16 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rockptx.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.4 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://www.rockptx.com/
373.64
204.756
9.484
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
205.964
173.732
7.164
Unattributable
90.84
3.352
0.596
Minimizes main-thread work — 0.8 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
405.388
Other
153.684
Style & Layout
72.672
Parse HTML & CSS
65.952
Script Parsing & Compilation
31.748
Rendering
31.5
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 — 25 requests • 439 KB
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
25
450044
Image
5
353463
Script
9
51734
Stylesheet
8
30071
Document
1
13984
Other
2
792
Media
0
0
Font
0
0
Third-party
2
28186
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)
727
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — No elements found
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.

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 — 3.6 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 5.6 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 5.4 s
The time taken for the page to become fully interactive.

Other

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

Opportunities

Remove unused JavaScript — Potential savings of 14 KB
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.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
33517
14267
Efficiently encode images — Potential savings of 57 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
314654
58542
Serve images in next-gen formats — Potential savings of 182 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
314654
165860
https://ads.greengeeks.com/Green_22.png
26877
20791

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 2,020 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Rockptx.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.rockptx.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4.2
7630
330
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/css/smpl-shortcodes.css?ver=5.4.2
5749
630
https://www.rockptx.com/wp-content/plugins/twenty20/assets/css/twenty20.css?ver=1.5.6
1479
480
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/skeleton-960.css?ver=2.1.1
1747
480
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/superfish.css?ver=2.1.1
1061
480
https://www.rockptx.com/wp-content/themes/smpl-skeleton/style.css?ver=5.4.2
8396
630
https://www.rockptx.com/wp-content/themes/smpl-skeleton/custom.css?ver=2.1.1
811
180
https://www.rockptx.com/wp-content/tablepress-combined.min.css?ver=74
3198
180
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
33517
630
https://www.rockptx.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4486
330
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/js/smpl-shortcodes.js?ver=1
1220
180
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Rockptx.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://rockptx.com/
0
https://rockptx.com/
630
https://www.rockptx.com/
480

Diagnostics

Serve static assets with an efficient cache policy — 21 resources found
Rockptx.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.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
3600000
315262
https://www.rockptx.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
3600000
33517
https://www.rockptx.com/wp-content/uploads/2015/11/gyroid-260x260-150x150.jpg
3600000
9503
https://www.rockptx.com/wp-content/themes/smpl-skeleton/style.css?ver=5.4.2
3600000
8396
https://www.rockptx.com/wp-includes/css/dist/block-library/style.min.css?ver=5.4.2
3600000
7630
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/css/smpl-shortcodes.css?ver=5.4.2
3600000
5749
https://www.rockptx.com/wp-includes/js/wp-emoji-release.min.js?ver=5.4.2
3600000
4758
https://www.rockptx.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
3600000
4486
https://www.rockptx.com/wp-content/tablepress-combined.min.css?ver=74
3600000
3198
https://www.rockptx.com/wp-content/plugins/twenty20/assets/js/jquery.event.move.js?ver=1.5.6
3600000
2349
https://www.rockptx.com/wp-content/themes/smpl-skeleton/javascripts/superfish.js?ver=2.1.1
3600000
2106
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/skeleton-960.css?ver=2.1.1
3600000
1747
https://www.rockptx.com/wp-content/plugins/twenty20/assets/css/twenty20.css?ver=1.5.6
3600000
1479
https://www.rockptx.com/wp-content/plugins/twenty20/assets/js/jquery.twenty20.js?ver=1.5.6
3600000
1315
https://www.rockptx.com/wp-content/plugins/smpl-shortcodes/assets/js/smpl-shortcodes.js?ver=1
3600000
1220
https://www.rockptx.com/wp-includes/js/wp-embed.min.js?ver=5.4.2
3600000
1149
https://www.rockptx.com/wp-content/themes/smpl-skeleton/css/superfish.css?ver=2.1.1
3600000
1061
https://www.rockptx.com/wp-content/themes/smpl-skeleton/javascripts/custom.js?ver=2.1.1
3600000
834
https://www.rockptx.com/wp-content/themes/smpl-skeleton/custom.css?ver=2.1.1
3600000
811
https://www.rockptx.com/wp-content/themes/smpl-skeleton/images/border_top.png
3600000
512
https://ads.greengeeks.com/Green_22.png
604800000
27459

Other

First Contentful Paint (3G) — 6994 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
74

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of rockptx.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.
`[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.
`[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-*]` 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 `[alt]` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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"]`
Rockptx.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Rockptx.com may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

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

Best practices

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

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
WordPress
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.

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
http://rockptx.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 4 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
4
Medium

Audits

Displays images with inappropriate size
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.rockptx.com/wp-content/uploads/2015/04/yoderite-1024-150-default-quality.jpg
300 x 200
360 x 240
788 x 525
https://www.rockptx.com/wp-content/uploads/2015/11/gyroid-260x260-150x150.jpg
26 x 26
26 x 26
69 x 69
80

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for rockptx.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 rockptx.com on mobile screens.
Document uses legible font sizes — 93.99% 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
#footer #credits
4.23%
11px
.themeauthor, .themeauthor a:link, .themeauthor a:hover, .themeauthor a:visited
1.77%
11px
93.99%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Mobile Friendly

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

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

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of rockptx.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 rockptx.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

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
http://rockptx.com/
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.
Web app manifest does not 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.
View Data

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: 65.60.38.10
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
SingleHop LLC
Registration

Domain Registrant

Private Registration: Yes
Name: Whois Agent (951615973)
Organization: Whois Privacy Protection Service, Inc.
Country: US
City: Kirkland
State: WA
Post Code: 98083
Email: jkwvwbrtfy@whoisprivacyprotect.com
Phone: +1.4252740657
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

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: *.rockptx.com
Issued By: R3
Valid From: 27th March, 2023
Valid To: 25th June, 2023
Subject: CN = *.rockptx.com
Hash: 7bd2be62
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x0388B128B73AC755BAC18DDBE8B1E6FE5AA4
Serial Number (Hex): 0388B128B73AC755BAC18DDBE8B1E6FE5AA4
Valid From: 27th March, 2024
Valid To: 25th June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Mar 27 12:17:58.364 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C7:2A:9D:5F:98:DB:12:AD:54:38:11:
62:A4:BF:54:93:5E:18:34:A2:08:4B:F1:C6:31:B6:94:
7E:0C:CA:E3:BD:02:20:33:6E:C3:6C:27:F1:AF:20:37:
CC:3D:E9:63:A3:E8:7E:A3:02:01:EC:63:BD:65:FB:89:
3B:4C:FE:A0:01:B0:17
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Mar 27 12:17:58.351 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:60:BC:1D:54:A7:70:3C:59:AC:DC:ED:21:
1A:08:4C:17:A4:25:19:FA:23:1E:A5:1F:EC:84:3C:B6:
8B:12:10:0E:02:20:7C:13:34:85:32:55:FD:66:CD:77:
F4:3A:66:A9:2D:0E:8D:81:2C:81:67:19:0A:9B:74:54:
56:A3:17:66:5E:E3
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:rockptx.com
DNS:*.rockptx.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
rockptx.com. 65.60.38.10 IN 14400

NS Records

Host Nameserver Class TTL
rockptx.com. ams-ns1.websitehostserver.net. IN 21600
rockptx.com. chi-ns2.websitehostserver.net. IN 21600
rockptx.com. chi-ns1.websitehostserver.net. IN 21600

MX Records

Priority Host Server Class TTL
0 rockptx.com. rockptx.com. IN 14400

SOA Records

Domain Name Primary NS Responsible Email TTL
rockptx.com. chi-ns1.websitehostserver.net. root.chi102.greengeeks.net. 21600

TXT Records

Host Value Class TTL
rockptx.com. v=spf1 IN 14400

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
date: 4th April, 2023
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
location: https://rockptx.com/
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff

Whois Lookup

Created: 1st April, 2015
Changed: 27th March, 2023
Expires: 1st April, 2024
Registrar: ENOM, INC.
Status: clientTransferProhibited
Nameservers: ams-ns1.greengeeks.com
chi-ns1.greengeeks.com
chi-ns2.greengeeks.com
Owner Name: Whois Agent (951615973)
Owner Organization: Whois Privacy Protection Service, Inc.
Owner Street: PO Box 639
C/O rockptx.com
Owner Post Code: 98083
Owner City: Kirkland
Owner State: WA
Owner Country: US
Owner Phone: +1.4252740657
Owner Email: mmqvxcyq@whoisprivacyprotect.com
Admin Name: Whois Agent
Admin Organization: Whois Privacy Protection Service, Inc.
Admin Street: PO Box 639
C/O rockptx.com
Admin Post Code: 98083
Admin City: Kirkland
Admin State: WA
Admin Country: US
Admin Phone: +1.4252740657
Admin Email: mmqvxcyq@whoisprivacyprotect.com
Tech Name: Whois Agent
Tech Organization: Whois Privacy Protection Service, Inc.
Tech Street: PO Box 639
C/O rockptx.com
Tech Post Code: 98083
Tech City: Kirkland
Tech State: WA
Tech Country: US
Tech Phone: +1.4252740657
Tech Email: mmqvxcyq@whoisprivacyprotect.com
Full Whois:

Domain Name: rockptx.com
Registry Domain ID: 1915559216_DOMAIN_COM-VRSN
Registrar WHOIS Server: WHOIS.ENOM.COM
Registrar URL: WWW.ENOM.COM
Updated Date: 2023-03-27T09:06:54.00Z
Creation Date: 2015-04-01T08:16:00.00Z
Registrar Registration Expiration Date: 2024-04-01T08:16:11.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registrant Name: Whois Agent (951615973)
Registrant Organization: Whois Privacy Protection Service, Inc.
Registrant Street: PO Box 639
Registrant Street: C/O rockptx.com
Registrant City: Kirkland
Registrant State/Province: WA
Registrant Postal Code: 98083
Registrant Country: US
Registrant Phone: +1.4252740657
Registrant Phone Ext:
Registrant Fax: +1.4259744730
Registrant Email: mmqvxcyq@whoisprivacyprotect.com
Admin Name: Whois Agent
Admin Organization: Whois Privacy Protection Service, Inc.
Admin Street: PO Box 639
Admin Street: C/O rockptx.com
Admin City: Kirkland
Admin State/Province: WA
Admin Postal Code: 98083
Admin Country: US
Admin Phone: +1.4252740657
Admin Phone Ext:
Admin Fax: +1.4259744730
Admin Email: mmqvxcyq@whoisprivacyprotect.com
Tech Name: Whois Agent
Tech Organization: Whois Privacy Protection Service, Inc.
Tech Street: PO Box 639
Tech Street: C/O rockptx.com
Tech City: Kirkland
Tech State/Province: WA
Tech Postal Code: 98083
Tech Country: US
Tech Phone: +1.4252740657
Tech Phone Ext:
Tech Fax: +1.4259744730
Tech Email: mmqvxcyq@whoisprivacyprotect.com
Name Server: AMS-NS1.GREENGEEKS.COM
Name Server: CHI-NS1.GREENGEEKS.COM
Name Server: CHI-NS2.GREENGEEKS.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: ABUSE@ENOM.COM
Registrar Abuse Contact Phone: +1.4259744689
URL of the ICANN WHOIS Data Problem Reporting System: HTTPS://ICANN.ORG/WICF
>>> Last update of WHOIS database: 2023-04-04T08:59:22.00Z <<<

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


The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do 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: (1)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us.

We reserve the right to modify these terms at any time. By submitting
this query, you agree to abide by these terms.
Version 6.3 4/3/2002

Nameservers

Name IP Address
ams-ns1.greengeeks.com 107.6.141.186
chi-ns1.greengeeks.com 75.2.69.7
chi-ns2.greengeeks.com 99.83.188.187
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5
0/5