805 ms in total
111 ms
504 ms
190 ms
Click here to check amazing SPUD content for Canada. Otherwise, check out these important facts you probably never knew about spud.ca
SPUD's online grocery delivery service provides the best in quality and services. Shop our online aisles like you would your local grocery store with SPUD!
Visit spud.caWe analyzed Spud.ca page load time and found that the first response time was 111 ms and then it took 694 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
spud.ca performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value12.6 s
0/100
25%
Value16.1 s
0/100
10%
Value8,750 ms
0/100
30%
Value0.082
94/100
15%
Value29.3 s
0/100
10%
111 ms
64 ms
48 ms
47 ms
30 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 69% of them (38 requests) were addressed to the original Spud.ca, 7% (4 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (144 ms) belongs to the original domain Spud.ca.
Page size can be reduced by 1.3 MB (69%)
1.9 MB
599.9 kB
In fact, the total size of Spud.ca main page is 1.9 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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 12.9 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 12.9 kB or 72% of the original size.
Potential reduce by 31.8 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. Obviously, SPUD needs image optimization as it can save up to 31.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 819.3 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 819.3 kB or 70% of the original size.
Potential reduce by 457.3 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. Spud.ca needs all CSS files to be minified and compressed as it can save up to 457.3 kB or 86% of the original size.
Number of requests can be reduced by 37 (84%)
44
7
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SPUD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
spud.ca
111 ms
cfmessage.js
64 ms
cfajax.js
48 ms
yahoo-dom-event.js
47 ms
animation-min.js
30 ms
ext-yui-adapter.js
29 ms
ext-all.js
76 ms
cfwindow.js
45 ms
cfform.js
45 ms
masks.js
55 ms
cfformhistory.js
52 ms
ext-all.css
58 ms
cf.css
51 ms
bootstrap.css
43 ms
bootstrap-theme.css
48 ms
spud-boot.css
135 ms
spud-boot-header.css
57 ms
spud-boot-footer.css
71 ms
spud-boot-mobile.css
130 ms
fhmm-main-spud.css
130 ms
fhmm-spud.css
144 ms
spud_last.css
127 ms
Deana_Login.css
131 ms
font-awesome.min.css
138 ms
bootstrap-glyphicons.css
140 ms
jquery-2.1.4.js
122 ms
bootstrap3.3.4.min.js
124 ms
dropit.js
122 ms
bootstrap-select.js
125 ms
fhmm.js
124 ms
typeahead.bundle.js
126 ms
farmbox-search.css
123 ms
bootstrap-select.css
124 ms
conversion.js
119 ms
css
57 ms
css
69 ms
opensans.css
15 ms
bg05.jpg
51 ms
spud_ca.png
24 ms
_aijTyevf54tkVDLy-dlnCZ2oysoEQEeKwjgmXLRnTc.ttf
75 ms
Ubuntu-300.woff
18 ms
sVvvcJDRTINJla2R4XwPVevvDin1pK8aKteLpeZ5c0A.ttf
107 ms
Ubuntu-regular.woff
16 ms
OsJ2DjdpjqFRVUSto6IffCZ2oysoEQEeKwjgmXLRnTc.ttf
110 ms
Ubuntu-500.woff
25 ms
0ihfXUL2emPh0ROJezvraCZ2oysoEQEeKwjgmXLRnTc.ttf
130 ms
Ubuntu-700.woff
24 ms
49 ms
dc.js
37 ms
inpage_linkid.js
26 ms
52 ms
__utm.gif
23 ms
__utm.gif
25 ms
ga-audiences
17 ms
roundtrip.js
7 ms
spud.ca accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
spud.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
spud.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Spud.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 Spud.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.
spud.ca
Open Graph description is not detected on the main page of SPUD. 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: