ws.org

ws.org is SSL secured

Free website and domain report on ws.org

Last Updated: 21st November, 2022 Update Now
Overview

Snoop Summary for ws.org

This is a free and comprehensive report about ws.org. Ws.org is hosted in British Virgin Islands on a server with an IP address of 208.91.197.39, where USD is the local currency and the local language is English. Ws.org has the potential to be earning an estimated $1 USD per day from advertising revenue. If ws.org was to be sold it would possibly be worth $1,063 USD (based on the daily revenue potential of the website over a 24 month period). Ws.org is somewhat popular with an estimated 506 daily unique visitors. This report was last updated 21st November, 2022.

About ws.org

Site Preview: ws.org ws.org
Title:
Description:
Keywords and Tags: parked domain, pups
Related Terms:
Fav Icon:
Age: Over 26 years old
Domain Created: 2nd November, 1997
Domain Updated: 18th September, 2022
Domain Expires: 2nd December, 2025
Review

Snoop Score

1/5

Valuation

$1,063 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,067,043
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: 506
Monthly Visitors: 15,402
Yearly Visitors: 184,696
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $44 USD
Yearly Revenue: $526 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: ws.org 6
Domain Name: ws 2
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 62
Performance 89
Accessibility 45
Best Practices 83
SEO 73
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
89

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.5 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

First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ws.org/
http/1.1
0
326.2959998101
7885
23807
200
text/html
Document
http://ws.org/px.js?ch=1
http/1.1
332.79999997467
468.11199979857
1085
346
200
application/javascript
Script
http://ws.org/px.js?ch=2
http/1.1
333.79299985245
466.62999968976
1084
346
200
application/javascript
Script
http://i1.cdn-image.com/__media__/js/min.js?v2.3
http/1.1
333.99299997836
371.80799990892
3421
8435
200
application/javascript
Script
http://i1.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
http/1.1
468.93499977887
532.05299982801
3401
3071
200
image/jpeg
Image
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
http/1.1
478.53800002486
672.7640000172
407
0
301
text/html
http://i1.cdn-image.com/__media__/pics/8934/frt_arr.jpg
http/1.1
483.6959997192
566.19299994782
20696
20383
200
image/jpeg
Image
http://i1.cdn-image.com/__media__/pics/8934/lst_arr.jpg
http/1.1
483.8930000551
533.27600006014
20763
20431
200
image/jpeg
Image
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
http/1.1
673.10300003737
898.78199994564
33603
101291
200
text/javascript
Script
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
http/1.1
991.76199967042
1591.05299972
4128
11922
200
text/html
Document
https://dts.gnpge.com/ptmdP
1544.7169998661
1557.449999731
0
0
-1
Ping
https://dts.gnpge.com/cenw.js?identifier=bafp
h2
1556.4069999382
1564.5729997195
502
36
200
text/html
XHR
https://dts6.gnpge.com/ptmdDual?t=%7B%22gh%22%3A%221668999727056102830201270%22%2C%22za%22%3A1%2C%22gcd%22%3A1668999727635%2C%22al%22%3A10%2C%22bcnd%22%3A1%7D
h2
1557.0379998535
1566.1339997314
441
70
200
image/gif
Image
https://dts.gnpge.com/cenw.js
h2
1628.3709998243
1632.5819999911
502
36
200
text/html
XHR
https://dts.gnpge.com/ptmd?t=1668999727056102830201270_N4IgtgniBcDasEYA0AWAHMtA2AnEgTAAwCsBKCAukrPqhktnvuQQOytWwDMdmubrJFwRdOKXg37CeXFDk6l0fPLJVpinLBMZD1qfJWqClkvCgOpiHamm38UV1DlFUQAdwCOMWK8gAnb1cAOwBDb3McOSxWfCxxERRCNFZCLjxiLkIk9EzgkIBnGHw8EABLELBvQldywuhbEAAPADMYEABTAGMAE3R2hHw0bs6rEJDWHHbMlBHOtM7OtDRCHBAkEABrMOgO-FYQnCxOwgBaXHQThAR27pPxxZOVkOFWNMJWZs61zYAjGGQQJ0AG5tYAAHRAABsAPadEKQgD6+QALtC-CEAObtCHQCHtPYHI6nc5oS7XW73UlPF5vD6dCFICH5dr5fKlaFBJGo9FYnF4gmHY5nSKkq43O6sB7UhCvHDvT4MiGdaHQjaldoI7ohZEhPm7faC4kisniymPHDPGW0hUgAC+3wxyNacEISFdyFdKFcjrqsFd7rdbtcKN9-sDHtcXWRlR2+GI+G+7UabUI33yyraCCwWDQODzMSwCPUKVzKFkxCwaeVzoB6ehyMz2dz+diRasSUi5cLPwQhE67UinWaxRwPeiP1YKBC5xQ7UIIS6OF6VfrNfWdeR3UbObzOALbZLnYchclaGaPzPzW6N2IDkmrB+Mysyxw+Ha5+6zhXm7XHS2bXxNAZmaZojQuMUKR+fB8DOZoQgcR9R3aHNEw2P5oABYE6hAcEoVheEuTRTFsRgfkgKHUDhXA8k7igmCsDghC5B+ZC0EVEBmVZdlORRIjeVI3ZyJAsDRRokI6Ng+DiEQlic3Y5VVXVTVtV1ATAOAyiSRNSDoMkpikLku1vlKEFoEIAA6UgOJ1ZEAFdfWQYohFdJgeAQeR1gAL22AEAAcMTaEF1gxAALbdmz3PYSCwXtBkyIgBhSb4gWwrBzIs4gEGIb54X+V0QE+GBLnWdpkVKcLdwLNNkQCsz1w2CqW0LYsOzLY9E1KXy2micyiGIcyRFYAa9mS9oAh2Xy-GhLcStsnz1ls8q6o6IFIUCdZfJS9aOMhFFGsilIBm+SFf06ezkQRUotx2YgAGEAFUACFWAASQAUTQABFZLSku66QAGOIs1vDJYi4fBZFYXsHS+DCm0qwYEBQcQQA8dp-nWZolvwW0gA
h2
2069.0649999306
2078.6560000852
497
70
200
image/gif
Image
https://dts.gnpge.com/ptmd?t=1668999727056102830201270_N4IgZghiBcDaDMB2AHPATI+A2ZAGANAIy4AsyArMjvgbTfcZoiYcmifevudsorgE429cuzTJk+NDhLxyJcliJLcAXXzgIAZxhKQAC30xY5RN2TrwYGIQ0BXOzHiFb4AG4wQIDQEsP0NA0tABcIYLsdODRyIgFLAC8oaFcABwBzTw8NNKNoEEIsHAFixAxcRWJxeFw0XEIy7xA3SJAsADpcNvJCckaIABsbAnAAYxgAWlcAU2CfTwKikulGkIzoYa0Aa3nC5GKBUqwAfQp+PdkFLEapnxTPLEQ22vI2wiRXjEa3KYAnTxSfgB7AAm1zsSVcdjm6w0UzcgzglhSzWMIFwAAJnuR0YQQJYtP0QjtFgcyvVGv1rMkNCMIsEjj5QXlyABhACqACFEABJACiyAAil8fAymflpCwsPIeNJ0PASIhiI00mNkrt9qUBFgSIEQABHKY2DRgaHwAC+QA
h2
3547.2140000202
3552.1760000847
497
70
200
image/gif
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)
330.367
8.749
471.748
10.801
482.561
11.87
910.196
643.607
1559.028
5.553
1564.596
23.986
1597.024
6.412
1607.084
9.18
1618.938
5.405
1624.356
5.553
1629.966
6.714
1645.931
9.975
1657.281
6.869
1666.427
7.735
1675.574
6.58
1682.955
5.142
1692.3
5.51
1702.307
5.623
1712.3
5.291
1742.293
5.087
1752.321
7.332
1762.301
6.639
1772.319
6.843
1782.32
5.45
1798.483
5.127
1804.414
6.388
1815.829
5.768
1822.964
7.123
1841.299
9.16
1852.369
6.67
1862.297
6.807
1872.31
5.91
1882.31
6.043
1898.983
5.846
1904.839
6.326
1912.305
5.115
1922.319
5.422
1932.306
6.882
1942.297
5.067
1952.331
6.613
1962.296
9.063
1972.301
9.918
1982.895
5.921
1992.496
6.591
2002.383
6.816
2012.298
6.304
2022.312
5.518
2032.312
6.715
2042.308
5.38
2048.242
19.857
2068.147
7.229
2075.985
6.913
2084.346
6.333
2092.278
6.821
2102.316
10.007
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Ws.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ws.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ws.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ws.org should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ws.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images — Potential savings of 10 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://i1.cdn-image.com/__media__/pics/8934/lst_arr.jpg
20431
5396
http://i1.cdn-image.com/__media__/pics/8934/frt_arr.jpg
20383
5351
Serve images in next-gen formats — Potential savings of 27 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://i1.cdn-image.com/__media__/pics/8934/lst_arr.jpg
20431
14096.25
http://i1.cdn-image.com/__media__/pics/8934/frt_arr.jpg
20383
14013.8
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://ws.org/
327.289
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Ws.org should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ws.org 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://i1.cdn-image.com/__media__/pics/8934/frt_arr.jpg
0
Avoids enormous network payloads — Total size was 97 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
33603
http://i1.cdn-image.com/__media__/pics/8934/lst_arr.jpg
20763
http://i1.cdn-image.com/__media__/pics/8934/frt_arr.jpg
20696
http://ws.org/
7885
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
4128
http://i1.cdn-image.com/__media__/js/min.js?v2.3
3421
http://i1.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
3401
http://ws.org/px.js?ch=1
1085
http://ws.org/px.js?ch=2
1084
https://dts.gnpge.com/cenw.js
502
Avoids an excessive DOM size — 64 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
64
Maximum DOM Depth
9
Maximum Child Elements
10
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ws.org 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.8 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://ws.org/
1074.064
761.791
2.303
Minimizes main-thread work — 1.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
796.582
Style & Layout
241.448
Other
53.834
Parse HTML & CSS
33.032
Rendering
21.824
Script Parsing & Compilation
10.77
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 — 16 requests • 97 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
16
98912
Image
6
46295
Script
4
39193
Document
2
12013
Other
4
1411
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
13
88858
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)
38138
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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)
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
581
322
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ws.org on mobile screens.

Budgets

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

Metrics

Total Blocking Time — 270 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Eliminate render-blocking resources — Potential savings of 190 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ws.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://ws.org/px.js?ch=1
1085
70
http://ws.org/px.js?ch=2
1084
110
http://i1.cdn-image.com/__media__/js/min.js?v2.3
3421
190
Serve static assets with an efficient cache policy — 10 resources found
Ws.org 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)
http://ws.org/px.js?ch=1
0
1085
http://ws.org/px.js?ch=2
0
1084
https://dts.gnpge.com/ptmd?t=1668999727056102830201270_N4IgtgniBcDasEYA0AWAHMtA2AnEgTAAwCsBKCAukrPqhktnvuQQOytWwDMdmubrJFwRdOKXg37CeXFDk6l0fPLJVpinLBMZD1qfJWqClkvCgOpiHamm38UV1DlFUQAdwCOMWK8gAnb1cAOwBDb3McOSxWfCxxERRCNFZCLjxiLkIk9EzgkIBnGHw8EABLELBvQldywuhbEAAPADMYEABTAGMAE3R2hHw0bs6rEJDWHHbMlBHOtM7OtDRCHBAkEABrMOgO-FYQnCxOwgBaXHQThAR27pPxxZOVkOFWNMJWZs61zYAjGGQQJ0AG5tYAAHRAABsAPadEKQgD6+QALtC-CEAObtCHQCHtPYHI6nc5oS7XW73UlPF5vD6dCFICH5dr5fKlaFBJGo9FYnF4gmHY5nSKkq43O6sB7UhCvHDvT4MiGdaHQjaldoI7ohZEhPm7faC4kisniymPHDPGW0hUgAC+3wxyNacEISFdyFdKFcjrqsFd7rdbtcKN9-sDHtcXWRlR2+GI+G+7UabUI33yyraCCwWDQODzMSwCPUKVzKFkxCwaeVzoB6ehyMz2dz+diRasSUi5cLPwQhE67UinWaxRwPeiP1YKBC5xQ7UIIS6OF6VfrNfWdeR3UbObzOALbZLnYchclaGaPzPzW6N2IDkmrB+Mysyxw+Ha5+6zhXm7XHS2bXxNAZmaZojQuMUKR+fB8DOZoQgcR9R3aHNEw2P5oABYE6hAcEoVheEuTRTFsRgfkgKHUDhXA8k7igmCsDghC5B+ZC0EVEBmVZdlORRIjeVI3ZyJAsDRRokI6Ng+DiEQlic3Y5VVXVTVtV1ATAOAyiSRNSDoMkpikLku1vlKEFoEIAA6UgOJ1ZEAFdfWQYohFdJgeAQeR1gAL22AEAAcMTaEF1gxAALbdmz3PYSCwXtBkyIgBhSb4gWwrBzIs4gEGIb54X+V0QE+GBLnWdpkVKcLdwLNNkQCsz1w2CqW0LYsOzLY9E1KXy2micyiGIcyRFYAa9mS9oAh2Xy-GhLcStsnz1ls8q6o6IFIUCdZfJS9aOMhFFGsilIBm+SFf06ezkQRUotx2YgAGEAFUACFWAASQAUTQABFZLSku66QAGOIs1vDJYi4fBZFYXsHS+DCm0qwYEBQcQQA8dp-nWZolvwW0gA
0
497
https://dts.gnpge.com/ptmd?t=1668999727056102830201270_N4IgZghiBcDaDMB2AHPATI+A2ZAGANAIy4AsyArMjvgbTfcZoiYcmifevudsorgE429cuzTJk+NDhLxyJcliJLcAXXzgIAZxhKQAC30xY5RN2TrwYGIQ0BXOzHiFb4AG4wQIDQEsP0NA0tABcIYLsdODRyIgFLAC8oaFcABwBzTw8NNKNoEEIsHAFixAxcRWJxeFw0XEIy7xA3SJAsADpcNvJCckaIABsbAnAAYxgAWlcAU2CfTwKikulGkIzoYa0Aa3nC5GKBUqwAfQp+PdkFLEapnxTPLEQ22vI2wiRXjEa3KYAnTxSfgB7AAm1zsSVcdjm6w0UzcgzglhSzWMIFwAAJnuR0YQQJYtP0QjtFgcyvVGv1rMkNCMIsEjj5QXlyABhACqACFEABJACiyAAil8fAymflpCwsPIeNJ0PASIhiI00mNkrt9qUBFgSIEQABHKY2DRgaHwAC+QA
0
497
https://dts6.gnpge.com/ptmdDual?t=%7B%22gh%22%3A%221668999727056102830201270%22%2C%22za%22%3A1%2C%22gcd%22%3A1668999727635%2C%22al%22%3A10%2C%22bcnd%22%3A1%7D
0
441
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
300000
33603
http://i1.cdn-image.com/__media__/js/min.js?v2.3
50115000
3421
http://i1.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
69155000
3401
http://i1.cdn-image.com/__media__/pics/8934/lst_arr.jpg
69586000
20763
http://i1.cdn-image.com/__media__/pics/8934/frt_arr.jpg
84435000
20696

Audits

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

Other

Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
http://i1.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
45

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ws.org. 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.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ws.org 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

Navigation

Heading elements are not 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.
Failing Elements

Internationalization and localization

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

Names and labels

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ws.org 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

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 — 8 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://ws.org/
Allowed
http://ws.org/px.js?ch=1
Allowed
http://ws.org/px.js?ch=2
Allowed
http://i1.cdn-image.com/__media__/js/min.js?v2.3
Allowed
http://i1.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
Allowed
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
Allowed
http://i1.cdn-image.com/__media__/pics/8934/frt_arr.jpg
Allowed
http://i1.cdn-image.com/__media__/pics/8934/lst_arr.jpg
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
73

SEO

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

Crawling and Indexing

Links are not 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.

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 ws.org. 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 ws.org 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) 66
Performance 96
Accessibility 48
Best Practices 83
SEO 75
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://ws.org
Updated: 21st November, 2022
Simulate loading on mobile
96

Performance

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

Metrics

First Contentful Paint — 1.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.1 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.
Largest Contentful Paint — 1.3 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.029
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 1.3 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://ws.org/
http/1.1
0
308.53800009936
6589
16342
200
text/html
Document
http://ws.org/px.js?ch=1
http/1.1
318.5480000684
451.91400009207
1084
346
200
application/javascript
Script
http://ws.org/px.js?ch=2
http/1.1
318.85700009298
402.17900008429
1085
346
200
application/javascript
Script
http://i3.cdn-image.com/__media__/js/min.js?v2.3
http/1.1
319.10100008827
488.6510000797
3421
8435
200
application/javascript
Script
http://i3.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
http/1.1
453.56600009836
514.12600011099
3401
3071
200
image/jpeg
Image
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
http/1.1
493.78200003412
739.71700004768
392
0
301
text/html
http://i3.cdn-image.com/__media__/pics/8934/arrow.png
http/1.1
499.36800007708
557.0070000831
1624
1314
200
image/png
Image
http://i3.cdn-image.com/__media__/pics/8934/searchIconN.gif
http/1.1
499.60300000384
648.89300009236
1711
1401
200
image/gif
Image
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
http/1.1
740.02600007225
977.40600001998
33606
101295
200
text/javascript
Script
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
http/1.1
1014.2080000369
1438.5089999996
4128
11922
200
text/html
Document
https://dts.gnpge.com/ptmdP
1079.9050000496
1090.0370000163
0
0
-1
Ping
https://dts.gnpge.com/cenw.js?identifier=bafp
h2
1086.4380000858
1092.684000032
502
36
200
text/html
XHR
https://dts6.gnpge.com/ptmdDual?t=%7B%22gh%22%3A%22166899974452710937323280%22%2C%22za%22%3A1%2C%22gcd%22%3A1668999744597%2C%22al%22%3A10%2C%22bcnd%22%3A1%7D
h2
1087.4340001028
1097.6120000705
441
70
200
image/gif
Image
https://dts.gnpge.com/cenw.js
h2
1482.1160000283
1486.5490000229
502
36
200
text/html
XHR
https://dts.gnpge.com/ptmd?t=166899974452710937323280_N4IgtgniBcDasEYA0BOJBmArMhAmTSuCCAukrLqhtobuoQBwAMZs9aWyuKl6ALClZ8qnDADZkfBA1YEONPuiZI+DAOwkyIAO4BHGLC2QATga0A7AIYG+3AWLW4xwhPybqm6NJiXvVSi0sAZxhuJBAAS0swA1w+FnCokOgGcIAPADMYEABTAGMAE1UcvAYCvMw1S0s1FBylPgq8rzy8hmYUEHCAa2toXLyUMSZMFCYAWjEUVXHiHILxgCNLMUtx7CdFhEt0Qpy+LpBuxZhkEDyAN2zgAB0QABsAezzLe4B9IIAXR+NLAHMcndoHd8kMRmNJtMGLMEPMlis1hsxFsdns+HckHcgjkgkEIo9zB9vr8AUCQYNhqMJlMZnMFstVus8MjtrsCvsMXc8o9Ht0Ijk3gVLJ9LGSBmCqZDabD6QimZtWWi7gBfQ5-T5ZODIZQ6whadXJWC641aL6G41IbVafKfGL9JzoQ4RK7QJgAOgIIC+woAroauBxlGgEIJwgAvPpnAAOf2yV3CfwAFtkEGIxAwUJm1Hw+JhcGoEEwUOg1Og6LhmIcLskQGI3e7sJhDq9TsoQBk8jBZuEcp8Iim0xmsznDl9Y67wkFugP05mUNm+G8EFIC3wC7UmAhDjkIlHsg43bgRm7XGoT-mqzlTP0o8ZHgVtz7I+Eff2J7kLvczOEo9Xv177i+Gch3nHNsDUQ57k1M48j9T43giB9+kwABhABVAAhNQAEkAFEGAARSrCIEKQkBSikMRMFzfgS1sAQvDVTtoFTWdh2wBBPV0HJTnCDI31wZUgA
h2
1590.1630000444
1598.7390000373
497
70
200
image/gif
Image
https://dts.gnpge.com/ptmd?t=166899974452710937323280_N4IgZghiBcDaDMB2AHPATI+A2ZAGANAIy4AsyArMjvgbTfcZoiYcmifevudsorgE429cuzTJk+NDhLxyJcliJLcAXXzgIAZxhKQAC30xYhKeXXgwMAiACutmCSxoNYAG4wQIDQFMAHp643iBaAMYA9p6EWDgCccwkAPqELIgpaYgCuITBYeFW0KYhEQAuUTHIcQIJyanphJnZiQBGxKE+AiShYGhxrViIzcwQWJ0kPrgQPqECACYkuaUFRXkls+Wx8SRJKQ31jYSJiKHIYM2nYLM+s-LkAj6DXeQogmg+Z7MC8Ivha8u+AGsoNAQNNZuxmiRcABaUZkaGEQjXaECZpgHzQnzkDriNBgUIkZoCYI+AHNGBFUJuHQg4AAHRAABtwqEIIzEloSuEAE4QADmPgZ0AZYIhUNhnWQCKRsxRaIxWJxbHxhIEDPwDK0Pi0WgAluEAHYcrm8gVCkWhcGE8VwqWI5Go9GY7ECXEqonqhkRcIA3U+RKzCAlCDm0GWsUw23Sh3y51KvEEj0gAC+wV1HmgLhCwZKthpsDQ5Ck8CIAgsAC9gUUAA58zweDR8owg6KbarbURpQRIdDoPDBameLAAOlww-IhHIwTZFJs+JgCN8JV1G0qWwWGk5degNi0ANXVRquzSJAyWRyvl11aHiGHaFw5GHhCQT4wA583M81e54XWvlsVYaLYK47r4biMsYFjVoOcAgLgAAE94pPBOQWFojKcge64TogwSMv8IChHmJSJLq6wguQADCACqABCiAAJIAKLIAAigOuqkeRICEOILBYLc8CyMw7BfMSjahBSFSHk4WC4JIIAAI4+BSrggfAyZAA
h2
3084.4010000583
3090.3440000257
497
70
200
image/gif
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)
313.098
11.038
492.392
6.49
498.904
11.142
986.868
101.373
1092.009
5.95
1097.971
36.516
1149.226
23.532
1174.097
10.354
1187.29
13.487
1202.746
10.268
1213.936
11.442
1226.18
11.696
1237.905
9.736
1248.723
9.863
1259.44
10.739
1270.2
8.904
1279.972
12.196
1293.013
8.79
1301.833
8.725
1311.562
10.068
1321.669
8.815
1331.216
7.814
1345.239
6.973
1352.364
9.938
1363.955
9.75
1376.404
7.569
1385.034
8.685
1394.867
9.723
1404.644
9.209
1414.453
7.854
1422.334
9.813
1432.832
8.565
1443.117
7.197
1453.982
8.257
1465.236
9.264
1474.521
9.28
1483.862
7.452
1495.021
8.048
1504.889
9.126
1515.299
9.764
1526.313
8.853
1538.164
10.561
1549.732
8.58
1559.907
11.608
1571.57
7.692
1580.229
7.41
1590.92
8
1599.698
9
1610.632
10.589
1621.257
9.324
1631.365
8.43
1639.834
8.92
1649.491
7.988
1659.4
8.892
1669.218
10.292
1680.45
12.988
1697.535
7.249
1707.097
13.099
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Ws.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ws.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ws.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ws.org should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ws.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 310 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://ws.org/
309.532
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Ws.org should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ws.org 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 58 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
33606
http://ws.org/
6589
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
4128
http://i3.cdn-image.com/__media__/js/min.js?v2.3
3421
http://i3.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
3401
http://i3.cdn-image.com/__media__/pics/8934/searchIconN.gif
1711
http://i3.cdn-image.com/__media__/pics/8934/arrow.png
1624
http://ws.org/px.js?ch=2
1085
http://ws.org/px.js?ch=1
1084
https://dts.gnpge.com/cenw.js
502
Avoids an excessive DOM size — 49 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
49
Maximum DOM Depth
7
Maximum Child Elements
11
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ws.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://ws.org/
2770.38
909.972
11.896
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
193.688
141.236
11.552
Unattributable
80.72
6.292
0
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
78.184
55.92
7.544
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 — 16 requests • 58 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
16
59480
Script
4
39196
Document
2
10717
Image
6
8171
Other
4
1396
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
13
50722
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)
38126
0.796
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.023619975153796
0.0029816521623442
0.0022386436799536
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 — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
1260
203
http://ws.org/
1463
146
https://pxlgnpgecom-a.akamaihd.net/javascripts/bfp_ssn.js?templateId=10
2520
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ws.org on mobile screens.
First Contentful Paint (3G) — 2504 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

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

Total Blocking Time — 210 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 610 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ws.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://ws.org/px.js?ch=1
1084
180
http://ws.org/px.js?ch=2
1085
330
http://i3.cdn-image.com/__media__/js/min.js?v2.3
3421
630
Serve static assets with an efficient cache policy — 10 resources found
Ws.org 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)
http://ws.org/px.js?ch=2
0
1085
http://ws.org/px.js?ch=1
0
1084
https://dts.gnpge.com/ptmd?t=166899974452710937323280_N4IgtgniBcDasEYA0BOJBmArMhAmTSuCCAukrLqhtobuoQBwAMZs9aWyuKl6ALClZ8qnDADZkfBA1YEONPuiZI+DAOwkyIAO4BHGLC2QATga0A7AIYG+3AWLW4xwhPybqm6NJiXvVSi0sAZxhuJBAAS0swA1w+FnCokOgGcIAPADMYEABTAGMAE1UcvAYCvMw1S0s1FBylPgq8rzy8hmYUEHCAa2toXLyUMSZMFCYAWjEUVXHiHILxgCNLMUtx7CdFhEt0Qpy+LpBuxZhkEDyAN2zgAB0QABsAezzLe4B9IIAXR+NLAHMcndoHd8kMRmNJtMGLMEPMlis1hsxFsdns+HckHcgjkgkEIo9zB9vr8AUCQYNhqMJlMZnMFstVus8MjtrsCvsMXc8o9Ht0Ijk3gVLJ9LGSBmCqZDabD6QimZtWWi7gBfQ5-T5ZODIZQ6whadXJWC641aL6G41IbVafKfGL9JzoQ4RK7QJgAOgIIC+woAroauBxlGgEIJwgAvPpnAAOf2yV3CfwAFtkEGIxAwUJm1Hw+JhcGoEEwUOg1Og6LhmIcLskQGI3e7sJhDq9TsoQBk8jBZuEcp8Iim0xmsznDl9Y67wkFugP05mUNm+G8EFIC3wC7UmAhDjkIlHsg43bgRm7XGoT-mqzlTP0o8ZHgVtz7I+Eff2J7kLvczOEo9Xv177i+Gch3nHNsDUQ57k1M48j9T43giB9+kwABhABVAAhNQAEkAFEGAARSrCIEKQkBSikMRMFzfgS1sAQvDVTtoFTWdh2wBBPV0HJTnCDI31wZUgA
0
497
https://dts.gnpge.com/ptmd?t=166899974452710937323280_N4IgZghiBcDaDMB2AHPATI+A2ZAGANAIy4AsyArMjvgbTfcZoiYcmifevudsorgE429cuzTJk+NDhLxyJcliJLcAXXzgIAZxhKQAC30xYhKeXXgwMAiACutmCSxoNYAG4wQIDQFMAHp643iBaAMYA9p6EWDgCccwkAPqELIgpaYgCuITBYeFW0KYhEQAuUTHIcQIJyanphJnZiQBGxKE+AiShYGhxrViIzcwQWJ0kPrgQPqECACYkuaUFRXkls+Wx8SRJKQ31jYSJiKHIYM2nYLM+s-LkAj6DXeQogmg+Z7MC8Ivha8u+AGsoNAQNNZuxmiRcABaUZkaGEQjXaECZpgHzQnzkDriNBgUIkZoCYI+AHNGBFUJuHQg4AAHRAABtwqEIIzEloSuEAE4QADmPgZ0AZYIhUNhnWQCKRsxRaIxWJxbHxhIEDPwDK0Pi0WgAluEAHYcrm8gVCkWhcGE8VwqWI5Go9GY7ECXEqonqhkRcIA3U+RKzCAlCDm0GWsUw23Sh3y51KvEEj0gAC+wV1HmgLhCwZKthpsDQ5Ck8CIAgsAC9gUUAA58zweDR8owg6KbarbURpQRIdDoPDBameLAAOlww-IhHIwTZFJs+JgCN8JV1G0qWwWGk5degNi0ANXVRquzSJAyWRyvl11aHiGHaFw5GHhCQT4wA583M81e54XWvlsVYaLYK47r4biMsYFjVoOcAgLgAAE94pPBOQWFojKcge64TogwSMv8IChHmJSJLq6wguQADCACqABCiAAJIAKLIAAigOuqkeRICEOILBYLc8CyMw7BfMSjahBSFSHk4WC4JIIAAI4+BSrggfAyZAA
0
497
https://dts6.gnpge.com/ptmdDual?t=%7B%22gh%22%3A%22166899974452710937323280%22%2C%22za%22%3A1%2C%22gcd%22%3A1668999744597%2C%22al%22%3A10%2C%22bcnd%22%3A1%7D
0
441
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
300000
33606
http://i3.cdn-image.com/__media__/pics/8934/arrow.png
14435000
1624
http://i3.cdn-image.com/__media__/js/min.js?v2.3
20007000
3421
http://i3.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
69575000
3401
http://i3.cdn-image.com/__media__/pics/8934/searchIconN.gif
85891000
1711
Minimize main-thread work — 3.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
1540.132
Script Evaluation
1117.028
Other
214.228
Parse HTML & CSS
152.108
Rendering
75.58
Script Parsing & Compilation
32.944

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
http://i3.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
48

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Internationalization and localization

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

Names and labels

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ws.org 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

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 — 8 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://ws.org/
Allowed
http://ws.org/px.js?ch=1
Allowed
http://ws.org/px.js?ch=2
Allowed
http://i3.cdn-image.com/__media__/js/min.js?v2.3
Allowed
http://i3.cdn-image.com/__media__/pics/8934/rcomlogo.jpg
Allowed
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=5CUB7IE8Q
Allowed
http://i3.cdn-image.com/__media__/pics/8934/arrow.png
Allowed
http://i3.cdn-image.com/__media__/pics/8934/searchIconN.gif
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
75

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ws.org. 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 ws.org on mobile screens.
Document uses legible font sizes — 69.39% 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 p
19.39%
11px
.footer p a
7.14%
11px
#header .whois a
4.08%
11px
69.39%
≥ 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.

Mobile Friendly

Tap targets are not sized appropriately — 80% 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
69x12
67x22

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

Crawling and Indexing

Links are not 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.

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 ws.org. 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 ws.org 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: 208.91.197.39
Continent: North America
Country: British Virgin Islands
British Virgin Islands Flag
Region:
City:
Longitude: -64.5
Latitude: 18.5
Currencies: USD
Languages: English

Web Hosting Provider

Name IP Address
Confluence Networks Inc
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Public Interest Registry 208.109.192.65
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: ws.org
Issued By: ZeroSSL ECC Domain Secure Site CA
Valid From: 16th September, 2022
Valid To: 15th December, 2022
Subject: CN = ws.org
Hash: a9684984
Issuer: CN = ZeroSSL ECC Domain Secure Site CA
O = ZeroSSL
S = AT
Version: 2
Serial Number: 123603633066554117756053390875164215033
Serial Number (Hex): 5CFD319DE96BE6D2FEB5541960D906F9
Valid From: 16th September, 2024
Valid To: 15th December, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA384
Signature Algorithm (Long Name): ecdsa-with-SHA384
Authority Key Identifier: keyid:0F:6B:E6:4B:CE:39:47:AE:F6:7E:90:1E:79:F0:30:91:92:C8:5F:A3
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.78
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://zerossl.crt.sectigo.com/ZeroSSLECCDomainSecureSiteCA.crt
OCSP - URI:http://zerossl.ocsp.sectigo.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Sep 16 22:38:28.867 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:D3:F5:3F:02:52:22:E5:AA:43:25:07:
C4:ED:59:8F:15:C2:46:08:98:AB:03:77:A0:22:0F:C9:
25:03:4B:A0:57:02:21:00:F4:81:CD:CD:B2:2F:C5:8D:
EA:60:3A:27:E5:D6:7E:56:17:21:1D:80:98:AC:23:B7:
49:37:67:87:D9:A0:52:E4
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Sep 16 22:38:28.830 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:91:24:32:C6:EA:64:76:2F:AC:DE:50:
4E:21:86:12:87:53:50:F2:15:58:7C:BB:0C:50:F7:29:
63:BB:69:EE:72:02:20:05:04:58:77:93:F2:EE:F8:60:
6B:18:96:07:A7:BF:48:EB:BF:3F:DE:C6:18:9F:AB:87:
6A:0F:57:89:4E:03:FC
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:ws.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
ws.org. 208.91.197.39 IN 14400

NS Records

Host Nameserver Class TTL
ws.org. dns046.a.register.com. IN 14400
ws.org. dns158.b.register.com. IN 14400
ws.org. dns053.c.register.com. IN 14400
ws.org. dns010.d.register.com. IN 14400

SOA Records

Domain Name Primary NS Responsible Email TTL
ws.org. dns046.a.register.com. root.register.com. 14400

HTTP Response Headers

Whois Lookup

Created: 2nd November, 1997
Changed: 18th September, 2022
Expires: 2nd December, 2025
Registrar: GoDaddy.com, LLC
Status: clientDeleteProhibited
clientRenewProhibited
clientTransferProhibited
clientUpdateProhibited
Nameservers: dns010.d.register.com
dns046.a.register.com
dns053.c.register.com
dns158.b.register.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Domains By Proxy, LLC
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: Arizona
Owner Country: US
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: ws.org
Registry Domain ID: 4307f761a5fd40d7885c418736ac6102-LROR
Registrar WHOIS Server: http://whois.godaddy.com
Registrar URL: http://www.whois.godaddy.com
Updated Date: 2022-09-18T18:56:38Z
Creation Date: 1997-02-11T05:00:00Z
Registry Expiry Date: 2025-02-12T05:00:00Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Domains By Proxy, LLC
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Arizona
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: dns010.d.register.com
Name Server: dns046.a.register.com
Name Server: dns053.c.register.com
Name Server: dns158.b.register.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-11-21T03:02:03Z <<<

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

Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
dns010.d.register.com 216.21.236.10
dns046.a.register.com 216.21.231.46
dns053.c.register.com 216.21.235.53
dns158.b.register.com 216.21.232.158
Related

Subdomains

Similar Sites

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

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$10 USD 2/5
0/5
0/5

Sites hosted on the same IP address

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