1.2 sec in total
49 ms
1 sec
146 ms
Welcome to foodlink.net homepage info - get ready to check Foodlink best content for United States right away, or after learning these important things about foodlink.net
Bringing Simplicity and Agility to the World’s Most Complex Supply Chains
Visit foodlink.netWe analyzed Foodlink.net page load time and found that the first response time was 49 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
foodlink.net performance score
49 ms
16 ms
22 ms
23 ms
28 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Foodlink.net, 8% (4 requests) were made to Rtp-static.marketo.com and 6% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (270 ms) relates to the external source Sjrtp5-cdn.marketo.com.
Page size can be reduced by 1.1 MB (70%)
1.5 MB
466.0 kB
In fact, the total size of Foodlink.net main page is 1.5 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. 65% of websites need less resources to load. Javascripts take 833.1 kB which makes up the majority of the site volume.
Potential reduce by 79.0 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 79.0 kB or 81% of the original size.
Potential reduce by 9.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. Obviously, Foodlink needs image optimization as it can save up to 9.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 551.2 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 551.2 kB or 66% of the original size.
Potential reduce by 431.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. Foodlink.net needs all CSS files to be minified and compressed as it can save up to 431.4 kB or 78% of the original size.
Number of requests can be reduced by 37 (80%)
46
9
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foodlink. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
49 ms
wp-emoji-release.min.js
16 ms
colorbox.css
22 ms
settings.css
23 ms
uaf.css
28 ms
css
30 ms
easy-twitter-feed-widget.css
27 ms
integrity-light.css
44 ms
style.css
26 ms
css
37 ms
fa-icon-classes.css
40 ms
jetpack.css
56 ms
addtoany.min.css
60 ms
jquery.js
62 ms
jquery-migrate.min.js
30 ms
jquery.colorbox.js
78 ms
wp-colorbox.js
80 ms
jquery.themepunch.tools.min.js
85 ms
jquery.themepunch.revolution.min.js
80 ms
x-head.min.js
81 ms
cs-head.min.js
82 ms
devicepx-jetpack.js
10 ms
x-body.min.js
77 ms
comment-reply.min.js
73 ms
cs-body.min.js
187 ms
widget-easy-twitter-feed-widget.js
186 ms
wp-embed.min.js
186 ms
e-201611.js
9 ms
page.js
180 ms
analytics.js
179 ms
munchkin.js
179 ms
rtp.js
270 ms
iTrade_logo-250-k1.png
135 ms
FoodLink-with-tagline-01-color-sm.jpg
136 ms
TrueTracLogo-sm.jpg
135 ms
widgets.js
192 ms
1bHRUMxmJHoup12DnI9XmQ.woff
71 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
70 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
71 ms
fontawesome-webfont.woff
71 ms
g.gif
67 ms
sm13.html
86 ms
collect
54 ms
munchkin.js
28 ms
icons.15.svg.css
54 ms
jquery.min.js
21 ms
jquery-ui-insightera-custom-1.8.css
16 ms
ga-integration-2.0.1.js
14 ms
visitWebPage
52 ms
collect
109 ms
ga.js
79 ms
jquery-custom-ui.min.js
27 ms
foodlink.net SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foodlink.net 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 Foodlink.net 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.
foodlink.net
Open Graph data is detected on the main page of Foodlink. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: