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.

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-DIV

nodeLabel: div.uk-width-1-1 > div.uk-width-1-1 > a > div.ls-http3check-logo

path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,DIV

selector: div.uk-width-1-1 > div.uk-width-1-1 > a > div.ls-http3check-logo

snippet: <div class="ls-http3check-logo uk-align-center" style="margin-bottom: 0px;">

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

value: No additional origins are good candidates for preconnecting

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
fonts.googleapis.com/css?family=Quicksand:400	943 B	787 ms
cdnjs.cloudflare.com/ajax/libs/uikit/3.0.3/css/uikit.min.css	22.1 KiB	1.1 s
cdnjs.cloudflare.com/ajax/libs/uikit/3.0.3/js/uikit.min.js	36.4 KiB	1.4 s
cdnjs.cloudflare.com/ajax/libs/uikit/3.0.3/js/uikit-icons.min.js	15.4 KiB	1.1 s
http3check.net/static/style.css	1.5 KiB

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.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
http3check.net/static/http3check-logo.svg	43200.0 s	2.5 KiB
http3check.net/static/style.css	43200.0 s	1.5 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
/s/quicksand/v37/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-...	5.0 ms

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

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

URL	Transfer Size	Est Savings
cdnjs.cloudflare.com/ajax/libs/uikit/3.0.3/css/uikit.min.css	21.5 KiB	21.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: 0.0 ms 214.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-JLT5PYGNHH&cx=c&gtm=4e6551	150.3 KiB	64.7 KiB
www.googletagmanager.com/gtag/js?id=G-J0HDFBP8SZ&cx=c&_slc=1	145.3 KiB	64.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-T8Z9663	124.5 KiB	62.7 KiB
cdnjs.cloudflare.com/ajax/libs/uikit/3.0.3/js/uikit.min.js	35.8 KiB	22.9 KiB

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

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 540 KiB

●User Timing marks and measures 12 user timings

●JavaScript execution time 1.0 s

●Minimizes main-thread work 1.5 s

●Avoid long main-thread tasks 8 long tasks found

●Avoid non-composited animations 1 animated element found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 40 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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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.

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
CHECK `div.uk-active > div.uk-padding-small > div.uk-margin-auto > button.uk-margin-auto`
www.facebook.com `div.uk-padding-small > div.uk-first-column > a.ls-suggestion-link > div.ls-suggestion`
www.litespeedtech.com `div.uk-padding-small > div.uk-grid-margin > a.ls-suggestion-link > div.ls-suggestion`
www.http3check.net `div.uk-padding-small > div.uk-grid-margin > a.ls-suggestion-link > div.ls-suggestion`
www.google.com `div.uk-padding-small > div.uk-grid-margin > a.ls-suggestion-link > div.ls-suggestion`
LiteSpeed Technologies Inc `div.uk-width-1-1 > div.uk-width-extend > p > a`
Privacy Policy `div.uk-width-1-1 > div.uk-width-extend > p > a`

These are opportunities to improve the legibility of your content.

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.ls-main `html.ls-main`

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

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.uk-margin-auto > div.uk-width-1-1 > div.uk-width-1-1 > a `div.uk-margin-auto > div.uk-width-1-1 > div.uk-width-1-1 > a`

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

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
Powered By LiteSpeed `div.uk-margin-auto > div.uk-width-1-1 > div.uk-width-1-1 > a`

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.ls-main `html.ls-main`

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-*]` attributes match their roles

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

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

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

●Buttons have an accessible name

●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 use only permitted ARIA attributes

●Document has a `<title>` element

●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

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

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

○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

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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

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

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

●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
1	`<!doctype html>`	`Syntax not understood`
2	`<html class="ls-main">`	`Syntax not understood`
3	`<head>`	`Syntax not understood`
4	`<meta charset="utf-8">`	`Syntax not understood`
5	`<meta name="viewport" content="width=device-width, initial-scale=1">`	`Syntax not understood`
6	`<meta name="description" content="Is my site using HTTP3? Check HTTP3 service on any URL. Test QUIC service, too.">`	`Syntax not understood`
7	`<title>HTTP/3 Check</title>`	`Syntax not understood`
8	`<!-- UIkit CSS -->`	`Syntax not understood`
9	`<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/uikit/3.0.3/css/uikit.min.css" />`	`Unknown directive`
10	`<!-- UIkit JS -->`	`Syntax not understood`
11	`<script src="https://cdnjs.cloudflare.com/ajax/libs/uikit/3.0.3/js/uikit.min.js"></script>`	`Unknown directive`
12	`<script src="https://cdnjs.cloudflare.com/ajax/libs/uikit/3.0.3/js/uikit-icons.min.js"></script>`	`Unknown directive`
13	`<link href="https://fonts.googleapis.com/css?family=Quicksand:400" rel="stylesheet">`	`Unknown directive`
14	`<link rel="stylesheet" href="/static/style.css">`	`Syntax not understood`
15	`<link rel="icon" type="image/png" href="/static/favicon-32x32.png" />`	`Syntax not understood`
16	`<!-- Google Tag Manager -->`	`Syntax not understood`
17	`<script>(function(w,d,s,l,i){w[l]=w[l]\|\|[];w[l].push({'gtm.start':`	`Unknown directive`
18	`new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],`	`Unknown directive`
19	`j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=`	`Unknown directive`
20	`'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);`	`Unknown directive`
21	`})(window,document,'script','dataLayer','GTM-T8Z9663');</script>`	`Syntax not understood`
22	`<!-- End Google Tag Manager -->`	`Syntax not understood`
23	`</head>`	`Syntax not understood`
26	`<body class="ls-body">`	`Syntax not understood`
27	`<!-- Google Tag Manager (noscript) -->`	`Syntax not understood`
28	`<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-T8Z9663"`	`Unknown directive`
29	`height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>`	`Unknown directive`
30	`<!-- End Google Tag Manager (noscript) -->`	`Syntax not understood`
31	`<div class="uk-container">`	`Syntax not understood`
32	`<div class="uk-align-center" style="margin-bottom:70px;">`	`Unknown directive`
33	`<div class="uk-margin-auto uk-margin-large-top uk-grid-small" uk-grid>`	`Syntax not understood`
34	`<div class="uk-width-1-1" style="padding:0;">`	`Unknown directive`
35	`<div class="uk-width-1-1 uk-width-1-2@s uk-width-2-5@m uk-margin-auto">`	`Syntax not understood`
36	`<a href="/">`	`Syntax not understood`
37	`<div class="ls-http3check-logo uk-align-center" style="margin-bottom: 0px;"></div>`	`Unknown directive`
38	`</a>`	`Syntax not understood`
39	`</div>`	`Syntax not understood`
40	`</div>`	`Syntax not understood`
41	`<div class="uk-width-1-1 uk-container" style="margin-top:0px;">`	`Unknown directive`
42	`<div class="uk-width-1-1 uk-width-1-2@s uk-width-2-5@m uk-margin-auto">`	`Syntax not understood`
43	`<a href="https://www.litespeedtech.com/" target='_blank'>`	`Unknown directive`
44	`<div class="uk-text-center uk-text-small uk-text-muted uk-margin-medium-left">`	`Syntax not understood`
45	`<span uk-icon="icon:bolt; ratio:.75" class="uk-text-warning"></span>Powered By LiteSpeed`	`Unknown directive`
46	`</div>`	`Syntax not understood`
47	`</a>`	`Syntax not understood`
48	`</div>`	`Syntax not understood`
49	`</div>`	`Syntax not understood`
50	`</div>`	`Syntax not understood`
51	`<div class="uk-margin-auto uk-margin-top uk-width-expand uk-width-3-4@s uk-width-2-3@m uk-position-relative">`	`Syntax not understood`
52	`<ul class="uk-flex-center@s" uk-tab="connect:.switcher-main;animation:uk-animation-fade;duration:125;">`	`Unknown directive`
53	`<li><a href="#"><small>Standard</small></a></li>`	`Syntax not understood`
54	`<li><a href="#"><small>Advanced</small></a></li>`	`Syntax not understood`
55	`</ul>`	`Syntax not understood`
56	`<div class="uk-position-top-right uk-margin-top-small ls-about">`	`Syntax not understood`
57	`<a class="ls-about-link uk-link-muted" href="/about"><small>About</small></a>`	`Syntax not understood`
58	`</div>`	`Syntax not understood`
59	`<div class="uk-switcher switcher-main">`	`Syntax not understood`
60	`<div>`	`Syntax not understood`
61	`<div class="uk-padding-small uk-border-rounded uk-box-shadow">`	`Syntax not understood`
62	`<form id="standard-form" method="get" class="uk-search uk-search-navbar uk-width-1 uk-flex" style="padding-left:10px;">`	`Unknown directive`
63	`<input class="uk-search-input" type="search" name="host" placeholder="Hostname" autofocus>`	`Syntax not understood`
64	`</form>`	`Syntax not understood`
65	`</div>`	`Syntax not understood`
66	`<div class="uk-padding-small">`	`Syntax not understood`
67	`<div class="uk-margin-auto" uk-grid>`	`Syntax not understood`
68	`<button class="uk-margin-auto uk-width-4-5 uk-width-3-5@s uk-width-2-5@m uk-button uk-button-primary uk-border-rounded" type="submit" form="standard-form">Check</button>`	`Syntax not understood`
69	`</div>`	`Syntax not understood`
70	`</div>`	`Syntax not understood`
71	`<h3 class="uk-heading-line uk-text-center uk-margin-medium-top"><span>Popular Searches</span></h3>`	`Syntax not understood`
72	`<div class="uk-padding-small uk-child-width-1-2@s uk-text-center uk-grid-small" uk-grid>`	`Syntax not understood`
73	`<div>`	`Syntax not understood`
74	`<a class="ls-suggestion-link" href="/?host=www.facebook.com">`	`Syntax not understood`
75	`<div class="ls-suggestion ls-suggestion-9 uk-card uk-card-body uk-card-small" style="padding:20px 10px;">www.facebook.com</div>`	`Unknown directive`
76	`</a>`	`Syntax not understood`
77	`</div>`	`Syntax not understood`
78	`<div>`	`Syntax not understood`
79	`<a class="ls-suggestion-link" href="/?host=www.litespeedtech.com">`	`Syntax not understood`
80	`<div class="ls-suggestion ls-suggestion-5 uk-card uk-card-body uk-card-small">www.litespeedtech.com</div>`	`Syntax not understood`
81	`</a>`	`Syntax not understood`
82	`</div>`	`Syntax not understood`
83	`<div>`	`Syntax not understood`
84	`<a class="ls-suggestion-link" href="/?host=www.http3check.net">`	`Syntax not understood`
85	`<div class="ls-suggestion ls-suggestion-7 uk-card uk-card-body uk-card-small">www.http3check.net</div>`	`Syntax not understood`
86	`</a>`	`Syntax not understood`
87	`</div>`	`Syntax not understood`
88	`<div>`	`Syntax not understood`
89	`<a class="ls-suggestion-link" href="/?host=www.google.com">`	`Syntax not understood`
90	`<div class="ls-suggestion ls-suggestion-4 uk-card uk-card-body uk-card-small">www.google.com</div>`	`Syntax not understood`
91	`</a>`	`Syntax not understood`
92	`</div>`	`Syntax not understood`
93	`</div>`	`Syntax not understood`
94	`</div>`	`Syntax not understood`
95	`<div class="uk-padding uk-border-rounded uk-box-shadow-small" style="padding-top: 25px;">`	`Unknown directive`
96	`<p class="uk-text-center uk-text-small">Use Advanced Search to bypass hostname resolution and use a custom IP address or port.</p>`	`Syntax not understood`
97	`<form method="get" class=" uk-grid-small uk-align-center" uk-grid>`	`Syntax not understood`
98	`<div class="uk-width-1-1">`	`Syntax not understood`
99	`<div class="uk-grid-small" uk-grid>`	`Syntax not understood`
100	`<div class="uk-width-extend uk-width-1-6@s">`	`Syntax not understood`
101	`<div class="uk-form-label">Address</div>`	`Syntax not understood`
102	`</div>`	`Syntax not understood`
103	`<div class="uk-width-extend uk-width-1-2@m">`	`Syntax not understood`
104	`<input class="uk-input uk-border-rounded" type="text" name="ip" placeholder="IP Address">`	`Syntax not understood`
105	`</div>`	`Syntax not understood`
106	`<div class="uk-width-extend uk-width-1-5@m">`	`Syntax not understood`
107	`<input class="uk-input uk-border-rounded valid-input" type="text" name="port" value="443" placeholder="Port">`	`Syntax not understood`
108	`</div>`	`Syntax not understood`
109	`</div>`	`Syntax not understood`
110	`</div>`	`Syntax not understood`
111	`<div class="uk-width-1-1">`	`Syntax not understood`
112	`<div class="uk-form-controls uk-grid-small" uk-grid>`	`Syntax not understood`
113	`<div class="uk-width-extend uk-width-1-6@s">`	`Syntax not understood`
114	`<div class="uk-form-label">Host</div>`	`Syntax not understood`
115	`</div>`	`Syntax not understood`
116	`<div class="uk-width-extend uk-width-1-2@m">`	`Syntax not understood`
117	`<input class="uk-input uk-border-rounded" type="text" name="host" placeholder="Hostname" required>`	`Syntax not understood`
118	`</div>`	`Syntax not understood`
119	`<div class="uk-width-extend uk-width-1-4@m">`	`Syntax not understood`
120	`<button class="uk-width-extend uk-button uk-button-primary uk-border-rounded" type="submit">Check</button>`	`Syntax not understood`
121	`</div>`	`Syntax not understood`
122	`</div>`	`Syntax not understood`
123	`</div>`	`Syntax not understood`
124	`<input type="text" name="advanced" value="true" hidden>`	`Syntax not understood`
125	`</form>`	`Syntax not understood`
126	`</div>`	`Syntax not understood`
127	`</div>`	`Syntax not understood`
128	`</div>`	`Syntax not understood`
129	`</div>`	`Syntax not understood`
130	`<div class="ls-footer uk-box-shadow-small" uk-grid>`	`Syntax not understood`
131	`<div class="uk-width-1-1">`	`Syntax not understood`
132	`<div class="uk-width-extend uk-width-1-2@s uk-margin-auto">`	`Syntax not understood`
133	`<p>`	`Syntax not understood`
134	`Copyright © 2019 - <script>document.write(new Date().getFullYear())</script> <a href="https://www.litespeedtech.com/" target="_blank">LiteSpeed Technologies Inc</a><br>`	`Unknown directive`
135	`All Rights Reserved. (<a href="https://www.litespeedtech.com/company/privacy-policy" target="_blank">Privacy Policy</a>)`	`Unknown directive`
136	`</p>`	`Syntax not understood`
137	`</div>`	`Syntax not understood`
138	`</div>`	`Syntax not understood`
139	`</div>`	`Syntax not understood`
140	`</div>`	`Syntax not understood`
141	`</body>`	`Syntax not understood`
143	`</html>`	`Syntax not understood`

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

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`