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.

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.

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

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

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	97.4 KiB
/signals/config/1297699559168375?v=2.9.319&r=stable&domai...	1200.0 s	31.9 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/883a1f27d85f/...	14400.0 s	10.2 KiB
/beacon.min.js/v833ccba57c9e4d2798f2e76cebdd09a1177817227...	86400.0 s	11.4 KiB
/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader...	172793.0 s	5.0 KiB
/tr/?id=1297699559168375&ev=PageView&dl=https%3A%2F%2Fvip...	0.0 ms	16 B

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
Vip Oftalmologia `nav.bg-card/95 > div.container > a.flex > img.h-12`	vipoftalmologia.com.br/assets/logo.webp	27.5 KiB	27.1 KiB

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
vipoftalmologia.com.br/assets/index-CYj1TzNj.css	21.1 KiB	1.0 s
/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader...	5.0 KiB	1.0 s

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

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: 652 ms

URL	Time Spent
vipoftalmologia.com.br/	752 ms

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 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: 160 ms 15.6 KiB

URL	Transfer Size	Est Savings
vipoftalmologia.com.br/assets/index-CYj1TzNj.css	19.1 KiB	15.6 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: 160 ms 177.7 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-73MSY1E9P5	158.0 KiB	67.7 KiB
connect.facebook.net/en_US/fbevents.js	97.3 KiB	37.0 KiB
vipoftalmologia.com.br/assets/index-D1rrpic_.js	57.1 KiB	26.6 KiB
vipoftalmologia.com.br/assets/radix-forms-SgqbhO9M.js	28.3 KiB	25.8 KiB
vipoftalmologia.com.br/assets/router-vendor-Ca-CWbEB.js	66.1 KiB	20.4 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
vipoftalmologia.com.br/	940 ms	53 ms	2.0 ms
Unattributable	516 ms	51 ms	0.0 ms
vipoftalmologia.com.br/cdn-cgi/challenge-platform/scripts/jsd/main.js	396 ms	382 ms	2.3 ms
www.googletagmanager.com/gtag/js?id=G-73MSY1E9P5	328 ms	274 ms	51 ms
vipoftalmologia.com.br/assets/router-vendor-Ca-CWbEB.js	238 ms	229 ms	0.8 ms
/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader...	228 ms	157 ms	14 ms
connect.facebook.net/en_US/fbevents.js	179 ms	130 ms	48 ms
/signals/config/1297699559168375?v=2.9.319&r=stable&domai...	139 ms	118 ms	20 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	1.5 s
Other	966 ms
Style & Layout	375 ms
Script Parsing & Compilation	168 ms
Rendering	115 ms
Parse HTML & CSS	37 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.2 KiB

URL	Transfer Size	Est Savings
vipoftalmologia.com.br/assets/utils-vendor-D-tsi9h0.js	13.4 KiB	3.2 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 1,167 KiB

●Avoid long main-thread tasks 10 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 530 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

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

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Avaliação 5 de 5 estrelas `div.container > div.text-center > div.flex > div.flex`
5 estrelas `div.rounded-lg > div.p-4 > div.flex > div.flex`
5 estrelas `div.rounded-lg > div.p-4 > div.flex > div.flex`
5 estrelas `div.rounded-lg > div.p-4 > div.flex > div.flex`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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
(61) 3011-2760 / (61) 99414-6446 `div.container > div.flex > a.flex > span.text-xs`
Consulta `header.sticky > div.bg-primary > div.container > a.flex`
Agendar Consulta `section.relative > div.relative > div.flex > a.inline-flex`
NOSSOS SERVIÇOS `section.py-12 > div.container > div.text-center > span.text-primary`
div.grid > div.relative > div.absolute > p.text-xs `div.grid > div.relative > div.absolute > p.text-xs`
div.container > div.grid > div.mt-6 > span.text-primary `div.container > div.grid > div.mt-6 > span.text-primary`
section.py-12 > div.container > div.text-center > span.text-primary `section.py-12 > div.container > div.text-center > span.text-primary`
div.rounded-lg > div.p-4 > div.flex > div.w-9 `div.rounded-lg > div.p-4 > div.flex > div.w-9`
Política de Privacidade `div.flex > div.flex-1 > p.text-xs > a.text-primary`
Aceitar Cookies `div.relative > div.flex > div.flex > button.inline-flex`

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
div.mt-6 > a.flex > div.min-w-0 > h4.font-bold `div.mt-6 > a.flex > div.min-w-0 > h4.font-bold`
div.p-4 > div.flex > div.flex-1 > h4.font-bold `div.p-4 > div.flex > div.flex-1 > h4.font-bold`
Sobre `div.container > div.grid > div > h4.font-bold`

These are opportunities to improve keyboard navigation in your application.

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
Cirurgia Refrativa LASIK e TransPRK para correção de miopia, astigmatismo e hi… `section.py-12 > div.container > div.grid > a`
Cirurgia de Catarata Remoção da catarata com implante de lente intraocular de … `section.py-12 > div.container > div.grid > a`
Tratamento de Ceratocone Crosslinking corneano e acompanhamento especializado … `section.py-12 > div.container > div.grid > a`
Saúde Ocular Artigos, dicas e novidades sobre cuidados com a visão e prevenção… `section.py-12 > div.container > div.grid > a`

○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

●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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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 with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Document has a `<title>` element

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

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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

○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
SharedStorage	vipoftalmologia.com.br/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	vipoftalmologia.com.br/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	vipoftalmologia.com.br/cdn-cgi/challenge-platform/scripts/jsd/main.js
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 1126

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

●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

100

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.

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`