Skip to content
https://plosone.org

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.

42

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
journals.plos.org/resource/js/defer.js?7a7aa422bfb89c5946263600.0 s313.4 KiB
journals.plos.org/resource/fonts/fontawesome-webfont.woff?v=4.1.03600.0 s81.8 KiB
js.hs-analytics.net/analytics/1776888000000/44092021.js300.0 s42.3 KiB
journals.plos.org/resource/img/one/logo.png3600.0 s39.5 KiB
js.hubspot.com/web-interactives-embed.js600.0 s27.9 KiB
js.hs-banner.com/v2/44092021/banner.js300.0 s25.9 KiB
journals.plos.org/resource/js/vendor/jquery.min.js3600.0 s28.8 KiB
journals.plos.org/resource/js/vendor/jquery-ui.min.js3600.0 s24.9 KiB
journals.plos.org/resource/img/sprites/structure.png3600.0 s24.6 KiB
journals.plos.org/resource/img/logo-plos-footer.png3600.0 s20.2 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
journals.plos.org/resource/js/vendor/moment.js3600.0 s10.8 KiB
journals.plos.org/resource/js/vendor/underscore.string.min.js3600.0 s6.5 KiB
extend.vimeocdn.com/ga4/1519726.js86400.0 s11.8 KiB
journals.plos.org/resource/js/vendor/underscore-min.js3600.0 s5.6 KiB
journals.plos.org/resource/js/vendor/vendor.min.js3600.0 s5.5 KiB
js.hsadspixel.net/pixels.js600.0 s3.9 KiB
journals.plos.org/resource/css/interface.css?460ce76d110431694cece1ea536cc9503600.0 s4.0 KiB
journals.plos.org/resource/css/mobile.css?460ce76d110431694cece1ea536cc9503600.0 s2.3 KiB
journals.plos.org/resource/js/content.js3600.0 s1.9 KiB
journals.plos.org/resource/js/navigation.js3600.0 s1.6 KiB
journals.plos.org/resource/js/sync.js?7a7aa422bfb89c5946263600.0 s1.4 KiB
js.hs-scripts.com/44092021.js90.0 s1.1 KiB
journals.plos.org/resource/js/share.js3600.0 s1.3 KiB
journals.plos.org/resource/img/bg/arrow-right.png3600.0 s1.2 KiB
journals.plos.org/resource/css/base.css?460ce76d110431694cece1ea536cc9503600.0 s914 B
journals.plos.org/resource/js/taxonomy.js3600.0 s833 B
/1/cf99e8d2a3?a=402703674&sa=1&v=1212.e95d35c&t=Unnamed%2...0.0 ms624 B
journals.plos.org/resource/js/util/utils.js3600.0 s725 B
/resource/css/mobile/one/branding.css?460ce76d110431694ce...3600.0 s457 B
/resource/css/plos-interface.css?460ce76d110431694cece1ea...3600.0 s283 B
journals.plos.org/resource/css/plos-mobile.css?460ce76d110431694cece1ea536cc9503600.0 s218 B

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.

URLEst Savings
journals.plos.org/resource/fonts/fontawesome-webfont.woff?v=4.1.0115 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.

URLResource SizeEst Savings
nav.cRcTKF1kQ5xNNwSAStfmxA== > ul.A6YueuXsuZeGkmFirvJ+gA== > li._7beRpKvO69ozFSkKu7RO4g== > a#siteLogo nav.cRcTKF1kQ5xNNwSAStfmxA== > ul.A6YueuXsuZeGkmFirvJ+gA== > li._7beRpKvO69ozFSkKu7RO4g== > a#siteLogo
journals.plos.org/resource/img/one/logo.png39.5 KiB25.8 KiB
Back to Top main#home-content > nav#home-bottom-article-menu > div.btn-top-container > a.btn
journals.plos.org/resource/img/sprites/structure.png24.5 KiB9.9 KiB
PLOS body.PLoSONE > div#container-main > footer#common-footer > img.logo-footer
journals.plos.org/resource/img/logo-plos-footer.png20.1 KiB7.0 KiB

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

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
journals.plos.org/resource/js/vendor/jquery.min.js28.8 KiB
journals.plos.org/resource/js/vendor/jquery-ui.min.js24.9 KiB153 ms
journals.plos.org/resource/js/vendor/underscore.string.min.js6.5 KiB153 ms
journals.plos.org/resource/js/vendor/underscore-min.js5.6 KiB
journals.plos.org/resource/js/sync.js?7a7aa422bfb89c5946261.4 KiB
journals.plos.org/resource/js/vendor/vendor.min.js5.5 KiB153 ms
/resource/css/mobile/one/branding.css?460ce76d110431694ce...457 B
journals.plos.org/resource/css/plos-mobile.css?460ce76d110431694cece1ea536cc950218 B
journals.plos.org/resource/css/interface.css?460ce76d110431694cece1ea536cc9504.0 KiB
/resource/css/plos-interface.css?460ce76d110431694cece1ea...283 B
journals.plos.org/resource/css/mobile.css?460ce76d110431694cece1ea536cc9502.3 KiB
journals.plos.org/resource/css/base.css?460ce76d110431694cece1ea536cc950914 B

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: 1.7 s
URLTime Spent
plosone.org/802 ms
journals.plos.org/plosone867 ms
journals.plos.org/plosone/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 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.3 s 598.6 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-EJPREQGMKT&cx=c&gtm=4e64k0174.2 KiB73.0 KiB
www.googletagmanager.com/gtag/js?id=G-QC8WLNV09G&cx=c&gtm=4e64k0169.3 KiB70.4 KiB
www.googletagmanager.com/gtag/js?id=G-TJKG55MN8J&cx=c&gtm=4e64k0174.9 KiB70.3 KiB
www.googletagmanager.com/gtag/js?id=AW-11128208251&cx=c&gtm=4e64k0145.3 KiB65.0 KiB
www.googletagmanager.com/gtag/js?id=AW-11124076945&cx=c&gtm=4e64k0139.0 KiB64.2 KiB
www.googletagmanager.com/gtag/js?id=AW-17421501988&cx=c&gtm=4e64k0140.3 KiB63.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-MQQMGF157.0 KiB62.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-TP26BH141.3 KiB55.7 KiB
journals.plos.org/resource/js/defer.js?7a7aa422bfb89c594626312.0 KiB52.1 KiB
journals.plos.org/resource/js/vendor/jquery-ui.min.js24.9 KiB21.3 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
js.hs-analytics.net/analytics/1776888000000/44092021.js445 ms318 ms7.8 ms
Unattributable327 ms14 ms0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-MQQMGF314 ms248 ms63 ms
journals.plos.org/resource/js/defer.js?7a7aa422bfb89c594626298 ms149 ms138 ms
www.googletagmanager.com/gtm.js?id=GTM-TP26BH255 ms205 ms49 ms
www.googletagmanager.com/gtag/js?id=G-QC8WLNV09G&cx=c&gtm=4e64k0247 ms161 ms43 ms
journals.plos.org/plosone/230 ms139 ms7.5 ms
www.googletagmanager.com/gtag/js?id=G-TJKG55MN8J&cx=c&gtm=4e64k0222 ms182 ms38 ms
www.googletagmanager.com/gtag/js?id=G-EJPREQGMKT&cx=c&gtm=4e64k0207 ms159 ms46 ms
www.googletagmanager.com/gtag/js?id=AW-11124076945&cx=c&gtm=4e64k0183 ms146 ms35 ms
www.googletagmanager.com/gtag/js?id=AW-17421501988&cx=c&gtm=4e64k0177 ms141 ms35 ms
www.googletagmanager.com/gtag/js?id=AW-11128208251&cx=c&gtm=4e64k0175 ms139 ms35 ms
journals.plos.org/resource/js/vendor/jquery.min.js150 ms109 ms11 ms
journals.plos.org/resource/js/vendor/vendor.min.js58 ms29 ms1.6 ms
js.hubspot.com/web-interactives-embed.js55 ms43 ms9.9 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 Evaluation2.3 s
Script Parsing & Compilation569 ms
Other347 ms
Style & Layout209 ms
Garbage Collection72 ms
Parse HTML & CSS24 ms
Rendering9.2 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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 118.2 KiB
URLTransfer SizeEst Savings
@media print{.RJTFKB562SZjYh8J5G1fZA\=\={display:none !important} …16.1 KiB16.1 KiB
@media print{.trqrJOIprDDLDk-EHioXNg\=\={display:none !important} …14.9 KiB14.9 KiB
@media print{._5FbTxc-uPyNfZEQX3vGItw\=\={display:none !important} …14.6 KiB14.6 KiB
@media print{.TiNqYv\+Tc2nJcskLZbC8Zg\=\={display:none !important} …14.5 KiB14.4 KiB
@media print{._1A9fMk4mEjKB2x\+pyuqsRA\=\={display:none !important} …14.0 KiB14.0 KiB
@media print{._0IUJCg4xNOQLOusmExeiRw\=\={display:none !important} …14.0 KiB13.9 KiB
@media print{.IfUDP69Mozy6j0c\+q\+iPFQ\=\={display:none !important} …10.2 KiB10.2 KiB
@media print{.tJGwuysS2X3ousgH1kcthg\=\={display:none !important} …10.1 KiB10.1 KiB
@media print{.e72nVXDjTLIeO0GPwB-alQ\=\={display:none !important} …10.0 KiB10.0 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 body.PLoSONE > div#container-main > footer#common-footer > img.logo-footer
journals.plos.org/resource/img/logo-plos-footer.png

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,991 KiB
●User Timing marks and measures 17 user timings
●Avoid long main-thread tasks 15 long tasks found
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 130 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 120 ms
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
○Avoid large layout shifts
100

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.

○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
●`<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.
●Heading elements appear in a sequentially-descending order
●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
○`<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
○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.
○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.
○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.
77

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
Unload event listeners are deprecated and will be removed.
journals.plos.org/plosone/ line 106, col 29072

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
journals.plos.org/favicon.ico
Failed to load resource: the server responded with a status of 404 ()
journals.plos.org/plosone/ line 106, col 29092
TypeError: Cannot read properties of undefined (reading 'trigger') at https://journals.plos.org/resource/js/defer.js?7a7aa422bfb89c594626:2:1244041 at nrWrapper (https://journals.plos.org/plosone/:107:29073)

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.

URLMap URL
journals.plos.org/resource/js/defer.js?7a7aa422bfb89c594626
js.hsadspixel.net/pixels.js/adsscriptloaderstatic/static-1.3043/bundles/pixels-relea...
●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
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
83

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Back to Top main#home-content > nav#home-bottom-article-menu > div.btn-top-container > a.btn
Expand Submissions nav.full-menu > ul.primary > li.accordion-item > a.expander
Expand Policies nav.full-menu > ul.primary > li.accordion-item > a.expander
Expand Manuscript Review and Publication nav.full-menu > ul.primary > li.accordion-item > a.expander
Expand About nav.full-menu > ul.primary > li.accordion-item > a.expander

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