3.2 sec in total
211 ms
2.6 sec
393 ms
Click here to check amazing Doxon content. Otherwise, check out these important facts you probably never knew about doxon.com
Doxon is a “one stop shop” for all commercial laundry distributors. We carry complete lines of laundry parts for all major b
Visit doxon.comWe analyzed Doxon.com page load time and found that the first response time was 211 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
doxon.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value22.2 s
0/100
25%
Value8.7 s
16/100
10%
Value210 ms
88/100
30%
Value0.422
23/100
15%
Value14.0 s
10/100
10%
211 ms
123 ms
945 ms
130 ms
173 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 57% of them (55 requests) were addressed to the original Doxon.com, 31% (30 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (945 ms) belongs to the original domain Doxon.com.
Page size can be reduced by 232.3 kB (7%)
3.2 MB
3.0 MB
In fact, the total size of Doxon.com main page is 3.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 192.6 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 192.6 kB or 84% of the original size.
Potential reduce by 32.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Doxon images are well optimized though.
Potential reduce by 4.2 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 3.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Doxon.com has all CSS files already compressed.
Number of requests can be reduced by 37 (65%)
57
20
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doxon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
doxon.com
211 ms
www.doxon.com
123 ms
www.doxon.com
945 ms
bootstrap.min.css
130 ms
slick-theme.css
173 ms
slick.css
176 ms
style.css
187 ms
font-awesome.min.css
25 ms
choices.min.css
139 ms
intl-tel-input.min.css
205 ms
richtext.min.css
166 ms
content.min.css
171 ms
wpforms-classic-full.min.css
189 ms
jquery-ui.min.css
192 ms
style.css
203 ms
jquery.min.js
284 ms
jquery-migrate.min.js
230 ms
jquery-ui.min.js
17 ms
divi-child.js
251 ms
wpforms-full.min.css
252 ms
bootstrap.bundle.min.js
270 ms
slick.min.js
270 ms
clearnine.js
402 ms
scripts.min.js
475 ms
scripts.js
402 ms
gtm4wp-form-move-tracker.js
412 ms
jquery.fitvids.js
412 ms
jquery.mobile.js
412 ms
easypiechart.js
413 ms
common.js
412 ms
jquery.validate.min.js
498 ms
mailcheck.min.js
469 ms
punycode.min.js
470 ms
utils.min.js
494 ms
wpforms.min.js
497 ms
gtm.js
131 ms
gtm.js
193 ms
Doxon-white.png
374 ms
Doxon-large.png
371 ms
new-banner-2.jpg
635 ms
70367301.jpg
196 ms
F200166302B.jpg
263 ms
100E.jpg
263 ms
3V_Belt_Opti.jpg
198 ms
9379-183-001-O.jpg
367 ms
510109-O.jpg
369 ms
AdobeStock_2709058-1536x1024-1.jpg
383 ms
submit-spin.svg
367 ms
Shop-Whirlpool-parts-1.jpg
378 ms
Shop-LG-parts.png
389 ms
Shop-Maytag-parts.jpg
567 ms
Shop-Dexter-parts.jpg
414 ms
wascomat-logo.jpeg
442 ms
Shop-Girbau-parts.jpg
446 ms
et-divi-dynamic-386-late.css
389 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
50 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
61 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
66 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
67 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
65 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
68 ms
fontawesome-webfont.woff
22 ms
pxiByp8kv8JHgFVrLEj6Z1JlEw.woff
67 ms
pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf
68 ms
pxiByp8kv8JHgFVrLCz7Z1JlEw.woff
68 ms
pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf
95 ms
pxiByp8kv8JHgFVrLDD4Z1JlEw.woff
88 ms
pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf
89 ms
pxiByp8kv8JHgFVrLBT5Z1JlEw.woff
90 ms
pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf
90 ms
pxiByp8kv8JHgFVrLGT9Z1JlEw.woff
89 ms
pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf
92 ms
pxiEyp8kv8JHgFVrJJnedA.woff
93 ms
pxiEyp8kv8JHgFVrJJnedw.ttf
91 ms
pxiByp8kv8JHgFVrLDz8Z1JlEw.woff
93 ms
pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf
94 ms
pxiByp8kv8JHgFVrLFj_Z1JlEw.woff
95 ms
pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf
95 ms
pxiGyp8kv8JHgFVrLPTufntG.woff
94 ms
pxiGyp8kv8JHgFVrLPTufntF.ttf
95 ms
modules.woff
496 ms
analytics.js
18 ms
collect
13 ms
js
34 ms
Doxon-white.png
64 ms
Doxon-white.png
135 ms
style.min.css
71 ms
zy7pid0fcmsegrvx8qqms06dg7b8sewa.js
160 ms
modules.woff
96 ms
render.ef0a530ad8eeaddb4937.js
26 ms
doxon.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
doxon.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
doxon.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doxon.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Doxon.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
doxon.com
Open Graph description is not detected on the main page of Doxon. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: