3.2 sec in total
404 ms
2.3 sec
491 ms
Click here to check amazing Store Whole Hearted Foods content. Otherwise, check out these important facts you probably never knew about store.wholeheartedfoods.com
US grown pumpkin seed and squash seed snacks and culinary oils
Visit store.wholeheartedfoods.comWe analyzed Store.wholeheartedfoods.com page load time and found that the first response time was 404 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
store.wholeheartedfoods.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value4.8 s
30/100
25%
Value6.8 s
34/100
10%
Value500 ms
58/100
30%
Value0.208
60/100
15%
Value12.6 s
14/100
10%
404 ms
312 ms
116 ms
176 ms
178 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 77% of them (100 requests) were addressed to the original Store.wholeheartedfoods.com, 8% (11 requests) were made to I0.wp.com and 6% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (766 ms) belongs to the original domain Store.wholeheartedfoods.com.
Page size can be reduced by 205.1 kB (22%)
925.2 kB
720.1 kB
In fact, the total size of Store.wholeheartedfoods.com main page is 925.2 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. 70% of websites need less resources to load. Images take 578.0 kB which makes up the majority of the site volume.
Potential reduce by 204.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 204.1 kB or 76% of the original size.
Potential reduce by 957 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. Store Whole Hearted Foods images are well optimized though.
Potential reduce by 66 B
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 95 (81%)
117
22
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Store Whole Hearted Foods. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
store.wholeheartedfoods.com
404 ms
store.wholeheartedfoods.com
312 ms
dashicons.min.css
116 ms
autoptimize_single_37faeb50ef52da086e0f8c2c289e66d4.css
176 ms
sbi-styles.min.css
178 ms
style.min.css
183 ms
mediaelementplayer-legacy.min.css
181 ms
wp-mediaelement.min.css
181 ms
autoptimize_single_b4cff11e39c2d54322f43448252c482a.css
181 ms
autoptimize_single_8b2637597ab5218d9ac392df2de3b822.css
234 ms
autoptimize_single_73136c6183029bfb517a3995c00da88a.css
237 ms
autoptimize_single_eeb616c7d096549b9792359164dafe24.css
238 ms
autoptimize_single_d2091ba0d42761c7e966c76f24de9bca.css
239 ms
wpmenucart-icons.min.css
236 ms
wpmenucart-main.min.css
239 ms
autoptimize_single_d09c181cb27e37d92e51acf810dc1778.css
292 ms
style.css
301 ms
wpfront-notification-bar.min.css
294 ms
autoptimize_single_8575eb81f52d33ca0c457788e06ff42e.css
296 ms
autoptimize_single_cfa2e906e81e3eb5807ec53d555a6a18.css
294 ms
autoptimize_single_06daef8969065933e7da84b7d75c6ec7.css
306 ms
autoptimize_single_4d06a0feec07dd75e1020e3436656f86.css
350 ms
cff-style.min.css
352 ms
font-awesome.min.css
52 ms
autoptimize_single_d6c280f1424cbd0ed62afdc7cd136712.css
353 ms
autoptimize_single_eaaafab3de35403bf092903915fc7d74.css
354 ms
sccss.css
356 ms
autoptimize_single_785409f71f29db85aa2628f8683b94cc.css
357 ms
autoptimize_single_6480fc17d1a86c513232871d52406592.css
407 ms
autoptimize_single_6903125ee17adaef69d3bad628516b08.css
412 ms
jquery.min.js
427 ms
jquery-migrate.min.js
424 ms
wp-polyfill-inert.min.js
426 ms
regenerator-runtime.min.js
427 ms
wp-polyfill.min.js
475 ms
hooks.min.js
471 ms
w.js
38 ms
jquery.blockUI.min.js
471 ms
add-to-cart.min.js
472 ms
s-202405.js
38 ms
e-202405.js
36 ms
css
48 ms
autoptimize_single_0dccf79e4ae955b32dea554e34e5a561.css
451 ms
autoptimize_single_7781b74872ebf54ac04b92ed258916de.css
390 ms
js.cookie.min.js
364 ms
woocommerce.min.js
360 ms
wpfront-notification-bar.min.js
358 ms
cart-fragments.min.js
359 ms
jquery.bind-first-0.2.3.min.js
360 ms
js.cookie-2.1.3.min.js
357 ms
autoptimize_single_2f7eaa3145f3d49d4d8abbdaff1005ee.js
364 ms
autoptimize_single_22b5ca4717452e7ab97f75a24e547d94.js
361 ms
autoptimize_single_7a575ed24e7c210825458efde43e5df6.js
362 ms
autoptimize_single_328b8123661abdd5f4a0c695e7aa9dcc.js
471 ms
sourcebuster.min.js
473 ms
order-attribution.min.js
471 ms
react.min.js
423 ms
deprecated.min.js
420 ms
dom.min.js
422 ms
react-dom.min.js
421 ms
escape-html.min.js
406 ms
element.min.js
407 ms
is-shallow-equal.min.js
376 ms
i18n.min.js
375 ms
keycodes.min.js
374 ms
priority-queue.min.js
371 ms
compose.min.js
370 ms
private-apis.min.js
371 ms
redux-routine.min.js
425 ms
data.min.js
408 ms
lodash.min.js
409 ms
autoptimize_single_36878700722ad5c1f9c12d4c1c543977.js
407 ms
url.min.js
383 ms
api-fetch.min.js
385 ms
autoptimize_single_178f4d3163b38b06e6b4a00d28fbb566.js
426 ms
data-controls.min.js
424 ms
html-entities.min.js
425 ms
g.gif
15 ms
notices.min.js
400 ms
autoptimize_single_bdc1e466fc436dc223abbd653674f2ad.js
401 ms
autoptimize_single_d362db0897dcd4f234bab878252648ae.js
401 ms
dom-ready.min.js
421 ms
a11y.min.js
421 ms
primitives.min.js
421 ms
warning.min.js
419 ms
autoptimize_single_32eebd049df2f836e758e968164ef6fe.js
420 ms
autoptimize_single_da81d17da809a68f4d7dab3e8e0e1326.js
480 ms
order-attribution-blocks.min.js
420 ms
mailchimp-woocommerce-public.min.js
390 ms
navigation.min.js
308 ms
cff-scripts.min.js
308 ms
autoptimize_single_d0371523eecceaae282b1b6c8c39215e.js
310 ms
autoptimize_single_a1ade95e21102c15d71ee475ac3818f6.js
365 ms
header-cart.min.js
360 ms
footer.min.js
371 ms
hoverIntent.min.js
373 ms
autoptimize_single_686da681608fac74564bd202cf8b14c2.js
373 ms
autoptimize_single_00644109bc37fbab6d10880cabb3d6ed.js
374 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff
46 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdo.woff
96 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff
133 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff
131 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdo.woff
131 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuvMQQ.woff
132 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuvMQQ.woff
132 ms
wARDj0u
8 ms
fontawesome-webfont.woff
16 ms
z7NHdQDnbTkabZAIOl9il_O6KJj73e7Fd_-7suD8S72T.woff
160 ms
lazyload.min.js
434 ms
fa-solid-900.woff
642 ms
sbi-sprite.png
430 ms
pumpkin_vine_transp3.gif
766 ms
arrow_down.png
396 ms
g.gif
40 ms
store.wholeheartedfoods.com
503 ms
loadingAnimation.gif
61 ms
cropped-logo_for_wordpress_apr18.png
51 ms
stony-brook-usa-pumpkin-seeds-field-2880x1500-1-scaled.jpg
54 ms
heirloom-pumpkins-american-grown-2880x1500-1-scaled.jpg
145 ms
raw-pumpkin-seeds-without-shell-2880x1500-1-scaled.jpg
154 ms
pumpkin-harvester-in-field-juan-2880x1500-1-scaled.jpg
53 ms
raw-pumpkin-seed-dryer-2880x1500-1-scaled.jpg
129 ms
family-owed-farm-sourced-2880x1500-1-scaled.jpg
110 ms
pepitas_bowl_wide2.jpg
83 ms
oil_bowls_wide.jpg
83 ms
seed_protein_powders.jpg
89 ms
stony_brook_wholeheartedfoods_seeds_cases_800px.jpg
86 ms
USA-grown-and-made-flag-150.gif
63 ms
place
456 ms
js
55 ms
store.wholeheartedfoods.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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>).
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.
store.wholeheartedfoods.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
store.wholeheartedfoods.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Store.wholeheartedfoods.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 Store.wholeheartedfoods.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.
store.wholeheartedfoods.com
Open Graph data is detected on the main page of Store Whole Hearted Foods. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: