14.4 sec in total
207 ms
12 sec
2.2 sec
Welcome to whatthecup.ca homepage info - get ready to check What The Cup best content right away, or after learning these important things about whatthecup.ca
Shop freshly roasted coffee beans from local Canadian roasters. Free shipping on orders over $75 across Ontario and $100 for other provinces. All the roasters ensure crop to cup traceability.
Visit whatthecup.caWe analyzed Whatthecup.ca page load time and found that the first response time was 207 ms and then it took 14.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
whatthecup.ca performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value23.3 s
0/100
25%
Value30.4 s
0/100
10%
Value37,680 ms
0/100
30%
Value0.042
99/100
15%
Value55.5 s
0/100
10%
207 ms
171 ms
637 ms
186 ms
233 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 36% of them (38 requests) were addressed to the original Whatthecup.ca, 29% (30 requests) were made to Fonts.gstatic.com and 7% (7 requests) were made to Downloads.mailchimp.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Whatthecup.ca.
Page size can be reduced by 242.8 kB (15%)
1.6 MB
1.4 MB
In fact, the total size of Whatthecup.ca main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 70.2 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 70.2 kB or 81% of the original size.
Potential reduce by 46.9 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. What The Cup images are well optimized though.
Potential reduce by 88.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 88.3 kB or 26% of the original size.
Potential reduce by 37.4 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. Whatthecup.ca needs all CSS files to be minified and compressed as it can save up to 37.4 kB or 21% of the original size.
Number of requests can be reduced by 35 (51%)
69
34
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What The Cup. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
whatthecup.ca
207 ms
www.whatthecup.ca
171 ms
autoptimize_7a5c651c8fc073c60eac4bc112071fda.css
637 ms
font-awesome.min.css
186 ms
css
233 ms
jquery.min.js
754 ms
widget.js
300 ms
s-202241.js
222 ms
classic-10_7.css
211 ms
wp-polyfill.min.js
463 ms
i18n.min.js
304 ms
lodash.min.js
538 ms
url.min.js
311 ms
hooks.min.js
382 ms
api-fetch.min.js
395 ms
api.js
238 ms
e-202241.js
211 ms
autoptimize_60bc5b075d557de59c7cdbf5868302ee.js
1255 ms
gtm.js
627 ms
fbevents.js
499 ms
11-1.jpg
1248 ms
8-2.jpg
1507 ms
6-2.jpg
1077 ms
10-1.jpg
1217 ms
5-1.jpg
1214 ms
8-1.jpg
1075 ms
7-1.jpg
726 ms
7-2.jpg
1238 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrcVIT9d4cw.woff
457 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrcVIT9d4cydYA.woff
661 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCHPrcVIT9d4cydYA.woff
770 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCMPrcVIT9d4cydYA.woff
768 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCFPrcVIT9d4cydYA.woff
769 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d4cw.woff
901 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrcVIT9d4cydYA.woff
907 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCHPrcVIT9d4cydYA.woff
906 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCMPrcVIT9d4cydYA.woff
935 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCFPrcVIT9d4cydYA.woff
933 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrcVIT9d4cw.woff
934 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrcVIT9d4cydYA.woff
934 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCHPrcVIT9d4cydYA.woff
933 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCMPrcVIT9d4cydYA.woff
934 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCFPrcVIT9d4cydYA.woff
1184 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrcVIT9d4cw.woff
1184 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrcVIT9d4cydYA.woff
1182 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CHPrcVIT9d4cydYA.woff
1182 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CMPrcVIT9d4cydYA.woff
1182 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CFPrcVIT9d4cydYA.woff
1182 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrcVIT9d4cw.woff
1216 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrcVIT9d4cydYA.woff
1216 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCHPrcVIT9d4cydYA.woff
1216 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCMPrcVIT9d4cydYA.woff
1215 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCFPrcVIT9d4cydYA.woff
1216 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrcVIT9d4cw.woff
1215 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrcVIT9d4cydYA.woff
1292 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCHPrcVIT9d4cydYA.woff
1291 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCMPrcVIT9d4cydYA.woff
1292 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCFPrcVIT9d4cydYA.woff
1290 ms
fontawesome-webfont.woff
288 ms
fontawesome-webfont.woff
1194 ms
fontawesome-webfont.woff
652 ms
f167c1d5596460538a7461643.js
1169 ms
wp-polyfill-fetch.min.js
178 ms
wp-polyfill-dom-rect.min.js
178 ms
wp-polyfill-url.min.js
283 ms
wp-polyfill-formdata.min.js
176 ms
wp-polyfill-element-closest.min.js
393 ms
identity.js
180 ms
1271441676398689
543 ms
conversion_async.js
551 ms
preloader.gif
327 ms
Untitled-design-22.jpg
1462 ms
Coffee-section-website.jpg
1375 ms
recaptcha__en.js
666 ms
analytics.js
599 ms
Subtext-Coffee-Roasters.jpg
896 ms
Ethica-Logo.jpg
449 ms
Pirates-of-coffee.jpg
892 ms
Angry-roaster-logo.jpg
1337 ms
5.jpg
891 ms
Hatch-Logo.jpg
1116 ms
465 ms
Barocco-Logo.jpg
607 ms
De-Mello-Palheta-Logo.jpg
604 ms
Coffee-by-Design-Logo.jpg
644 ms
Hale-coffee.jpg
683 ms
Pop-Coffee-Logo.jpg
1261 ms
4.jpg
866 ms
Website-Blog-2.jpg
1805 ms
Barocco-Tea-Logo.jpg
735 ms
Pluck-tea-logo.jpg
935 ms
embed.js
338 ms
collect
127 ms
collect
166 ms
148 ms
form-settings
382 ms
ga-audiences
30 ms
popup.js
5 ms
common.css
69 ms
banner.css
70 ms
layout-1.css
42 ms
modal-slidein.css
48 ms
textBadge.svg
129 ms
autoptimize_541e2ced151704f4ff1844c6de47ec02.css
88 ms
openbridge_plugin.js
739 ms
whatthecup.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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>).
whatthecup.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
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 Whatthecup.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 Whatthecup.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.
whatthecup.ca
Open Graph data is detected on the main page of What The Cup. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: