4 sec in total
211 ms
3.3 sec
451 ms
Visit clean.ns.ca now to see the best up-to-date Clean content for Canada and also check out these interesting facts you probably never knew about clean.ns.ca
A program delivery non-profit, Clean’s drive is to make real progress toward a cleaner future by taking on climate change challenges.
Visit clean.ns.caWe analyzed Clean.ns.ca page load time and found that the first response time was 211 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
clean.ns.ca performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value18.9 s
0/100
25%
Value27.5 s
0/100
10%
Value15,440 ms
0/100
30%
Value0.106
88/100
15%
Value23.2 s
1/100
10%
211 ms
1616 ms
165 ms
172 ms
174 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Clean.ns.ca, 76% (77 requests) were made to Cleanfoundation.ca and 15% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Cleanfoundation.ca.
Page size can be reduced by 371.7 kB (34%)
1.1 MB
716.2 kB
In fact, the total size of Clean.ns.ca main page is 1.1 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. Images take 466.1 kB which makes up the majority of the site volume.
Potential reduce by 280.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 280.4 kB or 86% of the original size.
Potential reduce by 42.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. Clean images are well optimized though.
Potential reduce by 33.9 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 33.9 kB or 22% of the original size.
Potential reduce by 14.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. Clean.ns.ca has all CSS files already compressed.
Number of requests can be reduced by 69 (83%)
83
14
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clean. 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 37 to 1 for CSS and as a result speed up the page load time.
clean.ns.ca
211 ms
cleanfoundation.ca
1616 ms
divi-stop-stacking.css
165 ms
mhmm-menus.css
172 ms
mhmm-menu-layout.css
174 ms
mhmm.css
175 ms
slick.css
174 ms
magnific-popup.css
174 ms
wp-pap-public.min.css
221 ms
pgafu-public.min.css
233 ms
core.min.css
228 ms
slick.min.css
227 ms
magnific-popup.min.css
230 ms
job-listings.css
232 ms
style.css
279 ms
css
29 ms
css
44 ms
style.min.css
226 ms
style.min.css
305 ms
style.min.css
227 ms
css
13 ms
bootstrap.css
291 ms
bootstrap-theme.css
228 ms
wpbc-tippy-popover.css
271 ms
wpbc-tippy-times.css
289 ms
material-design-icons.css
343 ms
wpbc_time-selector.css
288 ms
grey.css
327 ms
client.css
356 ms
calendar.css
357 ms
traditional.css
359 ms
timeline_v2.css
359 ms
timeline_skin_v2.css
382 ms
jquery.min.js
456 ms
jquery-migrate.min.js
422 ms
mhmm.min.js
423 ms
mhmm-menu-layout.min.js
422 ms
wpbc_vars.js
421 ms
popper.js
444 ms
tippy-bundle.umd.js
511 ms
css
18 ms
8c5aab1f2c87f093f30ee2408d873c6b183b0748.js
90 ms
et-core-unified-105.min.css
463 ms
mediaelementplayer-legacy.min.css
407 ms
wp-mediaelement.min.css
399 ms
style.css
399 ms
jquery.datepick.wpbc.9.0.js
468 ms
client.js
473 ms
wpbc_times.js
473 ms
wpbc_time-selector.js
363 ms
timeline_v2.js
398 ms
divi-stop-stacking.min.js
490 ms
slick.min.js
607 ms
jquery.magnific-popup.min.js
602 ms
idle-timer.min.js
601 ms
custom.js
550 ms
scripts.min.js
654 ms
jquery.fitvids.js
543 ms
easypiechart.js
590 ms
salvattore.js
548 ms
frontend-bundle.min.js
530 ms
frontend-bundle.min.js
519 ms
frontend-bundle.min.js
505 ms
common.js
568 ms
mediaelement-and-player.min.js
695 ms
mediaelement-migrate.min.js
523 ms
wp-mediaelement.min.js
523 ms
jquery.uniform.min.js
523 ms
custom.js
567 ms
idle-timer.min.js
569 ms
gtm.js
194 ms
AwjDylAe_normal.jpg
148 ms
logo.png
279 ms
preloader.gif
280 ms
wave.png
280 ms
Resources.png
325 ms
homewarming-white.png
325 ms
road3.png
437 ms
Untitled-design-23.png
383 ms
Cans-e1659095013716.jpg
627 ms
Untitled-design-23-1024x1024.png
436 ms
Clean-Logo-White.png
383 ms
et-divi-dynamic-tb-200-105-late.css
339 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQUwaEQXjM.woff
68 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff
79 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQUwaEQXjM.woff
88 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQUwaEQXjM.woff
98 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQUwaEQXjM.woff
99 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff
102 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQUwaEQXjM.woff
100 ms
pe03MImSLYBIv1o4X1M8cc8GBs5jU1cCVZl_.woff
101 ms
pe03MImSLYBIv1o4X1M8cc8aBc5jU1cCVZl_.woff
141 ms
pe03MImSLYBIv1o4X1M8cc8-BM5jU1cCVZl_.woff
131 ms
pe03MImSLYBIv1o4X1M8cc9iB85jU1cCVZl_.woff
156 ms
pe0qMImSLYBIv1o4X1M8cce9I91AcVwo.woff
118 ms
pe0qMImSLYBIv1o4X1M8ccezI91AcVwo.woff
115 ms
pe03MImSLYBIv1o4X1M8cc8WAc5jU1cCVZl_.woff
249 ms
pe03MImSLYBIv1o4X1M8cc9yAs5jU1cCVZl_.woff
151 ms
modules.ttf
513 ms
modules-v66.js
106 ms
CLEAN-LOGO-2022_Clean-Colour.png
181 ms
clean.ns.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
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.
clean.ns.ca 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
clean.ns.ca 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 Clean.ns.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 Clean.ns.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.
clean.ns.ca
Open Graph data is detected on the main page of Clean. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: