28/10/23, 16:09 Lighthouse Report Viewer
https://www.dominos.com.pe/es/pages/order/#!/locations/search/?type=Carryout
51 78 86 83
Performance Accessibility Best Practices SEO PWA
51
Performance
Values are estimated and may vary. The
performance score is calculated directly from these
metrics. See calculator.
0–49 50–89 90–100
METRICS Expand view
First Contentful Paint Largest Contentful Paint
2.6 s 5.8 s
Total Blocking Time Cumulative Layout Shift
210 ms 0.018
Speed Index
4.9 s
View Treemap
Show audits relevant to: All FCP LCP TBT CLS
https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fwww.dominos.com.pe%2Fes%2Fpages%2Forder%2F%23%21%2Fl… 1/7
28/10/23, 16:09 Lighthouse Report Viewer
DIAGNOSTICS
Serve static assets with an efficient cache policy — 296 resources found
Ensure text remains visible during webfont load
Does not use passive listeners to improve scrolling performance
Image elements do not have explicit width and height
Does not have a <meta name="viewport"> tag with width or initial-scale
Avoid enormous network payloads — Total size was 5,250 KiB
Reduce unused JavaScript — Potential savings of 2,131 KiB
Minimize main-thread work — 3.7 s
Serve images in next-gen formats — Potential savings of 437 KiB
Defer offscreen images — Potential savings of 514 KiB
Reduce JavaScript execution time — 2.0 s
Preload Largest Contentful Paint image — Potential savings of 210 ms
Reduce unused CSS — Potential savings of 183 KiB
Avoid chaining critical requests — 13 chains found
User Timing marks and measures — 24 user timings
Largest Contentful Paint element — 5,780 ms
Avoid large layout shifts — 5 elements found
Avoid long main-thread tasks — 9 long tasks found
Avoid non-composited animations — 1 animated element found
More information about the performance of your application. These numbers don't directly affect the Performance score.
PASSED AUDITS (18) Show
https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fwww.dominos.com.pe%2Fes%2Fpages%2Forder%2F%23%21%2Fl… 2/7
28/10/23, 16:09 Lighthouse Report Viewer
78
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.
NAMES AND LABELS
Buttons do not have an accessible name
Elements with visible text labels do not have matching accessible names.
Links do not have a discernible name
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.
ARIA
button, link, and menuitem elements do not have accessible names.
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.
CONTRAST
Links rely on color to be distinguishable.
These are opportunities to improve the legibility of your content.
TABLES AND LISTS
Lists do not contain only <li> elements and script supporting elements (<script> and
<template>).
https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fwww.dominos.com.pe%2Fes%2Fpages%2Forder%2F%23%21%2Fl… 3/7
28/10/23, 16:09 Lighthouse Report Viewer
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen
reader.
NAVIGATION
Heading elements are not in a sequentially-descending order
These are opportunities to improve keyboard navigation in your application.
ADDITIONAL ITEMS TO MANUALLY CHECK (10) Show
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an
accessibility review.
PASSED AUDITS (22) Show
NOT APPLICABLE (29) Show
86
Best Practices
TRUST AND SAFETY
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
USER EXPERIENCE
Serves images with low resolution
https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fwww.dominos.com.pe%2Fes%2Fpages%2Forder%2F%23%21%2Fl… 4/7
28/10/23, 16:09 Lighthouse Report Viewer
GENERAL
Browser errors were logged to the console
Detected JavaScript libraries
PASSED AUDITS (10) Show
NOT APPLICABLE (1) Show
83
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.
MOBILE FRIENDLY
Does not have a <meta name="viewport"> tag with width or initial-scale
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn
how to make pages mobile-friendly.
CONTENT BEST PRACTICES
Document does not have a meta description
Format your HTML in a way that enables crawlers to better understand your app’s content.
ADDITIONAL ITEMS TO MANUALLY CHECK (1) Show
Run these additional validators on your site to check additional SEO best practices.
https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fwww.dominos.com.pe%2Fes%2Fpages%2Forder%2F%23%21%2Fl… 5/7
28/10/23, 16:09 Lighthouse Report Viewer
PASSED AUDITS (10) Show
NOT APPLICABLE (2) Show
PWA
These checks validate the aspects of a Progressive Web App. Learn what
makes a good Progressive Web App.
INSTALLABLE
Web app manifest or service worker do not meet the installability requirements — 1 reason
PWA OPTIMIZED
Is not configured for a custom splash screen Failures: No manifest was fetched.
Does not set a theme color for the address bar.
Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Content is sized correctly for the viewport
Does not have a <meta name="viewport"> tag with width or initial-scale
Manifest doesn't have a maskable icon No manifest was fetched
ADDITIONAL ITEMS TO MANUALLY CHECK (3) Show
https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fwww.dominos.com.pe%2Fes%2Fpages%2Forder%2F%23%21%2Fl… 6/7
28/10/23, 16:09 Lighthouse Report Viewer
These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not
affect your score but it's important that you verify them manually.
Captured at Oct 28, 2023, 4:08 PM Emulated Desktop with Lighthouse Single page load
GMT-5 11.0.0
Initial page load Unknown Using HeadlessChromium
117.0.5938.149 with lr
Generated by Lighthouse 11.0.0 | File an issue
https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fwww.dominos.com.pe%2Fes%2Fpages%2Forder%2F%23%21%2Fl… 7/7