Tools & Wizards About Us
foodvisor.co screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

foodvisor.co

Foodvisor App - Nutrition Coaching - Eat Healthy & Lose Weight

Page Load Speed

1.1 sec in total

First Response

21 ms

Resources Loaded

1 sec

Page Rendered

80 ms

foodvisor.co screenshot

About Website

Visit foodvisor.co now to see the best up-to-date Foodvisor content and also check out these interesting facts you probably never knew about foodvisor.co

Foodvisor is the number 1 app for adopting healthier habits and losing weight. Get access to a team of dietitians, start your personalized diet plan, discover recipes and reach your health goal.

Visit foodvisor.co

Key Findings

We analyzed Foodvisor.co page load time and found that the first response time was 21 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

foodvisor.co performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

foodvisor.co

21 ms

292 ms

loader.js

430 ms

fvkit.863f60f3.css

68 ms

app.34dab90e.css

65 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Foodvisor.co, 82% (18 requests) were made to Cdn.foodvisor.io and 5% (1 request) were made to Foodvisor.io. The less responsive or slowest element that took the longest time to load (430 ms) relates to the external source Didomi.foodvisor.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.7 kB (4%)

Content Size

205.2 kB

After Optimization

196.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Foodvisor.co main page is 205.2 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. 40% of websites need less resources to load. Javascripts take 187.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 8.0 kB

  • Original 11.1 kB
  • After minification 10.6 kB
  • After compression 3.2 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 8.0 kB or 72% of the original size.

JavaScript Optimization

-0%

Potential reduce by 746 B

  • Original 187.1 kB
  • After minification 187.1 kB
  • After compression 186.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 30 B

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 6.9 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. Foodvisor.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (85%)

Requests Now

20

After Optimization

3

  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foodvisor. 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 as a result speed up the page load time.

Network Requests Diagram

foodvisor.co

foodvisor.co

21 ms

292 ms

loader.js

loader.js

430 ms

fvkit.863f60f3.css

fvkit.863f60f3.css

68 ms

app.34dab90e.css

app.34dab90e.css

65 ms

vue.85756ab0.js

vue.85756ab0.js

73 ms

pinia.45aa77fa.js

pinia.45aa77fa.js

73 ms

luxon.a97798fa.js

luxon.a97798fa.js

75 ms

lodash.0c2cad52.js

lodash.0c2cad52.js

73 ms

intlify.5701f90f.js

intlify.5701f90f.js

74 ms

strings.50b38dd2.js

strings.50b38dd2.js

77 ms

objects.962c80b4.js

objects.962c80b4.js

81 ms

vuetify.15bdba73.js

vuetify.15bdba73.js

81 ms

fvkit.12a52cdf.js

fvkit.12a52cdf.js

81 ms

amplitude.1b79c3de.js

amplitude.1b79c3de.js

80 ms

vite.f63e7675.js

vite.f63e7675.js

80 ms

axios.1cbd2f54.js

axios.1cbd2f54.js

81 ms

utils.e7be7f08.js

utils.e7be7f08.js

87 ms

vueuse.d261b90e.js

vueuse.d261b90e.js

87 ms

vuerouter.d6162a02.js

vuerouter.d6162a02.js

87 ms

app.6675f943.js

app.6675f943.js

86 ms

gtm.js

gtm.js

82 ms

Accessibility Review

foodvisor.co accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

foodvisor.co best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

foodvisor.co SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foodvisor.co 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 Foodvisor.co 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

foodvisor.co

Open Graph data is detected on the main page of Foodvisor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: