Skip to content
https://publico.es

Lighthouse Mobile

· 0 checks — Mobile 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.

—

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

RequestCache TTLTransfer Size
/d892ed41-2bfc-4977-a05e-07be26865229/loader.js?target=ww...7200.0 s34.8 KiB
s3.eu-central-1.amazonaws.com/sc-devel/Skins/SMCService.js0.0 ms24.3 KiB
static.chartbeat.com/js/chartbeat.js7200.0 s16.1 KiB
dphp.spxl.socy.es/pixel/js/DPHP_892_7658_912/427.0 s9.4 KiB
static.chartbeat.com/js/chartbeat_mab.js7200.0 s10.1 KiB
s3.eu-central-1.amazonaws.com/sc-devel/sc-tagmanager/publico.js0.0 ms3.6 KiB
/v1/Storage-a482323/smartclip-services/HeaderBidding/js/S...86400.0 s6.0 KiB

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
Fotomontaje con las imágenes de Jorge Azcón, Alejandro Nolasco y María Guardiol… a.image > figure.relative > picture > img
/files/image_horizontal_mobile/uploads/2026/04/22/69e8f47...507.4 KiB494.2 KiB
Un bote navega hacia unos petroleros en el Estrecho de Ormuz. a.image > figure.relative > picture > img
/files/image_horizontal_mobile/uploads/2026/04/22/69e8e1d...64.3 KiB51.1 KiB
Marc Giró en su programa 'Cara al show'. a.image > figure.relative > picture > img
/files/image_horizontal_mobile/uploads/2026/04/22/69e8dfd...50.1 KiB36.9 KiB
La presidenta reelegida de Extremadura María Guardiola es aplaudida por la banc… a.image > figure.relative > picture > img
/files/image_horizontal_mobile/files/fp/uploads/2026/04/2...48.9 KiB35.6 KiB
Ana Pardo de Vera a.block > figure > picture > img.relative
www.publico.es/files/avatar/uploads/2024/12/03/674ecb4d50ecc.jpeg6.1 KiB4.4 KiB
Jonathan Martínez a.block > figure > picture > img.relative
www.publico.es/files/avatar/uploads/2024/12/09/6756b73759c2d.jpeg6.0 KiB4.4 KiB

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.

URLTransfer Size
www.publico.es/assets/screen.c45744f6c7279d9e5dc5.css?v=17761475055.8 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

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.

URLTotal CPU TimeScript EvaluationScript Parse
www.publico.es/1.6 s156 ms14 ms
Unattributable691 ms183 ms0.0 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-w...245 ms166 ms19 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/sdk....223 ms192 ms31 ms
www.googletagmanager.com/gtag/js?id=G-QFCGYDTZLZ&cx=c&gtm=4e64k1219 ms181 ms34 ms
www.googletagmanager.com/gtm.js?id=GTM-PTC4Z5213 ms166 ms37 ms
www.googletagmanager.com/gtag/js?id=G-1B3Q8QTNDB&cx=c&gtm=4e64k1197 ms162 ms34 ms
www.googletagmanager.com/gtag/js?id=G-MJZ6HSFQQG&cx=c&gtm=4e64k1190 ms150 ms37 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...151 ms108 ms40 ms
static.chartbeat.com/js/chartbeat.js76 ms72 ms3.6 ms
www.googletagservices.com/tag/js/gpt.js71 ms62 ms8.5 ms
dphp.spxl.socy.es/pixel/js/DPHP_892_7658_912/70 ms60 ms4.4 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.

CategoryTime Spent
Script Evaluation1.7 s
Other972 ms
Style & Layout739 ms
Script Parsing & Compilation288 ms
Rendering129 ms
Garbage Collection124 ms
Parse HTML & CSS82 ms

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
Logo div.didomi-popup-container > div.didomi-popup-view > div.didomi-popup-notice-logo-container > img.didomi-popup-notice-logo
www.publico.es/bundles/appcms/images/logo/logo.png
Logo de Público div.desktop:flex > h1.text-publico > a > img.logo-stop-genocidio
www.publico.es/images/logo/stop-genocidio.svg
Logo de 'Mañana en Público' section.manana-en-publico-home > div.mt-5 > a.block > img.w-full
www.publico.es/images/logo/manana-en-publico-mobile.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
●Font display
●Forced reflow
●Modern HTTP
●Network dependency tree
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 2,313 KiB
●User Timing marks and measures 20 user timings
●Avoid non-composited animations 16 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 90 ms
●Server Backend Latencies 30 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 0 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP breakdown
○LCP request discovery
95

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.

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
P. A. C: ul.tablet:px-4 > li.flex > div.w-full > span.inline
L. A. ul.tablet:px-4 > li.flex > div.w-full > span.inline
R. B. ul.tablet:px-4 > li.flex > div.w-full > span.inline
TREMENDING div.body--wrapper > p.category > a > span.font-bold
TREMENDING div.body--wrapper > p.category > a > span.font-bold
TREMENDING div.body--wrapper > p.category > a > span.font-bold
TREMENDING div.supratitle-tremending > ul.desktop:flex > li.desktop:mr-auto > a.chevron-right-link
Mar Bermúdez i Jiménez ul.tablet:px-4 > li.flex > div.w-full > span.inline
PÚBLIC div.supratitle-public > ul.desktop:flex > li.desktop:mr-auto > a.chevron-right-link
1. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
2. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
3. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
4. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
5. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
6. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
7. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
8. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
9. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-2
10. div.desktop:max-w-[670px] > ul.tablet:px-4 > li.flex > span.mr-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
Si eres suscriptor, inicia sesión en Público div.didomi-popup-notice-text-container > div.didomi-popup-notice-text > div > h3#didomi-login-h3

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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●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 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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○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.
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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback