Skip to content
https://uba.ar

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.

55

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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
div.row > div.col > div.card > img.card-img-top div.row > div.col > div.card > img.card-img-top
uba.ar/storage/Vay0PyQmz0QM4FfFldiTSOYvlEjca339XJsfZy45.jpg509.4 KiB498.3 KiB
div.row > div.col > div.card > img.card-img-top div.row > div.col > div.card > img.card-img-top
uba.ar/storage/WqKOPBKn5jt9GAzGfwrbdWlsQWUsM1hmoupRaMHd.jpg270.7 KiB259.6 KiB
div.col-12 > div.row > div.col-12 > div.col-md-6 div.col-12 > div.row > div.col-12 > div.col-md-6
www.uba.ar/storage/WinpAOvN6NMBPT8tHiFltrvz8NmHyktV4ngNu59S.jpg263.1 KiB238.0 KiB
div#sliderFotos > div.carousel-inner > div.carousel-item > img.d-block div#sliderFotos > div.carousel-inner > div.carousel-item > img.d-block
uba.ar/storage/dKgViUZh5ILVIAFi4tniGlfm93oXAngCvqoL2kpI.jpg276.2 KiB145.9 KiB
div.col-12 > div.row > div.col-12 > div.col-md-6 div.col-12 > div.row > div.col-12 > div.col-md-6
www.uba.ar/storage/7EZzjiWzkwloNnXTmlPqunMGpyq3ouPta9jc6ecK.jpg171.0 KiB145.9 KiB
VER MÁS div.container-fluid > div.row > div.col-12 > img.img-fluid
www.uba.ar/storage/vWqLuWCXvO8kGxbp30TJtsxYTJ6ymqKumIg06H4s.jpg215.8 KiB109.1 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:16446.75 label:Time to first byte subpart:timeToFirstByte] map[duration:15914.47 label:Element render delay subpart:elementRenderDelay]]
lhId: page-6-P
nodeLabel: SIN APLICAR LA LEY DE FINANCIAMIENTO UNIVERSITARIO. LA UNIVERSIDAD PÚBLICA NO …
path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,1,DIV,3,DIV,0,P
selector: div.modal-content > div.modal-body > div.contador-texto > p.mb-4
snippet: <p class="mb-4">

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 15.8 s
URLTime Spent
uba.ar/15.9 s

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 0.0 ms 68.3 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-0ST2QP5PEG161.2 KiB68.3 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
div#sliderFotos > div.carousel-inner > div.carousel-item > img.d-block div#sliderFotos > div.carousel-inner > div.carousel-item > img.d-block
uba.ar/storage/dKgViUZh5ILVIAFi4tniGlfm93oXAngCvqoL2kpI.jpg
div.row > div.col > div.card > img.card-img-top div.row > div.col > div.card > img.card-img-top
uba.ar/storage/Vay0PyQmz0QM4FfFldiTSOYvlEjca339XJsfZy45.jpg
div.row > div.col > div.card > img.card-img-top div.row > div.col > div.card > img.card-img-top
uba.ar/storage/WqKOPBKn5jt9GAzGfwrbdWlsQWUsM1hmoupRaMHd.jpg
div.row > div.col > div.card > img.card-img-top div.row > div.col > div.card > img.card-img-top
uba.ar/storage/uNfrxusKCC50Bom0LbeIoCTvzAczgOTXbX9Cblss.jpg
VER MÁS div.container-fluid > div.row > div.col-12 > img.img-fluid
www.uba.ar/storage/vWqLuWCXvO8kGxbp30TJtsxYTJ6ymqKumIg06H4s.jpg
UBA Universidad de Buenos Aires header#inicio > nav.navbar > a.navbar-brand > img
uba.ar/imgs/logoheader40anios.png
UBA Universidad de Buenos Aires div.row > div.col-12 > a.mb-2 > img.img-fluid
uba.ar/imgs/logofooter.png

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

Layout shift culprits
Optimize DOM size
Forced reflow
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
User Timing marks and measures 5 user timings
JavaScript execution time 0.1 s
Minimizes main-thread work 0.3 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 670 ms
Server Backend Latencies 6,260 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
Avoid long main-thread tasks
Avoid non-composited animations
78

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
183 DÍAS 00 HORAS 36 MINUTOS 57 SEGUNDOS SIN APLICAR LA LEY DE FINANCIAMIENTO … body.modal-open > div#popupContador182

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
FACULTADES Y CARRERAS div.row > div.col-12 > a.stretched-link > h2
COLEGIOS div.row > div.col-12 > a.stretched-link > h2
POSGRADOS div.row > div.col-12 > a.stretched-link > h2
INVESTIGACIÓN div.row > div.col-12 > a.stretched-link > h2
COMUNIDAD UBA div.col-md-6 > a.stretched-link > div.f-blanco > h1
UNIVERSIDAD Y SOCIEDAD div.col-md-6 > a.stretched-link > div.f-blanco > h1
UBA NOTICIAS div.container-fluid > div.d-flex > div.me-auto > h2
VISITÁ EL PORTAL div.d-flex > div.ms-auto > a.f-blanco > span.d-none
JORNADA DE VISIBILIZACIÓN div.col > div.card > div.card-body > h5
EVITAR LA PROGRESIÓN div.col > div.card > div.card-body > h5
CREANDO CONCIENCIA div.col > div.card > div.card-body > h5
UBA CIENCIA div.container-fluid > div.d-flex > div.me-auto > h2
VISITÁ EL PORTAL div.d-flex > div.ms-auto > a.f-blanco > span.d-none
VER MÁS div.row > div.col-12 > div.position-absolute > a.btn-uba
Por más graduad@s div.col-12 > a.stretched-link > div.f-blanco > h1.f-blanco
Donar aquí Para las Becas Sarmiento a.stretched-link > div.f-blanco > h6.f-blanco > p
00 div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div#contadorHoras
HORAS div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div.contador-tiempo-label
36 div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div#contadorMinutos
MINUTOS div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div.contador-tiempo-label
57 div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div#contadorSegundos
SEGUNDOS div.modal-body > div.contador-tiempo-grid > div.contador-tiempo-item > div.contador-tiempo-label
LEY DE FINANCIAMIENTO UNIVERSITARIO. div.modal-body > div.contador-texto > p.mb-4 > span.texto-amarillo
CUIDEMOS LO QUE FUNCIONA. div.modal-content > div.modal-body > div.contador-texto > p.texto-amarillo-2

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Derechos Humanos div.carousel-item > div.caja > div > h4.mt-4
JORNADA DE VISIBILIZACIÓN div.col > div.card > div.card-body > h5
EVITAR LA PROGRESIÓN div.col > div.card > div.card-body > h5
CREANDO CONCIENCIA div.col > div.card > div.card-body > h5
Donar aquí Para las Becas Sarmiento   div.col-12 > a.stretched-link > div.f-blanco > h6.f-blanco

These are opportunities to improve keyboard navigation in your application.

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
div#navbarNav > ul.navbar-nav > li.nav-item > a.nav-link div#navbarNav > ul.navbar-nav > li.nav-item > a.nav-link
div.row > ul.nav > li > a div.row > ul.nav > li > a
div.row > ul.nav > li.ms-2 > a div.row > ul.nav > li.ms-2 > a
div.row > ul.nav > li.ms-2 > a div.row > ul.nav > li.ms-2 > a
div.row > ul.nav > li.ms-2 > a div.row > ul.nav > li.ms-2 > a
div.row > ul.nav > li.ms-2 > a div.row > ul.nav > li.ms-2 > a
div.row > ul.nav > li.ms-2 > a div.row > ul.nav > li.ms-2 > a
div.row > ul.nav > li.ms-2 > a div.row > ul.nav > li.ms-2 > a

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
seguinos!!!! footer.px-md-3 > div.col-12 > div.row > ul.nav

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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

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
`[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
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
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.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with 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
Form elements have associated labels
Links are distinguishable without relying on color.
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
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.
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

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Send Feedback