Webpage Performance Test Result

Lighthouse Metrics

Values are estimated and may vary.

The performance score is calculated directly from these metrics. See calculator.

Filmstrip

Opportunities (4)

1. Properly size images

   Estimated savings 0.06 s

   Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

   URL	Resource Size (bytes)	Potential Savings (bytes)
   https://avos.kitchen/media/pages/home/2f897ff3a4-1672760524/kitchen.png	58671	37956

2. Reduce unused CSS

   Estimated savings 0.02 s

   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.

   URL	Transfer Size (bytes)	Potential Savings (bytes)
   https://avos.kitchen/assets/css/index.css?v=330c7660	16788	14734

3. Eliminate render-blocking resources

   View Experiment!

   Estimated savings 0.01 s

   Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

   URL	Transfer Size (bytes)	Potential Savings (ms)
   https://avos.kitchen/assets/css/index.css?v=330c7660	16788	150

4. Initial server response time was short

   Root document took 90 ms

   Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

   URL	Time Spent (ms)
   https://avos.kitchen/	92

Diagnostics (9)

1. Page prevented back/forward cache restoration

   1 failure reason

   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

   Failure reason	Failure type
   Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
   Frame Url https://avos.kitchen/

2. Avoid chaining critical requests

   2 chains found

   The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.

   1. https://avos.kitchen/ 4kb
      1. https://avos.kitchen/assets/css/index.css?v=330c7660 16kb
         1. https://avos.kitchen/assets/fonts/CourierPrimeSans-Regular.woff2?f033e0e1201de2214448dad779f3c5ea 27kb
         2. https://avos.kitchen/assets/fonts/CourierPrimeSans-Bold.woff2?9bd035d561da27af89ae91c6aa532ed1 28kb

3. Largest Contentful Paint element

   760 ms

   This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element

4. Avoids enormous network payloads

   Total size was 175 KiB

   Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

   URL	Transfer Size (bytes)
   https://avos.kitchen/media/pages/home/2f897ff3a4-1672760524/kitchen.png	58808
   https://avos.kitchen/assets/fonts/CourierPrimeSans-Bold.woff2?9bd035d561da27af89ae91c6aa532ed1	28662
   https://avos.kitchen/assets/fonts/CourierPrimeSans-Regular.woff2?f033e0e1201de2214448dad779f3c5ea	28158
   https://avos.kitchen/assets/images/sprite.svg?v=330c7660	21808
   https://avos.kitchen/assets/css/index.css?v=330c7660	16788
   https://avos.kitchen/assets/images/bg-texture.png?7eb33784dd211e2598a10ef14cde3b4e	12276
   https://avos.kitchen/assets/js/index.js?v=330c7660	7230
   https://avos.kitchen/	3592
   https://avos.kitchen/favicon.png	1587
   https://avos.kitchen/manifest.json	304

5. Avoid long main-thread tasks

   1 long task found

   Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

   URL	Start Time	Duration
   https://avos.kitchen/	497	101

6. JavaScript execution time

   0.0 s

   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.

   URL	Total CPU Time	Script Evaluation	Script Parse
   https://avos.kitchen/	133	3	1
   Unattributable	72	2	0

7. Minimizes main-thread work

   0.2 s

   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

   Category	Time Spent
   Style & Layout	110
   Other	84
   Script Evaluation	23
   Parse HTML & CSS	7
   Rendering	4
   Script Parsing & Compilation	1

8. Avoids an excessive DOM size

   49 elements

   A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

   Statistic	Element	Value
   Total DOM Elements
   Maximum DOM Depth	div.c-linklist > ul.c-linklist__list > li > a.ghost-link
   Maximum Child Elements	nav.c-header__content > div.c-header__menu > div.c-linklist > ul.c-linklist__list

9. Avoid large layout shifts

   2 elements found

   These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

   Element	Layout shift impact
   body > footer.c-footer > div.c-footer__content > div.c-footer__copyright	0
   div.c-footer__menu > div.c-linklist > ul.c-linklist__list > li	0

Passed Audits (26)

1. Avoid multiple page redirects

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

2. Enable text compression

   Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

3. Preconnect to required origins

   Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.

4. Preload key requests

   Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn how to preload key requests.

5. All text remains visible during webfont loads

   Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.

6. Minify JavaScript

   Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

7. Minify CSS

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

8. Preload Largest Contentful Paint image

   If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.

9. Reduce unused JavaScript

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

10. Use video formats for animated content

    Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats

11. Largest Contentful Paint image was not lazily loaded

    Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.

    Element
    main.c-home > article.o-grid > figure.o-media > img

12. Minimize third-party usage

    Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

13. Lazy load third-party resources with facades

    Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.

14. Remove duplicate modules in JavaScript bundles

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

15. Avoid serving legacy JavaScript to modern browsers

    Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript

16. Has a <meta name="viewport"> tag with width or initial-scale

    A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.

17. Avoid non-composited animations

    Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animations

18. Image elements have explicit width and height

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

19. Defer offscreen images

    Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

20. Efficiently encode images

    Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

21. Serve images in next-gen formats

    Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

22. Use HTTP/2

    HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.

23. Uses efficient cache policy on static assets

    0 resources found

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

24. User Timing marks and measures

    Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.

25. Uses passive listeners to improve scrolling performance

    Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

26. Avoids document.write()

    For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().

Additional Items to Check Manually (10)

1. Interactive controls are keyboard focusable

   Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.

2. Interactive elements indicate their purpose and state

   Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.

3. The page has a logical tab order

   Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.

4. Visual order on the page follows DOM order

   DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.

5. User focus is not accidentally trapped in a region

   A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.

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

   If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.

7. HTML5 landmark elements are used to improve navigation

   Landmark elements (`<main>`, `<nav>`, etc.) are used to improve the keyboard navigation of the page for assistive technology.

8. Offscreen content is hidden from assistive technology

   Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.

9. Custom controls have associated labels

   Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.

10. Custom controls have ARIA roles

    Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.

Passed Audits (14)

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

   Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.

2. [aria-hidden="true"] elements do not contain focusable descendents

   Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.

3. Background and foreground colors have a sufficient contrast ratio

   Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

4. Document has a <title> element

   The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

5. Heading elements appear in a sequentially-descending order

   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.

6. <html> element has a [lang] attribute

   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.

7. <html> element has a valid value for its [lang] attribute

   Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.

8. Image elements have [alt] attributes

   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.

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

   Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.

10. Links are distinguishable without relying on color.

    Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

11. Links have a discernible name

    Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

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

    Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

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

    Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.

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

    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.

Not Applicable (40)

1. [accesskey] values are unique

   Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.

2. [aria-*] attributes match their roles

   Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.

3. Values assigned to role="" are valid ARIA roles.

   ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.

4. button, link, and menuitem elements have accessible names

   When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

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

   ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

6. ARIA input fields have accessible names

   When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

7. ARIA meter elements have accessible names

   When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.

8. ARIA progressbar elements have accessible names

   When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.

9. [role]s have all required [aria-*] attributes

   Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

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

    Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

11. [role]s are contained by their required parent element

    Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

12. [role] values are valid

    ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

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

    Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.

14. ARIA toggle fields have accessible names

    When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.

15. ARIA tooltip elements have accessible names

    When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.

16. ARIA treeitem elements have accessible names

    When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.

17. [aria-*] attributes have valid values

    Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

18. [aria-*] attributes are valid and not misspelled

    Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

19. Buttons have an accessible name

    When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

20. The page contains a heading, skip link, or landmark region

    Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.

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

    When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

22. Definition list items are wrapped in <dl> elements

    Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.

23. [id] attributes on active, focusable elements are unique

    All focusable elements must have a unique id to ensure that they're visible to assistive technologies. Learn how to fix duplicate ids.

24. ARIA IDs are unique

    The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.

25. No form fields have multiple labels

    Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.

26. <frame> or <iframe> elements have a title

    Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

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

    If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.

28. Input buttons have discernible text.

    Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

29. <input type="image"> elements have [alt] text

    When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.

30. Form elements have associated labels

    Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

31. The document does not use <meta http-equiv="refresh">

    Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

32. <object> elements have alternate text

    Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.

33. Select elements have associated label elements.

    Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.

34. Skip links are focusable.

    Including a skip link can help users skip to the main content to save time. Learn more about skip links.

35. No element has a [tabindex] value greater than 0

    A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.

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

    The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.

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

    Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.

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

    Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.

39. [lang] attributes have a valid value

    Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.

40. <video> elements contain a <track> element with [kind="captions"]

    When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.

Trust and Safety (1)

1. Ensure CSP is effective against XSS attacks

   A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS

   Description	Directive	Severity
   No CSP found in enforcement mode		High

Passed Audits (14)

1. Uses HTTPS

   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.

2. Avoids requesting the geolocation permission on page load

   Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.

3. Avoids requesting the notification permission on page load

   Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

4. Allows users to paste into input fields

   Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.

5. Displays images with correct aspect ratio

   Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

6. Serves images with appropriate resolution

   Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

7. Page has the HTML doctype

   Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

8. Properly defines charset

   A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

9. Avoids unload event listeners

   The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use pagehide or visibilitychange events instead. Learn more about unload event listeners

10. Avoids deprecated APIs

    Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

11. Avoids third-party cookies

    Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.

12. No browser errors logged to the console

    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

13. Page has valid source maps

    Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

14. No issues in the Issues panel in Chrome Devtools

    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.

Not Applicable (2)

1. Fonts with font-display: optional are preloaded

   Preload optional fonts so first-time visitors may use them. Learn more about preloading fonts

2. Detected JavaScript libraries

   All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.

Additional Items to Check Manually (1)

1. Structured data is valid

   Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.

Passed Audits (12)

1. Has a <meta name="viewport"> tag with width or initial-scale

   A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.

2. Document has a <title> element

   The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

3. Document has a meta description

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

4. Page has successful HTTP status code

   Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

5. Links have descriptive text

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

6. Links are crawlable

   Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

7. Page isn’t blocked from indexing

   Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

8. robots.txt is valid

   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.

9. Image elements have [alt] attributes

   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.

10. Document has a valid hreflang

    hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.

11. Document has a valid rel=canonical

    Canonical links suggest which URL to show in search results. Learn more about canonical links.

12. Document avoids plugins

    Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more about avoiding plugins.

Not Applicable (2)

1. Document uses legible font sizes

   Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.

2. Tap targets are sized appropriately

   Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

Installable (1)

1. Web app manifest or service worker do not meet the installability requirements

   2 reasons

   Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.

   Failure reason
   Manifest start URL is not valid
   Manifest `display` property must be one of `standalone`, `fullscreen`, or `minimal-ui`

PWA Optimized (5)

1. Is not configured for a custom splash screen

   A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens.

   Failures:

   • Manifest does not have a PNG icon of at least 512px

2. Sets a theme color for the address bar.

   The browser address bar can be themed to match your site. Learn more about theming the address bar.

3. Content is sized correctly for the viewport

   If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn how to size content for the viewport.

4. Has a <meta name="viewport"> tag with width or initial-scale

   A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.

5. Manifest doesn't have a maskable icon

   A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.

Additional Items to Check Manually (3)

1. Site works cross-browser

   To reach the most number of users, sites should work across every major browser. Learn about cross-browser compatibility.

2. Page transitions don't feel like they block on the network

   Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more about page transitions.

3. Each page has a URL

   Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more about providing deep links.