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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
d3rqem538l0q4a.cloudfront.net/Scripts/chloe.js	0.0 ms	74.4 KiB
cdn.cookielaw.org/scripttemplates/202312.1.0/otBannerSdk.js	86400.0 s	104.3 KiB
/signals/config/1419871268310720?v=2.9.303&r=stable&domai...	1200.0 s	46.5 KiB
/dcdn/settings.js?a=187274&settings_type=4&ts=1776871161&...	1800.0 s	47.4 KiB
/analytics.js/v1/In2Wg4CJeLPa4Kdnqq4dF6etJrf9vIIw/analyti...	120.0 s	28.8 KiB
schedule.zoominfo.com/zischedule.js	0.0 ms	17.2 KiB
tags.clickagy.com/data.js?rnd=62fe5c0e6ad96	0.0 ms	13.6 KiB
js.adsrvr.org/up_loader.1.1.0.js	0.0 ms	12.3 KiB
ws-assets.zoominfo.com/formcomplete.js	3600.0 s	14.4 KiB
static.hotjar.com/c/hotjar-47258.js?sv=5	60.0 s	8.4 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
js.zi-scripts.com/zi-tag.js	0.0 ms	5.9 KiB
/logos/1022f197-87bb-479d-afa6-bc21f295f504/c320b1ae-1c32...	86400.0 s	12.0 KiB
/logos/1022f197-87bb-479d-afa6-bc21f295f504/9e08b8a4-481d...	86400.0 s	11.6 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
snippet.growsumo.com/growsumo.min.js	14400.0 s	3.5 KiB
/attribution_tracking/conversions/715.js?p=https://unboun...	0.0 ms	2.2 KiB
analytics.ahrefs.com/analytics.js	14400.0 s	3.0 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.6 KiB
js.adsrvr.org/universal_pixel.js	0.0 ms	958 B
//i?stm=1776899803647&e=pv&url=https%3A%2F%2Funbounce.com...	0.0 ms	520 B
/collect?v=2&fmt=js&pid=85712&time=1776899802980&li_adsId...	0.0 ms	272 B
cdn.cookielaw.org/logos/static/ot_close.svg	86400.0 s	603 B
/v.gif?cd=0&a=187274&d=unbounce.com&u=D3829C690E8603C4434...	43200.0 s	147 B
/tr/?id=1419871268310720&ev=PageView&dl=https%3A%2F%2Funb...	0.0 ms	19 B

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:46.249 source:map[type:text value:[unattributed]]]]

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
home-hero-mobile-v2 `div.row > div.col-md-12 > div.mob-img > img.w-100`	unbounce.com/photos/home-hero-mobile-v2.png	100.4 KiB	89.7 KiB
Optimize effortlessly `div#bx3 > div.prodfeat-ig > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/frame_153822...	50.4 KiB	33.5 KiB
Get started `div#bx2 > div.prodfeat-ig > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/frame_153822...	37.9 KiB	25.2 KiB
Custom code `div#bx4 > div.prodfeat-ig > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/frame_153822...	33.8 KiB	22.4 KiB
Create your page `div#bx1 > div.prodfeat-ig > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/frame_153822...	27.6 KiB	18.3 KiB
Company Logo `div.ot-sdk-container > div.ot-sdk-row > div#onetrust-group-container > img.ot-bnr-logo`	/logos/1022f197-87bb-479d-afa6-bc21f295f504/c320b1ae-1c32...	11.8 KiB	11.7 KiB

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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

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

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.

Diagnostics

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: 500 ms 682.7 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-JHGNGKNMZM&cx=c&gtm=4e64k1	171.8 KiB	67.4 KiB
www.googletagmanager.com/gtag/js?id=G-B32DC3RBVY&cx=c&gtm=4e64k1	157.7 KiB	65.8 KiB
www.googletagmanager.com/gtag/js?id=G-8GFBJRYYE1&cx=c&gtm=4e64k1	158.0 KiB	65.2 KiB
www.googletagmanager.com/gtag/js?id=G-K17291L2CD&cx=c&gtm=4e64k1	153.8 KiB	63.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-981849952&cx=c&gtm=4e64k1	146.7 KiB	61.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-ND9H2L	185.1 KiB	59.7 KiB
cdn.cookielaw.org/scripttemplates/202312.1.0/otBannerSdk.js	104.0 KiB	54.5 KiB
www.googletagmanager.com/gtag/js?id=AW-947282172	144.6 KiB	54.0 KiB
assets.ubembed.com/universalscript/releases/v0.184.0/bundle.js	49.6 KiB	38.3 KiB
d3rqem538l0q4a.cloudfront.net/Scripts/chloe.js	74.0 KiB	38.0 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	36.5 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	32.1 KiB
assets.ubembed.com/universalscript/releases/v0.184.0/bundle.js	49.6 KiB	25.8 KiB
unbounce.com/wp-includes/js/jquery/jquery.min.js	32.1 KiB	21.2 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
unbounce.com/	1.9 s	809 ms	6.4 ms
Unattributable	1.4 s	330 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-ND9H2L	1.2 s	1.0 s	77 ms
	747 ms	548 ms	139 ms
www.googletagmanager.com/gtag/js?id=G-JHGNGKNMZM&cx=c&gtm=4e64k1	392 ms	338 ms	50 ms
www.googletagmanager.com/gtag/js?id=G-8GFBJRYYE1&cx=c&gtm=4e64k1	352 ms	298 ms	51 ms
www.googletagmanager.com/gtag/js?id=G-B32DC3RBVY&cx=c&gtm=4e64k1	340 ms	289 ms	47 ms
www.googletagmanager.com/gtag/js?id=G-K17291L2CD&cx=c&gtm=4e64k1	320 ms	272 ms	45 ms
www.googletagmanager.com/gtag/destination?id=AW-981849952&cx=c&gtm=4e64k1	311 ms	242 ms	66 ms
cdn.cookielaw.org/scripttemplates/202312.1.0/otBannerSdk.js	309 ms	205 ms	33 ms
assets.ubembed.com/universalscript/releases/v0.184.0/bundle.js	267 ms	141 ms	125 ms
ead777b108aa482aa23c97fd24389aad.js.ubembed.com/	231 ms	202 ms	16 ms
connect.facebook.net/en_US/fbevents.js	216 ms	141 ms	41 ms
/signals/config/1419871268310720?v=2.9.303&r=stable&domai...	173 ms	152 ms	18 ms
	163 ms	113 ms	6.5 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	148 ms	123 ms	23 ms
snap.licdn.com/li.lms-analytics/insight.min.js	123 ms	87 ms	29 ms
www.googletagmanager.com/gtag/js?id=AW-947282172	121 ms	78 ms	40 ms
/dcdn/settings.js?a=187274&settings_type=4&ts=1776871161&...	115 ms	64 ms	40 ms
/analytics.js/v1/In2Wg4CJeLPa4Kdnqq4dF6etJrf9vIIw/analyti...	100 ms	86 ms	10 ms
unbounce.com/wp-includes/js/jquery/jquery.min.js	92 ms	75 ms	8.7 ms
blob:https://unbounce.com/9005d4cd-90d3-45f5-a12b-45dec08cfb26	86 ms	76 ms	1.2 ms
d3rqem538l0q4a.cloudfront.net/Scripts/chloe.js	73 ms	63 ms	7.9 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	6.0 s
Other	1.6 s
Script Parsing & Compilation	940 ms
Style & Layout	406 ms
Parse HTML & CSS	208 ms
Garbage Collection	156 ms
Rendering	140 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
The page has an unload handler in the main frame.	Actionable

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: 0.0 ms 40.3 KiB

URL	Transfer Size	Est Savings
@font-face{font-family:"Figtree";font-style:italic;font-weight:300 900;font-display:swap; … } …	31.6 KiB	22.3 KiB
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …	20.6 KiB	18.0 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
Create your page `div#bx1 > div.prodfeat-ig > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/frame_153822...
Custom code `div#bx4 > div.prodfeat-ig > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/frame_153822...
Get started `div#bx2 > div.prodfeat-ig > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/frame_153822...
Optimize effortlessly `div#bx3 > div.prodfeat-ig > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/frame_153822...
Forrest Schaffer `div.prodcomp-sponsor > div.sponsor-ig > picture > img`	res.cloudinary.com/spiralyze/image/upload/f_auto/unbounce/1016/client_mob.png
Going `div.prodcomp-sponsor > div.sponsor-logo > picture > img`	/spiralyze/image/upload/f_auto/unbounce/1016/going_logo_m...

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,367 KiB

●User Timing marks and measures 38 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 370 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 20 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
search-icon `div.container-fluid > div.menu-container > div.nav-toggles > button.search-toggle`

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.graphic-content-block > div.graphic-content-block > div.mt-3 > img.mt-0 `div.graphic-content-block > div.graphic-content-block > div.mt-3 > img.mt-0`

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.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#footer-links-ai > ul#menu-footer-ai-nav > li.heading-ai-nav > a.dropdown-toggle `div#footer-links-ai > ul#menu-footer-ai-nav > li.heading-ai-nav > a.dropdown-toggle`

These are opportunities to improve the legibility of your content.

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
Build and test stunning pages without a single line of code `div.prodfeat-top > div#bx1 > div.prodfeat-disc > h4.prodfeat-add`

These are opportunities to improve keyboard navigation in your application.

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`

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
search-icon `div.container-fluid > div.menu-container > div.nav-toggles > button.search-toggle`

These items highlight common accessibility best practices.

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
toggle menu `div.container-fluid > div.menu-container > div.nav-toggles > button.navbar-toggler`

○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

●`[role]` values are valid

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

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

●Form elements have associated labels

●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

●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

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

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

○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

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

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

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

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○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

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.	cdn.cookielaw.org/scripttemplates/202312.1.0/otBannerSdk.js line 6, col 243254
Unload event listeners are deprecated and will be removed.	blob:https://unbounce.com/9005d4cd-90d3-45f5-a12b-45dec08cfb26

●Uses HTTPS

●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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

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

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
unbounce.com/concierge/	Learn more
cookiepedia.co.uk/giving-consent-to-cookies	More information

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.graphic-content-block > div.graphic-content-block > div.mt-3 > img.mt-0 `div.graphic-content-block > div.graphic-content-block > div.mt-3 > img.mt-0`

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

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Products `div.mobile-nav-wrap > ul#menu-main-menu > li.no-hover > a.dropdown-toggle`
Products and features `li.no-hover > ul.dropdown-menu > li.border-none > a.dropdown-toggle`
Landing pages `li.border-none > ul.dropdown-menu > li.visible > a`
A/B testing `li.border-none > ul.dropdown-menu > li.a-tag-none > a`
Smart Traffic `li.border-none > ul.dropdown-menu > li.a-tag-none > a`
Products and features `li.no-hover > ul.dropdown-menu > li.no-hover > a.dropdown-toggle`
AI Copywriting `li.no-hover > ul.dropdown-menu > li.a-tag-none > a`
Integrations `li.no-hover > ul.dropdown-menu > li.a-tag-none > a`
More solutions by Unbounce `li.no-hover > ul.dropdown-menu > li.no-hover > a.dropdown-toggle`
Insightly CRM `li.no-hover > ul.dropdown-menu > li.a-tag-none > a`
Solutions `div.mobile-nav-wrap > ul#menu-main-menu > li.no-hover > a.dropdown-toggle`
Industries `li.no-hover > ul.dropdown-menu > li.c > a.dropdown-toggle`
Use cases `li.no-hover > ul.dropdown-menu > li.no-hover > a.dropdown-toggle`
Resources `div.mobile-nav-wrap > ul#menu-main-menu > li.no-hover > a.dropdown-toggle`
The essentials `li.no-hover > ul.dropdown-menu > li.border-none > a.dropdown-toggle`
div#footer-links > ul#menu-footer-menu > li.dropdown > a.dropdown-toggle `div#footer-links > ul#menu-footer-menu > li.dropdown > a.dropdown-toggle`
div#footer-links > ul#menu-footer-menu > li.dropdown > a.dropdown-toggle `div#footer-links > ul#menu-footer-menu > li.dropdown > a.dropdown-toggle`
div#footer-links > ul#menu-footer-menu > li.dropdown > a.dropdown-toggle `div#footer-links > ul#menu-footer-menu > li.dropdown > a.dropdown-toggle`
div#footer-links > ul#menu-footer-menu > li.dropdown > a.dropdown-toggle `div#footer-links > ul#menu-footer-menu > li.dropdown > a.dropdown-toggle`

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

○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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`