Tools & Wizards About Us
ifood.be screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

ifood.be

Tout sur les plafonds Pinel - Plafond loi Pinel

Page Load Speed

5.3 sec in total

First Response

404 ms

Resources Loaded

4.8 sec

Page Rendered

100 ms

ifood.be screenshot

About Website

Welcome to ifood.be homepage info - get ready to check Ifood best content right away, or after learning these important things about ifood.be

Tout sur les plafonds de la loi Pinel pour l'investissement locatif : plafonds de loyers, plafonds de ressources, etc.

Visit ifood.be

Key Findings

We analyzed Ifood.be page load time and found that the first response time was 404 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

ifood.be performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

ifood.be

404 ms

blue_header.png

293 ms

main_full_top.jpg

212 ms

landingpage.jpg

540 ms

whats

523 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 75% of them (6 requests) were addressed to the original Ifood.be, 13% (1 request) were made to Netcraft.com and 13% (1 request) were made to Toolbar.netcraft.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Toolbar.netcraft.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.1 kB (69%)

Content Size

7.4 kB

After Optimization

2.3 kB

  • HTML

In fact, the total size of Ifood.be main page is 7.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 7.4 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 5.1 kB

  • Original 7.4 kB
  • After minification 6.8 kB
  • After compression 2.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 5.1 kB or 69% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

  • AJAX
  • Images

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ifood. According to our analytics all requests are already optimized.

Network Requests Diagram

ifood.be

ifood.be

404 ms

blue_header.png

blue_header.png

293 ms

main_full_top.jpg

main_full_top.jpg

212 ms

landingpage.jpg

landingpage.jpg

540 ms

whats

whats

523 ms

vseparator.png

vseparator.png

132 ms

footer.png

footer.png

181 ms

site_report

site_report

3900 ms

Accessibility Review

ifood.be accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

ifood.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ifood.be SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifood.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Ifood.be 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.

Social Sharing Optimization

ifood.be

Open Graph description is not detected on the main page of Ifood. 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: