Skip to content
https://mundodeportivo.com

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.

29

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
/etc/static/especial/hemeroteca-md/hemeroteca-md.jpg?code=mv600.0 s305.9 KiB
/045b8894-d300-4d6e-9660-5d16b7c213f9-web.js900.0 s216.0 KiB
dai.grupogodo.com/md/godo-adsx-nt.js?extension0.0 ms108.0 KiB
widgets.outbrain.com/outbrain.js14500.0 s109.6 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
cdn.jwplayer.com/libraries/7lOBAPdy.js180.0 s65.8 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=8461800.0 s60.2 KiB
service.wemass.com/dmp/cea5524788f821b6687cfc6c8027a6b8.js180.0 s40.8 KiB
/3da070b4-2745-4eb6-8fc9-1fabe5f634e6/loader.js?target=ww...7200.0 s37.9 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
rsc2.lavanguardia.com/js/accounts-v1001257.js2419200.0 s134.6 KiB
godo.spxl.socy.es/pixel/js/GODO_816_926_112/449.0 s9.4 KiB
dai.grupogodo.com/md/utils.js0.0 ms5.1 KiB
static.servg1.net/m.js0.0 ms4.2 KiB
es-config.sensic.net/s2s-web.js1209600.0 s31.0 KiB
rsc2.mundodeportivo.com/js/godo-base1x-v1000606.js2419200.0 s31.1 KiB
sb.scorecardresearch.com/beacon.js86400.0 s6.7 KiB
stories.mundodeportivo.com/optimize-v7/app.optimize.v7.min.js?c=v006600.0 s2.5 KiB
dai.grupogodo.com/md/adloader.js0.0 ms1.5 KiB
stories.mundodeportivo.com/optimize-v7/global/app.autorefresh.min.js?v=v006600.0 s922 B
rsc2.lavanguardia.com/js/godo-didomix-v1001225.js2419200.0 s7.8 KiB
stories.mundodeportivo.com/optimize-v7/home/app.home.min.js?v=v006600.0 s819 B
/css/web/generable/screens-v1000492.css?v=c7d0b436db2c7dd...2419200.0 s3.9 KiB
cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.css604800.0 s3.4 KiB
widget-pixels.outbrain.com/widget/detect/px.gif?ch=114400.0 s389 B
rsc2.mundodeportivo.com/css/web/xalok/md-resultsV7-v1000008.css?debug=2419200.0 s1.2 KiB

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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:44.415 source:map[column:278 line:92 type:source-location url:https://www.google-analytics.com/analytics.js urlProvider:network]] map[reflowTime:32.13 source:map[column:38273 line:1 type:source-location url:https://sdk.mrf.io/statics/marfeel-sdk.js?id=846 urlProvider:network]] map[reflowTime:0.154 source:map[column:184 line:0 type:source-location url: urlProvider:network]] map[reflowTime:47.381 source:map[column:488 line:0 type:source-location url:https://dai.grupogodo.com/md/utils.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: Horizontal
path: 1,HTML,1,BODY,15,MAIN,4,DIV,0,DIV,2,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,0,ARTICLE,0,FIGURE,0,PICTURE,2,IMG
selector: article.c-article > figure.c-article__thumb > picture > img
snippet: <img loading="lazy" alt="Horizontal" width="449" height="464" src="https://imagenes2.mundodeportivo.com/files/image_449_464/files/fp/uploads/…">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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 SizeDuration
cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.css3.4 KiB782 ms
static2-v7.mundodeportivo.com/assets/screen.69da0275fe9cd0174b0d.css?177625791849.2 KiB2.6 s
/assets/screenZD.496be485229c8268bfdc.css?17762579185.1 KiB151 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

Estimated savings: 812 ms
URLTime Spent
mundodeportivo.com/812 ms
www.mundodeportivo.com/0.0 ms

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 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: 300 ms 58.1 KiB
URLTransfer SizeEst Savings
static2-v7.mundodeportivo.com/assets/screen.69da0275fe9cd0174b0d.css?177625791848.9 KiB44.0 KiB
17.0 KiB14.1 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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 4.7 s 800.6 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...187.5 KiB136.7 KiB
/assets/global.51cd2619ddb5ac51de2b.bundle.js?1776257918114.2 KiB94.3 KiB
widgets.outbrain.com/outbrain.js109.3 KiB85.9 KiB
dai.grupogodo.com/md/godo-adsx-nt.js?extension107.6 KiB81.0 KiB
rsc2.lavanguardia.com/js/accounts-v1001257.js78.3 KiB65.5 KiB
www.googletagmanager.com/gtag/js?id=G-KHXQ0540MR&cx=c&gtm=4e64k1144.2 KiB61.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-WK8X9CS161.3 KiB58.9 KiB
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/sdk....101.3 KiB44.3 KiB
/045b8894-d300-4d6e-9660-5d16b7c213f9-web.js215.4 KiB42.5 KiB
fundingchoicesmessages.google.com/i/55964524?ers=368.5 KiB37.0 KiB
service.wemass.com/dmp/cea5524788f821b6687cfc6c8027a6b8.js39.6 KiB28.2 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=84659.9 KiB22.4 KiB
code.jquery.com/jquery-3.6.0.min.js30.2 KiB21.3 KiB
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-w...58.9 KiB20.9 KiB

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
Unattributable1.2 s385 ms0.0 ms
www.mundodeportivo.com/939 ms321 ms25 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=846666 ms525 ms1.1 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-w...373 ms216 ms24 ms
/045b8894-d300-4d6e-9660-5d16b7c213f9-web.js348 ms162 ms77 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/sdk....306 ms240 ms36 ms
www.googletagmanager.com/gtm.js?id=GTM-WK8X9CS295 ms198 ms66 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...288 ms197 ms48 ms
/experimentsexperience/render?id=AC_9O5Ssrp-Rb6CiJew_TBme...273 ms246 ms0.3 ms
www.google-analytics.com/analytics.js266 ms51 ms22 ms
fundingchoicesmessages.google.com/i/55964524?ers=3248 ms219 ms17 ms
www.googletagmanager.com/gtag/js?id=G-KHXQ0540MR&cx=c&gtm=4e64k1234 ms204 ms29 ms
es-config.sensic.net/s2s-web.js228 ms177 ms44 ms
dai.grupogodo.com/md/godo-adsx-nt.js?extension207 ms171 ms30 ms
dai.grupogodo.com/md/utils.js197 ms5.5 ms1.1 ms
widgets.outbrain.com/outbrain.js163 ms120 ms23 ms
securepubads.g.doubleclick.net/tag/js/gpt.js?network-code=55964524160 ms118 ms40 ms
rsc2.lavanguardia.com/js/accounts-v1001257.js159 ms99 ms41 ms
/assets/global.51cd2619ddb5ac51de2b.bundle.js?1776257918159 ms108 ms46 ms
/solomoto/clasificados/project/solomoto/banner_buscador.php85 ms1.8 ms9.5 ms
godo.spxl.socy.es/pixel/js/GODO_816_926_112/77 ms64 ms4.1 ms
code.jquery.com/jquery-1.11.0.min.js64 ms47 ms12 ms
service.wemass.com/dmp/cea5524788f821b6687cfc6c8027a6b8.js60 ms48 ms12 ms
/?uid=613bb0d66b6a5524b8fb18d3&oab=1&puburl=https%253A%25...59 ms50 ms0.5 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 Evaluation4.2 s
Other1.4 s
Style & Layout772 ms
Script Parsing & Compilation657 ms
Parse HTML & CSS195 ms
Garbage Collection115 ms
Rendering103 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
/etc/static/especial/hemeroteca-md/hemeroteca-md.jpg?code=mv305.9 KiB
/045b8894-d300-4d6e-9660-5d16b7c213f9-web.js216.0 KiB
static2-v7.mundodeportivo.com/assets/assets/iconsfont-v5.woff2190.2 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...187.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-WK8X9CS161.7 KiB
www.googletagmanager.com/gtag/js?id=G-KHXQ0540MR&cx=c&gtm=4e64k1144.2 KiB
rsc2.lavanguardia.com/js/accounts-v1001257.js134.6 KiB
fonts.gstatic.com/s/sourceserif4/v14/vEFI2_tTDB4M7-auWDN0ahZJW1gb8te1Xb7G.woff2119.3 KiB
/assets/global.51cd2619ddb5ac51de2b.bundle.js?1776257918114.6 KiB
widgets.outbrain.com/outbrain.js109.6 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
Edicion Impresa div.u-grid > div.u-grid > div.c-prefooter-box > img
/etc/static/especial/hemeroteca-md/hemeroteca-md.jpg?code=mv

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 10 user timings
●Avoid long main-thread tasks 20 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 120 ms
●Server Backend Latencies 40 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 60 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
80

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.c-header > div.c-header__middle > div.o-container > button.c-header__user header.c-header > div.c-header__middle > div.o-container > button.c-header__user

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.u-grid > div.u-grid-col-span-1 > div.u-flex > iframe div.u-grid > div.u-grid-col-span-1 > div.u-flex > iframe

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

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
MERCADO FICHAJES div.o-container--module > article.c-article > div.c-article__txt > p.c-article__epigraph
Contacto nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Ayuda nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Aviso Legal nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Política de Cookies nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Política de Privacidad nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Canal Ético nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Publicidad nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Mundo Deportivo USA nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Sitemap nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__link
Configuración de Cookies nav.c-footer__nav > ul.c-footer__list > li.c-footer__item > a.c-footer__item

These are opportunities to improve the legibility of your content.

Best practices

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh 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.

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
Rechazar y suscribirse div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-disagree-button
Aceptar y continuar div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-agree-button
○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
●`[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.
●`[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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○`<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
○`<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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Escudo Barcelona div.c-article__txt > div.c-article__score > div.c-article__score__team > img.c-article__score__team__thumb
/files/image_36_36/uploads/2021/07/19/60f53a8cf1dd0.png36 x 3636 x 3654 x 54
Escudo Celta de Vigo div.c-article__txt > div.c-article__score > div.c-article__score__team > img.c-article__score__team__thumb
/files/image_36_36/uploads/2021/07/19/60f53ace156d4.png36 x 3636 x 3654 x 54

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
/?&m=MundodeportivoWeb&r=www.mundodeportivo.com&p=es1&ins...
Failed to load resource: net::ERR_CONNECTION_REFUSED
●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
●Page has the HTML doctype
●Properly defines charset
●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
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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img
article.c-article > figure.c-article__thumb > picture > img article.c-article > figure.c-article__thumb > picture > img

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

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

Send Feedback