Skip to content
https://www.bing.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.

86

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
www.bing.com/th?id=OHR.SpaceTrails_ES-ES6596295414_768x1366.webp691200.0 s117.8 KiB
www.bing.com/rp/3Q-Qtx1VliX3e9Su_cQ43faPcLA.svg36770.0 s5.1 KiB
www.bing.com/rp/ocEt0h8hUeda41yHUYWzy5RxOGE.png204315.0 s3.4 KiB
www.bing.com/rp/29PIludr0ouX7uObDIN9ORIKUhg.png432000.0 s3.8 KiB
www.bing.com/rp/88F_WFp57AEhbuX2xUzJp0yKLEM.br.js432000.0 s3.4 KiB
www.bing.com/rp/f21jlSMmEDN43OaavcdaB-7Phq0.svg432000.0 s1.1 KiB
www.bing.com/rp/71mLq5OSx9PI8jgeJllXdk39KxM.br.js432000.0 s355 B
www.bing.com/rp/qwce00QJxdHzNxXh5H1mBc8QgBU.br.js432000.0 s233 B
/fd/ls/l?IG=950E6D474BCB4469BEFFC067667AD668&CID=0CD1DF23...0.0 ms17 B
www.bing.com/rp/0yKRkahHgilUPDT6ZPRr5FxoCu8.br.css35463.0 s0 B
www.bing.com/rp/KLrSbzDKMog0mCiPcB9iwoEvlE4.br.js432000.0 s0 B
www.bing.com/rp/MjkKTrIX9w2UKVd1W1WV1Gj2zWM.br.js432000.0 s0 B
www.bing.com/rp/bhhdQJeg8xXgunZIeh8xsZViHi0.br.js432000.0 s0 B
www.bing.com/rp/LXu4eYVt3NhFk3Ud9ZbhZ_PYFaA.br.js199041.0 s0 B
www.bing.com/rp/JXkjDPywJD9oeuWPLy7bD8Jc6mw.br.js432000.0 s0 B
www.bing.com/rp/x5filocM3n9wrEHQHUbXi0_r1yo.br.js309927.0 s0 B

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
value: No additional origins are good candidates for preconnecting

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

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 750 ms 144.2 KiB
URLTransfer SizeEst Savings
www.bing.com/rp/w19dDk2py2mlGW2GYbXdcuuQfy0.br.js132.5 KiB82.4 KiB
www.bing.com/rp/5RUBu5dEYIDzWQtuZRVAHjBjuyc.br.js88.9 KiB61.8 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 15.6 KiB
URLTransfer SizeEst Savings
@media(max-width:1440px){#id_n{white-space:nowrap;overflow:hidden;text-overflow:ellipsis; … } …19.0 KiB15.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
© EL PAÍS li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_7DC10ACBDD97F558F1337582C4FC3CAC&w=186&h...
© EL PAÍS li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_B79C3BE1C34C348218248BC6D31531D2&w=186&h...
© La Vanguardia li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_62D263A6EB689DA7C69B0890CDE0D3B4&w=186&h...
© El HuffPost li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_70F90EA2F68CE0F4D5943F5BBA474823&w=186&h...
© elEconomista.es li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_91113A509255210E4A133CD32B483195&w=186&h...
© La Vanguardia li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_725862519594558E0D19C5250F898E2E&w=186&h...
© OKDIARIO li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_681248126CE7F5718B0503A6F6DEF8A2&w=186&h...
© El HuffPost li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_9A1335FDD0D32D85F59106C501389139&w=186&h...
© La Vanguardia li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_1DA93A0FB06642B52B3320BC15DA5BD5&w=186&h...
© La Vanguardia li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_3557D8ABE5F4444C6BB81EEB02ADBC62&w=186&h...
© El Debate li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_45C226FDDF57F28C52A67BECF61E96F0&w=186&h...
© El HuffPost li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_00F51FF4D1421850EDE36D2C58BDDC01&w=186&h...
© Dailymotion li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_3D674FF33830BFB5F3C526BD4114E21D&w=186&h...
© La Razón li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_4D07E199A581FDF2FFB0E989393B1D36&w=186&h...
© El Debate li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_1E4C08F6BF49AE12CBA8A252AA2C2C94&w=186&h...
© El HuffPost li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_58E81655F51C2F367173B24EFAADB030&w=186&h...
© El Debate li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_C04DF63745F77995409A4B8FBF356572&w=186&h...
© El Debate li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_47C9C7ED903C073FE9007934A7EFBE7F&w=186&h...
© elEconomista.es li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_30AA3F4606421CCCB8258E8E09B14F43&w=186&h...
© La Razón li.pntile > a > span.crs_item > img
/th?id=OPN.TOBP2_2DD60D3E99848A805CFA8ED441577CE1&w=186&h...
div#bnp_cookie_banner > div#bnp_container > div.bnp_title_container > img.bnp_title_icon div#bnp_cookie_banner > div#bnp_container > div.bnp_title_container > img.bnp_title_icon
www.bing.com/rp/3Q-Qtx1VliX3e9Su_cQ43faPcLA.svg

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

●Time to Interactive 3.8 s
●Max Potential First Input Delay 120 ms
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 651 KiB
●User Timing marks and measures 2 user timings
●JavaScript execution time 0.7 s
●Minimizes main-thread work 1.7 s
●Avoid long main-thread tasks 2 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 120 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 80 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
92

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
Microsoft and our third-party vendors use cookies and similar technologies to d… body#bpage > div#bnp.nid.63245 > div#bnp_cookie_banner

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.

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
body#bpage > div#bnp.nid.63245 > div#cookie_preference > meta body#bpage > div#bnp.nid.63245 > div#cookie_preference > 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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○Buttons have an accessible name
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
73

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
chrome.loadTimes() is deprecated, instead use standardized API: Paint Timing.
www.bing.com/rp/70rhlhm1764HLXYuwL6dxslNwPk.br.js line 1, col 16769

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
www.bing.com/ line 5, col 530
ReferenceError: sj_evt is not defined at https://www.bing.com/:6:531

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Cookie

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.bing.com/rp/5RUBu5dEYIDzWQtuZRVAHjBjuyc.br.js
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
92

SEO

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Accept div.bnp_content > div.bnp_action_container > div#bnp_btn_accept > a
Reject div.bnp_content > div.bnp_action_container > div#bnp_btn_reject > a
More options div#bnp_container > div.bnp_content > div.bnp_action_container > a#bnp_btn_preference
El primer paso fuera de la Tierra div.musCard > div.headline > div.icon_text > a

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

Send Feedback