Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2	65 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:2080.458 label:Time to first byte subpart:timeToFirstByte] map[duration:809.696 label:Resource load delay subpart:resourceLoadDelay] map[duration:31.089 label:Resource load duration subpart:resourceLoadDuration] map[duration:11.93 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Featured articles left 1

path: 1,HTML,1,BODY,16,DIV,1,DIV,1,DIV,0,DIV,0,A,3,DIV,0,IMG

selector: div#gtm_track_newsinfo > a > div#hgl-img > img.entered

snippet: <img src="https://newsinfo.inquirer.net/files/2026/02/House-Committee-on-Justice-Rep…" alt="Featured articles left 1" data-lazy-src="https://newsinfo.inquirer.net/files/2026/02/House-Committee-on-Justice-Rep…" data-ll-status="loaded" class="entered lazyloaded">

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: Featured articles left 1

path: 1,HTML,1,BODY,16,DIV,1,DIV,1,DIV,0,DIV,0,A,3,DIV,0,IMG

selector: div#gtm_track_newsinfo > a > div#hgl-img > img.entered

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

value: No additional origins are good candidates for preconnecting

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	Duration
/wp-content/cache/min/1/ajax/libs/video.js/7.10.2/video-j...	10.1 KiB	151 ms
/wp-content/cache/background-css/1/www.inquirer.net/wp-co...	9.0 KiB	151 ms
fonts.googleapis.com/icon?family=Material+Icons	817 B	818 ms
www.inquirer.net/inq2016/swiper-v6.js	37.4 KiB	302 ms
/wp-content/cache/background-css/1/www.inquirer.net/wp-co...	10.5 KiB	302 ms
/wp-content/cache/min/1/font-awesome/4.5.0/css/font-aweso...	6.4 KiB
/wp-content/cache/min/1/inq2016/inqnewgallery-2020-g8-pro...	1.7 KiB
/wp-content/cache/background-css/1/www.inquirer.net/wp-co...	972 B
/wp-content/cache/background-css/1/www.inquirer.net/wp-co...	505 B
/wp-content/cache/min/1/wp-content/plugins/pdf-poster/bui...	672 B
/wp-content/cache/background-css/1/www.inquirer.net/wp-co...	1.1 KiB
/wp-content/cache/min/1/wp-content/plugins/inq-slider-sim...	917 B
/wp-content/cache/min/1/inq2016/home-livestream-embed.css...	572 B	151 ms
/wp-content/cache/background-css/1/www.inquirer.net/wp-co...	931 B
use.typekit.net/ymb2ppk.js	6.9 KiB	763 ms
/wp-content/cache/min/1/inq2016/nav2022/style-l.css?ver=1...	1.3 KiB
/wp-content/cache/min/1/inq2016/inq-special-2020-e.css?ve...	1.0 KiB
/wp-content/cache/min/1/inq2016/nav2022/global.css?ver=17...	688 B
/wp-content/cache/min/1/landing2017/voteph2025/vph-mob-wi...	1.7 KiB	151 ms
www.inquirer.net/wp-content/cache/min/1/inq2016/swiper-v6.css?ver=1776129566	4.1 KiB

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
cdn.izooto.com/scripts/sdk/izooto.js	1382400.0 s	95.4 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	11.9 KiB
use.typekit.net/ymb2ppk.js	600.0 s	6.9 KiB
analytics.inquirernetwork.net/js/track_v5.js?v=5.2	14400.0 s	1.8 KiB

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: 2.3 s

URL	Time Spent
inquirer.net/	1.5 s
www.inquirer.net/wp-signup.php?new=inquirer.net	802 ms
www.inquirer.net/	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

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: 210 ms 96.2 KiB

URL	Transfer Size	Est Savings
cdn.izooto.com/scripts/sdk/izooto.js	94.8 KiB	62.3 KiB
www.inquirer.net/inq2016/swiper-v6.js	37.2 KiB	33.9 KiB

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.

Estimated savings: 0.0 ms 2.6 KiB

URL	Transfer Size	Est Savings
:root { --widget-height: 550px; --widget-height-1366: 500px; … } …	11.5 KiB	2.6 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 11.4 KiB

URL	Transfer Size	Est Savings
:root { --widget-height: 550px; --widget-height-1366: 500px; … } …	11.5 KiB	11.4 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
Featured articles left 1 `div#gtm_track_newsinfo > a > div#hgl-img > img.entered`	/files/2026/02/House-Committee-on-Justice-Representative-...
Featured articles left 2 `div#gtm_track_newsinfo > a > div#hgl-img > img.entered`	newsinfo.inquirer.net/files/2026/04/Leni-Robredo-22April2026-620x349.jpg
Featured articles left 3 `div#gtm_track_newsinfo > a > div#hgl-img > img.entered`	newsinfo.inquirer.net/files/2026/04/romualdelz-21April2026-620x349.jpg
inquirer `div.twok-nav-main > div.twok-nm-logo > a > img`	www.inquirer.net/inq2016/nav2022/images/inq2016.svg
menu `div.twok-nm-menu-date > div#menutoggle2 > a > img`	www.inquirer.net/inq2016/nav2022/images/twok-menu.svg

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 703 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.2 s

●Avoid long main-thread tasks 2 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 650 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 300 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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
OPINION `div#gtm_track_opinion > a > div.flx-m-cat > span.opinion_clr`
div#gtm_track_business > a > div.flx-m-cat > span.business_clr `div#gtm_track_business > a > div.flx-m-cat > span.business_clr`
section > ul > li > h5 `section > ul > li > h5`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`

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
LATEST STORIES `div#popular_left > div#inq_popular_lbl > a > h4`
BUSINESS `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:58 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:39 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:34 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:31 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:24 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:15 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:15 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:00 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:55 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:50 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:45 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:40 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:35 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:25 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:20 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:10 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:06 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:04 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:03 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:02 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:01 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:00 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:55 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:50 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:45 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:40 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:35 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:30 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:30 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:20 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:15 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:12 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:11 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:10 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:09 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:08 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:07 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:06 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:04 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 01:28 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:58 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:50 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:15 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:10 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 21, 2026 11:41 PM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
div#inq_channels_wrap > div#track_property > div > h6 `div#inq_channels_wrap > div#track_property > div > h6`
div#inq_channels_wrap > div#track_business > div > h6 `div#inq_channels_wrap > div#track_business > div > h6`
div#inq_channels_wrap > div#track_sports > div > h6 `div#inq_channels_wrap > div#track_sports > div > h6`
div#inq_channels_wrap > div#track_entertainment > div > h6 `div#inq_channels_wrap > div#track_entertainment > div > h6`
div#inq_channels_wrap > div#track_lifestyle > div > h6 `div#inq_channels_wrap > div#track_lifestyle > div > h6`
div#inq_channels_wrap > div#track_usa > div > h6 `div#inq_channels_wrap > div#track_usa > div > h6`
div#inq_channels_wrap > div#track_cebudailynews > div > h6 `div#inq_channels_wrap > div#track_cebudailynews > div > h6`
div#inq_channels_wrap > div#track_nolisoli > div > h6 `div#inq_channels_wrap > div#track_nolisoli > div > h6`
div#inq_channels_wrap > div#track_globalnation > div > h6 `div#inq_channels_wrap > div#track_globalnation > div > h6`
div#inq_channels_wrap > div#track_technology > div > h6 `div#inq_channels_wrap > div#track_technology > div > h6`
div#inq_channels_wrap > div#track_world > div > h6 `div#inq_channels_wrap > div#track_world > div > h6`
div#inq_channels_wrap > div#track_metro > div > h6 `div#inq_channels_wrap > div#track_metro > div > h6`
div#inq_channels_wrap > div#track_regions > div > h6 `div#inq_channels_wrap > div#track_regions > div > h6`
div#inq_channels_wrap > div#track_pop > div > h6 `div#inq_channels_wrap > div#track_pop > div > h6`
div#inq_channels_wrap > div#track_west_philippine_sea > div > h6 `div#inq_channels_wrap > div#track_west_philippine_sea > div > h6`
div#inq_channels_wrap > div#track_radyo > div > h6 `div#inq_channels_wrap > div#track_radyo > div > h6`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

●`[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 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

●Touch targets have sufficient size and spacing.

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` 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

○`[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]`s are contained by their required parent element

○`[role]` values are valid

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

○No element has a `[tabindex]` value greater than 0

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
PCSO ribbon lotto2 – Apr19-May18 `div#flx-gl-right > div > a > img.pcso-ribbon-lotto2-apr19-may18_gallery_www`	www.inquirer.net/wp-content/uploads/2025/08/PCSO-Lotto-2.png	300 x 75 (4.00)	375 x 100 (3.75)

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 / Warning	Source
SharedStorage	www.inquirer.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.inquirer.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.inquirer.net/cdn-cgi/challenge-platform/scripts/jsd/main.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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
opinion.inquirer.net/191230/pax-silica-whats-in-it-for-ph	READ MORE
opinion.inquirer.net/	READ MORE

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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`