Skip to content
Audit Complete

Results for https://firebase.google.com

Visit site
United Stated United Stated · New York Completed: Apr 4, 2026 16:51 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C76

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

'unsafe-eval' found in script source

Security › Content Security Policy
2

'unsafe-inline' found in script source

Security › Content Security Policy
3

Page weighs 25.4 MB (17.4 MB transferred)

Performance › Page Weight Budget
4

3 link(s) with no accessible text

Accessibility › Link & Button Quality
5

is missing width/height — may cause layout shift

Performance › Image Optimization
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Ffirebase.google.com)](https://beavercheck.com/results/4d1b5e70-26db-445d-9935-09344c36ac5e)
<a href="https://beavercheck.com/results/4d1b5e70-26db-445d-9935-09344c36ac5e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ffirebase.google.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ffirebase.google.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

36
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

6.30 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

55.60 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.21 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.30 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

74.98 s

Detailed Report

Audit breakdown by category with detailed findings.

36

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:28.526 source:map[column:224 line:165 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]] map[reflowTime:0.544 source:map[column:330 line:243 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]] map[reflowTime:2.445 source:map[column:59 line:242 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
div.homepage-hero__content > div.homepage-hero__body > h1#make-your-app-the-best-it-can-be-with-firebase-and-generative-ai > video div.homepage-hero__content > div.homepage-hero__body > h1#make-your-app-the-best-it-can-be-with-firebase-and-generative-ai > video
firebase.google.com/images/homepage/Google_Firebase_LogotoIcon_Black_V01.gif8.7 MiB8.7 MiB
Android Studiologo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/android-studio.png13.6 KiB13.6 KiB
Slacklogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/slack.png6.7 KiB6.7 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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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.

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.

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.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

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

CategoryTime Spent
Script Evaluation2.5 s
Other2.2 s
Style & Layout1.2 s
Script Parsing & Compilation515 ms
Rendering206 ms
Parse HTML & CSS191 ms
Garbage Collection81 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Android Studiologo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/android-studio.png
Slacklogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/slack.png
Google Playlogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/playstore.png
Flutterlogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/flutter.png
Firebase AI Logic icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
firebase.google.com/static/images/icons/firebase-ai-logic.svg
Google Adslogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/google-ads.svg
AdMoblogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/ad-mob.svg
Google Marketing Platformlogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/google-marketing-platform.svg
BigQuerylogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/bigquery.svg
Agent Skills icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
firebase.google.com/static/images/icons/firebase-agent-skills.svg
Genkit icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
firebase.google.com/static/images/products/icons/build_genkit_white.svg
Jiralogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/jira.svg
Looker Studiologo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/lookerstudio.svg
Stream to BigQuery icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
Search with Algolia icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
Run Payments with Stripe icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image

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

Use efficient cache lifetimes
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 18 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 110 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 180 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
96

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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Failing Elements
div > div.code-picker > devsite-iframe > iframe div > div.code-picker > devsite-iframe > iframe

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.

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.

Failing Elements
Easily integrate Firebase with Gemini and the latest AI technology from Google div.highlights-row-wrapper > div.highlights-row__content > div.content > h3#easily-integrate-firebase-with-gemini-and-the-latest-ai-technology-from-google

These are opportunities to improve keyboard navigation in your application.

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
`[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 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
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
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
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 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
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.
Image elements do not have `[alt]` attributes that are redundant text.
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.
96

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

SourceDescription
Failed to load resource: the server responded with a status of 503 (Service Unavailable)
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 proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
92

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

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

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 are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

779 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.13 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

63 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.18 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.61 s

Detailed Report

Audit breakdown by category with detailed findings.

96

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:8.19 source:map[column:53 line:254 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:1.207 source:map[column:224 line:165 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]] map[reflowTime:1.802 source:map[column:330 line:243 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]] map[reflowTime:2.777 source:map[column:59 line:242 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]] map[reflowTime:0.104 source:map[column:249 line:247 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]] map[reflowTime:9.866 source:map[type:text value:[unattributed]]] map[reflowTime:2.136 source:map[column:348 line:7 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_devsite_header_module.js urlProvider:network]] map[reflowTime:8.125 source:map[column:106 line:165 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_app_module.js urlProvider:network]] map[reflowTime:3.284 source:map[column:90 line:1 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_devsite_carousel_module.js urlProvider:network]] map[reflowTime:10.352 source:map[column:451 line:1 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_devsite_carousel_module.js urlProvider:network]] map[reflowTime:0.033 source:map[column:288 line:2 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_devsite_carousel_module.js urlProvider:network]] map[reflowTime:0.061 source:map[column:225 line:1 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_devsite_carousel_module.js urlProvider:network]] map[reflowTime:4.452 source:map[column:441 line:22 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/firebase/js/devsite_devsite_book_nav_module.js urlProvider:network]]]

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
div.homepage-hero__content > div.homepage-hero__body > h1#make-your-app-the-best-it-can-be-with-firebase-and-generative-ai > video div.homepage-hero__content > div.homepage-hero__body > h1#make-your-app-the-best-it-can-be-with-firebase-and-generative-ai > video
firebase.google.com/images/homepage/Google_Firebase_LogotoIcon_Black_V01.gif8.7 MiB8.8 MiB
Stream to BigQuery Search with Algolia Run Payments with Stripe div.content-wrapper > section.highlights-row > div.highlights-row-wrapper > div.highlights-row__highlights
firebase.google.com/images/backgrounds/firebase-gradient.png3.2 MiB3.0 MiB
Android Studiologo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/android-studio.png13.6 KiB13.6 KiB
Slacklogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/slack.png6.7 KiB6.7 KiB

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.

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.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Android Studiologo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/android-studio.png
Slacklogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/slack.png
Google Playlogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/playstore.png
Flutterlogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/flutter.png
Run Payments with Stripe icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
www.gstatic.com/mobilesdk/200629_mobilesdk/stripe_subscriptions_120@2x.png
Firebase AI Logic icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
firebase.google.com/static/images/icons/firebase-ai-logic.svg
Google Adslogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/google-ads.svg
AdMoblogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/ad-mob.svg
Google Marketing Platformlogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/google-marketing-platform.svg
BigQuerylogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/bigquery.svg
Agent Skills icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
firebase.google.com/static/images/icons/firebase-agent-skills.svg
Genkit icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
firebase.google.com/static/images/products/icons/build_genkit_white.svg
Jiralogo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/jira.svg
Search with Algolia icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
firebase.google.com/static/images/products/mods/algolia-search.svg
Stream to BigQuery icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
firebase.google.com/static/images/products/mods/bigquery-export.svg
Looker Studiologo div.logo-row__container > div.logo-row__logo > a.gc-analytics-event > img
firebase.google.com/static/images/integrations/lookerstudio.svg

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

Max Potential First Input Delay 80 ms
Use efficient cache lifetimes
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 18 user timings
JavaScript execution time 0.7 s
Minimizes main-thread work 1.9 s
Avoid long main-thread tasks 7 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 110 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 300 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
96

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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Failing Elements
div > div.code-picker > devsite-iframe > iframe div > div.code-picker > devsite-iframe > iframe

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.

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.

Failing Elements
Easily integrate Firebase with Gemini and the latest AI technology from Google div.highlights-row-wrapper > div.highlights-row__content > div.content > h3#easily-integrate-firebase-with-gemini-and-the-latest-ai-technology-from-google

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.

Failing Elements
More devsite-tabs.upper-tabs > nav.devsite-tabs-wrapper > tab.devsite-overflow-tab > button#tab-overflow-button-gUoG
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
`[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 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
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
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[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
`<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.
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.
Image elements do not have `[alt]` attributes that are redundant text.
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.
92

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
Run Payments with Stripe icon a > div.highlights-row__card > div.highlights-row__image-wrapper > img.highlights-row__image
www.gstatic.com/mobilesdk/200629_mobilesdk/stripe_subscriptions_120@2x.png120 x 240 (0.50)240 x 240 (1.00)

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

SourceDescription
Access to fetch at 'https://cgc-ui-boq-autopush.corp.google.com/__/pingz?platform=devsite&page=%2F&ifgr=true' from origin 'https://firebase.google.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
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
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
92

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

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

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 are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback