4.2 sec in total
646 ms
2.9 sec
644 ms
Click here to check amazing Fruugo content for Canada. Otherwise, check out these important facts you probably never knew about fruugo.ca
Visit fruugo.caWe analyzed Fruugo.ca page load time and found that the first response time was 646 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fruugo.ca performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value11.4 s
0/100
25%
Value8.9 s
15/100
10%
Value220 ms
88/100
30%
Value0.014
100/100
15%
Value10.3 s
25/100
10%
646 ms
34 ms
61 ms
56 ms
71 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 85% of them (79 requests) were addressed to the original Fruugo.ca, 2% (2 requests) were made to Intilery-analytics.com and 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fruugo.ca.
Page size can be reduced by 255.1 kB (63%)
402.0 kB
146.9 kB
In fact, the total size of Fruugo.ca main page is 402.0 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. 50% of websites need less resources to load. Javascripts take 245.5 kB which makes up the majority of the site volume.
Potential reduce by 140.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. This page needs HTML code to be minified as it can gain 76.2 kB, which is 49% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 140.1 kB or 90% 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. Fruugo images are well optimized though.
Potential reduce by 115.0 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 115.0 kB or 47% of the original size.
Number of requests can be reduced by 16 (19%)
86
70
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fruugo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.fruugo.ca
646 ms
bootstrap.min-cdb3140a4873f61ca58a0a76e143ddfa.css
34 ms
all-e18a9bbacadd58555fbe5f72dc1c81df.css
61 ms
main-5f0de475a449c6411bb68ce004d4ad5d.css
56 ms
jcarousel.css
71 ms
flag-CA.png
52 ms
flag-AU.png
113 ms
flag-AT.png
113 ms
flag-BE.png
111 ms
jquery.min.js
124 ms
jquery.main-ea4e41d4009d9d5608eff6460960964b.js
105 ms
bootstrap.min-4b1cc3109717d1e6aa0c42647993f15f.js
98 ms
jsrender-ddb54f3fa799df1d851c81f9383c5177.js
99 ms
conversion.js
105 ms
jquery.jcarousel-core.min.js
627 ms
jquery.jcarousel-autoscroll.min.js
640 ms
pulse-carousel.js
658 ms
flag-DK.png
102 ms
flag-FI.png
101 ms
flag-FR.png
106 ms
flag-DE.png
107 ms
flag-IE.png
110 ms
flag-IT.png
112 ms
flag-LU.png
111 ms
flag-NL.png
117 ms
flag-NZ.png
114 ms
flag-NO.png
115 ms
flag-PL.png
118 ms
flag-PT.png
119 ms
flag-RU.png
179 ms
flag-ZA.png
172 ms
flag-ES.png
173 ms
flag-SE.png
174 ms
flag-CH.png
177 ms
flag-US.png
175 ms
flag-GB.png
179 ms
logo.png
177 ms
aden-anais.png
185 ms
brabantia.png
186 ms
denby.png
171 ms
diesel.png
159 ms
dualit.png
148 ms
elemis.png
100 ms
texgyreheros-regular.svg
246 ms
texgyreheros-bold.svg
112 ms
fisherprice.png
101 ms
magimix.png
102 ms
michael-kors.png
102 ms
new-balance.png
103 ms
ralph-lauren.png
101 ms
saucony.png
104 ms
shu-uemura.png
106 ms
ted-baker.png
230 ms
Sports_and_Leisure.jpg
918 ms
Health_and_Beauty.jpg
946 ms
Clothing.jpg
945 ms
Home_and_Garden.jpg
958 ms
Kids_and_Toys.jpg
939 ms
Electricals.jpg
879 ms
Food_and_Drink.jpg
1054 ms
img14.jpg
1158 ms
img15.jpg
974 ms
it.js
833 ms
dc.js
260 ms
px.js
172 ms
256 ms
bg-ticket.png
1255 ms
bg-list-block.jpg
1063 ms
img16.png
1075 ms
img17.png
1086 ms
img18.png
1251 ms
visa.png
1060 ms
mastercard.png
1060 ms
maestro.png
1059 ms
paypal.png
1063 ms
logo-footer.png
1066 ms
sprite-small.png
1067 ms
separator.png
1064 ms
bg-angle.png
1239 ms
bg-offers.jpg
1258 ms
texgyreheros-bold.woff
1033 ms
glyphicons-halflings-regular.woff
945 ms
icomoon.woff
1002 ms
124 ms
texgyreheros-regular.woff
915 ms
pixel
104 ms
__utm.gif
66 ms
ca.png
537 ms
ca.png
528 ms
clouds-img.jpg
525 ms
extra.js
45 ms
page-zone-groups
8 ms
1458424223000
135 ms
fruugo.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
Image elements do not have [alt] attributes
Links do not have a discernible name
fruugo.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
Browser errors were logged to the console
Page has valid source maps
fruugo.ca SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fruugo.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 Fruugo.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.
fruugo.ca
Open Graph description is not detected on the main page of Fruugo. 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: