workingproxy.net

workingproxy.net is SSL secured

Free website and domain report on workingproxy.net

Last Updated: 25th October, 2024
Overview

Snoop Summary for workingproxy.net

This is a free and comprehensive report about workingproxy.net. The domain workingproxy.net is currently hosted on a server located in Australia with the IP address 103.224.182.253, where AUD is the local currency and the local language is English. Our records indicate that workingproxy.net is privately registered by Super Privacy Service LTD c/o Dynadot. If workingproxy.net was to be sold it would possibly be worth $443 USD (based on the daily revenue potential of the website over a 24 month period). Workingproxy.net is somewhat popular with an estimated 208 daily unique visitors. This report was last updated 25th October, 2024.

About workingproxy.net

Site Preview: workingproxy.net workingproxy.net
Title:
Description: This domain may be for sale!
Keywords and Tags: anonymizers
Related Terms:
Fav Icon:
Age: Over 10 years old
Domain Created: 11th July, 2014
Domain Updated: 21st May, 2024
Domain Expires: 11th July, 2025
Review

Snoop Score

2/5

Valuation

$443 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,288,561
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: 208
Monthly Visitors: 6,331
Yearly Visitors: 75,920
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $18 USD
Yearly Revenue: $216 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: workingproxy.net 16
Domain Name: workingproxy 12
Extension (TLD): net 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.59 seconds
Load Time Comparison: Faster than 26% of sites

PageSpeed Insights

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

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://workingproxy.net/
http/1.1
0
326.78000000305
413
0
302
text/html
http://ww25.workingproxy.net/?subid1=20230219-1557-1182-82de-2a32f9ac27c7
http/1.1
327.14700000361
535.68400000222
1581
987
200
text/html
Document
http://ww25.workingproxy.net/js/parking.2.102.3.js
http/1.1
542.92799998075
658.66399998777
22622
69019
200
application/javascript
Script
http://ww25.workingproxy.net/_fd?subid1=20230219-1557-1182-82de-2a32f9ac27c7
http/1.1
675.37200008519
894.0789999906
2628
3997
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
676.64600000717
689.49300004169
54015
146577
200
text/javascript
Script
http://ww25.workingproxy.net/px.gif?ch=1&rn=8.995491156604867
http/1.1
678.5239999881
881.72100007068
421
42
200
image/gif
Image
http://ww25.workingproxy.net/px.gif?ch=2&rn=8.995491156604867
http/1.1
678.92800003756
860.96000007819
421
42
200
image/gif
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=ww25.workingproxy.net&client=partner-dp-bodis01_js&product=SAS&callback=__sasCookie
h2
906.73699998297
915.84200004581
771
372
200
text/javascript
Script
https://www.google.com/afs/ads?psid=2787661449&pcsa=false&channel=pid-bodis-gcontrol56%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol304%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol419&client=dp-bodis01_js&r=m&hl=en&rpbu=http%3A%2F%2Fww25.workingproxy.net%3Fcaf%26subid1%3D20230219-1557-1182-82de-2a32f9ac27c7&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2680060681568818&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=4461676782631996&num=0&output=afd_ads&domain_name=ww25.workingproxy.net&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1676782631999&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=76&frm=0&cl=507651520&uio=-&cont=rs&jsid=caf&jsv=507651520&rurl=http%3A%2F%2Fww25.workingproxy.net%2F%3Fsubid1%3D20230219-1557-1182-82de-2a32f9ac27c7&adbw=master-1%3A1334
h2
925.67200004123
1014.7199999774
2649
6006
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
1027.1580000408
1040.3139999835
54004
146543
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Michroma&display=swap
h2
1069.301999989
1085.9760000603
971
396
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
h2
1089.4689999986
1096.0980000673
1072
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
1089.6780000767
1095.6830000505
1078
444
200
image/svg+xml
Image
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
h2
1110.1910000434
1113.628000021
10701
9892
200
font/woff2
Font
http://ww25.workingproxy.net/_tr
http/1.1
1140.1470000856
1341.2210000679
565
2
200
text/html
Fetch
https://www.google.com/afs/gen_204?client=dp-bodis01_js&output=uds_ads_only&zx=qobsq2rhs5s8&aqid=KKzxY9_eA8eJ6toP_qK4uAw&psid=2787661449&pbt=bs&adbx=425&adby=65.8125&adbh=500&adbw=500&adbah=184%2C150%2C150&adbn=master-1&eawp=partner-dp-bodis01_js&errv=507651520&csala=12%7C0%7C110%7C32%7C57&lle=0&llm=1000&ifv=1&usr=1
h2
2622.4720000755
2646.836000029
1032
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis01_js&output=uds_ads_only&zx=qnujvag4pl03&aqid=KKzxY9_eA8eJ6toP_qK4uAw&psid=2787661449&pbt=bv&adbx=425&adby=65.8125&adbh=500&adbw=500&adbah=184%2C150%2C150&adbn=master-1&eawp=partner-dp-bodis01_js&errv=507651520&csala=12%7C0%7C110%7C32%7C57&lle=0&llm=1000&ifv=1&usr=1
h2
3123.2210000744
3140.4350000666
670
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
540.455
8.813
666.724
13.46
705.859
6.155
897.714
30.038
1019.743
8.578
1054.638
36.882
1093.099
5.69
1118.815
22.476
1141.479
5.087
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Workingproxy.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Workingproxy.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Workingproxy.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Workingproxy.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Workingproxy.net should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Workingproxy.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 63 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
54015
32671
https://www.google.com/adsense/domains/caf.js?pac=0
54004
31348
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 210 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://ww25.workingproxy.net/?subid1=20230219-1557-1182-82de-2a32f9ac27c7
209.531
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Workingproxy.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://workingproxy.net/
190
http://ww25.workingproxy.net/?subid1=20230219-1557-1182-82de-2a32f9ac27c7
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Workingproxy.net should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://ww25.workingproxy.net/js/parking.2.102.3.js
144
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 152 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
54015
https://www.google.com/adsense/domains/caf.js?pac=0
54004
http://ww25.workingproxy.net/js/parking.2.102.3.js
22622
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
10701
https://www.google.com/afs/ads?psid=2787661449&pcsa=false&channel=pid-bodis-gcontrol56%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol304%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol419&client=dp-bodis01_js&r=m&hl=en&rpbu=http%3A%2F%2Fww25.workingproxy.net%3Fcaf%26subid1%3D20230219-1557-1182-82de-2a32f9ac27c7&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2680060681568818&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=4461676782631996&num=0&output=afd_ads&domain_name=ww25.workingproxy.net&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1676782631999&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=76&frm=0&cl=507651520&uio=-&cont=rs&jsid=caf&jsv=507651520&rurl=http%3A%2F%2Fww25.workingproxy.net%2F%3Fsubid1%3D20230219-1557-1182-82de-2a32f9ac27c7&adbw=master-1%3A1334
2649
http://ww25.workingproxy.net/_fd?subid1=20230219-1557-1182-82de-2a32f9ac27c7
2628
http://ww25.workingproxy.net/?subid1=20230219-1557-1182-82de-2a32f9ac27c7
1581
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1078
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
1072
https://www.google.com/afs/gen_204?client=dp-bodis01_js&output=uds_ads_only&zx=qobsq2rhs5s8&aqid=KKzxY9_eA8eJ6toP_qK4uAw&psid=2787661449&pbt=bs&adbx=425&adby=65.8125&adbh=500&adbw=500&adbah=184%2C150%2C150&adbn=master-1&eawp=partner-dp-bodis01_js&errv=507651520&csala=12%7C0%7C110%7C32%7C57&lle=0&llm=1000&ifv=1&usr=1
1032
Uses efficient cache policy on static assets — 2 resources found
Workingproxy.net can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1078
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
82800000
1072
Avoids an excessive DOM size — 18 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
18
Maximum DOM Depth
7
Maximum Child Elements
5
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Workingproxy.net 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)
http://ww25.workingproxy.net/js/parking.2.102.3.js
61.556
54.316
1.723
https://www.google.com/adsense/domains/caf.js?pac=0
60.113
44.835
3.233
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
116.553
Other
51.774
Style & Layout
19.754
Script Parsing & Compilation
10.423
Rendering
8.465
Parse HTML & CSS
7.384
Garbage Collection
1.168
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 — 17 requests • 152 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
17
155614
Script
4
131412
Font
1
10701
Image
6
4694
Document
2
4230
Other
3
3606
Stylesheet
1
971
Media
0
0
Third-party
10
126963
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)
112370
0
11672
0
771
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.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.01587962962963
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of workingproxy.net on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Audits

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

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 7 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://workingproxy.net/
Allowed
http://ww25.workingproxy.net/?subid1=20230219-1557-1182-82de-2a32f9ac27c7
Allowed
http://ww25.workingproxy.net/js/parking.2.102.3.js
Allowed
http://ww25.workingproxy.net/_fd?subid1=20230219-1557-1182-82de-2a32f9ac27c7
Allowed
http://ww25.workingproxy.net/px.gif?ch=1&rn=8.995491156604867
Allowed
http://ww25.workingproxy.net/px.gif?ch=2&rn=8.995491156604867
Allowed
http://ww25.workingproxy.net/_tr
Allowed
90

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

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 workingproxy.net. 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 workingproxy.net 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) 74
Performance 69
Accessibility 85
Best Practices 92
SEO 92
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
69

Performance

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

Metrics

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.033
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://workingproxy.net/
http/1.1
0
318.73900000937
412
0
302
text/html
http://ww25.workingproxy.net/?subid1=20230219-1558-00a2-8d0c-b99c09380abd
http/1.1
319.19199996628
336.79400000256
1581
987
200
text/html
Document
http://ww25.workingproxy.net/js/parking.2.102.3.js
http/1.1
347.70899999421
581.63599995896
22622
69019
200
application/javascript
Script
http://ww25.workingproxy.net/_fd?subid1=20230219-1558-00a2-8d0c-b99c09380abd
http/1.1
600.59699998237
680.47000002116
2626
3997
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
602.36200003419
615.46200001612
54033
146610
200
text/javascript
Script
http://ww25.workingproxy.net/px.gif?ch=1&rn=8.25259606352857
http/1.1
605.02100002486
635.98299992736
421
42
200
image/gif
Image
http://ww25.workingproxy.net/px.gif?ch=2&rn=8.25259606352857
http/1.1
605.51199992187
622.55999993067
421
42
200
image/gif
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=ww25.workingproxy.net&client=partner-dp-bodis01_js&product=SAS&callback=__sasCookie
h2
695.20999991801
705.50799998455
771
372
200
text/javascript
Script
https://www.google.com/afs/ads?psid=9278340425&pcsa=false&channel=pid-bodis-gcontrol52%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol304%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol419&client=dp-bodis01_js&r=m&hl=en&rpbu=http%3A%2F%2Fww25.workingproxy.net%3Fcaf%26subid1%3D20230219-1558-00a2-8d0c-b99c09380abd&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2680060681568818&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17301075%2C17301078&format=r3&nocache=1611676782680790&num=0&output=afd_ads&domain_name=ww25.workingproxy.net&v=3&bsl=8&pac=2&u_his=2&u_tz=-480&dt=1676782680792&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=507651520&uio=-&cont=rs&jsid=caf&jsv=507651520&rurl=http%3A%2F%2Fww25.workingproxy.net%2F%3Fsubid1%3D20230219-1558-00a2-8d0c-b99c09380abd&adbw=master-1%3A344
h2
715.562999947
825.11199999135
52552
151999
200
text/html
Document
https://fonts.googleapis.com/css?family=Michroma&display=swap
h2
873.20599996019
890.54199995007
971
396
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
h2
897.50099997036
901.75499999896
1072
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
898.11099995859
904.52899993397
1078
444
200
image/svg+xml
Image
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
h2
927.76500002947
932.16800002847
10702
9892
200
font/woff2
Font
http://ww25.workingproxy.net/_tr
http/1.1
963.30499998294
1178.5329999402
565
2
200
text/html
Fetch
https://www.google.com/afs/gen_204?client=dp-bodis01_js&output=uds_ads_only&zx=5akml5ss0b05&aqid=WKzxY6PmM6OA6toPy8mMwA8&psid=9278340425&pbt=bs&adbx=0&adby=65.8125&adbh=540&adbw=360&adbah=152%2C186%2C186&adbn=master-1&eawp=partner-dp-bodis01_js&errv=507651520&csala=14%7C0%7C132%7C25%7C72&lle=0&llm=1000&ifv=1&usr=1
h2
2442.2560000094
2463.3380000014
573
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis01_js&output=uds_ads_only&zx=rlz30e9u300k&aqid=WKzxY6PmM6OA6toPy8mMwA8&psid=9278340425&pbt=bv&adbx=0&adby=65.8125&adbh=540&adbw=360&adbah=152%2C186%2C186&adbn=master-1&eawp=partner-dp-bodis01_js&errv=507651520&csala=14%7C0%7C132%7C25%7C72&lle=0&llm=1000&ifv=1&usr=1
h2
2944.0789999207
2959.4219999854
211
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
342.563
9.231
590.259
16.651
631.356
8.246
684.116
35.914
829.855
11
841.789
58.731
901.244
11.38
938.696
25.957
964.794
8.546
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Workingproxy.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Workingproxy.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Workingproxy.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Workingproxy.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Workingproxy.net should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Workingproxy.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 20 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://ww25.workingproxy.net/?subid1=20230219-1558-00a2-8d0c-b99c09380abd
18.595
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Workingproxy.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://workingproxy.net/
630
http://ww25.workingproxy.net/?subid1=20230219-1558-00a2-8d0c-b99c09380abd
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Workingproxy.net should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://ww25.workingproxy.net/js/parking.2.102.3.js
144
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 147 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
54033
https://www.google.com/afs/ads?psid=9278340425&pcsa=false&channel=pid-bodis-gcontrol52%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol304%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol419&client=dp-bodis01_js&r=m&hl=en&rpbu=http%3A%2F%2Fww25.workingproxy.net%3Fcaf%26subid1%3D20230219-1558-00a2-8d0c-b99c09380abd&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2680060681568818&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17301075%2C17301078&format=r3&nocache=1611676782680790&num=0&output=afd_ads&domain_name=ww25.workingproxy.net&v=3&bsl=8&pac=2&u_his=2&u_tz=-480&dt=1676782680792&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=507651520&uio=-&cont=rs&jsid=caf&jsv=507651520&rurl=http%3A%2F%2Fww25.workingproxy.net%2F%3Fsubid1%3D20230219-1558-00a2-8d0c-b99c09380abd&adbw=master-1%3A344
52552
http://ww25.workingproxy.net/js/parking.2.102.3.js
22622
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
10702
http://ww25.workingproxy.net/_fd?subid1=20230219-1558-00a2-8d0c-b99c09380abd
2626
http://ww25.workingproxy.net/?subid1=20230219-1558-00a2-8d0c-b99c09380abd
1581
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1078
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
1072
https://fonts.googleapis.com/css?family=Michroma&display=swap
971
https://partner.googleadservices.com/gampad/cookie.js?domain=ww25.workingproxy.net&client=partner-dp-bodis01_js&product=SAS&callback=__sasCookie
771
Uses efficient cache policy on static assets — 2 resources found
Workingproxy.net can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1078
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
82800000
1072
Avoids an excessive DOM size — 18 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
18
Maximum DOM Depth
7
Maximum Child Elements
5
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Workingproxy.net 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.6 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.google.com/afs/ads?psid=9278340425&pcsa=false&channel=pid-bodis-gcontrol52%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol304%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol419&client=dp-bodis01_js&r=m&hl=en&rpbu=http%3A%2F%2Fww25.workingproxy.net%3Fcaf%26subid1%3D20230219-1558-00a2-8d0c-b99c09380abd&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2680060681568818&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17301075%2C17301078&format=r3&nocache=1611676782680790&num=0&output=afd_ads&domain_name=ww25.workingproxy.net&v=3&bsl=8&pac=2&u_his=2&u_tz=-480&dt=1676782680792&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=507651520&uio=-&cont=rs&jsid=caf&jsv=507651520&rurl=http%3A%2F%2Fww25.workingproxy.net%2F%3Fsubid1%3D20230219-1558-00a2-8d0c-b99c09380abd&adbw=master-1%3A344
434.132
183.196
63.996
http://ww25.workingproxy.net/js/parking.2.102.3.js
286.192
268.628
7.808
https://www.google.com/adsense/domains/caf.js
132.052
71.576
11.62
Unattributable
118.704
1.876
0
http://ww25.workingproxy.net/?subid1=20230219-1558-00a2-8d0c-b99c09380abd
83.876
7.628
5.856
Minimizes main-thread work — 1.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)
Script Evaluation
537.464
Other
224.992
Style & Layout
117.244
Script Parsing & Compilation
89.696
Parse HTML & CSS
57.644
Rendering
37.024
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 • 147 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
150611
Script
3
77426
Document
2
54133
Font
1
10702
Image
6
3776
Other
3
3603
Stylesheet
1
971
Media
0
0
Third-party
9
121963
Minimize third-party usage — Third-party code blocked the main thread for 60 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)
107369
64.852
11673
0
771
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.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.03349609375
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 — 4 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/afs/ads?psid=9278340425&pcsa=false&channel=pid-bodis-gcontrol52%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol304%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol419&client=dp-bodis01_js&r=m&hl=en&rpbu=http%3A%2F%2Fww25.workingproxy.net%3Fcaf%26subid1%3D20230219-1558-00a2-8d0c-b99c09380abd&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2680060681568818&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17301075%2C17301078&format=r3&nocache=1611676782680790&num=0&output=afd_ads&domain_name=ww25.workingproxy.net&v=3&bsl=8&pac=2&u_his=2&u_tz=-480&dt=1676782680792&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=507651520&uio=-&cont=rs&jsid=caf&jsv=507651520&rurl=http%3A%2F%2Fww25.workingproxy.net%2F%3Fsubid1%3D20230219-1558-00a2-8d0c-b99c09380abd&adbw=master-1%3A344
3531
235
http://ww25.workingproxy.net/js/parking.2.102.3.js
2809
104
http://ww25.workingproxy.net/js/parking.2.102.3.js
2737
72
http://ww25.workingproxy.net/js/parking.2.102.3.js
1590
67
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of workingproxy.net on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

Time to Interactive — 4.7 s
The time taken for the page to become fully interactive.
Speed Index — 4.6 s
The time taken for the page contents to be visibly populated.

Other

Reduce unused JavaScript — Potential savings of 61 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
54033
32674
https://www.google.com/afs/ads?psid=9278340425&pcsa=false&channel=pid-bodis-gcontrol52%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol304%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol419&client=dp-bodis01_js&r=m&hl=en&rpbu=http%3A%2F%2Fww25.workingproxy.net%3Fcaf%26subid1%3D20230219-1558-00a2-8d0c-b99c09380abd&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2680060681568818&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17301075%2C17301078&format=r3&nocache=1611676782680790&num=0&output=afd_ads&domain_name=ww25.workingproxy.net&v=3&bsl=8&pac=2&u_his=2&u_tz=-480&dt=1676782680792&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=507651520&uio=-&cont=rs&jsid=caf&jsv=507651520&rurl=http%3A%2F%2Fww25.workingproxy.net%2F%3Fsubid1%3D20230219-1558-00a2-8d0c-b99c09380abd&adbw=master-1%3A344
52433
29310

Metrics

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

Audits

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

Other

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

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Contrast

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 7 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://workingproxy.net/
Allowed
http://ww25.workingproxy.net/?subid1=20230219-1558-00a2-8d0c-b99c09380abd
Allowed
http://ww25.workingproxy.net/js/parking.2.102.3.js
Allowed
http://ww25.workingproxy.net/_fd?subid1=20230219-1558-00a2-8d0c-b99c09380abd
Allowed
http://ww25.workingproxy.net/px.gif?ch=1&rn=8.25259606352857
Allowed
http://ww25.workingproxy.net/px.gif?ch=2&rn=8.25259606352857
Allowed
http://ww25.workingproxy.net/_tr
Allowed
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for workingproxy.net. 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 workingproxy.net on mobile screens.
Document uses legible font sizes — 72.73% 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
.privacy
18.18%
11px
.si133
9.09%
10px
72.73%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

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 workingproxy.net. 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 workingproxy.net 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: 103.224.182.253
Continent: Oceania
Country: Australia
Australia Flag
Region:
City:
Longitude: 143.2104
Latitude: -33.494
Currencies: AUD
Languages: English

Web Hosting Provider

Name IP Address
Trellian Pty. Limited
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: Super Privacy Service LTD c/o Dynadot
Country: US
City: San Mateo
State: California
Post Code: 94401
Email:
Phone: +1.6505854708
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
DYNADOT LLC 104.16.152.132
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: woolworthscareer.com
Issued By: R11
Valid From: 17th October, 2024
Valid To: 15th January, 2025
Subject: CN = woolworthscareer.com
Hash: 85c18679
Issuer: CN = R11
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x0454A6A9546DFFDAAED5CADFC3C81B4B82F0
Serial Number (Hex): 0454A6A9546DFFDAAED5CADFC3C81B4B82F0
Valid From: 17th October, 2024
Valid To: 15th January, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
Timestamp : Oct 17 03:45:00.111 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B6:8F:8D:84:FB:2F:7F:97:11:98:0E:
5D:F8:D1:D1:A6:E6:90:BB:0A:08:D8:C4:17:B6:5C:FB:
D4:92:75:C3:A9:02:20:02:7D:DD:07:CC:A5:A9:52:92:
EF:4C:9D:1A:D4:B6:BB:8C:0A:C7:52:CB:BF:5B:47:21:
91:E4:62:A3:2A:AD:C5
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
Timestamp : Oct 17 03:45:00.297 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:81:EB:C8:A0:80:83:9A:6B:E9:E4:7D:
BB:20:4D:FF:E8:5F:CE:D1:D2:8C:E2:97:F3:7F:3D:E4:
57:CE:DE:0F:16:02:21:00:FD:38:9C:DF:DE:7D:E9:F4:
BC:2A:6B:11:3B:5A:7D:E6:6E:72:A1:6F:CA:D1:34:E3:
F3:8A:42:86:B4:FF:67:D6
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.936h.cc
DNS:*.acrylic.co.za
DNS:*.atlassian-int.net
DNS:*.autovillemotors.com
DNS:*.avmoo.com.cn
DNS:*.bashful.group
DNS:*.batfrog.site
DNS:*.bf1h.cc
DNS:*.bubget.com
DNS:*.crusdartrav.eu
DNS:*.cryptofcthulhu.xyz
DNS:*.domore.site
DNS:*.duvely.org
DNS:*.emploi-alternance.net
DNS:*.eorixvmt.com
DNS:*.eyeglassses.com
DNS:*.fackeyou.com
DNS:*.gmworldwide.org
DNS:*.grantavod.blog
DNS:*.hro1.org
DNS:*.ifcmarkts.com.br
DNS:*.jewelrystunnernpdpc.net
DNS:*.kemeixiezhen.com
DNS:*.manaroki3.net
DNS:*.metrolink.online
DNS:*.nrghook.club
DNS:*.obter.ru
DNS:*.paleomom.com
DNS:*.pattersonchevycars.com
DNS:*.pinuplive.com
DNS:*.prudentbank.com
DNS:*.scottrobertsoninteriors.net
DNS:*.shawty.io
DNS:*.studiohaga.net
DNS:*.thankstoyo.co
DNS:*.tikulo.net
DNS:*.tndmv.com
DNS:*.tunegeni.com
DNS:*.uniquelynautical.com
DNS:*.woolworthscareer.com
DNS:*.workingproxy.net
DNS:*.x11119.cc
DNS:*.xn--lungenschtzen-4ob.de
DNS:*.xvidroes.com
DNS:42gramsfilm.com
DNS:936h.cc
DNS:acrylic.co.za
DNS:atlassian-int.net
DNS:autovillemotors.com
DNS:avmoo.com.cn
DNS:bashful.group
DNS:batfrog.site
DNS:bf1h.cc
DNS:bubget.com
DNS:crusdartrav.eu
DNS:cryptofcthulhu.xyz
DNS:domore.site
DNS:duvely.org
DNS:emploi-alternance.net
DNS:eorixvmt.com
DNS:eyeglassses.com
DNS:fackeyou.com
DNS:gmworldwide.org
DNS:grantavod.blog
DNS:hro1.org
DNS:ifcmarkts.com.br
DNS:jewelrystunnernpdpc.net
DNS:kemeixiezhen.com
DNS:manaroki3.net
DNS:metrolink.online
DNS:nrghook.club
DNS:obter.ru
DNS:paleomom.com
DNS:pattersonchevycars.com
DNS:pinuplive.com
DNS:prudentbank.com
DNS:scottrobertsoninteriors.net
DNS:shawty.io
DNS:studiohaga.net
DNS:thankstoyo.co
DNS:tikulo.net
DNS:tndmv.com
DNS:tunegeni.com
DNS:uniquelynautical.com
DNS:woolworthscareer.com
DNS:workingproxy.net
DNS:x11119.cc
DNS:xn--lungenschtzen-4ob.de
DNS:xvidroes.com
DNS:*.42gramsfilm.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
workingproxy.net. 103.224.182.253 IN 3600

NS Records

Host Nameserver Class TTL
workingproxy.net. ns1.abovedomains.com. IN 21600
workingproxy.net. ns2.abovedomains.com. IN 21600

MX Records

Priority Host Server Class TTL
10 workingproxy.net. park-mx.above.com. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
workingproxy.net. ns1.abovedomains.com. hostmaster.trellian.com. 60

TXT Records

Host Value Class TTL
workingproxy.net. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 302 Found
date: 25th October, 2024
server: Apache
content-type: text/html; charset=UTF-8
set-cookie: *
location: http://ww38.workingproxy.net/
connection: close

Whois Lookup

Created: 11th July, 2014
Changed: 21st May, 2024
Expires: 11th July, 2025
Registrar: DYNADOT LLC
Status: clientTransferProhibited
Nameservers: 1107.ns1.abovedomains.com
1107.ns2.abovedomains.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Super Privacy Service LTD c/o Dynadot
Owner Street: PO Box 701
Owner Post Code: 94401
Owner City: San Mateo
Owner State: California
Owner Country: US
Owner Phone: +1.6505854708
Owner Email: https://www.dynadot.com/domain/contact-request?domain=workingproxy.net
Admin Name: REDACTED FOR PRIVACY
Admin Organization: Super Privacy Service LTD c/o Dynadot
Admin Street: PO Box 701
Admin Post Code: 94401
Admin City: San Mateo
Admin State: California
Admin Country: US
Admin Phone: +1.6505854708
Admin Email: https://www.dynadot.com/domain/contact-request?domain=workingproxy.net
Tech Name: REDACTED FOR PRIVACY
Tech Organization: Super Privacy Service LTD c/o Dynadot
Tech Street: PO Box 701
Tech Post Code: 94401
Tech City: San Mateo
Tech State: California
Tech Country: US
Tech Phone: +1.6505854708
Tech Email: https://www.dynadot.com/domain/contact-request?domain=workingproxy.net
Full Whois: Domain Name: WORKINGPROXY.NET
Registry Domain ID: 1866462559_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.dynadot.com
Registrar URL: http://www.dynadot.com
Updated Date: 2024-05-21T23:40:31.0Z
Creation Date: 2014-07-11T15:33:14.0Z
Registrar Registration Expiration Date: 2025-07-11T15:33:14.0Z
Registrar: DYNADOT LLC
Registrar IANA ID: 472
Registrar Abuse Contact Email: abuse@dynadot.com
Registrar Abuse Contact Phone: +1.6502620100
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Super Privacy Service LTD c/o Dynadot
Registrant Street: PO Box 701
Registrant Street:
Registrant City: San Mateo
Registrant State/Province: California
Registrant Postal Code: 94401
Registrant Country: US
Registrant Phone: +1.6505854708
Registrant Email: https://www.dynadot.com/domain/contact-request?domain=workingproxy.net
Registry Admin ID:
Admin Name: REDACTED FOR PRIVACY
Admin Organization: Super Privacy Service LTD c/o Dynadot
Admin Street: PO Box 701
Admin Street:
Admin City: San Mateo
Admin State/Province: California
Admin Postal Code: 94401
Admin Country: US
Admin Phone: +1.6505854708
Admin Email: https://www.dynadot.com/domain/contact-request?domain=workingproxy.net
Registry Tech ID:
Tech Name: REDACTED FOR PRIVACY
Tech Organization: Super Privacy Service LTD c/o Dynadot
Tech Street: PO Box 701
Tech Street:
Tech City: San Mateo
Tech State/Province: California
Tech Postal Code: 94401
Tech Country: US
Tech Phone: +1.6505854708
Tech Email: https://www.dynadot.com/domain/contact-request?domain=workingproxy.net
Name Server: 1107.ns1.abovedomains.com
Name Server: 1107.ns2.abovedomains.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-05-21 16:40:31 -0700 <<<

Nameservers

Name IP Address
1107.ns1.abovedomains.com 103.224.182.9
1107.ns2.abovedomains.com 103.224.182.10
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$3,919 USD 2/5
$54 USD 2/5
$397 USD 1/5
0/5