6.4 sec in total
1.9 sec
4 sec
473 ms
Click here to check amazing DIY content for Ireland. Otherwise, check out these important facts you probably never knew about diy.ie
Shop for everything you need to complete your home and garden project. Order online for 1hour Click+Collect, or free home delivery on orders over €50.
Visit diy.ieWe analyzed Diy.ie page load time and found that the first response time was 1.9 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
diy.ie performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value6.2 s
11/100
25%
Value9.3 s
13/100
10%
Value4,220 ms
1/100
30%
Value0.064
97/100
15%
Value20.8 s
2/100
10%
1910 ms
21 ms
362 ms
99 ms
243 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 92% of them (44 requests) were addressed to the original Diy.ie, 2% (1 request) were made to Edge1.certona.net and 2% (1 request) were made to Consent.trustarc.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Diy.ie.
Page size can be reduced by 519.0 kB (76%)
678.9 kB
159.8 kB
In fact, the total size of Diy.ie main page is 678.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. HTML takes 625.8 kB which makes up the majority of the site volume.
Potential reduce by 512.9 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 512.9 kB or 82% of the original size.
Potential reduce by 6.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 6.2 kB or 12% of the original size.
Number of requests can be reduced by 34 (77%)
44
10
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DIY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.diy.ie
1910 ms
ruxitagentjs_A7NVfghqrux_10291240606133530.js
21 ms
hash-fef1be99abb7d0186217.css
362 ms
4.hash-10f9c588cb6b47d011b8.css
99 ms
5.hash-590ad11593dbffc855ad.css
243 ms
22.hash-3cf095f460aa568c4718.css
247 ms
8.hash-705eb306e0cbd9ae09dc.css
265 ms
25.hash-877ead442f6799ee7253.css
331 ms
136.hash-7ed81e44416d69f1f025.css
383 ms
235.hash-80986e6b4825ce5e9b28.css
480 ms
resonance.js
32 ms
jquery.initial.min.js
711 ms
notice
99 ms
108.hash-7d72324586411fcfc550.js
587 ms
109.hash-e91d23d64b9bc1d32bfe.js
904 ms
hash-d506d9d30d94b22f30fb.js
596 ms
1.hash-37fe1f24731a8f8ff545.js
583 ms
4.hash-17ce22ac0794e9fd69ee.js
634 ms
5.hash-e7ad604fdd5d4db5b856.js
801 ms
22.hash-ba1050db297c268e28b0.js
641 ms
8.hash-4a73cb5806ec5464ee2e.js
795 ms
25.hash-cc613e34253d5e103ce7.js
687 ms
136.hash-971c4d14977c61361013.js
741 ms
167.hash-7cbacf403c26c1f8c92a.js
872 ms
111.hash-a67593d2c93c26d771dd.js
923 ms
0.hash-cfff840b67498066a9f0.js
1056 ms
2.hash-7af53f13337f739beabe.js
891 ms
17.hash-054c2a328089c6509cce.js
916 ms
7.hash-5861d2df98b6f80e5316.js
1098 ms
34.hash-2e676484ca07f031e961.js
1000 ms
3.hash-a2eb4e1826c0ea7276df.js
996 ms
10.hash-e31624794fbfb5ffbec7.js
1148 ms
16.hash-afb540be285ce9abd19f.js
1157 ms
24.hash-d7eb9079a06d88596d44.js
1228 ms
235.hash-3a589baf491f4896515c.js
1229 ms
BQ_icons-services-clickandcollect-ff6600-nobg.svg
224 ms
c08f9.svg
789 ms
92352.svg
841 ms
ac483.svg
1030 ms
b915f.svg
884 ms
5be44.svg
1032 ms
1c81d.svg
1076 ms
e961d.svg
1109 ms
utag.js
259 ms
GoodHome-Regular.woff
789 ms
GoodHome-Light.woff
905 ms
GoodHome-Bold.woff
806 ms
jquery.bundle.min.js
1322 ms
diy.ie 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.
diy.ie 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
diy.ie SEO score
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 Diy.ie 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 Diy.ie 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.
diy.ie
Open Graph description is not detected on the main page of DIY. 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: