dishonest.co.za

dishonest.co.za is SSL secured

Free website and domain report on dishonest.co.za

Last Updated: 27th October, 2020 Update Now
Overview

Snoop Summary for dishonest.co.za

This is a free and comprehensive report about dishonest.co.za. If dishonest.co.za was to be sold it would possibly be worth $555 USD (based on the daily revenue potential of the website over a 24 month period). Dishonest.co.za receives an estimated 262 unique visitors every day - a decent amount of traffic! This report was last updated 27th October, 2020.

About dishonest.co.za

Site Preview: dishonest.co.za dishonest.co.za
Title: start [Threat Awareness Wiki]
Description:
Keywords and Tags: internet services, start
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$555 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 5,312,251
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: 262
Monthly Visitors: 7,974
Yearly Visitors: 95,630
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $23 USD
Yearly Revenue: $273 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: dishonest.co.za 15
Domain Name: dishonest 9
Extension (TLD): coza 4

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

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

Performance

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

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 0.6 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.5 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.5 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.5 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive dishonest.co.za as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://dishonest.co.za/
0
68.770000012591
660
0
301
https://dishonest.co.za/
69.255999987945
972.78399998322
1267
0
302
text/html
https://dishonest.co.za/doku.php
973.43200002797
1932.4400000041
9445
36843
200
text/html
Document
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
1947.5680000032
3169.8280000128
36714
150215
200
text/css
Stylesheet
https://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
1947.7690000203
3477.4600000237
95657
343146
200
application/javascript
Script
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
3179.2330000317
4295.5209999927
29807
109387
200
application/javascript
Script
https://dishonest.co.za/lib/exe/fetch.php?media=wiki:logo.png
3179.3780000298
4115.4359999928
6274
5237
200
image/png
Image
https://dishonest.co.za/lib/exe/fetch.php?w=1000&tok=7049dc&media=undefined:irs_red_flag.jpg
3179.5960000018
4966.8139999849
220247
219108
200
image/jpeg
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-donate.gif
3180.0350000267
3203.3630000078
1032
187
200
image/gif
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-php.gif
3180.2150000003
3232.7640000149
1046
207
200
image/gif
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-html5.png
3180.3850000142
3231.5810000291
1059
305
200
image/png
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-css.png
3180.6840000208
3235.7729999931
1134
297
200
image/png
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-dw.png
3180.8310000342
3236.5759999957
1239
398
200
image/png
Image
https://dishonest.co.za/lib/exe/taskrunner.php?id=start&1603790228
3180.9849999845
4321.9720000052
989
42
200
image/gif
Image
https://dishonest.co.za/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
3171.6710000183
3188.983
1536
1239
200
application/javascript
Script
3189.0790000325
3189.1109999851
0
209
200
image/png
Image
3192.6990000065
3192.7489999798
0
307
200
image/png
Image
3193.6340000248
3193.6620000051
0
113
200
image/png
Image
3194.1499999957
3194.1770000267
0
431
200
image/png
Image
4328.611999983
4328.6480000243
0
225
200
image/png
Image
https://dishonest.co.za/lib/exe/ajax.php
4354.216000007
5394.1629999899
982
0
200
text/html
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1964.879
8.015
1975.39
6.545
3200.828
6.744
3207.664
8.188
3215.867
36.379
3256.658
7.047
3522.5
36.251
4330.582
13.006
4354.313
16.04
4370.373
8.048
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 90 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dishonest.co.za should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
36714
110
Properly size images — Potential savings of 36 KiB
Images can slow down the page's load time. Dishonest.co.za should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dishonest.co.za/lib/exe/fetch.php?w=1000&tok=7049dc&media=undefined:irs_red_flag.jpg
219108
36837
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Dishonest.co.za should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dishonest.co.za should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dishonest.co.za should consider minifying JS files.
Remove unused CSS — Potential savings of 33 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dishonest.co.za should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
36714
34130
Remove unused JavaScript — Potential savings of 92 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://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
95657
72242
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
29807
22357
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Dishonest.co.za 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.

Diagnostics

Avoids enormous network payloads — Total size was 400 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://dishonest.co.za/lib/exe/fetch.php?w=1000&tok=7049dc&media=undefined:irs_red_flag.jpg
220247
https://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
95657
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
36714
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
29807
https://dishonest.co.za/doku.php
9445
https://dishonest.co.za/lib/exe/fetch.php?media=wiki:logo.png
6274
https://dishonest.co.za/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
1536
https://dishonest.co.za/
1267
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-dw.png
1239
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-css.png
1134
Avoids an excessive DOM size — 511 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
511
Maximum DOM Depth
13
Maximum Child Elements
39
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dishonest.co.za should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://dishonest.co.za/doku.php
82.871
2.38
1.237
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
56.81
45.717
2.878
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
80.101
Other
36.091
Style & Layout
35.34
Rendering
26.29
Parse HTML & CSS
19.859
Script Parsing & Compilation
9.565
Garbage Collection
2.524
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 • 400 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
409088
Image
8
233020
Script
3
127000
Stylesheet
1
36714
Document
1
9445
Other
3
2909
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

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

Speed Index — 2.3 s
The time taken for the page contents to be visibly populated.

Opportunities

Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Dishonest.co.za should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dishonest.co.za/
190
https://dishonest.co.za/
150
https://dishonest.co.za/doku.php
0

Opportunities

Reduce initial server response time — Root document took 960 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://dishonest.co.za/doku.php
960.005

Diagnostics

Serve static assets with an efficient cache policy — 11 resources found
Dishonest.co.za 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://dishonest.co.za/lib/exe/fetch.php?w=1000&tok=7049dc&media=undefined:irs_red_flag.jpg
86400000
220247
https://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
86400000
95657
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
86400000
36714
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
86400000
29807
https://dishonest.co.za/lib/exe/fetch.php?media=wiki:logo.png
86400000
6274
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-dw.png
86400000
1239
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-css.png
86400000
1134
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-html5.png
86400000
1059
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-php.gif
86400000
1046
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-donate.gif
86400000
1032
https://dishonest.co.za/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000
1536
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dishonest.co.za. 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.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[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"]`
Dishonest.co.za may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Dishonest.co.za may provide relevant information that dialogue cannot, by using audio descriptions.

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

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
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.

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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
jQuery UI
1.12.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://dishonest.co.za/
73

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for dishonest.co.za. 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 dishonest.co.za 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.
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 avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Document does not have a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
52

Progressive Web App

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

Fast and reliable

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dishonest.co.za on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

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

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://dishonest.co.za/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Performance

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

Metrics

First Contentful Paint — 1.6 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.8 s
The timing of the largest text or image that is painted.
Time to Interactive — 2.5 s
The time taken for the page to become fully interactive.
Total Blocking Time — 40 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

First CPU Idle — 2.4 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 120 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.6 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive dishonest.co.za as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://dishonest.co.za/
0
20.749000133947
645
0
301
https://dishonest.co.za/
21.280999993905
882.17900018208
1224
0
302
text/html
https://dishonest.co.za/doku.php
882.7220001258
1785.8949999791
9456
36843
200
text/html
Document
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
1798.596000066
3026.1109999847
36604
150215
200
text/css
Stylesheet
https://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
1798.746000044
3304.5040001161
95402
343146
200
application/javascript
Script
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
3034.821000183
4191.1969999783
29839
109387
200
application/javascript
Script
https://dishonest.co.za/lib/exe/fetch.php?media=wiki:logo.png
3035.0650001783
3977.5460001547
6359
5237
200
image/png
Image
https://dishonest.co.za/lib/exe/fetch.php?w=1000&tok=7049dc&media=undefined:irs_red_flag.jpg
3035.5650000274
4811.5350001026
220243
219108
200
image/jpeg
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-donate.gif
3035.6740001589
3088.265000144
941
187
200
image/gif
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-php.gif
3035.9000000171
3083.3420001436
961
207
200
image/gif
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-html5.png
3036.0420001671
3089.8290001787
1142
305
200
image/png
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-css.png
3036.158000119
3056.8490000442
1138
297
200
image/png
Image
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-dw.png
3036.2790001091
3059.5299999695
1241
398
200
image/png
Image
https://dishonest.co.za/lib/exe/taskrunner.php?id=start&1603790253
3036.4420001861
3981.3980001491
981
42
200
image/gif
Image
https://dishonest.co.za/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
3028.5000000149
3045.8649999928
1524
1239
200
application/javascript
Script
3041.9550000224
3041.9960001018
0
209
200
image/png
Image
3043.3490001597
3043.3900000062
0
307
200
image/png
Image
3044.487999985
3044.5330000948
0
113
200
image/png
Image
3045.1130000874
3045.1410000678
0
431
200
image/png
Image
4221.6340000741
4221.6640000697
0
225
200
image/png
Image
https://dishonest.co.za/lib/exe/ajax.php
4249.1540000774
5256.6760000773
980
0
200
text/html
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1815.027
7.238
3054.726
5.372
3060.188
5.299
3065.499
29.63
3346.818
30.728
4223.256
12.274
4245.277
13.204
4258.501
7.925
4476.374
5.981
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 3120 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Dishonest.co.za should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dishonest.co.za should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dishonest.co.za should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Dishonest.co.za 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.

Diagnostics

Avoids enormous network payloads — Total size was 399 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://dishonest.co.za/lib/exe/fetch.php?w=1000&tok=7049dc&media=undefined:irs_red_flag.jpg
220243
https://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
95402
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
36604
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
29839
https://dishonest.co.za/doku.php
9456
https://dishonest.co.za/lib/exe/fetch.php?media=wiki:logo.png
6359
https://dishonest.co.za/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
1524
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-dw.png
1241
https://dishonest.co.za/
1224
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-html5.png
1142
Avoids an excessive DOM size — 511 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
511
Maximum DOM Depth
13
Maximum Child Elements
39
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dishonest.co.za should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://dishonest.co.za/doku.php
314.5
9.204
4.852
https://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
236.696
132.912
17.788
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
208.112
165.016
11.44
Unattributable
82.896
3.796
0.76
Minimizes main-thread work — 0.9 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
319.832
Rendering
159.816
Other
159.428
Style & Layout
153.62
Parse HTML & CSS
46.472
Script Parsing & Compilation
36.092
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 • 399 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
408680
Image
8
233006
Script
3
126765
Stylesheet
1
36604
Document
1
9456
Other
3
2849
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.099977779159388
0.075689392131966
0.071826886644276
0.025982925657242
0.025219870537595
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 — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
2550
123
https://dishonest.co.za/doku.php
1299
59
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

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.

Opportunities

Eliminate render-blocking resources — Potential savings of 260 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dishonest.co.za should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
36604
330
Properly size images — Potential savings of 57 KiB
Images can slow down the page's load time. Dishonest.co.za should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dishonest.co.za/lib/exe/fetch.php?w=1000&tok=7049dc&media=undefined:irs_red_flag.jpg
219108
58542
Remove unused CSS — Potential savings of 33 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dishonest.co.za should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
36604
34039
Remove unused JavaScript — Potential savings of 92 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://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
95402
71390
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
29839
22354

Metrics

Speed Index — 6.2 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.3
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Reduce initial server response time — Root document took 900 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://dishonest.co.za/doku.php
904.171
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Dishonest.co.za should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dishonest.co.za/
630
https://dishonest.co.za/
480
https://dishonest.co.za/doku.php
0

Diagnostics

Serve static assets with an efficient cache policy — 11 resources found
Dishonest.co.za 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://dishonest.co.za/lib/exe/fetch.php?w=1000&tok=7049dc&media=undefined:irs_red_flag.jpg
86400000
220243
https://dishonest.co.za/lib/exe/jquery.php?tseed=34a552433bc33cc9c3bc32527289a0b2
86400000
95402
https://dishonest.co.za/lib/exe/css.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
86400000
36604
https://dishonest.co.za/lib/exe/js.php?t=dokuwiki&tseed=1da76149fd06991e03491ad123202321
86400000
29839
https://dishonest.co.za/lib/exe/fetch.php?media=wiki:logo.png
86400000
6359
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-dw.png
86400000
1241
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-html5.png
86400000
1142
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-css.png
86400000
1138
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-php.gif
86400000
961
https://dishonest.co.za/lib/tpl/dokuwiki/images/button-donate.gif
86400000
941
https://dishonest.co.za/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000
1524
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dishonest.co.za. 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.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

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

Contrast

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

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[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"]`
Dishonest.co.za may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Dishonest.co.za may provide relevant information that dialogue cannot, by using audio descriptions.

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

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
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.

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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
jQuery UI
1.12.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://dishonest.co.za/

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://dishonest.co.za/lib/exe/fetch.php?media=wiki:logo.png
64 x 64
64 x 64
168 x 168
70

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for dishonest.co.za. 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 dishonest.co.za on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 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.
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 avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Document does not have a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Mobile Friendly

Tap targets are not sized appropriately — 12% 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
90x16
19x14
272x17
MMM
39x17
MMM
39x17
95x17
110x17
94x17
163x17
115x17
84x17
42x17
42x17
47x17
47x17
OFM
53x17
86x17
82x17
82x17
48x17
87x17
87x17
166x17
109x17
132x17
62x17
62x17
59x17
72x17
85x17
79x17
79x17
189x17
136x17
185x17
129x17
144x17
96x17
154x17
72x17
72x17
90x17
95x17
110x17
89x17
89x17
94x17
81x17
81x17
115x17
84x17
86x17
109x17
61x17
61x17
158x17
130x17
264x17
194x17
125x17
54x17
54x17
79x17
150x17
126x17
255x17
253x17
253x17
224x17
109x18
76x18
122x18
94x18
95x18
76x18
80x16
80x16

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
54

Progressive Web App

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

Fast and reliable

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dishonest.co.za on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

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

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://dishonest.co.za/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

Server IP Address: 104.24.96.60
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Cloudflare, 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

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: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 9th October, 2020
Valid To: 9th October, 2021
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 4d04c09a
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 15093443249526269461046757346278009605
Serial Number (Hex): 0B5AE434E025800723F49C6B9ABE6B05
Valid From: 9th October, 2024
Valid To: 9th October, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Oct 9 07:38:26.569 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:0F:CF:0E:70:B9:1B:5C:74:C5:C7:74:B5:
09:1E:5A:3B:7B:45:D5:7E:90:0D:68:45:10:46:EE:E8:
D8:AB:44:08:02:21:00:AA:E6:27:A6:7A:36:4B:A9:35:
80:BB:C2:E4:B1:C6:58:C6:76:BA:5B:F3:81:58:A6:71:
82:76:3A:CF:C6:07:F3
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Oct 9 07:38:26.660 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:D3:D2:60:08:85:98:04:7E:41:38:DA:
08:21:61:FA:3E:DB:A2:68:CA:54:89:89:4F:96:09:46:
4C:13:84:1A:8D:02:21:00:F8:7C:E3:A8:4D:E5:AE:90:
FE:A3:73:2B:F3:96:32:64:3E:3A:DE:F4:00:0C:C5:CB:
1C:E9:17:A3:4F:6C:44:89
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.dishonest.co.za
DNS:sni.cloudflaressl.com
DNS:dishonest.co.za
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 27th October, 2020
Content-Type: text/html; charset=utf-8
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate
Server: cloudflare
Connection: keep-alive
Set-Cookie: *
Vary: Cookie,User-Agent
Pragma: no-cache
X-XSS-Protection: 1; mode=block
CF-Cache-Status: DYNAMIC
cf-request-id: 060af1a36f0000159f57394000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=mpca9vzMEulhGFXFihWF69IXRwNQofvbvKEMekNEnndgx8P%2FPc2753OC2VT9nIKQboD%2BQACM5HMqzCpbElhz1%2B0w3VPVBM%2BuyuQK5WbVE8E%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
CF-RAY: 5e8b5218bea6159f-EWR

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: lee.ns.cloudflare.com
may.ns.cloudflare.com
Owner Phone: REDACTED
Owner Fax: REDACTED
Owner Email: REDACTED
Admin Name: REDACTED
Admin Organization: REDACTED
Admin Phone: REDACTED
Admin Fax: REDACTED
Admin Email: REDACTED
Tech Name: REDACTED
Tech Organization: REDACTED
Tech Phone: REDACTED
Tech Fax: REDACTED
Tech Email: REDACTED
Billing Name: REDACTED
Billing Email: REDACTED
Full Whois: simple CO.ZA whois server
The CO.ZA simple whois server
&copy; Copyright ZACR 1995-2020
Use of this facility subject to theterms of site usage
Your query has generated the following reply:-


Search on dishonest (.co.za)
Match: One

Domain: dishonest.co.za

Accounting info....
Date |Type| Cost |Invoices are E-Mail to....|Paid Date |ICnt| TrkNo |Billing Info


Flashing RED indicates that payment has not been received - please
confirm with the ZACR accounting department, accounts@co.za, should this
not be according to your records. You have been sent 0 invoices/statements.


0a. lastupdate :
0b. emailsource : REDACTED
0c. emailposted :
0d. emailsubject :
0g. historycount :
0h. invoiceno :
0i. contracttype :
0j. rcsversion :
1a. domain : dishonest.co.za
1b. action :
1c. Registrar : Domains
2a. registrant : REDACTED
2b. registrantpostaladdress: REDACTED
2c. registrantstreetaddress: REDACTED
2d. amount : REDACTED
2e. paymenttype : REDACTED
2f. billingaccount : REDACTED
2g. billingemail : REDACTED
2i. invoiceaddress : REDACTED
2j. registrantphone : REDACTED
2k. registrantfax : REDACTED
2l. registrantemail : REDACTED
2n. vat : REDACTED
3b. cname :
3c. cnamesub1 :
3d. cnamesub2 :
3e. creationdate : 2020/10/09 09:13:04
4a. admin : REDACTED
4b. admintitle : REDACTED
4c. admincompany : REDACTED
4d. adminpostaladdr : REDACTED
4e. adminphone : REDACTED
4f. adminfax : REDACTED
4g. adminemail : REDACTED
4h. adminnic : REDACTED
5a. tec : REDACTED
5b. tectitle : REDACTED
5c. teccompany : REDACTED
5d. tecpostaladdr : REDACTED
5e. tecphone : REDACTED
5f. tecfax : REDACTED
5g. tecemail : REDACTED
5h. tecnic : REDACTED
6a. primnsfqdn : lee.ns.cloudflare.com
6b. primnsip :
6c. primnsipv6 :
6e. secns1fqdn : may.ns.cloudflare.com
6f. secns1ip :
6g. secns1ipv6 :
6i. secns2fqdn :
6j. secns2ip :
6k. secns2ipv6 :
6m. secns3fqdn :
6n. secns3ip :
6o. secns3ipv6 :
6q. secns4fqdn :
6r. secns4ip :
6s. secns4ipv6 :
8a. netblock1start :
8b. netblock1end :
8c. netblock2start :
8d. netblock2end :
8e. netblock3start :
8f. netblock3end :
9a. description1 :
9b. description2 :
9c. description3 :
9d. description4 :
9e. description5 :
9f. description6 :


Next Query - Domain name
.co.za
Please refer to the CO.ZA contact details should you have any problems

Nameservers

Name IP Address
lee.ns.cloudflare.com 172.64.33.129
may.ns.cloudflare.com 172.64.32.135
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address