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.

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
/pagead/managed/js/adsense/m202604160101/show_ads_impl_fy...	1209600.0 s	177.5 KiB
medx.b-cdn.net/tmpl/mobile/css/main.2563887066.css	604800.0 s	42.5 KiB
/mEmluGgI0DucS-wKGmUbiEO7UwhIGLNuqFOLUk1fbWacJag9HbZTyM3j...	86400.0 s	9.3 KiB
medx.b-cdn.net/tmpl/mobile/js/libs.2574936669.js	604800.0 s	24.4 KiB
medx.b-cdn.net/tmpl/mobile/js/main.2574936669.js	604800.0 s	7.9 KiB
medx.b-cdn.net/tmpl/mobile/js/visual-stories.2574936669.js	604800.0 s	3.7 KiB

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:34.702 source:map[column:19934 line:1 type:source-location url:https://medx.b-cdn.net/tmpl/mobile/js/main.2574936669.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:98.221 source:map[type:text value:[unattributed]]] map[reflowTime:32.907 source:map[column:449 line:19 type:source-location url:/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads-contributor.ContributorServingResponseClientJs.en_US.DsKGN-qqfrQ.es5.O/d=1/exm=kernel_loader,loader_js_executable,monetization_cookie_state_migration_initialization_executable,monetization_providers_initialization_executable/ed=1/rs=AJlcJMz2YRLcgcQw7bN4By8dD3CBlNJULw/m=web_iab_tcf_v2_wall_executable urlProvider:network]] map[reflowTime:33.608 source:map[column:35550 line:19 type:source-location url:https://medx.b-cdn.net/tmpl/mobile/js/libs.2574936669.js urlProvider:network]] map[reflowTime:1.094 source:map[column:21254 line:19 type:source-location url:https://medx.b-cdn.net/tmpl/mobile/js/libs.2574936669.js urlProvider:network]] map[reflowTime:0.575 source:map[column:23813 line:19 type:source-location url:https://medx.b-cdn.net/tmpl/mobile/js/libs.2574936669.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-DIV

nodeLabel: Does the brain work like an LLM in predicting words? New study spells out a com…

path: 1,HTML,1,BODY,1,SECTION,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV

selector: div.card-lg > div.card > div.card-image > div.main-news_wrapper

snippet: <div class="main-news_wrapper" style="background-image: url("https://scx1.b-cdn.net/csz/news/800w/2026/does-the-…");">

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

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
medx.b-cdn.net/tmpl/mobile/css/main.2563887066.css	42.5 KiB	1.1 s

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
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...	5.0 ms

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
Welcome to Medical Xpress `div.fc-header > div.fc-header > div.fc-header-image-container > img.fc-header-image`	/mEmluGgI0DucS-wKGmUbiEO7UwhIGLNuqFOLUk1fbWacJag9HbZTyM3j...	8.9 KiB	6.9 KiB

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

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.

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 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: 150 ms 50.1 KiB

URL	Transfer Size	Est Savings
medx.b-cdn.net/tmpl/mobile/css/main.2563887066.css	41.8 KiB	36.2 KiB
.fc-consent-root .fc-dialog-container.fc-fullscreen { height: 100% !important; … } …	16.2 KiB	13.9 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: 3.2 s 499.9 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/adsense/m202604160101/show_ads_impl_fy...	177.5 KiB	149.8 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	187.4 KiB	131.6 KiB
www.googletagmanager.com/gtag/js?id=G-9JGWNNG80H	169.8 KiB	67.7 KiB
/pagead/js/adsbygoogle.js?client=ca-pub-0536483524803400	54.4 KiB	43.5 KiB
/pagead/js/adsbygoogle.js?client=ca-pub-0536483524803400	54.4 KiB	43.5 KiB
fundingchoicesmessages.google.com/i/4988204?ers=3	70.4 KiB	36.0 KiB
/pagead/js/adsbygoogle.js?client=ca-pub-0536483524803400	54.4 KiB	27.8 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.

URL	Total CPU Time	Script Evaluation	Script Parse
medicalxpress.com/	1.4 s	16 ms	8.4 ms
/f/AGSKWxXU9ZTVVXNNqVM_b68iid-_lDi_apEfS0qHc937qamFJAP3rB...	643 ms	276 ms	85 ms
Unattributable	637 ms	16 ms	0.0 ms
fundingchoicesmessages.google.com/i/4988204?ers=3	515 ms	466 ms	35 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	456 ms	343 ms	96 ms
www.googletagmanager.com/gtag/js?id=G-9JGWNNG80H	436 ms	351 ms	81 ms
medx.b-cdn.net/tmpl/mobile/js/main.2574936669.js	398 ms	127 ms	3.6 ms
/pagead/js/adsbygoogle.js?client=ca-pub-0536483524803400	368 ms	226 ms	128 ms
/pagead/managed/js/adsense/m202604160101/show_ads_impl_fy...	263 ms	170 ms	91 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	121 ms	102 ms	18 ms
medx.b-cdn.net/tmpl/mobile/js/libs.2574936669.js	70 ms	51 ms	13 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	2.2 s
Other	1.3 s
Style & Layout	960 ms
Script Parsing & Compilation	570 ms
Parse HTML & CSS	234 ms
Rendering	137 ms
Garbage Collection	37 ms

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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,619 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 16 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 80 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 130 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

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
Latest news `div.row-filter > ul.tabs-filter-wrap > li.tabs-filter-item > a`
Weekly top `div.row-filter > ul.tabs-filter-wrap > li.tabs-filter-item > a`
Spotlights only `div.row-filter > ul.tabs-filter-wrap > li.tabs-filter-item > a`
9 minutes ago `div.card-content > div.card-content-footer > div.date > span`
49 minutes ago `div.card-content > div.card-content-footer > div.date > span`
19 minutes ago `div.card-content > div.card-content-footer > div.date > span`
39 minutes ago `div.card-content > div.card-content-footer > div.date > span`
1 hour ago `div.card-content > div.card-content-footer > div.date > span`
1 hour ago `div.card-content > div.card-content-footer > div.date > span`
1 hour ago `div.card-content > div.card-content-footer > div.date > span`
2 hours ago `div.card-content > div.card-content-footer > div.date > span`
1 hour ago `div.card-content > div.card-content-footer > div.date > span`
3 hours ago `div.card-content > div.card-content-footer > div.date > span`
4 hours ago `div.news-info > div.card-content-footer > div.date > span`
Apr 20, 2026 `div.news-info > div.card-content-footer > div.date > span`
16 `div.news-info > div.card-content-footer > div.comments > span`
Apr 20, 2026 `div.news-info > div.card-content-footer > div.date > span`
Apr 19, 2026 `div.news-info > div.card-content-footer > div.date > span`
29 `div.news-info > div.card-content-footer > div.comments > span`
Apr 19, 2026 `div.news-info > div.card-content-footer > div.date > span`
44 `div.news-info > div.card-content-footer > div.comments > span`
1 hour ago `div.news-info > div.card-content-footer > div.date > span`
3 hours ago `div.news-info > div.card-content-footer > div.date > span`
3 hours ago `div.news-info > div.card-content-footer > div.date > span`
4 hours ago `div.news-info > div.card-content-footer > div.date > span`
4 hours ago `div.news-info > div.card-content-footer > div.date > span`
2 hours ago `div.news-info > div.card-content-footer > div.date > span`
2 hours ago `div.news-info > div.card-content-footer > div.date > span`
6 hours ago `div.news-info > div.card-content-footer > div.date > span`
Subscribe `div.footer-wrapper > div.form-subscribe > form > button.recaptcha`
© Medical Xpress 2011 - 2026 powered by Science X Network `div.container > div.footer-wrapper > div.copyright > p`
Science X Network `div.footer-wrapper > div.copyright > p > a`
Learn more `div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label`
List of partners. `div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog`
Manage options `div.fc-dialog > div.fc-footer-buttons-container > button.fc-button > p.fc-manage-options-third-button-label`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li.tabs-filter-item > div.switch > label > input `li.tabs-filter-item > div.switch > label > input`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.nav-extended > div.fixed-container > div.nav-wrapper > a.brand-logo `nav.nav-extended > div.fixed-container > div.nav-wrapper > a.brand-logo`
div.nav-wrapper > ul.right > li > a.modal-trigger `div.nav-wrapper > ul.right > li > a.modal-trigger`
div.footer-wrapper > div > div.socials-wrapper > a `div.footer-wrapper > div > div.socials-wrapper > a`
div.footer-wrapper > div > div.socials-wrapper > a `div.footer-wrapper > div > div.socials-wrapper > a`
div.footer-wrapper > div > div.socials-wrapper > a `div.footer-wrapper > div > div.socials-wrapper > a`
div.footer-wrapper > div > div.socials-wrapper > a `div.footer-wrapper > div > div.socials-wrapper > a`
div.footer-wrapper > div > div.socials-wrapper > a `div.footer-wrapper > div > div.socials-wrapper > a`
div.footer-wrapper > div > div.socials-wrapper > a `div.footer-wrapper > div > div.socials-wrapper > a`
div.footer-wrapper > div > div.socials-wrapper > a `div.footer-wrapper > div > div.socials-wrapper > a`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Phys.org `div.col > ul.menu-footer > li > a`
Tech Xplore `div.col > ul.menu-footer > li > a`
Science X `div.col > ul.menu-footer > li > a`
Android app `div.col > ul.menu-footer > li > a`
iOS app `div.col > ul.menu-footer > li > a`
RSS feeds `div.col > ul.menu-footer > li > a`
Help `div.col > ul.menu-footer > li > a`
FAQ `div.col > ul.menu-footer > li > a`
Terms of use `div.col > ul.menu-footer > li > a`
Privacy policy `div.col > ul.menu-footer > li > a`
Newsletter `div.col > ul.menu-footer > li > a`
Archive `div.col > ul.menu-footer > li > a`

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

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

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

●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

●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

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

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

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 / Warning	Source
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.	/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads... line 19, col 449

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.

Source	Description
medx.b-cdn.net/tmpl/mobile/js/visual-stories.2574936669.js	`Uncaught ReferenceError: cash is not defined`

●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

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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
sciencex.com/help/about-us/	Read more

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

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
Conditions `body > div#conditions-sidenav > div.container-fluid > a.header-settings-back`

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid