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.

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
www.gob.bo/_next/static/media/material-icons-outlined.f86cb7b0.woff2	630 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
chacana_a1 `div.MuiGrid-root > div.anim-fade-in > div.chacana-box > img`	www.gob.bo/_next/image?url=%2Fa1.png&w=750&q=75	155.4 KiB	91.9 KiB
div.MuiBox-root > main.MuiBox-root > div.MuiBox-root > div.MuiGrid-root `div.MuiBox-root > main.MuiBox-root > div.MuiBox-root > div.MuiGrid-root`	www.gob.bo/patron_footer.png	8.8 KiB	7.3 KiB
logo_entidad `a.MuiButtonBase-root > div.MuiStack-root > div.MuiBox-root > img`	/_next/image?url=https%3A%2F%2Fwww.gob.bo%2Fws%2Fapi%2Far...	7.3 KiB	4.9 KiB
logo_entidad `a.MuiButtonBase-root > div.MuiStack-root > div.MuiBox-root > img`	/_next/image?url=https%3A%2F%2Fwww.gob.bo%2Fws%2Fapi%2Far...	7.1 KiB	4.4 KiB
logo_entidad `a.MuiButtonBase-root > div.MuiStack-root > div.MuiBox-root > img`	/_next/image?url=https%3A%2F%2Fwww.gob.bo%2Fws%2Fapi%2Far...	5.9 KiB	4.4 KiB
logo_entidad `a.MuiButtonBase-root > div.MuiStack-root > div.MuiBox-root > img`	/_next/image?url=https%3A%2F%2Fwww.gob.bo%2Fws%2Fapi%2Far...	6.8 KiB	4.1 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.

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
www.gob.bo/_next/static/css/d645a791e5bd11f8.css	873 B
www.gob.bo/_next/static/css/42fd053aa1d08e8c.css	1.0 KiB
www.gob.bo/_next/static/css/37f8ef6183feaba4.css	2.2 KiB
www.gob.bo/_next/static/css/b20cd94c892c251a.css	647 B

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

Diagnostics

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.2 s
Other	590 ms
Style & Layout	360 ms
Rendering	127 ms
Script Parsing & Compilation	112 ms
Parse HTML & CSS	25 ms
Garbage Collection	13 ms

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

●Max Potential First Input Delay 110 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 950 KiB

●JavaScript execution time 1.2 s

●Avoid long main-thread tasks 7 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 220 ms

●Server Backend Latencies 80 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 450 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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

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
keyboard_arrow_up `body > div.MuiBox-root > div.MuiBox-root > button#scrollToTop`

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.

○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

●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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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.

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

○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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source Description

Source	Description
www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js	Error: Minified React error #422; visit https://react.dev/errors/422 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:63990 at lZ (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:65341) at iZ (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:121136) at ia (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:95165) at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91091 at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91098 at oZ (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91203) at MessagePort.M (https://www.gob.bo/_next/static/chunks/2117-d99617515412d413.js:1:85057)
www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js	Error: Minified React error #425; visit https://react.dev/errors/425 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at sq (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:146768) at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:101026 at iu (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:103870) at ia (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:95226) at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91091 at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91098 at oZ (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91203) at MessagePort.M (https://www.gob.bo/_next/static/chunks/2117-d99617515412d413.js:1:85057)

www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js

Error: Minified React error #422; visit https://react.dev/errors/422 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:63990
    at lZ (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:65341)
    at iZ (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:121136)
    at ia (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:95165)
    at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91091
    at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91098
    at oZ (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91203)
    at MessagePort.M (https://www.gob.bo/_next/static/chunks/2117-d99617515412d413.js:1:85057)

www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js

Error: Minified React error #425; visit https://react.dev/errors/425 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at sq (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:146768)
    at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:101026
    at iu (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:103870)
    at ia (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:95226)
    at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91091
    at https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91098
    at oZ (https://www.gob.bo/_next/static/chunks/fd9d1056-7939e9ddc510e184.js:1:91203)
    at MessagePort.M (https://www.gob.bo/_next/static/chunks/2117-d99617515412d413.js:1:85057)

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

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`