5.3 sec in total
1.2 sec
3.9 sec
220 ms
Welcome to foodprint.io homepage info - get ready to check Foodprint best content right away, or after learning these important things about foodprint.io
Our Story About Us We are Foodprint, a multi award-winning social enterprise, that run a social supermarket and redistribution network in the heart of Sneinton, Nottingham. Our store, is run by our st...
Visit foodprint.ioWe analyzed Foodprint.io page load time and found that the first response time was 1.2 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
foodprint.io performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value6.1 s
12/100
25%
Value6.8 s
35/100
10%
Value760 ms
38/100
30%
Value0.006
100/100
15%
Value8.7 s
36/100
10%
1211 ms
65 ms
103 ms
195 ms
248 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 81% of them (79 requests) were addressed to the original Foodprint.io, 15% (15 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Foodprint.io.
Page size can be reduced by 179.3 kB (23%)
784.5 kB
605.2 kB
In fact, the total size of Foodprint.io main page is 784.5 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. 60% of websites need less resources to load. CSS take 236.0 kB which makes up the majority of the site volume.
Potential reduce by 74.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 74.1 kB or 79% of the original size.
Potential reduce by 13.3 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. Foodprint images are well optimized though.
Potential reduce by 25.7 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 25.7 kB or 11% of the original size.
Potential reduce by 66.2 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. Foodprint.io needs all CSS files to be minified and compressed as it can save up to 66.2 kB or 28% of the original size.
Number of requests can be reduced by 68 (92%)
74
6
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foodprint. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
www.foodprint.io
1211 ms
js
65 ms
sbi-styles.min.css
103 ms
style-block-editor.css
195 ms
styles.css
248 ms
cookie-law-info-public.css
282 ms
cookie-law-info-gdpr.css
260 ms
style.css
364 ms
woo-mini-cart.min.css
285 ms
all.min.css
287 ms
simple-line-icons.min.css
329 ms
style.min.css
419 ms
css
33 ms
elementor-icons.min.css
360 ms
frontend.min.css
446 ms
swiper.min.css
367 ms
post-1731.css
405 ms
animate.css
520 ms
sliders.min.css
442 ms
icomoon.css
451 ms
lae-frontend.css
482 ms
lae-grid.css
498 ms
lae-widgets.min.css
523 ms
all.min.css
528 ms
v4-shims.min.css
531 ms
global.css
557 ms
post-1860.css
574 ms
woocommerce.min.css
598 ms
woo-star-font.min.css
603 ms
woo-quick-view.min.css
605 ms
widgets.css
608 ms
css
30 ms
frontend-gtag.min.js
632 ms
jquery.min.js
651 ms
jquery-migrate.min.js
675 ms
cookie-law-info-public.js
677 ms
v4-shims.min.js
683 ms
index.js
730 ms
index.js
735 ms
jquery.blockUI.min.js
734 ms
add-to-cart.min.js
620 ms
js.cookie.min.js
575 ms
woocommerce.min.js
541 ms
cart-fragments.min.js
527 ms
imagesloaded.min.js
517 ms
masonry.min.js
542 ms
owl-carousel.min.js
556 ms
imagesloaded.pkgd.min.js
517 ms
main.js
506 ms
theme.min.js
505 ms
drop-down-mobile-menu.min.js
503 ms
magnific-popup.min.js
490 ms
ow-lightbox.min.js
500 ms
flickity.pkgd.min.js
484 ms
ow-slider.min.js
504 ms
scroll-effect.min.js
503 ms
select.min.js
469 ms
woo-custom-features.min.js
476 ms
woo-cat-widget.min.js
486 ms
woo-quick-view.min.js
481 ms
underscore.min.js
494 ms
wp-util.min.js
502 ms
add-to-cart-variation.min.js
477 ms
jquery.flexslider.min.js
477 ms
woo-mini-cart.min.js
484 ms
webpack.runtime.min.js
485 ms
frontend-modules.min.js
498 ms
waypoints.min.js
496 ms
core.min.js
484 ms
frontend.min.js
468 ms
frontend.min.js
490 ms
sbi-sprite.png
471 ms
logo-v2-smaller.png
455 ms
Enactus_UoN_Nottingham_0319_023-700x525.jpg
537 ms
IMG_8217-700x525.jpg
540 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
20 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
26 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
42 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
49 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
48 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
50 ms
fa-brands-400.woff
545 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
47 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
47 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
50 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
66 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
63 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
63 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
65 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
65 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
65 ms
fa-brands-400.ttf
726 ms
Simple-Line-Icons.ttf
571 ms
fa-regular-400.woff
483 ms
fa-regular-400.ttf
635 ms
fa-solid-900.woff
651 ms
fa-solid-900.ttf
703 ms
foodprint.io 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
foodprint.io 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
foodprint.io 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
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 Foodprint.io 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 Foodprint.io 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.
foodprint.io
Open Graph data is detected on the main page of Foodprint. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: