C — https://publico.es | BeaverCheck Audit

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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.

How the composite score is calculated

How you compare

Amazon Route 53 · 975 peers

You 74

Avg 72

At average

0 50 100

Better than 64% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Bootstrap · 823 peers

You 74

Avg 73

At average

0 50 100

Better than 55% of Bootstrap sites See full Bootstrap benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality

1 image-in-link without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fpublico.es)](https://beavercheck.com/results/7b52db65-6f7a-4396-86b8-1bf8a70207be)

HTML

<a href="https://beavercheck.com/results/7b52db65-6f7a-4396-86b8-1bf8a70207be"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpublico.es" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fpublico.es

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

4 warning

4 barrier(s) likely increasing bounce by ~7%.

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€248 investment → €0.53/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -97%

Investment

€248

4h · 5 findings

Monthly returns

€0.53 /mo

~€6.32 / year

Bandwidth savings €0.53

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
RGPD EUR 20,000,000
EAA EUR 500,000

€83 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€248

4.5 developer hours at €55/hr

Based on Spain rates (€55/hr)

Quick wins

€83 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,006 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveRGPDEAA

No privacy policy link detected
RGPD: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
RGPD: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
RGPD: EUR 10,000 – EUR 20,000,000

+9 more

Bandwidth Waste

€0.53 /mo

7106.3 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~711 KB per page load
Saves €0.53/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

100

SEO

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.

1.96 s

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

0 ms

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

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

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

0 ms

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Request	Cache TTL	Transfer Size
/d892ed41-2bfc-4977-a05e-07be26865229/loader.js?target=ww...	7200.0 s	34.8 KiB
s3.eu-central-1.amazonaws.com/sc-devel/Skins/SMCService.js	0.0 ms	24.3 KiB
static.chartbeat.com/js/chartbeat.js	7200.0 s	16.1 KiB
dphp.spxl.socy.es/pixel/js/DPHP_892_7658_912/	427.0 s	9.4 KiB
static.chartbeat.com/js/chartbeat_mab.js	7200.0 s	10.1 KiB
s3.eu-central-1.amazonaws.com/sc-devel/sc-tagmanager/publico.js	0.0 ms	3.6 KiB
/v1/Storage-a482323/smartclip-services/HeaderBidding/js/S...	86400.0 s	6.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.

	URL	Resource Size	Est 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 KiB	494.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 KiB	51.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 KiB	36.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 KiB	35.6 KiB
Ana Pardo de Vera `a.block > figure > picture > img.relative`	www.publico.es/files/avatar/uploads/2024/12/03/674ecb4d50ecc.jpeg	6.1 KiB	4.4 KiB
Jonathan Martínez `a.block > figure > picture > img.relative`	www.publico.es/files/avatar/uploads/2024/12/09/6756b73759c2d.jpeg	6.0 KiB	4.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.

URL	Transfer Size
www.publico.es/assets/screen.c45744f6c7279d9e5dc5.css?v=1776147505	5.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.publico.es/	1.6 s	156 ms	14 ms
Unattributable	691 ms	183 ms	0.0 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-w...	245 ms	166 ms	19 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/sdk....	223 ms	192 ms	31 ms
www.googletagmanager.com/gtag/js?id=G-QFCGYDTZLZ&cx=c&gtm=4e64k1	219 ms	181 ms	34 ms
www.googletagmanager.com/gtm.js?id=GTM-PTC4Z5	213 ms	166 ms	37 ms
www.googletagmanager.com/gtag/js?id=G-1B3Q8QTNDB&cx=c&gtm=4e64k1	197 ms	162 ms	34 ms
www.googletagmanager.com/gtag/js?id=G-MJZ6HSFQQG&cx=c&gtm=4e64k1	190 ms	150 ms	37 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	151 ms	108 ms	40 ms
static.chartbeat.com/js/chartbeat.js	76 ms	72 ms	3.6 ms
www.googletagservices.com/tag/js/gpt.js	71 ms	62 ms	8.5 ms
dphp.spxl.socy.es/pixel/js/DPHP_892_7658_912/	70 ms	60 ms	4.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.

Category	Time Spent
Script Evaluation	1.7 s
Other	972 ms
Style & Layout	739 ms
Script Parsing & Compilation	288 ms
Rendering	129 ms
Garbage Collection	124 ms
Parse HTML & CSS	82 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

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

100

SEO

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.

744 ms

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

1.27 s

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

12 ms

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.

986 ms

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

2.67 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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.

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

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
/d892ed41-2bfc-4977-a05e-07be26865229/loader.js?target=ww...	7200.0 s	34.8 KiB
s3.eu-central-1.amazonaws.com/sc-devel/Skins/SMCService.js	0.0 ms	24.3 KiB
static.chartbeat.com/js/chartbeat.js	7200.0 s	16.1 KiB
dphp.spxl.socy.es/pixel/js/DPHP_892_7658_912/	502.0 s	9.4 KiB
static.chartbeat.com/js/chartbeat_mab.js	7200.0 s	10.1 KiB
s3.eu-central-1.amazonaws.com/sc-devel/sc-tagmanager/publico.js	0.0 ms	3.6 KiB
/v1/Storage-a482323/smartclip-services/HeaderBidding/js/S...	86400.0 s	6.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.

	URL	Resource Size	Est Savings
Fotomontaje con las imágenes de Jorge Azcón, Alejandro Nolasco y María Guardiol… `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_225/uploads/2026/04/...	112.0 KiB	107.3 KiB
–––––––––– Hace 18 años nacimos con un compromiso: hacer un periodismo útil par… `a.image > figure.relative > picture > img`	/files/main_image_horizontal_desktop/uploads/2026/04/21/6...	81.6 KiB	41.8 KiB
El senador Bernie Sanders durante un discurso durante un a acto del movimiento … `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_300/uploads/2026/04/...	45.3 KiB	37.1 KiB
Carlos Cuerpo este martes en el Senado. `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_300/uploads/2026/04/...	35.2 KiB	27.0 KiB
La presidenta reelegida de Extremadura María Guardiola es aplaudida por la banc… `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_425/files/fp/uploads...	41.0 KiB	24.5 KiB
El expresidente del Gobierno José Luis Rodríguez Zapatero en el programa 'Mañan… `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_300/files/fp/uploads...	30.7 KiB	22.5 KiB
Ignacio López del Hierro, exmarido de Dolores de Cospedal, en el juicio sobre '… `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_300/uploads/2026/04/...	28.3 KiB	20.0 KiB
La presidenta de la Comunidad de Madrid, Isabel Díaz Ayuso, ofrece declaracione… `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_300/uploads/2026/04/...	27.7 KiB	19.5 KiB
Un bote navega hacia unos petroleros en el Estrecho de Ormuz. `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_300/uploads/2026/04/...	27.3 KiB	19.1 KiB
Marc Giró en su programa 'Cara al show'. `a.image > figure.relative > picture > img`	/files/home_image_horizontal_desktop_225/uploads/2026/04/...	16.3 KiB	11.6 KiB
Cristina Fallarás `a.block > figure > picture > img.relative`	www.publico.es/files/avatar/uploads/2024/12/09/6756b5fc951e0.jpeg	6.9 KiB	5.3 KiB
Ana Pardo de Vera `a.block > figure > picture > img.relative`	www.publico.es/files/avatar/uploads/2024/12/03/674ecb4d50ecc.jpeg	6.1 KiB	4.4 KiB
Jonathan Martínez `a.block > figure > picture > img.relative`	www.publico.es/files/avatar/uploads/2024/12/09/6756b73759c2d.jpeg	6.0 KiB	4.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.

URL	Transfer Size
www.publico.es/assets/screen.c45744f6c7279d9e5dc5.css?v=1776147505	5.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

Estimated savings: 0.0 ms 7.9 KiB

URL	Transfer Size	Est Savings
s3.eu-central-1.amazonaws.com/sc-devel/Skins/SMCService.js	23.8 KiB	7.9 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 31.6 KiB

URL	Transfer Size	Est Savings
@font-face{font-display:swap;font-family:Publico;font-style:normal;font-weight:900; … } …	21.8 KiB	16.1 KiB
	18.8 KiB	15.5 KiB

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 413.7 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...	187.7 KiB	143.3 KiB
www.googletagmanager.com/gtag/js?id=G-QFCGYDTZLZ&cx=c&gtm=4e64k1	151.4 KiB	63.8 KiB
www.googletagmanager.com/gtag/js?id=G-1B3Q8QTNDB&cx=c&gtm=4e64k1	152.0 KiB	62.9 KiB
www.googletagmanager.com/gtag/js?id=G-MJZ6HSFQQG&cx=c&gtm=4e64k1	156.9 KiB	60.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-PTC4Z5	131.5 KiB	60.1 KiB
s3.eu-central-1.amazonaws.com/sc-devel/Skins/SMCService.js	23.8 KiB	23.1 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
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.hidden > img.w-full`	www.publico.es/images/logo/manana-en-publico-lite.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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Avoids enormous network payloads Total size was 2,103 KiB

●User Timing marks and measures 20 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 19 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 30 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 0 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

Accessibility

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

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

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

Results for https://publico.es

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Trust (2)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Best Practices

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Best Practices

SEO

Keyboard Shortcuts