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
js.hsforms.net/forms/embed/v2.js	300.0 s	193.8 KiB
js.hs-analytics.net/analytics/1776797400000/44092021.js	300.0 s	42.3 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.2 KiB
js.hs-banner.com/v2/44092021/banner.js	300.0 s	25.9 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
js.hsadspixel.net/pixels.js	600.0 s	3.9 KiB
js.hs-scripts.com/44092021.js?integration=WordPress&ver=11.3.45	90.0 s	1.1 KiB
js-na1.hs-scripts.com/44092021.js	0.0 ms	902 B
/collect?v=2&fmt=js&pid=2702956&time=1776797412484&li_ads...	0.0 ms	451 B

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:0.453 source:map[column:86058 line:19 type:source-location url:https://js.hs-analytics.net/analytics/1776797400000/44092021.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-SECTION

nodeLabel: We believe in a better future where science is open to all, for all

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

selector: div#content > main.main > div.elementor > section.elementor-section

snippet: <section class="elementor-section elementor-top-section elementor-element elementor-elemen…" data-id="dbf0bf6" data-element_type="section" data-e-type="section" data-settings="{"background_background":"classic"}">

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
plos.org/wp-content/themes/plos/dist/styles/main_bf93fbf5.css?ver=6.9.4	79.7 KiB	907 ms
/wp-content/themes/plos/resources/lib/scripts/jquery-3.5....	33.1 KiB	605 ms
plos.org/wp-content/uploads/elementor/css/custom-frontend.min.css?ver=1776412090	8.2 KiB
/wp-content/plugins/elementor/assets/css/widget-divider.m...	1.1 KiB
plos.org/wp-content/plugins/orcid-master/assets/orcid.js?ver=6.9.4	1.3 KiB	151 ms
plos.org/wp-content/uploads/elementor/css/post-51.css?ver=1776412090	2.2 KiB
/wp-content/plugins/elementor/assets/lib/eicons/css/eleme...	4.8 KiB
plos.org/wp-content/plugins/snazzy-maps/snazzymaps.js?ver=1.5.0	2.5 KiB
plos.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.5 KiB	151 ms
plos.org/wp-content/plugins/orcid-master/assets/orcid.css?ver=6.9.4	548 B
/wp-content/plugins/elementor/assets/css/widget-heading.m...	436 B
plos.org/wp-content/plugins/elementor/assets/css/widget-spacer.min.css?ver=4.0.2	648 B
plos.org/wp-content/uploads/elementor/css/post-3286.css?ver=1776412090	966 B
/css2?family=Merriweather:ital,opsz,wght@0,18..144,300..9...	2.4 KiB	760 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
section.elementor-section > div.elementor-container > div.elementor-column > div.elementor-widget-wrap `section.elementor-section > div.elementor-container > div.elementor-column > div.elementor-widget-wrap`	/wp-content/uploads/2024/12/Images-1200x628px-web-page-fe...	292.4 KiB	169.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

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: 750 ms 78.0 KiB

URL	Transfer Size	Est Savings
plos.org/wp-content/themes/plos/dist/styles/main_bf93fbf5.css?ver=6.9.4	79.4 KiB	78.0 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: 900 ms 262.1 KiB

URL	Transfer Size	Est Savings
js.hsforms.net/forms/embed/v2.js	186.4 KiB	106.9 KiB
plos.org/wp-content/themes/plos/dist/scripts/main_bf93fbf5.js?ver=0.0.8	88.2 KiB	78.2 KiB
js.hsforms.net/forms/embed/v2.js	186.4 KiB	76.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.

URL	Total CPU Time	Script Evaluation	Script Parse
plos.org/	833 ms	110 ms	59 ms
js.hsforms.net/forms/embed/v2.js	783 ms	488 ms	264 ms
js.hs-analytics.net/analytics/1776797400000/44092021.js	747 ms	517 ms	14 ms
/wp-content/themes/plos/resources/lib/scripts/jquery-3.5....	473 ms	400 ms	23 ms
Unattributable	472 ms	21 ms	0.0 ms
plos.org/wp-content/plugins/snazzy-maps/snazzymaps.js?ver=1.5.0	231 ms	155 ms	1.5 ms
snap.licdn.com/li.lms-analytics/insight.min.js	110 ms	92 ms	7.4 ms
plos.org/wp-content/themes/plos/dist/scripts/main_bf93fbf5.js?ver=0.0.8	86 ms	34 ms	52 ms
js.hubspot.com/web-interactives-embed.js	80 ms	62 ms	14 ms
static.ads-twitter.com/uwt.js	72 ms	64 ms	6.4 ms
plos.org/wp-content/themes/plos/dist/styles/main_bf93fbf5.css?ver=6.9.4	64 ms	0.0 ms	0.0 ms
plos.org/wp-includes/js/wp-emoji-release.min.js?ver=6.9.4	52 ms	49 ms	3.2 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
Style & Layout	784 ms
Other	604 ms
Script Parsing & Compilation	511 ms
Parse HTML & CSS	164 ms
Rendering	43 ms
Garbage Collection	18 ms

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 9.8 KiB

URL	Transfer Size	Est Savings
/wp-content/plugins/plos-elementor-widgets/assets/lib/sli...	16.8 KiB	6.8 KiB
/wp-content/plugins/plos-elementor-widgets/assets/js/widg...	7.5 KiB	3.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
PLOS logo `header.app-header > div.app-header__container > a.app-header__brand > img.app-header__logo`	plos.org/wp-content/uploads/2024/11/logo-plos-full-color.svg
PLOS logo `div.app-footer__container > div.app-footer__col > a.app-footer__brand > img.app-footer__logo`	plos.org/wp-content/uploads/2024/11/logo-plos-white.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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

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

●Avoid long main-thread tasks 17 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 280 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 40 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

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

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
PLOS is a non-profit organization on a mission to drive open science forward wi… `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > 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.

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

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○Uses ARIA roles only on compatible elements

○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
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

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
plos.org/wp-content/themes/plos/favicon/site.webmanifest	`Failed to load resource: the server responded with a status of 403 ()`
plos.org/wp-content/themes/plos/favicon/site.webmanifest	`Failed to load resource: the server responded with a status of 403 ()`
plos.org/	`Manifest fetch from https://plos.org/wp-content/themes/plos/favicon/site.webmanifest failed, code 403`
plos.org/	`Manifest fetch from https://plos.org/wp-content/themes/plos/favicon/site.webmanifest failed, code 403`
/wp-content/themes/plos/resources/lib/scripts/jquery-3.5.... line 1, col 31669	SyntaxError: "undefined" is not valid JSON at JSON.parse (<anonymous>) at Object.init (https://plos.org/wp-content/themes/plos/dist/scripts/main_bf93fbf5.js?ver=0.0.8:287:11266) at HTMLDocument.<anonymous> (https://plos.org/wp-content/themes/plos/dist/scripts/main_bf93fbf5.js?ver=0.0.8:287:11355) at e (https://plos.org/wp-content/themes/plos/resources/lib/scripts/jquery-3.5.1.min.js?ver=3.5.1:2:30005) at t (https://plos.org/wp-content/themes/plos/resources/lib/scripts/jquery-3.5.1.min.js?ver=3.5.1:2:30307)

●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 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
plos.org/open-science/	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
Topic areas `li#menu-item-42192 > ul.sub-menu > li#menu-item-45740 > 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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`