Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.eatright.org/Areas/Shared/scripts/main.bundle.js?v=639124805295673283	0.0 ms	95.0 KiB
www.eatright.org/Areas/Shared/css/styles.css?v=639124805295673283	0.0 ms	78.7 KiB
www.eatright.org/Areas/Shared/scripts/9257.bbee844077b63eeed19f.js	0.0 ms	38.1 KiB
www.eatright.org/areas/shared/fonts/lato-regular.woff2	0.0 ms	28.8 KiB
www.eatright.org/areas/shared/fonts/lato-bold.woff2	0.0 ms	28.3 KiB
www.eatright.org/areas/shared/fonts/lato-black.woff2	0.0 ms	27.9 KiB
consent.cookiebot.com/uc.js	172.0 s	27.0 KiB
www.eatright.org/Areas/Shared/scripts/3252.d5597fe09586c9e38784.js	0.0 ms	3.9 KiB
www.eatright.org/Areas/Shared/scripts/429.88c0160240874acd67a4.js	0.0 ms	3.8 KiB
www.eatright.org/Areas/Shared/scripts/3870.5d49eddb73ab2a7c4bbe.js	0.0 ms	1.1 KiB
www.eatright.org/Areas/Shared/scripts/5320.5da7700442ccd83bddc1.js	0.0 ms	799 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: A Seat at Every Table logo with tagline Fueling Fresh Conversations

path: 1,HTML,1,BODY,9,DIV,1,MAIN,1,SECTION,0,ARTICLE,0,DIV,0,A,0,SPAN,0,SPAN,0,PICTURE,4,IMG

selector: span.image > span.image__wrapper > picture > img

snippet: <img src="https://www.eatright.org/-/media/images/eatright-campaigns/and_campaign-ma…" width="967" height="554" alt="A Seat at Every Table logo with tagline Fueling Fresh Conversations" loading="lazy">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.eatright.org/Areas/Shared/css/styles.css?v=639124805295673283	78.7 KiB	787 ms
consent.cookiebot.com/uc.js	27.0 KiB	1.1 s

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Photo of someone scrolling the Find a Nutrition Expert directory on a mobile de… `div.topic-cards__card-container > article#card-R230da27e16cd41c4b1c070490b329310 > picture.accent-card__image-container > img.accent-card__image`	/-/media/images/eatrightpro-landing-pages/aboutus-findanu...	143.2 KiB	104.6 KiB
Nutrition Fact Check logo `div.topic-cards__card-container > article#card-R3e143d26346f4ea3831debb32732d14d > picture.accent-card__image-container > img.accent-card__image`	/-/media/images/eatright-campaigns/nutrition-fact-check/n...	109.6 KiB	88.1 KiB
10 Reasons to See an RDN `div.topic-cards__card-container > article#card-R8acc5b3b185e48ddb58d799be6223b0f > picture.accent-card__image-container > img.accent-card__image`	/-/media/images/eatright-articles/eatright-article-featur...	52.5 KiB	18.8 KiB
eatright.org Logo `div.footer__top > div.footer__logo-container > a > img`	/-/media/images/navigation/footer/logo-eatright-footer.pn...	11.5 KiB	9.4 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 946 ms

URL	Time Spent
eatright.org/	946 ms
www.eatright.org/	0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 310 ms 79.5 KiB

URL	Transfer Size	Est Savings
www.eatright.org/Areas/Shared/css/styles.css?v=639124805295673283	78.4 KiB	68.5 KiB
	13.4 KiB	11.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 630 ms 178.6 KiB

URL	Transfer Size	Est Savings
www.eatright.org/Areas/Shared/scripts/main.bundle.js?v=639124805295673283	94.8 KiB	68.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-NCQLCZ	156.0 KiB	58.2 KiB
www.eatright.org/Areas/Shared/scripts/9257.bbee844077b63eeed19f.js	37.8 KiB	27.1 KiB
/b5127385-71c8-4bdd-a05e-d3bbf7db2473/cc.js?renew=false&r...	106.1 KiB	25.1 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.eatright.org/	797 ms	20 ms	3.0 ms
/b5127385-71c8-4bdd-a05e-d3bbf7db2473/cc.js?renew=false&r...	640 ms	249 ms	37 ms
www.googletagmanager.com/gtm.js?id=GTM-NCQLCZ	612 ms	511 ms	74 ms
www.eatright.org/Areas/Shared/scripts/main.bundle.js?v=639124805295673283	342 ms	184 ms	31 ms
Unattributable	342 ms	14 ms	0.0 ms
consent.cookiebot.com/uc.js	199 ms	170 ms	14 ms
www.eatright.org/Areas/Shared/scripts/9257.bbee844077b63eeed19f.js	149 ms	62 ms	15 ms
www.eatright.org/Areas/Shared/css/styles.css?v=639124805295673283	101 ms	0.0 ms	0.0 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.3 s
Style & Layout	819 ms
Other	450 ms
Parse HTML & CSS	399 ms
Script Parsing & Compilation	185 ms
Rendering	117 ms
Garbage Collection	17 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Photo of someone scrolling the Find a Nutrition Expert directory on a mobile de… `div.topic-cards__card-container > article#card-R230da27e16cd41c4b1c070490b329310 > picture.accent-card__image-container > img.accent-card__image`	/-/media/images/eatrightpro-landing-pages/aboutus-findanu...
Nutrition Fact Check logo `div.topic-cards__card-container > article#card-R3e143d26346f4ea3831debb32732d14d > picture.accent-card__image-container > img.accent-card__image`	/-/media/images/eatright-campaigns/nutrition-fact-check/n...
10 Reasons to See an RDN `div.topic-cards__card-container > article#card-R8acc5b3b185e48ddb58d799be6223b0f > picture.accent-card__image-container > img.accent-card__image`	/-/media/images/eatright-articles/eatright-article-featur...

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,291 KiB

●Avoid long main-thread tasks 11 long tasks found

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 530 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
The Academy of Nutrition and Dietetics’ A Seat at Every Table is a nationwide i… `section.featured-promo > article.card > div.card__content > h3#Rad32694326814e1b938a2534c48883eb`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn More `section.featured-promo > article.card > div.card__content > a.link-button`
See More `div.main-featured-content__wrapper > article.card > div.card__content > a.button`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.eatright.org/everytable	Learn More
/food/home-food-safety/cleaning-tips/how-clean-is-your-re...	See More
/health/wellness/nutrition-panels-and-food-labels/increas...	Learn More
/health/wellness/awareness-campaigns/reduce-risk-during-c...	Learn More
www.eatright.org/health/wellness/diet-trends/staying-away-from-fad-diets	Learn More

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`