4.3 sec in total
1.3 sec
2.7 sec
429 ms
Welcome to durrie.com homepage info - get ready to check Durrie best content right away, or after learning these important things about durrie.com
Why do distributors rely on Durrie Wholesale as their manufacturers’ representative? The right stock, dependable shipments and great customer service.
Visit durrie.comWe analyzed Durrie.com page load time and found that the first response time was 1.3 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
durrie.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value12.5 s
0/100
25%
Value9.3 s
13/100
10%
Value2,200 ms
6/100
30%
Value0.097
90/100
15%
Value20.5 s
2/100
10%
1251 ms
66 ms
322 ms
187 ms
184 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 67% of them (48 requests) were addressed to the original Durrie.com, 17% (12 requests) were made to Chat-widget.hiverhq.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Durrie.com.
Page size can be reduced by 286.9 kB (10%)
2.9 MB
2.6 MB
In fact, the total size of Durrie.com main page is 2.9 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 197.8 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 197.8 kB or 87% of the original size.
Potential reduce by 80.3 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. Durrie images are well optimized though.
Potential reduce by 7.4 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 1.4 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. Durrie.com has all CSS files already compressed.
Number of requests can be reduced by 27 (40%)
67
40
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Durrie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
durrie.com
1251 ms
same-category-posts.css
66 ms
b2b8e23b145d6352ba73486267553548.min.css
322 ms
jquery.min.js
187 ms
jquery-migrate.min.js
184 ms
js
79 ms
embed.php
471 ms
style.min.css
187 ms
9028731.js
184 ms
357fc444dc2fee7498db40cfc8bc198e.min.js
310 ms
Durrie-logo-white-bg.png
75 ms
ABA-Logo.png
74 ms
airmasterlogo.jpg
374 ms
azusalogo.jpg
75 ms
download.png
76 ms
breeze-hose-clamps-logo-vector.png
75 ms
coilhouse.png
142 ms
DAPRA-Category-Logo_101122.jpg
141 ms
devcon-logo-0D8DFEF5E4-seeklogo.com_.png
142 ms
dorian.png
207 ms
duMONT-CNC.jpg
141 ms
duMONT-MM-Logo.png
214 ms
fabcel.jpg
213 ms
fabrika.png
218 ms
FiveStar.jpg
212 ms
GMauvaisUSA-Logo.png
271 ms
grobet-USA.jpg
274 ms
gwslogo.jpg
275 ms
halter-logo.jpg
278 ms
HS-logo.png
284 ms
kifix-toggle-clamps.png
397 ms
LEXINGTON.jpg
337 ms
Main-logo-2_410x.webp
339 ms
magafor-logo.png
342 ms
Norma_Group_Logo_Card.png
530 ms
northwesternlogo.jpg
404 ms
osbornlogo.jpg
402 ms
Palbit-CTS-LOGO-crop.png
408 ms
Pilot-Precision-LOGO.png
436 ms
rg-ray.png
460 ms
sprayway.png
466 ms
suburban-industries-logo.jpg
465 ms
tap-magic-logo-vector.png
472 ms
Vermont-Gage-Transparent.png
500 ms
vikingdrill-logo-scaled.jpg
524 ms
young-bros.png
470 ms
awb-icons.woff
460 ms
fa-solid-900.woff
472 ms
fa-regular-400.woff
496 ms
tool-delivery.jpg
516 ms
diffuser.js
71 ms
fa-brands-400.woff
501 ms
collectedforms.js
89 ms
banner.js
86 ms
9028731.js
209 ms
fb.js
86 ms
sdk.js
49 ms
prism.app-us1.com
147 ms
widget.html
8 ms
css2
33 ms
css2
53 ms
widget.1939dad9.css
10 ms
widget-3d068545fa3bd2146609.js
17 ms
roboto
30 ms
chunk-3221f8fa.83e9dfb4.css
5 ms
chunk-4971ae1e.e04bd085.css
3 ms
chunk-797d17b4.e4f0a052.css
4 ms
chunk-2d423d8a.754cbf9b.js
5 ms
chunk-3221f8fa.90dd00c1.js
3 ms
chunk-4971ae1e.c7b3f6b2.js
4 ms
chunk-797d17b4.996f22db.js
5 ms
chunk-8f03a7fc.813d2a5f.js
4 ms
durrie.com accessibility score
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
durrie.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
Missing source maps for large first-party JavaScript
durrie.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Durrie.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 Durrie.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.
durrie.com
Open Graph data is detected on the main page of Durrie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: