6.6 sec in total
1.7 sec
4.3 sec
554 ms
Visit zulo.ca now to see the best up-to-date Zulo content for Canada and also check out these interesting facts you probably never knew about zulo.ca
DOES YOUR BUSINESS NEED MORE LEADS? We're experts at Canada SEO and driving new revenue generating leads to your business. Contact us today.
Visit zulo.caWe analyzed Zulo.ca page load time and found that the first response time was 1.7 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
zulo.ca performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value9.5 s
0/100
25%
Value7.8 s
23/100
10%
Value1,170 ms
21/100
30%
Value0.179
67/100
15%
Value10.7 s
22/100
10%
1690 ms
145 ms
75 ms
90 ms
153 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 78% of them (63 requests) were addressed to the original Zulo.ca, 5% (4 requests) were made to F.vimeocdn.com and 4% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Zulo.ca.
Page size can be reduced by 1.8 MB (67%)
2.7 MB
871.6 kB
In fact, the total size of Zulo.ca main page is 2.7 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. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 40.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 40.4 kB or 77% of the original size.
Potential reduce by 27.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. Zulo images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 73% of the original size.
Potential reduce by 716.8 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. Zulo.ca needs all CSS files to be minified and compressed as it can save up to 716.8 kB or 87% of the original size.
Number of requests can be reduced by 49 (73%)
67
18
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zulo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
zulo.ca
1690 ms
wp-emoji-release.min.js
145 ms
css
75 ms
css
90 ms
cf7msm.css
153 ms
styles.css
126 ms
jquery.lazyloadxt.fadein.min.css
157 ms
jquery.lazyloadxt.spinner.min.css
154 ms
frontend-render.css
183 ms
mediaelementplayer.min.css
199 ms
wp-mediaelement.css
245 ms
rgs.css
227 ms
font-awesome.min.css
238 ms
style.css
400 ms
responsive.css
292 ms
dynamic-combined.css
272 ms
ascend.css
308 ms
js_composer.css
339 ms
jquery.js
448 ms
jquery-migrate.min.js
424 ms
inboundAnalytics.min.js
423 ms
jquery.lazyloadxt.min.js
436 ms
jquery.lazyloadxt.print.min.js
431 ms
modernizr.js
486 ms
ProgressCircle.js
511 ms
jquery.vc_chart.js
509 ms
core.min.js
509 ms
widget.min.js
592 ms
position.min.js
592 ms
menu.min.js
631 ms
autocomplete.min.js
631 ms
wpss-search-suggest.js
630 ms
cf7msm.js
632 ms
jquery.form.min.js
631 ms
scripts.js
644 ms
superfish.js
732 ms
respond.js
714 ms
sticky.js
731 ms
prettyPhoto.js
622 ms
isotope.min.js
689 ms
init.js
1104 ms
infinitescroll.js
682 ms
mediaelement-and-player.min.js
743 ms
wp-mediaelement.js
641 ms
comment-reply.min.js
676 ms
wp-embed.min.js
688 ms
js_composer_front.js
674 ms
124412159
131 ms
logo.png
1315 ms
toronto-sky-line.jpg
1102 ms
CTV-Logo_3D-BW.jpg
555 ms
toronto-star-logo-Optimized.jpg
544 ms
yahoo-news.png
483 ms
cbc-television.png
611 ms
analytics.js
46 ms
OpenSans-Regular-webfont.woff
1575 ms
OpenSans-Regular-webfont.woff
601 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
66 ms
OpenSans-Bold-webfont.woff
1114 ms
OpenSansBold-webfont.woff
1034 ms
icomoon.woff
1034 ms
OpenSans-Semibold-webfont.woff
1506 ms
OpenSans-Semibold-webfont.woff
1034 ms
fontawesome-webfont.svg
1362 ms
fontawesome-webfont.woff
1060 ms
OpenSans-Light-webfont.woff
1982 ms
OpenSans-Light-webfont.woff
1256 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
82 ms
collect
50 ms
player.js
119 ms
player.css
96 ms
ga.js
66 ms
vuid.min.js
91 ms
__utm.gif
26 ms
proxy.html
44 ms
517945039.jpg
348 ms
9388891_60x60.jpg
62 ms
124412159
56 ms
517945039.jpg
191 ms
__utm.gif
3 ms
fontawesome-webfont.woff
480 ms
zulo.ca 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
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
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>).
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.
zulo.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
Missing source maps for large first-party JavaScript
zulo.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 Zulo.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 Zulo.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.
zulo.ca
Open Graph data is detected on the main page of Zulo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: