dexter.com

dexter.com is SSL secured

Free website and domain report on dexter.com

Last Updated: 26th January, 2023 Update Now
Overview

Snoop Summary for dexter.com

This is a free and comprehensive report about dexter.com. Dexter.com is hosted in United States on a server with an IP address of 74.85.140.65, where USD is the local currency and the local language is English. Our records indicate that dexter.com is privately registered by Domains By Proxy, LLC. Dexter.com has the potential to be earning an estimated $2 USD per day from advertising revenue. If dexter.com was to be sold it would possibly be worth $1,477 USD (based on the daily revenue potential of the website over a 24 month period). Dexter.com receives an estimated 705 unique visitors every day - a decent amount of traffic! This report was last updated 26th January, 2023.

About dexter.com

Site Preview: dexter.com dexter.com
Title: www.dexterlaundry.com
Description: The Dexter Company is an employee owned manufacturer based in Fairfield, Iowa, USA. Founded in 1894, the company has grown to offer a full line of front load washers, drying tumblers, Easy Cardä systems, and equipment financing serving the on-premise and commercial laundry industries. Learn more at www.dexterlaundry.com or call 1-800-524-2954 to find your local Dexter distributor.
Keywords and Tags: hardware, software
Related Terms: bernie dexter, dexter, dexter new blood, dexter shoes, drying, plain washers manufacturer, washers
Fav Icon:
Age: Over 26 years old
Domain Created: 25th May, 1998
Domain Updated: 7th January, 2020
Domain Expires: 24th May, 2025
Review

Snoop Score

2/5

Valuation

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

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 962,355
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: 705
Monthly Visitors: 21,458
Yearly Visitors: 257,325
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $2 USD
Monthly Revenue: $61 USD
Yearly Revenue: $733 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: dexter.com 10
Domain Name: dexter 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.45 seconds
Load Time Comparison: Faster than 93% of sites

PageSpeed Insights

Avg. (All Categories) 65
Performance 78
Accessibility 45
Best Practices 73
SEO 82
Progressive Web App 45
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://dexter.com/
Updated: 6th April, 2021

3.44 seconds
First Contentful Paint (FCP)
19%
51%
30%

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

Simulate loading on desktop
78

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.1 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 2.0 s
The time taken for the page's main thread to be quiet enough to handle input.
Estimated Input Latency — 20 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 dexter.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://dexter.com/
http/1.1
0
118.79999982193
398
0
302
text/html
https://dexter.com/
http/1.1
119.59199979901
415.51599977538
4862
14965
200
text/html
Document
https://dexter.com/css/global.css
http/1.1
481.1809998937
866.14299984649
77753
358056
200
text/css
Stylesheet
https://dexter.com/js/modernizr.min.js
http/1.1
481.49199970067
719.0629998222
20953
20512
200
text/javascript
Script
https://use.typekit.net/ppp2xka.css
h2
481.70799994841
511.23599987477
1125
3219
200
text/css
Stylesheet
https://www.google.com/recaptcha/api.js
h2
481.89399996772
490.11899996549
1152
850
200
text/javascript
Script
https://dexter.com/images/icons/dexter.svg
http/1.1
868.88800002635
1165.648999624
7020
22371
200
image/svg+xml
Image
https://dexter.com/images/global/made-in-usa.png
http/1.1
1069.0069999546
1366.1199999042
19371
18951
200
image/png
Image
https://dexter.com/js/global.js
http/1.1
767.31499982998
1167.5069998018
208268
207825
200
text/javascript
Script
https://p.typekit.net/p.css?s=1&k=ppp2xka&ht=tk&f=36599.36601.36602.36608&a=12234733&app=typekit&e=css
h2
998.96799959242
1065.0989999995
317
5
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/539Evs44yecoSf-lkJBQzKKj/recaptcha__en.js
h2
1069.2739998922
1090.7499999739
133467
340607
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-WJLSBFK
h2
1069.4979997352
1099.0909999236
37002
108007
200
application/javascript
Script
https://use.typekit.net/af/3bd84d/00000000000000003b9b0ee4/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3
h2
1076.6469999216
1100.8389997296
36986
36668
200
application/font-woff2
Font
https://dexter.com/images/homepage/lifestyle-waterloo-024.jpg
http/1.1
1079.7819998115
1399.7339997441
277770
277347
200
image/jpeg
Image
https://dexter.com/images/homepage/lifestyle_o-series_001.jpg
http/1.1
1080.0089999102
1384.977999609
144010
143587
200
image/jpeg
Image
https://use.typekit.net/af/359d41/00000000000000003b9b0eea/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
h2
1086.5039997734
1166.7859996669
37238
36920
200
application/font-woff2
Font
https://dexter.com/fonts/fontawesome-webfont.woff2
http/1.1
1087.7559999935
1366.9129996561
77632
77160
200
text/plain
Font
https://use.typekit.net/af/b15395/00000000000000003b9b0ee1/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3
h2
1087.9999999888
1166.2619998679
37034
36716
200
application/font-woff2
Font
https://dexter.com/images/global/homepage-machine.png
http/1.1
1397.8129997849
1793.5219998471
846685
846263
200
image/png
Image
https://dexter.com/images/global/homepage-machine2.png
http/1.1
1398.2459995896
1780.1279998384
779747
779325
200
image/png
Image
https://dexter.com/images/backgrounds/homepage.jpg
http/1.1
1398.4889998101
1765.3989996761
109121
108698
200
image/jpeg
Image
https://dexter.com/images/backgrounds/homepage3.jpg
http/1.1
1399.0029999986
1966.3279997185
35924
35503
200
image/jpeg
Image
https://dexter.com/images/global/dext-live.png
http/1.1
1401.4769997448
1766.6070000269
23273
22853
200
image/png
Image
https://dexter.com/images/homepage/lifestyle_o-series_001_v2.jpg
http/1.1
1401.7619998194
1768.7109997496
145384
144961
200
image/jpeg
Image
https://dexter.com/images/backgrounds/homepage-events.jpg
http/1.1
1401.8989996985
1703.8669995964
165651
165228
200
image/jpeg
Image
https://dexter.com/images/global/homepage/Lifestyle_Waterloo_007.jpg
http/1.1
1402.0329997875
1771.7140000314
220190
219767
200
image/jpeg
Image
https://dexter.com/images/icons/callout-logo.svg
http/1.1
1402.1729999222
1619.265999645
1648
2338
200
image/svg+xml
Image
https://dexter.com/images/global/footer-img3.png
http/1.1
1402.3179998621
1770.7109996118
187215
186793
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
1402.5299996138
1408.0209997483
20093
48759
200
text/javascript
Script
https://pixel.mathtag.com/event/js?mt_id=1441414&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
1570.3069996089
1699.3370000273
1067
597
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j89&a=1458873296&t=pageview&_s=1&dl=https%3A%2F%2Fdexter.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20-%20Dexter%20Laundry&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAABAAAAAC~&jid=1604890714&gjid=821689715&cid=268891974.1617743863&tid=UA-41719634-1&_gid=785423366.1617743863&_r=1&_slc=1&z=829924738
h2
1984.5839999616
1989.8119997233
616
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j89&tid=UA-41719634-1&cid=268891974.1617743863&jid=1604890714&gjid=821689715&_gid=785423366.1617743863&_u=IEBAAAAAAAAAAC~&z=1327221568
h2
2070.7419998944
2075.6679996848
686
1
200
text/plain
XHR
https://pixel.mathtag.com/event/js?mt_id=1441415&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
2085.1239999756
2272.978999652
920
597
200
text/javascript
Script
https://pixel.mathtag.com/misc/img?mm_bnc&bcdv=0
http/1.1
2102.1010000259
2371.8159999698
479
43
200
image/gif
Image
https://pixel.mathtag.com/event/js?mt_id=1441416&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
2285.5069995858
2565.4439995997
921
597
200
text/javascript
Script
https://pixel.mathtag.com/event/js?mt_id=1441417&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
2574.2559996434
2866.8289999478
921
597
200
text/javascript
Script
https://pixel.mathtag.com/event/js?mt_id=1441418&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
2872.7229996584
3065.0919997133
921
597
200
text/javascript
Script
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)
548.735
10.57
802.97
45.955
950.576
20.182
970.848
110.223
1155.38
112.631
1271.454
5.288
1276.756
7.093
1288.698
60.054
1350.554
10.797
1361.573
23.666
1386.889
177.708
1565.065
5.016
1570.127
77.804
1648.038
28.216
1686.853
93.749
1780.703
8.481
1792.432
63.718
1859.175
207.824
2084.454
65.545
2150.711
5.769
2156.72
9.345
2167.673
8.439
2249.567
20.791
2351.983
7.217
2360.457
5.093
2485.44
63.876
2779.388
68.227
3083.62
63.862
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images — Potential savings of 19 KiB
Time to Interactive can be slowed down by resources on the page. Dexter.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dexter.com/images/global/made-in-usa.png
18951
18951
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dexter.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 48 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dexter.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://dexter.com/js/global.js
208268
45484
https://dexter.com/js/modernizr.min.js
20953
3311
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 300 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://dexter.com/
296.921
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Dexter.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dexter.com/
190
https://dexter.com/
0
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 an excessive DOM size — 264 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
264
Maximum DOM Depth
13
Maximum Child Elements
10
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dexter.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.5 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://dexter.com/js/global.js
484.554
61.826
62.224
https://www.google-analytics.com/analytics.js
274.343
268.214
1.683
https://dexter.com/
268.923
4.848
1.934
Unattributable
262.925
1.369
0.192
https://www.googletagmanager.com/gtm.js?id=GTM-WJLSBFK
112.215
105.176
3.503
https://dexter.com/js/modernizr.min.js
109.522
32.221
1.676
Minimizes main-thread work — 1.6 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
494.271
Other
461.731
Style & Layout
339.252
Rendering
160.626
Script Parsing & Compilation
82.78
Parse HTML & CSS
26.993
Garbage Collection
4.289
Keep request counts low and transfer sizes small — 37 requests • 3,578 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
37
3663820
Image
15
2963488
Script
11
425685
Font
4
188890
Stylesheet
3
79195
Document
1
4862
Other
3
1700
Media
0
0
Third-party
17
310945
Minimize third-party usage — Third-party code blocked the main thread for 190 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
20709
167.483
37002
26.934
133467
0
112700
0
5229
0
1152
0
686
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
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.0010760431930253
0.00095645340800353
0.00052891661564859
0.00026937499749089
0.00017173649360684
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 — 9 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google-analytics.com/analytics.js
1969
208
https://dexter.com/js/global.js
1610
89
https://www.googletagmanager.com/gtm.js?id=GTM-WJLSBFK
969
78
https://dexter.com/js/global.js
1831
68
https://www.google-analytics.com/analytics.js
2177
66
Unattributable
296
64
Unattributable
236
60
https://dexter.com/
374
56
https://dexter.com/js/modernizr.min.js
760
55
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element

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 — 1.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.3 s
The timing of the largest text or image that is painted.
Total Blocking Time — 170 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

Max Potential First Input Delay — 210 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 510 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dexter.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://dexter.com/css/global.css
77753
310
https://use.typekit.net/ppp2xka.css
1125
230
https://dexter.com/js/modernizr.min.js
20953
190
https://www.google.com/recaptcha/api.js
1152
230
Properly size images — Potential savings of 899 KiB
Images can slow down the page's load time. Dexter.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dexter.com/images/global/homepage-machine.png
846263
458883
https://dexter.com/images/global/homepage-machine2.png
779325
422586
https://dexter.com/images/global/dext-live.png
22853
21362
https://dexter.com/images/global/made-in-usa.png
18951
18080
Remove unused CSS — Potential savings of 69 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dexter.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://dexter.com/css/global.css
77753
70481
Remove unused JavaScript — Potential savings of 229 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://dexter.com/js/global.js
208268
130269
https://www.gstatic.com/recaptcha/releases/539Evs44yecoSf-lkJBQzKKj/recaptcha__en.js
133467
104641
Enable text compression — Potential savings of 154 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://dexter.com/js/global.js
207825
144478
https://dexter.com/js/modernizr.min.js
20512
12742
Preload key requests — Potential savings of 430 ms
Key requests can be preloaded by using '<link rel=preload>'. Dexter.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://dexter.com/fonts/fontawesome-webfont.woff2
430
Preload Largest Contentful Paint image — Potential savings of 230 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://dexter.com/images/global/homepage-machine2.png
233

Diagnostics

Avoid enormous network payloads — Total size was 3,578 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://dexter.com/images/global/homepage-machine.png
846685
https://dexter.com/images/global/homepage-machine2.png
779747
https://dexter.com/images/homepage/lifestyle-waterloo-024.jpg
277770
https://dexter.com/images/global/homepage/Lifestyle_Waterloo_007.jpg
220190
https://dexter.com/js/global.js
208268
https://dexter.com/images/global/footer-img3.png
187215
https://dexter.com/images/backgrounds/homepage-events.jpg
165651
https://dexter.com/images/homepage/lifestyle_o-series_001_v2.jpg
145384
https://dexter.com/images/homepage/lifestyle_o-series_001.jpg
144010
https://www.gstatic.com/recaptcha/releases/539Evs44yecoSf-lkJBQzKKj/recaptcha__en.js
133467

Opportunities

Serve images in next-gen formats — Potential savings of 2,013 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dexter.com/images/global/homepage-machine.png
846263
795647
https://dexter.com/images/global/homepage-machine2.png
779325
736849
https://dexter.com/images/global/footer-img3.png
186793
172541
https://dexter.com/images/homepage/lifestyle-waterloo-024.jpg
277347
92543
https://dexter.com/images/homepage/lifestyle_o-series_001.jpg
143587
69289
https://dexter.com/images/backgrounds/homepage-events.jpg
165228
68726
https://dexter.com/images/homepage/lifestyle_o-series_001_v2.jpg
144961
68179
https://dexter.com/images/global/homepage/Lifestyle_Waterloo_007.jpg
219767
57929

Diagnostics

Serve static assets with an efficient cache policy — 20 resources found
Dexter.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://dexter.com/images/global/homepage-machine.png
0
846685
https://dexter.com/images/global/homepage-machine2.png
0
779747
https://dexter.com/images/homepage/lifestyle-waterloo-024.jpg
0
277770
https://dexter.com/images/global/homepage/Lifestyle_Waterloo_007.jpg
0
220190
https://dexter.com/js/global.js
0
208268
https://dexter.com/images/global/footer-img3.png
0
187215
https://dexter.com/images/backgrounds/homepage-events.jpg
0
165651
https://dexter.com/images/homepage/lifestyle_o-series_001_v2.jpg
0
145384
https://dexter.com/images/homepage/lifestyle_o-series_001.jpg
0
144010
https://dexter.com/images/backgrounds/homepage.jpg
0
109121
https://dexter.com/css/global.css
0
77753
https://dexter.com/fonts/fontawesome-webfont.woff2
0
77632
https://dexter.com/images/backgrounds/homepage3.jpg
0
35924
https://dexter.com/images/global/dext-live.png
0
23273
https://dexter.com/js/modernizr.min.js
0
20953
https://dexter.com/images/global/made-in-usa.png
0
19371
https://dexter.com/images/icons/dexter.svg
0
7020
https://dexter.com/images/icons/callout-logo.svg
0
1648
https://www.google-analytics.com/analytics.js
7200000
20093
https://p.typekit.net/p.css?s=1&k=ppp2xka&ht=tk&f=36599.36601.36602.36608&a=12234733&app=typekit&e=css
604800000
317
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://use.typekit.net/af/3bd84d/00000000000000003b9b0ee4/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3
24.191999807954
https://use.typekit.net/af/359d41/00000000000000003b9b0eea/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
80.281999893486
https://dexter.com/fonts/fontawesome-webfont.woff2
279.15699966252
https://use.typekit.net/af/b15395/00000000000000003b9b0ee1/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3
78.261999879032
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://dexter.com/images/global/dext-live.png
img
https://dexter.com/images/icons/dexter.svg
img
https://dexter.com/images/global/made-in-usa.png
img
45

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dexter.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.

Names and labels

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

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

Best practices

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

Audio and video

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

ARIA

ARIA IDs are not unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Failing Elements

Names and labels

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

Best practices

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

Manual Checks

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

Best Practices

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

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.
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
1.8.2
Modernizr
2.6.1
Underscore
1.8.2
yepnope
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.
URL Map URL
https://dexter.com/js/global.js
https://dexter.com/js/underscore-min.map
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://dexter.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 6 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
6
Medium

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://dexter.com/images/global/homepage-machine.png
500 x 720 (0.69)
749 x 1050 (0.71)
https://dexter.com/images/global/homepage-machine2.png
500 x 720 (0.69)
749 x 1050 (0.71)
82

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dexter.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img

Manual Checks

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

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

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.
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 dexter.com on mobile screens.
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.

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
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) 70
Performance 63
Accessibility 66
Best Practices 80
SEO 89
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://dexter.com/
Updated: 6th April, 2021

4.96 seconds
First Contentful Paint (FCP)
13%
28%
59%

0.02 seconds
First Input Delay (FID)
96%
4%
0%

Simulate loading on mobile
63

Performance

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

Metrics

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

Max Potential First Input Delay — 80 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive dexter.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://dexter.com/
http/1.1
0
44.088000082411
398
0
302
text/html
https://dexter.com/
http/1.1
44.672999996692
258.03000002634
4862
14965
200
text/html
Document
https://dexter.com/css/global.css
http/1.1
270.50500002224
574.18500003405
77753
358056
200
text/css
Stylesheet
https://dexter.com/js/modernizr.min.js
http/1.1
270.63600008842
511.1480000196
20953
20512
200
text/javascript
Script
https://use.typekit.net/ppp2xka.css
h2
270.8430000348
294.28400006145
1125
3219
200
text/css
Stylesheet
https://www.google.com/recaptcha/api.js
h2
271.11400000285
275.73100000154
1152
850
200
text/javascript
Script
https://dexter.com/images/icons/dexter.svg
http/1.1
576.92900008988
781.74500004388
7020
22371
200
image/svg+xml
Image
https://dexter.com/images/global/made-in-usa.png
http/1.1
734.94100000244
1002.5190000888
19371
18951
200
image/png
Image
https://dexter.com/js/global.js
http/1.1
512.71100004669
898.55000004172
208268
207825
200
text/javascript
Script
https://p.typekit.net/p.css?s=1&k=ppp2xka&ht=tk&f=36599.36601.36602.36608&a=12234733&app=typekit&e=css
h2
629.12000005599
731.29700007848
317
5
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/539Evs44yecoSf-lkJBQzKKj/recaptcha__en.js
h2
735.175000038
745.71799999103
133467
340607
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-WJLSBFK
h2
735.4120000964
755.98100002389
37041
108247
200
application/javascript
Script
https://dexter.com/images/homepage/lifestyle-waterloo-024.jpg
http/1.1
739.95499999728
1068.9680000069
277770
277347
200
image/jpeg
Image
https://dexter.com/images/homepage/lifestyle_o-series_001.jpg
http/1.1
740.48800009768
1042.0710000908
144010
143587
200
image/jpeg
Image
https://use.typekit.net/af/3bd84d/00000000000000003b9b0ee4/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3
h2
742.4090000568
763.16600001883
36986
36668
200
application/font-woff2
Font
https://use.typekit.net/af/359d41/00000000000000003b9b0eea/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
h2
743.13100008294
782.33700001147
37238
36920
200
application/font-woff2
Font
https://dexter.com/fonts/fontawesome-webfont.woff2
http/1.1
743.28600009903
1008.6170000723
77632
77160
200
text/plain
Font
https://use.typekit.net/af/b15395/00000000000000003b9b0ee1/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3
h2
743.70900006033
783.15200004727
37034
36716
200
application/font-woff2
Font
https://dexter.com/images/global/homepage-machine.png
http/1.1
935.87100005243
1367.2830000287
846685
846263
200
image/png
Image
https://dexter.com/images/global/homepage-machine2.png
http/1.1
935.98100007512
1382.127000019
779747
779325
200
image/png
Image
https://dexter.com/images/backgrounds/homepage.jpg
http/1.1
936.10500008799
1294.2780000158
109121
108698
200
image/jpeg
Image
https://dexter.com/images/backgrounds/homepage3.jpg
http/1.1
936.2770000007
1249.850000022
35924
35503
200
image/jpeg
Image
https://dexter.com/images/global/dext-live.png
http/1.1
936.42600008752
1208.5450000595
23273
22853
200
image/png
Image
https://dexter.com/images/homepage/lifestyle_o-series_001_v2.jpg
http/1.1
936.57700007316
1297.8860000148
145384
144961
200
image/jpeg
Image
https://dexter.com/images/backgrounds/homepage-events.jpg
http/1.1
936.7510000011
1312.4240000034
165651
165228
200
image/jpeg
Image
https://dexter.com/images/global/homepage/Lifestyle_Waterloo_007.jpg
http/1.1
936.90299999435
1292.4880000064
220190
219767
200
image/jpeg
Image
https://dexter.com/images/icons/callout-logo.svg
http/1.1
937.08300008439
1192.2750000376
1648
2338
200
image/svg+xml
Image
https://dexter.com/images/global/footer-img3.png
http/1.1
937.21600004937
1285.8460000716
187215
186793
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
937.46700009797
941.79700000677
20093
48759
200
text/javascript
Script
https://pixel.mathtag.com/event/js?mt_id=1441414&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
962.89200009778
1178.8840000518
1067
597
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j89&a=1095463152&t=pageview&_s=1&dl=https%3A%2F%2Fdexter.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20-%20Dexter%20Laundry&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAAABAAAAAC~&jid=1042127886&gjid=1441209173&cid=1100417175.1617743900&tid=UA-41719634-1&_gid=2022264550.1617743900&_r=1&_slc=1&z=181158884
h2
978.30600000452
981.98500007857
616
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j89&tid=UA-41719634-1&cid=1100417175.1617743900&jid=1042127886&gjid=1441209173&_gid=2022264550.1617743900&_u=IEBAAAAAAAAAAC~&z=1869107720
h2
1003.2130000181
1010.2980000665
686
1
200
text/plain
XHR
https://pixel.mathtag.com/event/js?mt_id=1441415&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
1184.1100000311
1422.2790000495
921
597
200
text/javascript
Script
https://pixel.mathtag.com/misc/img?mm_bnc&bcdv=0
http/1.1
1184.3910000753
1307.7439999906
479
43
200
image/gif
Image
https://pixel.mathtag.com/event/js?mt_id=1441416&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
1432.1370000253
1646.007000003
921
597
200
text/javascript
Script
https://pixel.mathtag.com/event/js?mt_id=1441417&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
1654.576000059
1781.2430000631
920
597
200
text/javascript
Script
https://pixel.mathtag.com/event/js?mt_id=1441418&mt_adid=188448&mt_exem=&mt_excl=&v1=&v2=&v3=&s1=&s2=&s3=
http/1.1
1786.8940000189
2190.0930000702
921
597
200
text/javascript
Script
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)
298.128
6.902
614.003
12.612
626.695
40.143
774.361
36.022
812.685
5.431
818.176
10.54
829.379
6.181
840.286
9.202
851.12
7.6
858.84
19.18
878.035
5.357
946.461
41.274
992.023
6.172
999.26
17.209
1016.519
22.318
1047.321
7.936
1251.241
5.605
1462.009
6.483
2229.861
5.968
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 19 KiB
Images can slow down the page's load time. Dexter.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dexter.com/images/global/dext-live.png
22853
12577
https://dexter.com/images/global/made-in-usa.png
18951
7021
Defer offscreen images — Potential savings of 19 KiB
Time to Interactive can be slowed down by resources on the page. Dexter.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dexter.com/images/global/made-in-usa.png
18951
18951
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dexter.com should consider minifying CSS files.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 210 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://dexter.com/
214.354
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Dexter.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dexter.com/
630
https://dexter.com/
0
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 an excessive DOM size — 264 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
264
Maximum DOM Depth
13
Maximum Child Elements
10
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dexter.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.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://dexter.com/
637.704
9.472
4.464
Unattributable
284.552
3.388
0.776
https://dexter.com/js/global.js
187.768
138.192
17.272
https://dexter.com/js/modernizr.min.js
157.756
111.528
5.768
https://www.googletagmanager.com/gtm.js?id=GTM-WJLSBFK
149.348
127.484
11.4
https://www.gstatic.com/recaptcha/releases/539Evs44yecoSf-lkJBQzKKj/recaptcha__en.js
83.316
47.652
29.932
https://www.google-analytics.com/analytics.js
79.596
66.056
4.908
https://dexter.com/css/global.css
50.448
0
0
Minimizes main-thread work — 1.7 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
519.204
Other
518.404
Style & Layout
286.684
Rendering
185.756
Script Parsing & Compilation
82.328
Parse HTML & CSS
69.636
Keep request counts low and transfer sizes small — 37 requests • 3,578 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
37
3663859
Image
15
2963488
Script
11
425724
Font
4
188890
Stylesheet
3
79195
Document
1
4862
Other
3
1700
Media
0
0
Third-party
17
310984
Minimize third-party usage — Third-party code blocked the main thread for 10 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
20709
11.056
133467
0
112700
0
37041
0
5229
0
1152
0
686
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
div
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
div
0.13742759663952
0.0053434058981726
div
0.004443359375
0.0040457787879197
0.0040457787879197
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 — 7 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://dexter.com/
1208
89
https://dexter.com/js/global.js
5910
83
https://dexter.com/js/modernizr.min.js
3270
80
https://www.gstatic.com/recaptcha/releases/539Evs44yecoSf-lkJBQzKKj/recaptcha__en.js
4791
77
https://dexter.com/
1115
72
https://www.google-analytics.com/analytics.js
6923
69
https://dexter.com/css/global.css
2640
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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 — 2.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.5 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 6.9 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.156
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 3.2 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5600 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Minify JavaScript — Potential savings of 48 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dexter.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://dexter.com/js/global.js
208268
45484
https://dexter.com/js/modernizr.min.js
20953
3311
Remove unused CSS — Potential savings of 67 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dexter.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://dexter.com/css/global.css
77753
68798
Efficiently encode images — Potential savings of 29 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dexter.com/images/backgrounds/homepage.jpg
108698
30118
Enable text compression — Potential savings of 154 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://dexter.com/js/global.js
207825
144478
https://dexter.com/js/modernizr.min.js
20512
12742

Diagnostics

Avoid enormous network payloads — Total size was 3,578 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://dexter.com/images/global/homepage-machine.png
846685
https://dexter.com/images/global/homepage-machine2.png
779747
https://dexter.com/images/homepage/lifestyle-waterloo-024.jpg
277770
https://dexter.com/images/global/homepage/Lifestyle_Waterloo_007.jpg
220190
https://dexter.com/js/global.js
208268
https://dexter.com/images/global/footer-img3.png
187215
https://dexter.com/images/backgrounds/homepage-events.jpg
165651
https://dexter.com/images/homepage/lifestyle_o-series_001_v2.jpg
145384
https://dexter.com/images/homepage/lifestyle_o-series_001.jpg
144010
https://www.gstatic.com/recaptcha/releases/539Evs44yecoSf-lkJBQzKKj/recaptcha__en.js
133467

Metrics

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

Other

First CPU Idle — 6.7 s
The time taken for the page's main thread to be quiet enough to handle input.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,640 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dexter.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://dexter.com/css/global.css
77753
1530
https://use.typekit.net/ppp2xka.css
1125
780
https://dexter.com/js/modernizr.min.js
20953
780
https://www.google.com/recaptcha/api.js
1152
780
Remove unused JavaScript — Potential savings of 233 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://dexter.com/js/global.js
208268
134231
https://www.gstatic.com/recaptcha/releases/539Evs44yecoSf-lkJBQzKKj/recaptcha__en.js
133467
104632
Serve images in next-gen formats — Potential savings of 2,128 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://dexter.com/images/global/homepage-machine.png
846263
795647
https://dexter.com/images/global/homepage-machine2.png
779325
736849
https://dexter.com/images/global/footer-img3.png
186793
172541
https://dexter.com/images/homepage/lifestyle-waterloo-024.jpg
277347
92543
https://dexter.com/images/backgrounds/homepage.jpg
108698
92488
https://dexter.com/images/homepage/lifestyle_o-series_001.jpg
143587
69289
https://dexter.com/images/backgrounds/homepage-events.jpg
165228
68726
https://dexter.com/images/homepage/lifestyle_o-series_001_v2.jpg
144961
68179
https://dexter.com/images/global/homepage/Lifestyle_Waterloo_007.jpg
219767
57929
https://dexter.com/images/backgrounds/homepage3.jpg
35503
24769
Preload key requests — Potential savings of 2,130 ms
Key requests can be preloaded by using '<link rel=preload>'. Dexter.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://dexter.com/fonts/fontawesome-webfont.woff2
2130
Preload Largest Contentful Paint image — Potential savings of 3,780 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://dexter.com/images/backgrounds/homepage.jpg
3780

Diagnostics

Serve static assets with an efficient cache policy — 20 resources found
Dexter.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://dexter.com/images/global/homepage-machine.png
0
846685
https://dexter.com/images/global/homepage-machine2.png
0
779747
https://dexter.com/images/homepage/lifestyle-waterloo-024.jpg
0
277770
https://dexter.com/images/global/homepage/Lifestyle_Waterloo_007.jpg
0
220190
https://dexter.com/js/global.js
0
208268
https://dexter.com/images/global/footer-img3.png
0
187215
https://dexter.com/images/backgrounds/homepage-events.jpg
0
165651
https://dexter.com/images/homepage/lifestyle_o-series_001_v2.jpg
0
145384
https://dexter.com/images/homepage/lifestyle_o-series_001.jpg
0
144010
https://dexter.com/images/backgrounds/homepage.jpg
0
109121
https://dexter.com/css/global.css
0
77753
https://dexter.com/fonts/fontawesome-webfont.woff2
0
77632
https://dexter.com/images/backgrounds/homepage3.jpg
0
35924
https://dexter.com/images/global/dext-live.png
0
23273
https://dexter.com/js/modernizr.min.js
0
20953
https://dexter.com/images/global/made-in-usa.png
0
19371
https://dexter.com/images/icons/dexter.svg
0
7020
https://dexter.com/images/icons/callout-logo.svg
0
1648
https://www.google-analytics.com/analytics.js
7200000
20093
https://p.typekit.net/p.css?s=1&k=ppp2xka&ht=tk&f=36599.36601.36602.36608&a=12234733&app=typekit&e=css
604800000
317
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://use.typekit.net/af/3bd84d/00000000000000003b9b0ee4/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3
20.756999962032
https://use.typekit.net/af/359d41/00000000000000003b9b0eea/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
39.205999928527
https://dexter.com/fonts/fontawesome-webfont.woff2
265.33099997323
https://use.typekit.net/af/b15395/00000000000000003b9b0ee1/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3
39.442999986932
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://dexter.com/images/global/dext-live.png
img
https://dexter.com/images/icons/dexter.svg
img
https://dexter.com/images/global/made-in-usa.png
img
66

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dexter.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.

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.
`<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.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

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

Best practices

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

Audio and video

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

ARIA

ARIA IDs are not unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Best practices

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

Manual Checks

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

Best Practices

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

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
1.8.2
Modernizr
2.6.1
Underscore
1.8.2
yepnope
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.
URL Map URL
https://dexter.com/js/global.js
https://dexter.com/js/underscore-min.map
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://dexter.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 6 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
6
Medium
89

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dexter.com 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.
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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 64% 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
37x22
116x22
48x22
94x22
49x22
49x22
63x22
68x22

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.

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

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

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.
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 dexter.com on mobile screens.
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.

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

Web Hosting Provider

Name IP Address
Flexential iNETu Corp.
Registration

Domain Registrant

Private Registration: Yes
Name: Registration Private
Organization: Domains By Proxy, LLC
Country: US
City: Scottsdale
State: Arizona
Post Code: 85260
Email: DEXTER.COM@domainsbyproxy.com
Phone: +1.4806242599
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com LLC 23.220.132.43
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 3/5 (0 reviews)
WOT Trustworthiness: 60/100
WOT Child Safety: 63/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

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

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
Timestamp : Mar 27 05:00:46.435 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:E2:60:D6:9B:B4:CA:D8:4E:4B:A0:EE:
99:48:13:3B:DC:A2:8C:37:A5:D2:04:01:09:D4:6C:6A:
0D:98:D4:2A:96:02:20:33:57:7F:95:78:FC:B0:78:B5:
24:45:54:40:D5:0F:52:0B:3A:2F:FA:AB:85:20:A8:82:
13:EA:02:5D:54:0A:5E
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 : Mar 27 05:00:46.416 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C5:5D:A5:00:C1:2B:DE:B2:A3:40:26:
B3:AB:DE:9B:92:72:39:D8:F9:3F:C4:0B:82:5D:18:8F:
C7:8E:B4:5F:91:02:20:09:1A:AE:F6:28:85:AA:55:39:
19:96:39:A9:CF:E7:3C:7F:22:4D:82:9C:9E:01:BC:EF:
CB:25:A3:9A:13:A2:4C
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:go.dexter.com
DNS:www.dexter.com
DNS:dexter.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
dexter.com. 74.85.140.65 IN 299

NS Records

Host Nameserver Class TTL
dexter.com. dns2.lisco.com. IN 299
dexter.com. dns1.lisco.com. IN 299

MX Records

Priority Host Server Class TTL
10 dexter.com. d78987a.ess.barracudanetworks.com. IN 299
20 dexter.com. d78987b.ess.barracudanetworks.com. IN 299

SOA Records

Domain Name Primary NS Responsible Email TTL
dexter.com. dexter.com. hostmaster.dexter.com. 299

TXT Records

Host Value Class TTL
dexter.com. v=spf1 IN 299
dexter.com. j9ug8ugl3itp62cl853fik1tl2 IN 299
dexter.com. MS=ms66157033 IN 299

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 6th April, 2021
Server: Apache/2.2.15 (Red Hat)
Content-Type: text/html; charset=utf-8
Referrer-Policy: no-referrer-when-downgrade
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
X-UA-Compatible: IE=Edge,chrome=1
Content-Security-Policy: frame-ancestors 'self';
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Connection: close

Whois Lookup

Created: 25th May, 1998
Changed: 7th January, 2020
Expires: 24th May, 2025
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: dns1.lisco.com
dns2.lisco.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
14455 N. Hayden Road
Owner Post Code: 85260
Owner City: Scottsdale
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: DEXTER.COM@domainsbyproxy.com
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
14455 N. Hayden Road
Admin Post Code: 85260
Admin City: Scottsdale
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: DEXTER.COM@domainsbyproxy.com
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
14455 N. Hayden Road
Tech Post Code: 85260
Tech City: Scottsdale
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: DEXTER.COM@domainsbyproxy.com
Full Whois: Domain Name: DEXTER.COM
Registry Domain ID: 4780217_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2020-01-07T15:47:57Z
Creation Date: 1998-05-25T23:00:00Z
Registrar Registration Expiration Date: 2025-05-24T23:00:00Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 14455 N. Hayden Road
Registrant City: Scottsdale
Registrant State/Province: Arizona
Registrant Postal Code: 85260
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: DEXTER.COM@domainsbyproxy.com
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 14455 N. Hayden Road
Tech City: Scottsdale
Tech State/Province: Arizona
Tech Postal Code: 85260
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: DEXTER.COM@domainsbyproxy.com
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 14455 N. Hayden Road
Admin City: Scottsdale
Admin State/Province: Arizona
Admin Postal Code: 85260
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: DEXTER.COM@domainsbyproxy.com
Name Server: DNS1.LISCO.COM
Name Server: DNS2.LISCO.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-04-06T21:17:35Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
dns1.lisco.com 69.18.32.50
dns2.lisco.com 69.18.32.51
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$717 USD 1/5
0/5
0/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
$422 USD

Sites hosted on the same IP address