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
/libs/cookbook-web-fonts/v1.0.12/bagoss-standard/BagossSt...	1440.0 s	58.8 KiB
/libs/cookbook-web-fonts/v1.0.12/bagoss-standard/BagossSt...	1440.0 s	58.6 KiB
assets.grubhub.com/libs/mochi/2.0.433/graphik-regular/graphik-regular.woff	1440.0 s	41.8 KiB
gh-prod-umami-grubhub.s3.us-east-1.amazonaws.com/css/grubhub-out-of-country.css	0.0 ms	30.2 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
assets.grubhub.com/libs/mochi/2.0.433/graphik-regular/graphik-regular.woff	105 ms
/libs/cookbook-web-fonts/v1.0.12/bagoss-standard/BagossSt...	5.0 ms

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
gh-prod-umami-grubhub.s3.us-east-1.amazonaws.com/css/grubhub-out-of-country.css	30.2 KiB	1.3 s

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.

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

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 250 ms 7.1 KiB

URL	Transfer Size	Est Savings
gh-prod-umami-grubhub.s3.us-east-1.amazonaws.com/css/grubhub-out-of-country.css	30.2 KiB	7.1 KiB

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: 490 ms 26.8 KiB

URL	Transfer Size	Est Savings
gh-prod-umami-grubhub.s3.us-east-1.amazonaws.com/css/grubhub-out-of-country.css	29.8 KiB	26.8 KiB

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
div.errorPage-container > div.errorPage > div.errorPage-image > img `div.errorPage-container > div.errorPage > div.errorPage-image > img`	/img/grubhub-error-image.svg

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 194 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.1 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 20 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html#ng-app `html#ng-app`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mainNav > div.mainNavCol > a.mainNavBrand-logo > img `div.mainNav > div.mainNavCol > a.mainNavBrand-logo > img`
div.errorPage-container > div.errorPage > div.errorPage-image > img `div.errorPage-container > div.errorPage > div.errorPage-image > img`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html#ng-app `html#ng-app`

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[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]`s are contained by their required parent element

○`[role]` values are valid

○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

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

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

○Buttons have an accessible name

○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 a valid value for its `[lang]` attribute

○`<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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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.

○`[lang]` attributes have a valid value

○`<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.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○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.

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
/href/grubhub/favicon.ico	Blocked
gh-prod-umami-grubhub.s3-website-us-east-1.amazonaws.com/img/grubhub/favicon.ico	Blocked
/img/grubhub-error-image.svg	Automatically upgraded to HTTPS

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
/img/grubhub-error-image.svg	`Failed to load resource: net::ERR_CONNECTION_RESET`
grubhub.com/	`Mixed Content: The page at 'https://grubhub.com/' was loaded over HTTPS, but requested an insecure favicon 'http://gh-prod-umami-grubhub.s3-website-us-east-1.amazonaws.com/href/grubhub/favicon.ico'. This request has been blocked; the content must be served over HTTPS.`
grubhub.com/	`Mixed Content: The page at 'https://grubhub.com/' was loaded over HTTPS, but requested an insecure favicon 'http://gh-prod-umami-grubhub.s3-website-us-east-1.amazonaws.com/img/grubhub/favicon.ico'. This request has been blocked; the content must be served over HTTPS.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content

●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

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
2	<!DOCTYPE html><html id="ng-app"><head><meta charset="utf-8"><meta http-equiv="X-UA-Compatible" content="IE=edge"><meta name="viewport" content="width=device-width,initial-scale=1,user-scalable=no"><meta name="prerender-status-code" content="503"><base href="/"><title>Grubhub food delivery is not available in your country</title><meta name="description" content="Free online ordering from restaurants near you! With more than 30,000 restaurants in 500+ cities, food delivery or takeout is just a click away. Because with Grubhub: Click, click, food!"><meta property="og:url" content="https://grubhub.com/about/error/out-of-country"><meta property="og:type" content="website"><meta property="og:title" content="Grubhub food delivery is not available in your country"><meta property="og:description" content="Free online ordering from restaurants near you! With more than 30,000 restaurants in 500+ cities, food delivery or takeout is just a click away. Because with Grubhub: Click, click, food!"><meta name="twitter:card" content="summary_large_image"><meta name="twitter:site" content="@grubhub"><meta name="twitter:creator" content="@grubhub"><meta name="twitter:title" content="Grubhub food delivery is not available in your country"><meta name="twitter:description" content="Free online ordering from restaurants near you! With more than 30,000 restaurants in 500+ cities, food delivery or takeout is just a click away. Because with Grubhub: Click, click, food!"><link rel="icon" type="image/x-icon" href="http://gh-prod-umami-grubhub.s3-website-us-east-1.amazonaws.com/img/grubhub/favicon.ico"><link rel="shortcut icon" type="image/x-icon" href="http://gh-prod-umami-grubhub.s3-website-us-east-1.amazonaws.com/href/grubhub/favicon.ico"><link rel="stylesheet" href="https://gh-prod-umami-grubhub.s3.us-east-1.amazonaws.com/css/grubhub-out-of-country.css"<link rel="canonical" href="https://grubhub.com/about/error/out-of-country"></head><body><div class="mainNav"><div class="mainNavCol mainNavBrand"><a href="/" title="grubhub" class="mainNavBrand-logo"><img src="https://res.cloudinary.com/grubhub-assets/image/upload/v1651068764/Citrus-assets/Logos/No%20Registered%20Mark/1_Grubhub_Logo_NotRegistered/SVG/grubhub_NotRegistered_Orange_RGB.svg"></a></div></div><div class="outerWrapper clearfix"><div class="innerWrapper clearfix"><div class="errorPage-container"><div class="errorPage"><div class="errorPage-reasons"><h1 id="sorry-about-that">Sorry about that</h1><p>Grubhub food delivery is not available in your country</p></div><div class="errorPage-image"><img src="http://gh-prod-umami-grubhub.s3-website-us-east-1.amazonaws.com/img/grubhub-error-image.svg"></div></div></div></div></div><dashi-analytics-tag page-group="convenience features" page-subgroup="help" view-name="viewed-error-page"></dashi-analytics-tag></body></html>	`Unknown directive`

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mainNav > div.mainNavCol > a.mainNavBrand-logo > img `div.mainNav > div.mainNavCol > a.mainNavBrand-logo > img`
div.errorPage-container > div.errorPage > div.errorPage-image > img `div.errorPage-container > div.errorPage > div.errorPage-image > img`

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

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`