2.8 sec in total
64 ms
2.1 sec
600 ms
Visit dustspares.co.uk now to see the best up-to-date Dust Spares content and also check out these interesting facts you probably never knew about dustspares.co.uk
Suppliers of dust spares including dust extraction parts, ductwork, ducting, filters and consumables. Order online today for fast delivery.
Visit dustspares.co.ukWe analyzed Dustspares.co.uk page load time and found that the first response time was 64 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
dustspares.co.uk performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value13.7 s
0/100
25%
Value12.2 s
3/100
10%
Value12,490 ms
0/100
30%
Value0.704
7/100
15%
Value35.2 s
0/100
10%
64 ms
543 ms
284 ms
27 ms
338 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 59% of them (38 requests) were addressed to the original Dustspares.co.uk, 5% (3 requests) were made to Tools.luckyorange.com and 5% (3 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (543 ms) belongs to the original domain Dustspares.co.uk.
Page size can be reduced by 421.6 kB (23%)
1.8 MB
1.4 MB
In fact, the total size of Dustspares.co.uk main page is 1.8 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 195.7 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 195.7 kB or 81% of the original size.
Potential reduce by 55.7 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. Dust Spares images are well optimized though.
Potential reduce by 87 B
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 170.1 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. Dustspares.co.uk needs all CSS files to be minified and compressed as it can save up to 170.1 kB or 80% of the original size.
Number of requests can be reduced by 22 (40%)
55
33
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dust Spares. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
dustspares.co.uk
64 ms
www.dustspares.co.uk
543 ms
eae8918bc315d4659878b5a9f4103621.min.css
284 ms
styles-l.min.css
27 ms
8f0152b0b3fa8bfc3e81f84b099ac835.min.js
338 ms
font-awesome.min.css
53 ms
lo.js
48 ms
klaviyo.js
44 ms
dist.js
54 ms
dist.js
67 ms
dist.js
87 ms
carousel-widget.css
70 ms
style.css
82 ms
dist.js
81 ms
loader.min.js
157 ms
logo.png
4 ms
nav_contact_block.jpg
23 ms
Loyalty.jpg
23 ms
Loyalty_Mobile.jpg
23 ms
Extractor.jpg
29 ms
Extractor_Mobile.jpg
29 ms
2024.jpg
30 ms
2024_MOBILE_1.jpg
24 ms
dust_extractor_collector_bag_3.jpg
23 ms
pu_flex_550_1.jpg
23 ms
ducting_steel_1.jpg
29 ms
binks_filter_opened.jpg
30 ms
dsc_1048_long_extraction_arm.jpg
30 ms
ceiling-hangar-bracket-kit.jpg
31 ms
ducting_reducer.jpg
31 ms
pressed_reducer.png
32 ms
heavy_duty_blue_spiral.jpg
33 ms
dsc_0976_blast_gate_damper.jpg
34 ms
brand_ministry_of_defence1.jpg
33 ms
warburton_200_100.jpg
33 ms
bbc_200_100.jpg
34 ms
Dyson.jpg
34 ms
brand_RR_copy.jpg
35 ms
brand_nhs_copy.jpg
35 ms
DS_Free_Delivery_350.png
37 ms
cards.png
36 ms
Montserrat-Bold.woff
437 ms
Montserrat-Regular.woff
436 ms
Montserrat-Light.woff
436 ms
lo.legacy.js
46 ms
fontawesome-webfont.woff
28 ms
fontawesome-webfont.woff
85 ms
Blank-Theme-Icons.woff
3 ms
fender_analytics.8b21fd7cc915ea15c535.js
53 ms
static.047f24ade89e4aff54a9.js
53 ms
runtime.11af7f1367618718ecb4.js
11 ms
sharedUtils.cb05181f91b3f2ceea9d.js
18 ms
box-stack.png
34 ms
widget
25 ms
style.css
26 ms
axios.min.js
72 ms
style-cf.css
101 ms
bd1c5033
39 ms
icomoon.ttf
3 ms
loader.js
259 ms
w.js
21 ms
core.legacy.js
48 ms
reviewsio-logo.svg
187 ms
settings.luckyorange.net
30 ms
dustspares.co.uk accessibility score
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-hidden="true"] elements contain focusable descendents
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA IDs are not unique
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
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
Form elements do not have associated labels
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
dustspares.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
dustspares.co.uk 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dustspares.co.uk 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 Dustspares.co.uk 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.
dustspares.co.uk
Open Graph description is not detected on the main page of Dust Spares. 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: