7.8 sec in total
1.3 sec
6 sec
424 ms
Click here to check amazing Foosye content. Otherwise, check out these important facts you probably never knew about foosye.com
Foosye®, short for food systems, is the market maker for the food truck industry! The world's only comprehensive platform solely for the Food Truck Industry
Visit foosye.comWe analyzed Foosye.com page load time and found that the first response time was 1.3 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
foosye.com performance score
1344 ms
75 ms
133 ms
110 ms
223 ms
Our browser made a total of 200 requests to load all elements on the main page. We found that 89% of them (178 requests) were addressed to the original Foosye.com, 9% (17 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Foosye.com.
Page size can be reduced by 2.4 MB (72%)
3.3 MB
947.8 kB
In fact, the total size of Foosye.com main page is 3.3 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. 85% 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. CSS take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 112.3 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 112.3 kB or 81% of the original size.
Potential reduce by 51.8 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, Foosye needs image optimization as it can save up to 51.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 401.5 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 401.5 kB or 66% of the original size.
Potential reduce by 1.8 MB
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. Foosye.com needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 86% of the original size.
Number of requests can be reduced by 169 (93%)
181
12
The browser has sent 181 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foosye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 120 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.
foosye.com
1344 ms
wp-emoji-release.min.js
75 ms
layerslider.css
133 ms
css
110 ms
style.min.css
223 ms
wide_open_big.css
196 ms
styles.css
206 ms
styles.css
297 ms
matweetfeeds-style.css
207 ms
pps_style.css
216 ms
listing.css
384 ms
listing-responsive.min.css
248 ms
qode-membership.min.css
292 ms
qode-membership-responsive.min.css
284 ms
qode-quick-links.min.css
285 ms
qode-restaurant.min.css
327 ms
qode-restaurant-responsive.min.css
329 ms
rs6.css
329 ms
job-listings.css
356 ms
checkbox.min.css
347 ms
mediaelementplayer-legacy.min.css
378 ms
wp-mediaelement.min.css
436 ms
style.css
426 ms
font-awesome.min.css
427 ms
style.min.css
437 ms
style.css
459 ms
dripicons.css
439 ms
kiko-all.css
454 ms
font-awesome-5.min.css
447 ms
stylesheet.min.css
570 ms
print.css
421 ms
style_dynamic_callback.php
1347 ms
responsive.min.css
496 ms
style_dynamic_responsive_callback.php
1245 ms
vertical_responsive.min.css
477 ms
js_composer.min.css
723 ms
css
79 ms
core-dashboard.min.css
540 ms
platform.js
97 ms
form.min.css
531 ms
dashicons.min.css
809 ms
common-style.css
753 ms
magnific-popup.css
562 ms
shortcode.css
670 ms
socialshare.css
671 ms
style.css
661 ms
cforms-common.css
689 ms
jquery.min.js
672 ms
jquery-migrate.min.js
631 ms
admin.js
631 ms
greensock.js
656 ms
layerslider.kreaturamedia.jquery.js
617 ms
layerslider.transitions.js
611 ms
cforms.js
600 ms
fts-global.js
597 ms
rbtools.min.js
598 ms
rs6.min.js
620 ms
bpopup.js
525 ms
jquery.popupslider.js
526 ms
jquery.cookie.js
537 ms
jquery.easing.1.3.js
525 ms
pps_script.js
534 ms
regenerator-runtime.min.js
533 ms
wp-polyfill.min.js
536 ms
index.js
548 ms
core.min.js
547 ms
datepicker.min.js
520 ms
accordion.min.js
516 ms
menu.min.js
493 ms
dom-ready.min.js
454 ms
hooks.min.js
437 ms
i18n.min.js
451 ms
a11y.min.js
291 ms
autocomplete.min.js
190 ms
controlgroup.min.js
189 ms
checkboxradio.min.js
200 ms
button.min.js
216 ms
mouse.min.js
219 ms
resizable.min.js
186 ms
draggable.min.js
192 ms
dialog.min.js
216 ms
droppable.min.js
215 ms
progressbar.min.js
227 ms
selectable.min.js
210 ms
sortable.min.js
235 ms
slider.min.js
256 ms
spinner.min.js
248 ms
tooltip.min.js
272 ms
tabs.min.js
286 ms
effect.min.js
295 ms
effect-blind.min.js
309 ms
effect-bounce.min.js
296 ms
effect-clip.min.js
318 ms
effect-drop.min.js
328 ms
effect-explode.min.js
322 ms
effect-fade.min.js
343 ms
effect-fold.min.js
373 ms
effect-highlight.min.js
371 ms
effect-pulsate.min.js
383 ms
effect-size.min.js
781 ms
effect-scale.min.js
778 ms
effect-shake.min.js
924 ms
effect-slide.min.js
929 ms
effect-transfer.min.js
926 ms
doubletaptogo.js
924 ms
modernizr.min.js
910 ms
jquery.appear.js
1028 ms
hoverIntent.min.js
1018 ms
counter.js
1013 ms
easypiechart.js
998 ms
mixitup.js
984 ms
jquery.prettyPhoto.js
975 ms
jquery.fitvids.js
974 ms
jquery.flexslider-min.js
969 ms
mediaelement-and-player.min.js
1039 ms
mediaelement-migrate.min.js
942 ms
wp-mediaelement.min.js
930 ms
infinitescroll.min.js
933 ms
jquery.waitforimages.js
904 ms
jquery.form.min.js
891 ms
waypoints.min.js
884 ms
jplayer.min.js
954 ms
bootstrap.carousel.js
939 ms
skrollr.js
935 ms
Chart.min.js
916 ms
jquery.easing.1.3.js
914 ms
abstractBaseClass.js
903 ms
jquery.countdown.js
928 ms
jquery.multiscroll.min.js
881 ms
jquery.justifiedGallery.min.js
963 ms
bigtext.js
947 ms
jquery.sticky-kit.min.js
915 ms
owl.carousel.min.js
914 ms
typed.js
901 ms
jquery.carouFredSel-6.2.1.min.js
850 ms
lemmon-slider.min.js
825 ms
ga.js
282 ms
jquery.fullPage.min.js
683 ms
jquery.mousewheel.min.js
675 ms
jquery.touchSwipe.min.js
680 ms
jquery.isotope.min.js
679 ms
packery-mode.pkgd.min.js
699 ms
jquery.stretch.js
566 ms
imagesloaded.js
569 ms
rangeslider.min.js
566 ms
jquery.event.move.js
569 ms
jquery.twentytwenty.js
569 ms
swiper.min.js
739 ms
default_dynamic_callback.php
1337 ms
default.min.js
745 ms
comment-reply.min.js
563 ms
ajax.js
733 ms
js_composer_front.min.js
733 ms
qode-like.min.js
732 ms
qode-news-like.js
732 ms
jquery.slimscroll.min.js
732 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3iQ.woff
489 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTo3iQ.woff
490 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTo3iQ.woff
503 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTo3iQ.woff
508 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3iQ.woff
508 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3iQ.woff
509 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTo3iQ.woff
508 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTo3iQ.woff
503 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
507 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
513 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
512 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
513 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
511 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
510 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
509 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
512 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
513 ms
jquery.cookie.js
698 ms
__utm.gif
456 ms
jquery.magnific-popup.min.js
646 ms
qcld-wp-chatbot-plugin.js
646 ms
qcld-wp-chatbot-front.js
646 ms
socialshare.js
644 ms
rangeslider.min.js
643 ms
select2.min.js
644 ms
underscore.min.js
645 ms
listing.js
656 ms
fontawesome-webfont.woff
639 ms
foosyeLinearTextR.png
559 ms
cropped-foosyeLogoOnly.png
689 ms
foosye-truck.jpeg
606 ms
iPhone6plus1.png
608 ms
ipad1.png
621 ms
edge1.png
332 ms
iWatch1.png
379 ms
icon-3.png
384 ms
vertical_menu_cross.png
403 ms
socialshare.png
792 ms
if_facebook_115476.png
385 ms
if_twitter_alt_115673.png
775 ms
if_linkedin_115546.png
773 ms
if_33-pinterest_104469.png
775 ms
if_18-youtube_104482.png
772 ms
if_38-instagram_104466.png
772 ms
foosye.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foosye.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 Foosye.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.
foosye.com
Open Graph data is detected on the main page of Foosye. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: