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
/wp-content/plugins/coming-soon/public/fontawesome/css/al...	0.0 ms	94.5 KiB
cabochon.ae/wp-includes/js/jquery/jquery.min.js	0.0 ms	85.7 KiB
/wp-content/plugins/coming-soon/public/css/tailwind.min.c...	0.0 ms	74.8 KiB
cabochon.ae/wp-content/plugins/coming-soon/public/js/sp-scripts.min.js	0.0 ms	44.7 KiB
cabochon.ae/wp-content/uploads/2017/11/Cabochon_logo_w250.png	0.0 ms	14.3 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:1362.531 label:Time to first byte subpart:timeToFirstByte] map[duration:16.874 label:Resource load delay subpart:resourceLoadDelay] map[duration:1240.067 label:Resource load duration subpart:resourceLoadDuration] map[duration:10.141 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: figure#sp-brhhwi > div > span > img.sp-image-block-brhhwi

path: 1,HTML,1,BODY,0,DIV,0,SECTION,1,DIV,0,DIV,0,FIGURE,0,DIV,0,SPAN,0,IMG

selector: figure#sp-brhhwi > div > span > img.sp-image-block-brhhwi

snippet: <img src="https://cabochon.ae/wp-content/uploads/2017/11/Cabochon_logo_w250.png" alt="" width="250" height="27" data-dynamic-tag="" data-image-src="wpmedia" class="sp-image-block-brhhwi custom-preview-class" srcset=" https://cabochon.ae/wp-content/uploads/2017/11/Cabochon_logo_w250-150x27.…" style="width: 250px;">

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

nodeLabel: figure#sp-brhhwi > div > span > img.sp-image-block-brhhwi

path: 1,HTML,1,BODY,0,DIV,0,SECTION,1,DIV,0,DIV,0,FIGURE,0,DIV,0,SPAN,0,IMG

selector: figure#sp-brhhwi > div > span > img.sp-image-block-brhhwi

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
cabochon.ae/wp-includes/js/jquery/jquery.min.js	85.7 KiB	450 ms
/wp-content/plugins/coming-soon/public/css/tailwind.min.c...	74.8 KiB	450 ms
/wp-content/plugins/coming-soon/public/fontawesome/css/al...	94.5 KiB	450 ms

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
figure#sp-brhhwi > div > span > img.sp-image-block-brhhwi `figure#sp-brhhwi > div > span > img.sp-image-block-brhhwi`	cabochon.ae/wp-content/uploads/2017/11/Cabochon_logo_w250.png	14.1 KiB	13.0 KiB

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

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: 750 ms 165.4 KiB

URL	Transfer Size	Est Savings
/wp-content/plugins/coming-soon/public/fontawesome/css/al...	94.3 KiB	94.0 KiB
/wp-content/plugins/coming-soon/public/css/tailwind.min.c...	74.6 KiB	71.4 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: 450 ms 98.4 KiB

URL	Transfer Size	Est Savings
cabochon.ae/wp-includes/js/jquery/jquery.min.js	85.5 KiB	56.8 KiB
cabochon.ae/wp-content/plugins/coming-soon/public/js/sp-scripts.min.js	44.6 KiB	41.6 KiB

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
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 960 ms

URL	Time Spent
cabochon.ae/	960 ms
/z0f76a1d14fd21a8fb5fd0d03e0fdc3d3cedae52f?wsidchk=967387...	0.0 ms
cabochon.ae/	0.0 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.1 s

URL	Time Spent
cabochon.ae/	1.2 s

●Time to Interactive 2.6 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 330 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 2 long tasks found

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

●Network Requests

●Network Round Trip Times 190 ms

●Server Backend Latencies 210 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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
Under Maintenance `div#sp-vw3kvy > div#sp-ggzp6w > span.sp-header-block-link > h1#sp-jkhbii`

These are opportunities to improve the legibility of your content.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.sp-html `html.sp-html`

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

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.sp-html `html.sp-html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

●Image elements have `[alt]` attributes

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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

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

○`[role]`s are contained by their required parent element

○`[role]` values are valid

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

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

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○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

○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

○Touch targets have sufficient size and spacing.

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

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

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
figure#sp-brhhwi > div > span > img.sp-image-block-brhhwi `figure#sp-brhhwi > div > span > img.sp-image-block-brhhwi`	cabochon.ae/wp-content/uploads/2017/11/Cabochon_logo_w250.png	250 x 27	250 x 27	375 x 41

●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

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.sp-html `html.sp-html`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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="sp-html`	`Syntax not understood`
3	`sp-seedprod sp-h-full" lang="en-US">`	`Syntax not understood`
4	`<head>`	`Syntax not understood`
10	`<!-- Open Graph -->`	`Syntax not understood`
11	`<meta property="og:url" content="https://cabochon.ae/robots.txt" />`	`Unknown directive`
12	`<meta property="og:type" content="website" />`	`Unknown directive`
14	`<!-- Twitter Card -->`	`Syntax not understood`
15	`<meta name="twitter:card" content="summary" />`	`Unknown directive`
17	`<meta charset="UTF-8">`	`Syntax not understood`
18	`<meta name="viewport" content="width=device-width, initial-scale=1.0">`	`Syntax not understood`
19	`<!-- Default CSS -->`	`Syntax not understood`
20	`<link rel='stylesheet' id='seedprod-css-css' href='https://cabochon.ae/wp-content/plugins/coming-soon/public/css/tailwind.min.css?ver=6.20.4' type='text/css' media='all' /> <link rel='stylesheet' id='seedprod-fontawesome-css' href='https://cabochon.ae/wp-content/plugins/coming-soon/public/fontawesome/css/all.min.css?ver=6.20.4' type='text/css' media='all' />`	`Unknown directive`
32	`<!-- Global Styles -->`	`Syntax not understood`
33	`<style>`	`Syntax not understood`
37	`@media only screen and (max-width: 480px) {`	`Unknown directive`
39	`}`	`Syntax not understood`
41	`@media only screen and (min-width: 481px) and (max-width: 1024px) {`	`Unknown directive`
43	`}`	`Syntax not understood`
45	`@media only screen and (min-width: 1024px) {`	`Unknown directive`
46	`}`	`Syntax not understood`
50	`</style>`	`Syntax not understood`
52	`<!-- JS -->`	`Syntax not understood`
53	`<script>`	`Syntax not understood`
54	`</script>`	`Syntax not understood`
58	`<script src="https://cabochon.ae/wp-content/plugins/coming-soon/public/js/sp-scripts.min.js" defer></script>`	`Unknown directive`
65	`<script src="https://cabochon.ae/wp-includes/js/jquery/jquery.min.js"></script>`	`Unknown directive`
66	`</head>`	`Syntax not understood`
67	`<body data-rsssl=1 class="spBgcover sp-h-full sp-antialiased sp-bg-slideshow">`	`Syntax not understood`
69	<div id="sp-page" class="spBgcover sp-content-4" style="background-color: rgb(255, 255, 255); font-family: 'Helvetica Neue', Arial, sans-serif; font-weight: 400;"><section id="sp-ks8a8s" class="sp-el-section " style="width: 600px; max-width: 100%; padding: 10px;"><div></div><div id="sp-vw3kvy" class="sp-el-row sp-w-full sp-m-auto sm:sp-flex sp-justify-between" style="padding: 0px; width: auto; max-width: 1000px;"><div id="sp-ggzp6w" class="sp-el-col sp-w-full" style="width: calc(100% + 0px);"><figure id="sp-brhhwi" class="sp-image-wrapper sp-el-block" style="margin: 0px; text-align: center; padding: 0px 0px 50px;"><div><span><img src="https://cabochon.ae/wp-content/uploads/2017/11/Cabochon_logo_w250.png" alt="" width="250" height="27" data-dynamic-tag="" data-image-src="wpmedia" class="sp-image-block-brhhwi custom-preview-class" srcset=" https://cabochon.ae/wp-content/uploads/2017/11/Cabochon_logo_w250-150x27.png 150w, https://cabochon.ae/wp-content/uploads/2017/11/Cabochon_logo_w250.png 250w" style="width: 250px;"></span></div><div id="sp-image-dynamic-tags-js-brhhwi"><script>jQuery(function(){var n=0;(function r(){if(typeof image_dynamic_tags==="function"){image_dynamic_tags('brhhwi' );}else if(n++<100){setTimeout(r,50);}})();});</script></div></figure><span href="" target="" rel="" class="sp-header-block-link" style="text-decoration: none;"><h1 id="sp-jkhbii" class="sp-css-target sp-el-block sp-headline-block-jkhbii sp-type-header" style="font-size: 22px; font-weight: bold; color: rgb(204, 204, 204); text-align: center; margin: 0px;">Under Maintenance</h1></span></div></div></section></div>	`Unknown directive`
72	`<div class="tv">`	`Syntax not understood`
73	`<div class="screen mute" id="tv"></div>`	`Syntax not understood`
74	`</div>`	`Syntax not understood`
77	`<script>`	`Syntax not understood`
78	`var sp_is_mobile = false;`	`Syntax not understood`
79	`</script>`	`Syntax not understood`
81	`</body>`	`Syntax not understood`
83	`</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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`