3.6 sec in total
107 ms
3.3 sec
222 ms
Visit digitalhome.ca now to see the best up-to-date Digital Home content for India and also check out these interesting facts you probably never knew about digitalhome.ca
A forum community dedicated to Canadian TV, computing and home theatre owners and enthusiasts. Come join the discussion about home audio/video, displays...
Visit digitalhome.caWe analyzed Digitalhome.ca page load time and found that the first response time was 107 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
digitalhome.ca performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value7.0 s
6/100
25%
Value13.9 s
1/100
10%
Value2,480 ms
4/100
30%
Value0.001
100/100
15%
Value32.4 s
0/100
10%
107 ms
369 ms
76 ms
96 ms
97 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 15% of them (27 requests) were addressed to the original Digitalhome.ca, 8% (14 requests) were made to Images.intellitxt.com and 6% (10 requests) were made to S1.2mdn.net. The less responsive or slowest element that took the longest time to load (590 ms) relates to the external source Mono.vizu.com.
Page size can be reduced by 914.4 kB (52%)
1.8 MB
848.0 kB
In fact, the total size of Digitalhome.ca 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. 70% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 60.4 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 60.4 kB or 73% of the original size.
Potential reduce by 25.0 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. Digital Home images are well optimized though.
Potential reduce by 778.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 778.4 kB or 66% of the original size.
Potential reduce by 50.6 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. Digitalhome.ca needs all CSS files to be minified and compressed as it can save up to 50.6 kB or 85% of the original size.
Number of requests can be reduced by 126 (75%)
167
41
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digital Home. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 72 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
digitalhome.ca
107 ms
www.digitalhome.ca
369 ms
style.css
76 ms
widget.css
96 ms
addtoany.min.css
97 ms
wpsf-js.php
141 ms
google_service.js
16 ms
brand
17 ms
widgets.js
7 ms
brand
81 ms
urchin.js
20 ms
subnav.js
71 ms
front.asp
47 ms
cc_af.js
79 ms
spxw.js
60 ms
wp-emoji-release.min.js
41 ms
google_ads.js
18 ms
bg.gif
35 ms
ads
257 ms
header.png
41 ms
logo.png
40 ms
timthumb.php
43 ms
timthumb.php
74 ms
timthumb.php
65 ms
timthumb.php
75 ms
timthumb.php
107 ms
timthumb.php
108 ms
timthumb.php
107 ms
timthumb.php
100 ms
rss.png
106 ms
1019.js
75 ms
osd.js
11 ms
sync
17 ms
173492-2.js
116 ms
4a5c72ec-c463-4737-af09-c39886bf1f42
10 ms
0RV82NSGzg_1651222459.html
8 ms
emily.html
11 ms
navbar.png
37 ms
navside.png
37 ms
ads
111 ms
cl
53 ms
creative_add_on.js
63 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
27 ms
lidar.js
6 ms
analytics.js
59 ms
controltag
144 ms
smart_tag.js
590 ms
rs.js
44 ms
g-3147.xgi
43 ms
index.html
80 ms
loaded.js
16 ms
ads
260 ms
postback
35 ms
DcmEnabler_01_93.js
10 ms
fabric-pattern-16.png
6 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
78 ms
btn_replay.png
4 ms
cta-txt-16.png
5 ms
logo-24.png
7 ms
txt2-8.png
8 ms
callout-24.png
8 ms
txt12-8.png
7 ms
bg-5.jpg
10 ms
sync
10 ms
407100-15.js
159 ms
336e6650-dd61-4a6b-b3b6-168982ddcaeb
5 ms
gpt.js
9 ms
pubads_impl_81.js
7 ms
ads
263 ms
container.html
9 ms
rpc.flow
46 ms
vce_st.js
22 ms
surly.js
14 ms
dvtp_src.js
50 ms
a.gif
204 ms
p2
7 ms
ba.html
29 ms
4.gif
26 ms
p
17 ms
p
46 ms
2532.js
36 ms
dvtp_src_internal25.js
35 ms
cms-2c.html
47 ms
postback
179 ms
2964
112 ms
Pug
108 ms
rum
100 ms
sync
99 ms
t2tv7.html
149 ms
visit.js
83 ms
demconf.jpg
30 ms
rum
57 ms
pixel
98 ms
385636.gif
75 ms
tap.php
185 ms
sd
49 ms
postback
65 ms
icon.gif
56 ms
rs
35 ms
pixel.gif
52 ms
m.gif
30 ms
google_custom_search_watermark.gif
70 ms
searchbar.png
54 ms
rss.png
51 ms
footer.gif
52 ms
__utm.gif
12 ms
page.js
25 ms
load
26 ms
fod.js
36 ms
avs564.js
97 ms
event.gif
39 ms
ga.js
33 ms
beacon.js
17 ms
vglnk.js
31 ms
jquery.min.js
116 ms
match-result
108 ms
event.gif
77 ms
m_yahoo.gif
52 ms
pixel.gif
59 ms
__utm.gif
53 ms
pixel.gif
47 ms
event.jpg
86 ms
spxboot.js
80 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
76 ms
underscore-min-ns-1.4.2.js
42 ms
core_1446569672.js
41 ms
data_1444835675.js
42 ms
debug_1395261999.js
37 ms
fx_1395261999.js
37 ms
fx2_1395261999.js
36 ms
itxt_1426253035.js
57 ms
metrics_1395261999.js
56 ms
tmpl_1443709758.js
56 ms
ui_1447845393.js
56 ms
ui_mobile_1423653241.js
56 ms
itxtcss_1446206988.css
57 ms
cookie_consent.php
208 ms
get
126 ms
optout_check
54 ms
box_19_top-right.png
36 ms
ci.png
34 ms
event.gif
43 ms
spxmain.js
42 ms
118 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
29 ms
px.gif
28 ms
loading.gif
26 ms
activeview
14 ms
jquery.min.js
26 ms
net.php
57 ms
provider.html
61 ms
xrefid.xgi
13 ms
pixel
36 ms
generic
34 ms
jot
111 ms
generic
7 ms
init
41 ms
ping
38 ms
pixel.gif
13 ms
domains
78 ms
pixel.gif
18 ms
jones-pla.png
28 ms
in
53 ms
log
43 ms
log
9 ms
pixel.gif
4 ms
pixel.gif
5 ms
xrefid.xgi
4 ms
nr-852.min.js
54 ms
rt=ifr
16 ms
5907
46 ms
g.json
13 ms
tpc=na_id
20 ms
pixel
26 ms
30 ms
tpid=164220501885000501889
15 ms
18 ms
0f2b0d60a0
55 ms
362738.gif
7 ms
digitalhome.ca 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-*] attributes do not match their roles
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
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>).
digitalhome.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
digitalhome.ca 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 Digitalhome.ca 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 Digitalhome.ca 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.
digitalhome.ca
Open Graph description is not detected on the main page of Digital Home. 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: