dickiesb2b.com

dickiesb2b.com is SSL secured

Free website and domain report on dickiesb2b.com

Last Updated: 11th October, 2022 Update Now
Overview

Snoop Summary for dickiesb2b.com

This is a free and comprehensive report about dickiesb2b.com. The domain dickiesb2b.com is currently hosted on a server located in Washington, Virginia in United States with the IP address 40.117.176.117, where the local currency is USD and English is the local language. If dickiesb2b.com was to be sold it would possibly be worth $738 USD (based on the daily revenue potential of the website over a 24 month period). Dickiesb2b.com receives an estimated 350 unique visitors every day - a decent amount of traffic! This report was last updated 11th October, 2022.

About dickiesb2b.com

Site Preview: dickiesb2b.com dickiesb2b.com
Title: Application Login Screen
Description:
Keywords and Tags: business
Related Terms:
Fav Icon:
Age: Over 23 years old
Domain Created: 16th February, 2001
Domain Updated: 15th January, 2022
Domain Expires: 16th February, 2023
Review

Snoop Score

2/5

Valuation

$738 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,753,848
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: 350
Monthly Visitors: 10,653
Yearly Visitors: 127,750
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $30 USD
Yearly Revenue: $364 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: dickiesb2b.com 14
Domain Name: dickiesb2b 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.95 seconds
Load Time Comparison: Faster than 78% of sites

PageSpeed Insights

Avg. (All Categories) 60
Performance 95
Accessibility 58
Best Practices 75
SEO 70
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.dickiesb2b.com/
Updated: 11th October, 2022

1.32 seconds
First Contentful Paint (FCP)
87%
9%
4%

0.01 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
95

Performance

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

Metrics

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Speed Index — 1.1 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 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://dickiesb2b.com/
http/1.1
0
72.706999955699
196
0
302
text/html
https://www.dickiesb2b.com/
http/1.1
73.059999966063
439.07299998682
23547
23044
200
text/html
Document
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
http/1.1
445.50199998775
643.11599999201
31286
89476
200
application/javascript
Script
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
http/1.1
445.81199996173
609.38300000271
4332
10056
200
application/javascript
Script
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
http/1.1
446.15500001237
607.62899997644
15523
15260
200
application/javascript
Script
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
http/1.1
446.50499999989
573.98499996634
253933
253669
200
application/javascript
Script
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
http/1.1
446.74499996472
621.64899997879
27624
27376
200
text/css
Stylesheet
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
http/1.1
698.74799996614
1019.4669999764
342799
342547
200
image/jpeg
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)
442.925
9.88
651.428
15.64
667.094
31.29
698.397
9.27
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Dickiesb2b.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Dickiesb2b.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 6 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dickiesb2b.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27624
5753
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dickiesb2b.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 27 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dickiesb2b.com 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://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27624
27624
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 370 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://www.dickiesb2b.com/
367.008
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Dickiesb2b.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dickiesb2b.com/
190
https://www.dickiesb2b.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Dickiesb2b.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
0
Avoids enormous network payloads — Total size was 683 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
342799
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
253933
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
31286
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27624
https://www.dickiesb2b.com/
23547
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
15523
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
4332
http://dickiesb2b.com/
196
Avoids an excessive DOM size — 82 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
82
Maximum DOM Depth
8
Maximum Child Elements
10
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dickiesb2b.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time
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.
Minimizes main-thread work — 0.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
48.464
Other
21.669
Script Parsing & Compilation
7.994
Style & Layout
7.77
Parse HTML & CSS
6.363
Rendering
3.446
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 — 8 requests • 683 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
8
699240
Image
1
342799
Script
4
305074
Stylesheet
1
27624
Document
1
23547
Other
1
196
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.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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.
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.0 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.3 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 620 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dickiesb2b.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27624
150
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
31286
230
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
4332
150
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
15523
190
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
253933
430
Reduce unused JavaScript — Potential savings of 222 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.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
253933
226972
Efficiently encode images — Potential savings of 208 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
342547
213034
Serve images in next-gen formats — Potential savings of 273 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
342547
279403.15
Enable text compression — Potential savings of 229 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
253669
185883
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27376
22396
https://www.dickiesb2b.com/
23044
16703
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
15260
9395

Other

Serve static assets with an efficient cache policy — 6 resources found
Dickiesb2b.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
0
342799
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
0
253933
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
0
31286
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
0
27624
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
0
15523
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
0
4332
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dickiesb2b.com on mobile screens.
58

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<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.
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"]`
Dickiesb2b.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Internationalization and localization

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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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.
75

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

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 Request Resolution
http://dickiesb2b.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
High

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for dickiesb2b.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
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.

Mobile Friendly

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dickiesb2b.com on mobile screens.

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.

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

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dickiesb2b.com on mobile screens.
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) 51
Performance 66
Accessibility 58
Best Practices 75
SEO 58
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
66

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 110 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://dickiesb2b.com/
http/1.1
0
71.126000024378
196
0
302
text/html
https://www.dickiesb2b.com/
http/1.1
71.415000013076
208.44399998896
23547
23044
200
text/html
Document
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
http/1.1
219.79700005613
354.94800005108
89739
89476
200
application/javascript
Script
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
http/1.1
220.0919999741
272.69999997225
10318
10056
200
application/javascript
Script
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
http/1.1
220.58299998753
273.14100007061
15523
15260
200
application/javascript
Script
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
http/1.1
220.89100000449
488.86500007939
253933
253669
200
application/javascript
Script
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
http/1.1
221.23500006273
273.5930000199
27624
27376
200
text/css
Stylesheet
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
http/1.1
538.30899996683
749.76000003517
342799
342547
200
image/jpeg
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)
213.19
13.637
363.427
20.643
384.1
8.34
502.809
28.064
530.905
6.903
537.822
11.987
556.392
6.85
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Dickiesb2b.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Dickiesb2b.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 6 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dickiesb2b.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27624
5753
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dickiesb2b.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 27 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dickiesb2b.com 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://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27624
27624
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 140 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://www.dickiesb2b.com/
138.022
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Dickiesb2b.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dickiesb2b.com/
630
https://www.dickiesb2b.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Dickiesb2b.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
0
Avoids enormous network payloads — Total size was 746 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
342799
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
253933
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
89739
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27624
https://www.dickiesb2b.com/
23547
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
15523
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
10318
http://dickiesb2b.com/
196
Avoids an excessive DOM size — 82 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
82
Maximum DOM Depth
8
Maximum Child Elements
10
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dickiesb2b.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.dickiesb2b.com/
170.084
23.268
11.952
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
155.304
135.644
7.04
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
112.256
90.032
14.664
Unattributable
80.652
15.336
0.84
Minimizes main-thread work — 0.5 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
286.284
Other
118.188
Style & Layout
40.5
Script Parsing & Compilation
36.76
Parse HTML & CSS
31.136
Rendering
29.972
Garbage Collection
4.568
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 — 8 requests • 746 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
8
763679
Script
4
369513
Image
1
342799
Stylesheet
1
27624
Document
1
23547
Other
1
196
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.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
4260
112
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
2370
83
https://www.dickiesb2b.com/
1560
55
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.
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.3 s
The time taken for the page to become fully interactive.
Speed Index — 4.3 s
The time taken for the page contents to be visibly populated.

Metrics

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

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 2,730 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dickiesb2b.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27624
630
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
89739
1680
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
10318
780
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
15523
780
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
253933
2580
Reduce unused JavaScript — Potential savings of 274 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.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
253933
226972
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
89739
53579
Efficiently encode images — Potential savings of 208 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
342547
213034
Serve images in next-gen formats — Potential savings of 273 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
342547
279403.15
Enable text compression — Potential savings of 292 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
253669
185883
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
89476
58526
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
27376
22396
https://www.dickiesb2b.com/
23044
16702
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
15260
9395
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
10056
6042
Serve static assets with an efficient cache policy — 6 resources found
Dickiesb2b.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.dickiesb2b.com/Img/VendorHomePage/Dickies_Home.jpg
0
342799
https://www.dickiesb2b.com/assets/script/jquery-ui-1.12.1.min.js
0
253933
https://www.dickiesb2b.com/assets/script/jquery-3.5.1.min.js
0
89739
https://www.dickiesb2b.com/assets/css/jquery_ui_themes/smoothness/jquery-ui-1.7.2.custom.css
0
27624
https://www.dickiesb2b.com/assets/script/jquery.form-3.51.js
0
15523
https://www.dickiesb2b.com/assets/script/jquery-migrate-1.4.1.min.js
0
10318
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dickiesb2b.com on mobile screens.
First Contentful Paint (3G) — 8989.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
58

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<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.
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"]`
Dickiesb2b.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Internationalization and localization

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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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.
75

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

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 Request Resolution
http://dickiesb2b.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
High

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for dickiesb2b.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dickiesb2b.com on mobile screens.
Document doesn't use 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 not 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 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.

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

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

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
Content is not 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dickiesb2b.com on mobile screens.
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: 40.117.176.117
Continent: North America
Country: United States
United States Flag
Region: Virginia
City: Washington
Longitude: -78.1539
Latitude: 38.7095
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Microsoft Corporation
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
MarkMonitor, Inc. 172.64.148.104
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: www.dickiesb2b.com
Issued By: RapidSSL Global TLS RSA4096 SHA256 2022 CA1
Valid From: 22nd September, 2022
Valid To: 22nd September, 2023
Subject: CN = www.dickiesb2b.com
Hash: 48f2f54d
Issuer: CN = RapidSSL Global TLS RSA4096 SHA256 2022 CA1
O = DigiCert, Inc.
S = US
Version: 2
Serial Number: 8869628246932535132158635385090773241
Serial Number (Hex): 06AC3A6F7C4F4A9A7B57E2ED751490F9
Valid From: 22nd September, 2024
Valid To: 22nd September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:F0:9C:85:FD:A2:9F:7D:8F:C9:68:BB:D5:D4:89:4D:1D:BE:D3:90:FF
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/RapidSSLGlobalTLSRSA4096SHA2562022CA1.crl

Full Name:
URI:http://crl4.digicert.com/RapidSSLGlobalTLSRSA4096SHA2562022CA1.crl

Certificate Policies: Policy: 2.23.140.1.2.1
CPS: http://www.digicert.com/CPS

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Sep 22 22:47:31.406 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A9:C5:23:3E:D5:4C:5D:23:31:82:FE:
19:BF:91:44:D5:70:21:4E:B6:25:90:34:E8:E6:FA:3D:
0F:2B:79:D3:66:02:21:00:88:C4:61:E4:10:9C:A6:2E:
ED:F8:D6:46:14:EF:33:3C:7C:DE:82:F3:3C:21:46:E0:
C3:8E:95:C8:41:63:D7:A6
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Sep 22 22:47:31.464 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:2B:AF:BE:47:B5:2A:5E:C1:95:1E:CB:F2:
1D:F1:C2:D5:35:81:BB:E0:2D:E5:AA:EF:A2:CB:5A:22:
FE:B7:5F:61:02:20:77:DF:4E:A2:6E:7A:82:33:74:7B:
C4:36:E2:95:22:BB:5A:D0:86:40:C3:A6:F0:27:09:34:
78:1C:44:02:65:29
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Sep 22 22:47:31.477 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A1:0F:3E:54:50:F6:0E:B3:CA:21:71:
3D:E6:69:89:61:BE:80:C2:5D:91:6D:D2:78:4B:E9:AE:
66:89:C2:BD:42:02:21:00:8E:15:0F:DA:39:32:40:90:
08:74:6A:AA:8C:BD:48:01:85:AB:65:9C:A8:C6:13:65:
60:5F:43:65:32:16:89:55
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.dickiesb2b.com
Technical

DNS Lookup

NS Records

Host Nameserver Class TTL
dickiesb2b.com. ns1.vfc.com. IN 21600
dickiesb2b.com. ns2.vfc.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
dickiesb2b.com. ns1.vfc.com. vfc_domain_admin.vfc.com. 21600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html;charset=UTF-8
Server: Microsoft-IIS/10.0
Date: 11th October, 2022
Transfer-Encoding: chunked
Set-Cookie: *
X-Frame-Options: DENY

Whois Lookup

Created: 16th February, 2001
Changed: 15th January, 2022
Expires: 16th February, 2023
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
Nameservers: dns1.vfc.com
dns2.vfc.com
Owner Organization: W-D Apparel Company, LLC
Owner State: DE
Owner Country: US
Owner Email: Select Request Email Form at https://domains.markmonitor.com/whois/dickiesb2b.com
Admin Organization: W-D Apparel Company, LLC
Admin State: DE
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/dickiesb2b.com
Tech Organization: W-D Apparel Company, LLC
Tech State: DE
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/dickiesb2b.com
Full Whois: Domain Name: dickiesb2b.com
Registry Domain ID: 62142579_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2022-01-15T09:30:06+0000
Creation Date: 2001-02-16T19:08:48+0000
Registrar Registration Expiration Date: 2023-02-16T00:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895770
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registrant Organization: W-D Apparel Company, LLC
Registrant State/Province: DE
Registrant Country: US
Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/dickiesb2b.com
Admin Organization: W-D Apparel Company, LLC
Admin State/Province: DE
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/dickiesb2b.com
Tech Organization: W-D Apparel Company, LLC
Tech State/Province: DE
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/dickiesb2b.com
Name Server: dns1.vfc.com
Name Server: dns2.vfc.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-10-11T16:21:06+0000 <<<

For more information on WHOIS status codes, please visit:
https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
(1) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
(2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

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

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220

Nameservers

Name IP Address
dns1.vfc.com 167.64.243.37
dns2.vfc.com 167.64.143.37
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$13,910 USD 2/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address