10.4 sec in total
2.2 sec
7.9 sec
278 ms
Welcome to foyerz.com homepage info - get ready to check Foyerz best content for Canada right away, or after learning these important things about foyerz.com
food catering
Visit foyerz.comWe analyzed Foyerz.com page load time and found that the first response time was 2.2 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
foyerz.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.7 s
3/100
25%
Value10.5 s
7/100
10%
Value1,490 ms
14/100
30%
Value0.577
12/100
15%
Value14.2 s
9/100
10%
2161 ms
172 ms
255 ms
211 ms
195 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 97% of them (60 requests) were addressed to the original Foyerz.com, 2% (1 request) were made to Maps.google.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Foyerz.com.
Page size can be reduced by 417.1 kB (17%)
2.5 MB
2.1 MB
In fact, the total size of Foyerz.com main page is 2.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. 35% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 16.7 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 16.7 kB or 78% of the original size.
Potential reduce by 102.9 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. Foyerz images are well optimized though.
Potential reduce by 164.3 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 164.3 kB or 71% of the original size.
Potential reduce by 133.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. Foyerz.com needs all CSS files to be minified and compressed as it can save up to 133.2 kB or 82% of the original size.
Number of requests can be reduced by 32 (52%)
61
29
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foyerz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
foyerz.com
2161 ms
wp-emoji-release.min.js
172 ms
index.css
255 ms
style.css
211 ms
wp-customer-reviews-generated.css
195 ms
form_style.css
213 ms
style.min.css
215 ms
screen.min.css
235 ms
font-awesome.min.css
323 ms
woocommerce-layout.css
297 ms
woocommerce.css
422 ms
default.min.css
295 ms
jquery.js
501 ms
jquery-migrate.min.js
353 ms
js
47 ms
wp-customer-reviews.js
350 ms
cntctfrm.js
386 ms
front.js
415 ms
dpagination.js
416 ms
shortcode.css
449 ms
superfish.js
451 ms
smthemes.js
453 ms
jquery.cycle.all.js
582 ms
comment-reply.min.js
498 ms
add-to-cart.min.js
517 ms
jquery.blockUI.min.js
518 ms
woocommerce.min.js
533 ms
jquery.cookie.min.js
579 ms
cart-fragments.min.js
600 ms
wp-embed.min.js
600 ms
css
26 ms
wide.css
67 ms
top.png
133 ms
arrow-up.png
133 ms
header.png
205 ms
logo-edit3-50-font20.png
131 ms
search.png
133 ms
baghilpolo333.jpg
397 ms
salad3331.jpg
395 ms
gheymeh333.jpg
519 ms
ghormeh-sabzi33.jpg
338 ms
salad-shirazi3332.jpg
599 ms
ZERESHK-3333.jpg
506 ms
Lubia-Polo-33.jpg
596 ms
pickl2.jpg
583 ms
jam.jpg
606 ms
nankin.jpg
697 ms
jam-carrot.jpg
766 ms
HalalLogo.png
649 ms
menu.png
669 ms
slide-right.png
657 ms
slide-left.png
665 ms
top-n.png
707 ms
main-n.png
723 ms
bottom-n.png
730 ms
footer.png
732 ms
foyerz.com
2490 ms
slider-page-active.png
652 ms
slider-page.png
662 ms
woocommerce-smallscreen.css
68 ms
mobile.css
67 ms
tablet.css
69 ms
foyerz.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
foyerz.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
Missing source maps for large first-party JavaScript
foyerz.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foyerz.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Foyerz.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.
foyerz.com
Open Graph description is not detected on the main page of Foyerz. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: