2.9 sec in total
1 sec
1.8 sec
117 ms
Visit ilovesavings.ca now to see the best up-to-date Ilovesavings content for Canada and also check out these interesting facts you probably never knew about ilovesavings.ca
Visit ilovesavings.caWe analyzed Ilovesavings.ca page load time and found that the first response time was 1 sec and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ilovesavings.ca performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value5.7 s
16/100
25%
Value15.4 s
1/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value5.7 s
68/100
10%
1006 ms
412 ms
667 ms
60 ms
59 ms
Our browser made a total of 12 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Ilovesavings.ca, 42% (5 requests) were made to I2.cdn-image.com and 17% (2 requests) were made to Cdn.consentmanager.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Ilovesavings.ca.
Page size can be reduced by 68.6 kB (34%)
202.5 kB
134.0 kB
In fact, the total size of Ilovesavings.ca main page is 202.5 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. 15% of websites need less resources to load. Javascripts take 106.3 kB which makes up the majority of the site volume.
Potential reduce by 61.1 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 61.1 kB or 78% of the original size.
Potential reduce by 0 B
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. Ilovesavings images are well optimized though.
Potential reduce by 7.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 6 (67%)
9
3
The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ilovesavings. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
ilovesavings.ca
1006 ms
cmp.php
412 ms
cmp_en.min.js
667 ms
px.js
60 ms
px.js
59 ms
min.js
111 ms
bg1.png
16 ms
arrrow.png
24 ms
montserrat-bold.woff
20 ms
montserrat-regular.woff
17 ms
cmp.php
115 ms
bV8xLndfNjg4ODQucl9VU1ZDRFBBLmxfZW4uZF8zMzY2OC54XzM3LnYucC50XzMzNjY4Lnh0XzMy.js
250 ms
ilovesavings.ca accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
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.
ilovesavings.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
ilovesavings.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ilovesavings.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ilovesavings.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.
ilovesavings.ca
Open Graph description is not detected on the main page of Ilovesavings. 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: