3.6 sec in total
126 ms
3.3 sec
156 ms
Visit cub.com now to see the best up-to-date Cub content for United States and also check out these interesting facts you probably never knew about cub.com
Shop online or plan your instore visit with Cub's exclusive online grocery shopping experience. See what's on sale every week in our digital Weekly Ad. Get free pickup, same day delivery and exclusive...
Visit cub.comWe analyzed Cub.com page load time and found that the first response time was 126 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
cub.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value22.7 s
0/100
25%
Value9.5 s
12/100
10%
Value2,160 ms
6/100
30%
Value0.136
80/100
15%
Value20.5 s
2/100
10%
126 ms
588 ms
137 ms
724 ms
20 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 74% of them (35 requests) were addressed to the original Cub.com, 6% (3 requests) were made to Fast.fonts.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Cub.com.
Page size can be reduced by 690.0 kB (38%)
1.8 MB
1.1 MB
In fact, the total size of Cub.com main page is 1.8 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. 30% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 26.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 26.1 kB or 76% of the original size.
Potential reduce by 72.5 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. Cub images are well optimized though.
Potential reduce by 215.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 215.4 kB or 70% of the original size.
Potential reduce by 376.1 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. Cub.com needs all CSS files to be minified and compressed as it can save up to 376.1 kB or 87% of the original size.
Number of requests can be reduced by 15 (36%)
42
27
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cub. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
cub.com
126 ms
www.cub.com
588 ms
9af7ce82-63af-4c4a-99bb-73f6122d2174.css
137 ms
cub-combinedss.css
724 ms
jquery-1.9.1.min.js
20 ms
csrf.js
188 ms
header-js-combined.js
618 ms
jquery-ui.min.js
78 ms
footer-js-combined.js
423 ms
token.json
53 ms
1456515735754.png
123 ms
1447362244601.png
137 ms
CUB_WK01_HP_PorkShoulder.png
505 ms
Easter_HP.png
447 ms
WK47_CUB_MNZOO_HP.png
417 ms
WK01_CUB_HP_29Cents.png
480 ms
1456518312586.png
290 ms
1456518370435.jpg
508 ms
icn-facebook.png
339 ms
img-social-twitter.png
459 ms
img-app-ios.png
499 ms
img-app-android.png
557 ms
img-rewards-card.png
537 ms
gtm.js
131 ms
bg-header-customer.png
547 ms
bg-input-field.gif
536 ms
icn-grey-arrow-round.png
537 ms
c5b1c170-d8f7-41f9-85c2-0ab670780c6b.woff
104 ms
bg-header-logo.png
577 ms
gray-background.png
559 ms
sprite-secondary-nav.png
623 ms
img-footer-bar.png
618 ms
all.js
192 ms
c22866d7-ca67-4170-a113-cae280eea669.woff
83 ms
utilityNav.userinfo.html
507 ms
_jcr_content.header.html
571 ms
shoppinglist.activelist.json
523 ms
_jcr_content.breadcrumbajax.html
1660 ms
btn-slideshow-next-prev-new.png
618 ms
img-slideshow-pagination.png
637 ms
analytics.js
53 ms
collect
24 ms
collect
61 ms
49 ms
xd_arbiter.php
137 ms
1456639200588.png
1191 ms
0.gif
50 ms
cub.com 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 IDs are not unique
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
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>).
cub.com 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
cub.com SEO score
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 Cub.com 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 Cub.com 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.
cub.com
Open Graph data is detected on the main page of Cub. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: