Skip to content
https://nubank.com.br

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

67

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:167.004 source:map[column:238493 line:1 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/338-3bed1db7cb8d00eb.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:118.838 source:map[type:text value:[unattributed]]] map[reflowTime:67.431 source:map[column:328259 line:0 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/418-429e5feeab27c497.js urlProvider:network]] map[reflowTime:13.716 source:map[column:408299 line:0 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/418-429e5feeab27c497.js urlProvider:network]] map[reflowTime:26.851 source:map[column:414970 line:0 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/418-429e5feeab27c497.js urlProvider:network]] map[reflowTime:1.815 source:map[column:727694 line:0 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/750-af1d8f19789dce46.js urlProvider:network]] map[reflowTime:34.082 source:map[column:636356 line:0 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/750-af1d8f19789dce46.js urlProvider:network]] map[reflowTime:23.109 source:map[column:96820 line:0 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/750-af1d8f19789dce46.js urlProvider:network]] map[reflowTime:7.064 source:map[column:11298 line:0 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/52774a7f-971f6d93da707a26.js urlProvider:network]] map[reflowTime:30.597 source:map[column:401677 line:0 type:source-location url:https://static.nubank.com.br/17a5d9c7cc870ad93ba9f958fb7cb827793f07e7/_next/static/chunks/418-429e5feeab27c497.js urlProvider:network]] map[reflowTime:0.916 source:map[column:200 line:0 type:source-location url: 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Dois cartões Nubank Ultravioleta sobrepostos e flutuando na tela. div.css-djrn8d > div > div.css-tv8qb4 > img.chakra-image
/120597/1718985255-render-cartoes-nubank-ultravioleta-ptb...72.6 KiB67.1 KiB
Mulher em cafeteria pagando com o cartão Nubank div#swiper-wrapper-1910266dfde17f58b > div.swiper-slide > div.css-8sdrgt > img.chakra-image
/120597/1754405239-mulher-cafeteria-pagando-com-cartao-nu...88.9 KiB42.9 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

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.

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

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

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.

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.

CategoryTime Spent
Script Evaluation4.1 s
Other2.2 s
Style & Layout1.9 s
Rendering436 ms
Script Parsing & Compilation363 ms
Garbage Collection91 ms
Parse HTML & CSS38 ms

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
Font display
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
User Timing marks and measures 2 user timings
Avoid long main-thread tasks 17 long tasks found
Avoid non-composited animations 15 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 270 ms
Server Backend Latencies 530 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 10 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
84

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Nubank Nubank Ultravioleta Nu Empresas Segurança Saiba Mais Login Empresas Quer… div#header-theme-holder > header.css-x8sfzv > div.css-16balko > div.css-1x72l5n
Atendimento em dias úteis das 8h às 18h (horário de Brasília) 0800 887 0463 F… div.css-xju829 > div.css-142n66a > div.css-i5ufy3 > ul.css-lnx3wm
Capitais e regiões metropolitanas 4020 0185 Demais localidades 0800 591 2117… div.css-xju829 > div.css-142n66a > div.css-i5ufy3 > ul.css-lnx3wm
Encarregada: Raíssa Moura Ferreira dpo@nubank.com.br div.css-xju829 > div.css-142n66a > div.css-i5ufy3 > ul.css-lnx3wm

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
Me Roubaram div.css-1m9kjrf > div.css-1rr4qq7 > div.css-4unfe6 > div.chakra-linkbox
Canal de Denúncias div.css-1m9kjrf > div.css-1rr4qq7 > div.css-6eg7o3 > div.chakra-linkbox
Central de Proteção div.css-1m9kjrf > div.css-1rr4qq7 > div.css-vmqn6v > div.chakra-linkbox
Canais de Atendimento div.css-1m9kjrf > div.css-1rr4qq7 > div.css-947n7u > div.chakra-linkbox

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
Digite seu CPF form.css-dvxtzn > div.chakra-form-control > div.chakra-input__group > label#cpf-label

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Me Roubaram div.css-1rr4qq7 > div.css-4unfe6 > div.chakra-linkbox > a.chakra-linkbox__overlay
Canal de Denúncias div.css-1rr4qq7 > div.css-6eg7o3 > div.chakra-linkbox > a.chakra-linkbox__overlay
Central de Proteção div.css-1rr4qq7 > div.css-vmqn6v > div.chakra-linkbox > a.chakra-linkbox__overlay
Canais de Atendimento div.css-1rr4qq7 > div.css-947n7u > div.chakra-linkbox > a.chakra-linkbox__overlay

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.__variable_aa8daf html.__variable_aa8daf

These items highlight common accessibility best practices.

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
0800 887 0463 div.css-i5ufy3 > ul.css-lnx3wm > li.css-155za0w > a.chakra-link
4020 0185 div.css-i5ufy3 > ul.css-lnx3wm > li.css-155za0w > a.chakra-link
0800 591 2117 div.css-i5ufy3 > ul.css-lnx3wm > li.css-155za0w > a.chakra-link
dpo@nubank.com.br div.css-i5ufy3 > ul.css-lnx3wm > li.css-155za0w > a.chakra-link
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]`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.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
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
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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.
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.
81

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.

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
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
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`

Send Feedback