5.8 sec in total
1.2 sec
4.4 sec
217 ms
Welcome to gree.ca homepage info - get ready to check Gree best content for Canada right away, or after learning these important things about gree.ca
Visit gree.caWe analyzed Gree.ca page load time and found that the first response time was 1.2 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
gree.ca performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value5.4 s
20/100
25%
Value6.0 s
46/100
10%
Value550 ms
54/100
30%
Value0.057
98/100
15%
Value7.0 s
53/100
10%
1180 ms
217 ms
96 ms
246 ms
106 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 91% of them (29 requests) were addressed to the original Gree.ca, 6% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Gree.ca.
Page size can be reduced by 628.2 kB (15%)
4.2 MB
3.6 MB
In fact, the total size of Gree.ca main page is 4.2 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. 20% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 7.8 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 7.8 kB or 74% of the original size.
Potential reduce by 105.3 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. Gree images are well optimized though.
Potential reduce by 234.8 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 234.8 kB or 71% of the original size.
Potential reduce by 280.2 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. Gree.ca needs all CSS files to be minified and compressed as it can save up to 280.2 kB or 86% of the original size.
Number of requests can be reduced by 14 (50%)
28
14
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gree. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
1180 ms
widgetkit-d6f2f78c.css
217 ms
template.css
96 ms
jquery.min.js
246 ms
jquery-noconflict.js
106 ms
jquery-migrate.min.js
123 ms
widgetkit-25f0846a.js
237 ms
bootstrap.css
397 ms
theme.css
325 ms
custom.css
281 ms
uikit.js
357 ms
autocomplete.js
306 ms
search.js
356 ms
tooltip.js
376 ms
social.js
381 ms
theme.js
427 ms
lightbox.js
188 ms
mediaelement-and-player.js
208 ms
spotlight.js
190 ms
css
71 ms
gree_logo.jpg
99 ms
cmpxbanner3.jpg
420 ms
Bandeau_pour_le_web_U-Crown_White_EN.jpg
142 ms
Lomo_Banner_No_SEER_En.jpg
475 ms
Baniere_Heatpump_-_EN.jpg
325 ms
nav.png
218 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
30 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
36 ms
fontawesome-webfont.woff
284 ms
slideshow.js
266 ms
close.png
115 ms
blank.gif
186 ms
gree.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
gree.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
Page has valid source maps
gree.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gree.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 Gree.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.
gree.ca
Open Graph description is not detected on the main page of Gree. 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: