https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8?form_factor=desktop

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
/s/googlematerialicons/v144/Gw6kwdfw6UnXLJCcmafZyFRXb3BL9...	95 ms
/s/googlesans/v62/4UasrENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...	45 ms

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

value: No additional origins are good candidates for preconnecting

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

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 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: 170 ms 131.9 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-S8N9N15MT1	156.4 KiB	66.7 KiB
/_/mss/boq-chrome-wdi-lightbrary/_/js/k=boq-chrome-wdi-li...	188.5 KiB	65.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
/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43...	1.3 s	69 ms	117 ms
/_/mss/boq-chrome-wdi-lightbrary/_/js/k=boq-chrome-wdi-li...	635 ms	599 ms	1.6 ms
Unattributable	378 ms	7.5 ms	0.0 ms
/_/mss/boq-chrome-wdi-lightbrary/_/js/k=boq-chrome-wdi-li...	276 ms	218 ms	11 ms
www.googletagmanager.com/gtag/js?id=G-S8N9N15MT1	274 ms	195 ms	38 ms
/_/mss/boq-chrome-wdi-lightbrary/_/js/k=boq-chrome-wdi-li...	274 ms	203 ms	44 ms
/_/mss/boq-chrome-wdi-lightbrary/_/js/k=boq-chrome-wdi-li...	51 ms	44 ms	6.2 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.4 s
Other	755 ms
Style & Layout	471 ms
Rendering	237 ms
Script Parsing & Compilation	227 ms
Parse HTML & CSS	132 ms
Garbage Collection	59 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
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 4.8 KiB

URL	Transfer Size	Est Savings
report-styles.css	15.9 KiB	4.8 KiB

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 43.8 KiB

URL	Transfer Size	Est Savings
body,html{height:100%;overflow:hidden} …	34.9 KiB	27.9 KiB
report-styles.css	15.9 KiB	15.9 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
Final Screenshot `div#performance > div.lh-category-header > div.lh-category-headercol > img.lh-final-ss-image`
Screenshot `div#screenshot-thumbnails > div.lh-filmstrip > div.lh-filmstrip__frame > img.lh-filmstrip__thumbnail`
Screenshot `div#screenshot-thumbnails > div.lh-filmstrip > div.lh-filmstrip__frame > img.lh-filmstrip__thumbnail`
Screenshot `div#screenshot-thumbnails > div.lh-filmstrip > div.lh-filmstrip__frame > img.lh-filmstrip__thumbnail`
Screenshot `div#screenshot-thumbnails > div.lh-filmstrip > div.lh-filmstrip__frame > img.lh-filmstrip__thumbnail`
Screenshot `div#screenshot-thumbnails > div.lh-filmstrip > div.lh-filmstrip__frame > img.lh-filmstrip__thumbnail`
Screenshot `div#screenshot-thumbnails > div.lh-filmstrip > div.lh-filmstrip__frame > img.lh-filmstrip__thumbnail`
Screenshot `div#screenshot-thumbnails > div.lh-filmstrip > div.lh-filmstrip__frame > img.lh-filmstrip__thumbnail`
Screenshot `div#screenshot-thumbnails > div.lh-filmstrip > div.lh-filmstrip__frame > img.lh-filmstrip__thumbnail`
Google Developers Logo `div.GX2tW > div.UuJ0zd > a > img.Dv5Rkc`	gstatic.com/webvitalsdashboard/img/google_developers.svg

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

●Render blocking requests

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 965 KiB

●User Timing marks and measures 86 user timings

●Avoid long main-thread tasks 12 long tasks found

●Avoid non-composited animations 7 animated elements found

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 70 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 90 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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
header#kO001e > span.yTTzpb > div.VfPpkd-dgl2Hf-ppHlrf-sM5MNb > button.VfPpkd-LgbsSe `header#kO001e > span.yTTzpb > div.VfPpkd-dgl2Hf-ppHlrf-sM5MNb > button.VfPpkd-LgbsSe`

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
https://accounts.google.com/v3/signin/identifier?continue= `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
%3D118jxoze_up*MQ..%26gclid%3DCjwKCAjwhZDUBhBGEiwAbi5bjoetsyty1ASr_fSL6o5Qwbl… `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
https://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044?_gl%3D `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
%26 `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
%3D `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
%26 `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
%3D `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
%26 `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
%3Dtrue&passive `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
1209600&flowName=GlifWebSignIn&flowEn `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
y=S `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`
rviceLogin&dsh=S-518547135:1787240865721924 `div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
record a trace `div.lh-perf-audits > div.lh-audit-group > span.lh-audit-group__description > a`
directly affect `div.lh-perf-audits > div.lh-audit-group > span.lh-audit-group__description > a`
conducting an accessibility review `div#accessibility > div.lh-audit-group > span.lh-audit-group__description > a`

These are opportunities to improve the legibility of your content.

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`

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 `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-*]` 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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

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

○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

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43...

●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

●Use a strong HSTS policy

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Ensure CSP is effective against XSS attacks

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Mitigate DOM-based XSS with Trusted Types

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

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`

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
100 Accessibility `div#accessibility > div.lh-category-header > div.lh-score__gauge > a.lh-gauge__wrapper`
100 Best Practices `div#best-practices > div.lh-category-header > div.lh-score__gauge > a.lh-gauge__wrapper`
91 SEO `div#seo > div.lh-category-header > div.lh-score__gauge > a.lh-gauge__wrapper`
100 Accessibility `div#accessibility > div.lh-category-header > div.lh-score__gauge > a.lh-gauge__wrapper`
100 Best Practices `div#best-practices > div.lh-category-header > div.lh-score__gauge > a.lh-gauge__wrapper`
91 SEO `div#seo > div.lh-category-header > div.lh-score__gauge > a.lh-gauge__wrapper`

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

Content Best Practices

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.

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
web.dev/articles/vitals/	Learn more
web.dev/articles/vitals/	Learn more
/docs/lighthouse/pwa/redirects-http/?utm_source=lighthous...	Learn more
web.dev/articles/vitals/	Learn more
web.dev/articles/vitals/	Learn more

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

○Structured data is valid

●Document has a `<title>` element

●Page has successful HTTP status code

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid