Skip to content
Audit Complete

Results for https://jmir.org

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 20:00 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C71

Site Health

Score: 71 / 100

Based on 8 categories, 0 sections

Room to improve — your 26.8s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Good content signals with minor gaps.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon Route 53 · 777 peers
You 71
·
Avg 72
At average
0 50 100
Better than 23% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Apple · 972 peers
You 71
·
Avg 73
At average
0 50 100
Better than 22% of Apple sites See full Apple benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

1 image-in-link without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fjmir.org)](https://beavercheck.com/results/ae96d133-d525-4fb7-b7f0-340b7ded76a1)
<a href="https://beavercheck.com/results/ae96d133-d525-4fb7-b7f0-340b7ded76a1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fjmir.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fjmir.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 5 warning

8 barrier(s) likely increasing bounce by ~33%.

Speed (2)

Page takes 26.8s to load

+12% bounce

Users abandon at ~3s — you're 24.3s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 3.0s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (3)

Mixed content on HTTPS page

+8% bounce

Browsers block insecure subresources — broken images, missing scripts, warning badge

Fix: Change http:// URLs inside the page to https:// (or protocol-relative)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€383 investment → €0.86/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -97%

Investment

€383

4h · 5 findings

Monthly returns

€0.86 /mo

~€10 / year

  • Bandwidth savings €0.86

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€383

4.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,668 / month at risk

~€120,500,010 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • 1 advertising/retargeting trackers detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000

+6 more

Bandwidth Waste

€0.86 /mo

11645.3 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.2 MB per page load
    Saves €0.86/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

36
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
67
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.80 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

26.76 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.04 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.064

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

5.35 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

27.74 s

Detailed Report

Audit breakdown by category with detailed findings.

36

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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
app.enzuzo.com/scripts/cookiebar/aa022ba6-b337-11ef-b288-3fb59f57942d3600.0 s131.1 KiB
js.hs-analytics.net/analytics/1776887700000/19668141.js300.0 s42.7 KiB
js.hubspot.com/web-interactives-embed.js600.0 s28.5 KiB
js.hscollectedforms.net/collectedforms.js300.0 s26.4 KiB
js.hs-banner.com/v2/19668141/banner.js300.0 s24.4 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
asset.jmir.pub/resources/images/partners/ORCID.jpg0.0 ms13.8 KiB
asset.jmir.pub/resources/images/partners/oaspa.jpg0.0 ms13.3 KiB
asset.jmir.pub/resources/images/logos/JMIR_logo.png0.0 ms12.1 KiB
asset.jmir.pub/resources/images/partners/trend-MD.jpg0.0 ms11.8 KiB
asset.jmir.pub/resources/images/partners/open-access.jpg0.0 ms11.1 KiB
asset.jmir.pub/resources/images/partners/crossref.jpg0.0 ms10.8 KiB
asset.jmir.pub/resources/images/partners/cope.jpg0.0 ms7.6 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
asset.jmir.pub/placeholder.svg0.0 ms6.1 KiB
static.zdassets.com/ekr/asset_composer.js3600.0 s4.7 KiB
js.hsadspixel.net/pixels.js600.0 s3.9 KiB
d1uo4w7k31k5mn.cloudfront.net/v2_hq/17.png0.0 ms2.2 KiB
d1uo4w7k31k5mn.cloudfront.net/v2_hq/22.png0.0 ms2.2 KiB
d1uo4w7k31k5mn.cloudfront.net/v2_hq/1.png0.0 ms2.1 KiB
js.hs-scripts.com/19668141.js90.0 s1.1 KiB
d1bxh8uas1mnw7.cloudfront.net/assets/embed.js0.0 ms1.0 KiB
/collect?v=2&fmt=js&pid=3149908&time=1776887954326&url=ht...0.0 ms696 B
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s6.7 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s5.5 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s5.0 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s4.9 KiB
/v1/internal-556fdf0f/doi/10.2196/98143?callback=_altmetr...3600.0 s458 B
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s3.6 KiB
/v1/internal-556fdf0f/doi/10.2196/79928?callback=_altmetr...3600.0 s447 B
/v1/internal-556fdf0f/doi/10.2196/97777?callback=_altmetr...3600.0 s432 B
/v1/internal-556fdf0f/doi/10.2196/80500?callback=_altmetr...3600.0 s430 B
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s3.4 KiB
/v1/internal-556fdf0f/doi/10.2196/87542?callback=_altmetr...3600.0 s426 B
/v1/internal-556fdf0f/doi/10.2196/82004?callback=_altmetr...3600.0 s423 B
/v1/internal-556fdf0f/doi/10.2196/86097?callback=_altmetr...3600.0 s423 B
/v1/internal-556fdf0f/doi/10.2196/87198?callback=_altmetr...3600.0 s411 B
/v1/internal-556fdf0f/doi/10.2196/89151?callback=_altmetr...3600.0 s400 B
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s3.0 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.9 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.8 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.1 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.0 KiB
/v.gif?cd=0&a=544689&d=jmir.org&u=DA5A23A95C74DF870A026FA...43200.0 s145 B

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.

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:74.443 source:map[type:text value:[unattributed]]] map[reflowTime:2.28 source:map[column:86058 line:68 type:source-location url:https://js.hs-analytics.net/analytics/1776887700000/19668141.js urlProvider:network]]]

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
JMIR Publications div.corporate__logo > a > div > img.logo-img
asset.jmir.pub/resources/images/logos/JMIR_logo.png11.7 KiB8.7 KiB

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:419.4789990234375 label:Time to first byte subpart:timeToFirstByte] map[duration:2170.0410009765624 label:Element render delay subpart:elementRenderDelay]]
lhId: page-1-SPAN
nodeLabel: We and our 5 partners may use, with your consent, cookies or similar technologi…
path: 1,HTML,1,BODY,68,DIV,1,DIV,0,DIV,1,DIV,0,SPAN
selector: div#ez-cookie-notification > div.enzuzo-notification-text > div.enzuzo-notification-desc > span
snippet: <span>

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.

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

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: 150 ms 18.7 KiB
URLTransfer SizeEst Savings
badge.dimensions.ai/badge.js80.8 KiB18.7 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: 110 ms 91.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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.

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 Evaluation5.6 s
Style & Layout1.2 s
Other1.0 s
Script Parsing & Compilation890 ms
Rendering245 ms
Parse HTML & CSS192 ms
Garbage Collection157 ms

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
JMIR Publications div.corporate__logo > a > div > img.logo-img
asset.jmir.pub/resources/images/logos/JMIR_logo.png
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
ORCID Member li > p > a > img
asset.jmir.pub/resources/images/partners/ORCID.jpg
PubMed li > p > a > img
/hubfs/19668141/00 Marketing/Logos/External logos for jou...
Committee on Publication Ethics li > p > a > img
asset.jmir.pub/resources/images/partners/cope.jpg
Open Access ul > li > p > img
asset.jmir.pub/resources/images/partners/open-access.jpg
Crossref Member li > p > a > img
asset.jmir.pub/resources/images/partners/crossref.jpg
TrendMD Member li > p > a > img
asset.jmir.pub/resources/images/partners/trend-MD.jpg
Open Access Scholarly Publishers Association li > p > a > img
asset.jmir.pub/resources/images/partners/oaspa.jpg

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
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 10 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 120 ms
Server Backend Latencies 270 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 180 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
88

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.corporate > div.corporate__mobile-menu > button div.container > div.corporate > div.corporate__mobile-menu > button

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > p > a > img.image_resized li > p > a > img.image_resized
ul > li > p > img ul > li > p > img

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.

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
our 5 partners div.enzuzo-notification-text > div.enzuzo-notification-desc > span > a#ez-tcf-notification-message-vendors-link
Privacy Policy ↗ div.enzuzo-notification-text > div.enzuzo-notification-desc > span > a#notificationPolicyLink
Manage preferences div.ez-consent > div#ez-cookie-notification > div.enzuzo-notification-buttons > a#notificationManagerLink

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Get Alerts div.container > div.row > div.email-subscribtion-button > a
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
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.
Select elements have associated label elements.
`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
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 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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` 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
`<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
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.
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

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.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
PubMed Central li > p > a > img.image_resized
/hubfs/19668141/00 Marketing/Logos/External logos for jou...317 x 81 (3.91)461 x 81 (5.69)

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
AttributionReporting
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
67

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.

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > p > a > img.image_resized li > p > a > img.image_resized
ul > li > p > img ul > li > p > img

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
Crossref Member ul > li > p > a
Committee on Publication Ethics ul > li > p > a
Open Access Scholarly Publishers Association ul > li > p > a
TrendMD Member ul > li > p > a
PubMed ul > li > p > a
PubMed Central ul > li > p > a
  section.partners-wrapper > ul > li > 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
Page has successful HTTP status code
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

39
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
67
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.40 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.10 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

424 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.244

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.92 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

6.11 s

Detailed Report

Audit breakdown by category with detailed findings.

39

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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
app.enzuzo.com/scripts/cookiebar/aa022ba6-b337-11ef-b288-3fb59f57942d3600.0 s130.6 KiB
js.hs-analytics.net/analytics/1776887700000/19668141.js300.0 s42.7 KiB
js.hubspot.com/web-interactives-embed.js600.0 s28.5 KiB
js.hscollectedforms.net/collectedforms.js300.0 s26.4 KiB
js.hs-banner.com/v2/19668141/banner.js300.0 s24.4 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
asset.jmir.pub/resources/images/partners/ORCID.jpg0.0 ms13.8 KiB
asset.jmir.pub/resources/images/partners/oaspa.jpg0.0 ms13.3 KiB
asset.jmir.pub/resources/images/logos/JMIR_logo.png0.0 ms12.1 KiB
asset.jmir.pub/resources/images/partners/trend-MD.jpg0.0 ms11.8 KiB
asset.jmir.pub/resources/images/partners/open-access.jpg0.0 ms11.1 KiB
asset.jmir.pub/resources/images/partners/crossref.jpg0.0 ms10.8 KiB
asset.jmir.pub/resources/images/partners/cope.jpg0.0 ms7.6 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
asset.jmir.pub/placeholder.svg0.0 ms6.1 KiB
static.zdassets.com/ekr/asset_composer.js3600.0 s4.7 KiB
js.hsadspixel.net/pixels.js600.0 s3.9 KiB
d1uo4w7k31k5mn.cloudfront.net/v2_hq/17.png0.0 ms2.2 KiB
d1uo4w7k31k5mn.cloudfront.net/v2_hq/22.png0.0 ms2.2 KiB
d1uo4w7k31k5mn.cloudfront.net/v2_hq/1.png0.0 ms2.2 KiB
js.hs-scripts.com/19668141.js90.0 s1.1 KiB
d1bxh8uas1mnw7.cloudfront.net/assets/embed.js0.0 ms1.0 KiB
/collect?v=2&fmt=js&pid=3149908&time=1776887975448&url=ht...0.0 ms694 B
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s6.7 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s5.5 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s5.2 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s5.0 KiB
/v1/internal-556fdf0f/doi/10.2196/97777?callback=_altmetr...3600.0 s483 B
/v1/internal-556fdf0f/doi/10.2196/82004?callback=_altmetr...3600.0 s455 B
/v1/internal-556fdf0f/doi/10.2196/89151?callback=_altmetr...3600.0 s431 B
/v1/internal-556fdf0f/doi/10.2196/98143?callback=_altmetr...3600.0 s429 B
/v1/internal-556fdf0f/doi/10.2196/87542?callback=_altmetr...3600.0 s427 B
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s3.4 KiB
/v1/internal-556fdf0f/doi/10.2196/79928?callback=_altmetr...3600.0 s425 B
/v1/internal-556fdf0f/doi/10.2196/86097?callback=_altmetr...3600.0 s424 B
/v1/internal-556fdf0f/doi/10.2196/80500?callback=_altmetr...3600.0 s423 B
/v1/internal-556fdf0f/doi/10.2196/87198?callback=_altmetr...3600.0 s416 B
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s3.3 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.9 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.9 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.8 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.2 KiB
/hubfs/19668141/00 Marketing/Logos/External logos for jou...1209600.0 s2.2 KiB
/v.gif?cd=0&a=544689&d=jmir.org&u=DC67936617867866597297E...43200.0 s145 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.243596] map[node:map[boundingRect:map[bottom:6672 height:6540 left:0 right:1350 top:132 width:1350] lhId:page-1-DIV nodeLabel:Journal of Medical Internet Research The leading peer-reviewed journal for dig… path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,5,DIV,0,DIV,1,DIV selector:div#jmir-html > div#main-layout-container > div > div.container-fluid snippet:<div class="container-fluid" style="padding: 0px;"> type:node] score:0.243265 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:78 height:78 left:120 right:460 top:0 width:340] lhId:page-10-IMG nodeLabel:JMIR Publications path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,5,DIV,0,DIV,0,DIV,0,HEADER,0,SECTION,0,NAV,0,DIV,0,HEADER,0,SECTION,0,DIV,1,DIV,0,DIV,0,A,0,DIV,0,IMG selector:div.corporate__logo > a > div > img.logo-img snippet:<img src="https://asset.jmir.pub/resources/images/logos/JMIR_logo.png" alt="JMIR Publications" class="logo-img"> type:node]]] type:subitems]] map[score:0.000331 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:78 height:78 left:120 right:460 top:0 width:340] lhId:page-10-IMG nodeLabel:JMIR Publications path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,5,DIV,0,DIV,0,DIV,0,HEADER,0,SECTION,0,NAV,0,DIV,0,HEADER,0,SECTION,0,DIV,1,DIV,0,DIV,0,A,0,DIV,0,IMG selector:div.corporate__logo > a > div > img.logo-img snippet:<img src="https://asset.jmir.pub/resources/images/logos/JMIR_logo.png" alt="JMIR Publications" class="logo-img"> type:node]]] type:subitems]]]

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.

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:71.256 source:map[type:text value:[unattributed]]] map[reflowTime:0.608 source:map[column:86058 line:68 type:source-location url:https://js.hs-analytics.net/analytics/1776887700000/19668141.js urlProvider:network]] map[reflowTime:13.036 source:map[column:15077 line:0 type:source-location url:https://jmir.org/_nuxt/16f5249.js urlProvider:network]] map[reflowTime:28.736 source:map[column:8784 line:1 type:source-location url:https://jmir.org/_nuxt/90f100e.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: div > div.slider
path: 0,DIV
selector: div > div.slider
snippet: <div data-v-2d93858b="" class="slider slide" style="">

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.

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
JMIR Publications div.corporate__logo > a > div > img.logo-img
asset.jmir.pub/resources/images/logos/JMIR_logo.png11.7 KiB10.7 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Journal of Medical Internet Research The leading peer-reviewed journal for dig… div#jmir-html > div#main-layout-container > div > div.container-fluid
0.243
0.000

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: 160 ms 91.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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.

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 Evaluation1.5 s
Style & Layout363 ms
Other250 ms
Script Parsing & Compilation241 ms
Rendering83 ms
Parse HTML & CSS56 ms
Garbage Collection32 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 18.7 KiB
URLTransfer SizeEst Savings
badge.dimensions.ai/badge.js80.8 KiB18.7 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
JMIR Publications div.corporate__logo > a > div > img.logo-img
asset.jmir.pub/resources/images/logos/JMIR_logo.png
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
Article Thumbnail div.card-header > div.card-img > div > img.lazyLoad
asset.jmir.pub/placeholder.svg
ORCID Member li > p > a > img
asset.jmir.pub/resources/images/partners/ORCID.jpg
PubMed li > p > a > img
/hubfs/19668141/00 Marketing/Logos/External logos for jou...
Committee on Publication Ethics li > p > a > img
asset.jmir.pub/resources/images/partners/cope.jpg
Open Access ul > li > p > img
asset.jmir.pub/resources/images/partners/open-access.jpg
Crossref Member li > p > a > img
asset.jmir.pub/resources/images/partners/crossref.jpg
TrendMD Member li > p > a > img
asset.jmir.pub/resources/images/partners/trend-MD.jpg
Open Access Scholarly Publishers Association li > p > a > img
asset.jmir.pub/resources/images/partners/oaspa.jpg

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

Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 10 user timings
Avoid long main-thread tasks 7 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 120 ms
Server Backend Latencies 210 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 180 ms
INP breakdown
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.

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
our 5 partners div.enzuzo-notification-text > div.enzuzo-notification-desc > span > a#ez-tcf-notification-message-vendors-link
Privacy Policy ↗ div.enzuzo-notification-text > div.enzuzo-notification-desc > span > a#notificationPolicyLink
Manage preferences div.ez-consent > div#ez-cookie-notification > div.enzuzo-notification-buttons > a#notificationManagerLink

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > p > a > img.image_resized li > p > a > img.image_resized
ul > li > p > img ul > li > p > img

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Peer Review Me div.peer-review-cards > div.peer-review-card > div.peer-review-footer > a.btn
Get Alerts div.container > div.row > div.email-subscribtion-button > a
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
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.
Select elements have associated label elements.
`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
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 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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` 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
`<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
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.
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.
81

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
AttributionReporting
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 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
67

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.

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > p > a > img.image_resized li > p > a > img.image_resized
ul > li > p > img ul > li > p > img

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
Crossref Member ul > li > p > a
Committee on Publication Ethics ul > li > p > a
Open Access Scholarly Publishers Association ul > li > p > a
TrendMD Member ul > li > p > a
PubMed ul > li > p > a
PubMed Central ul > li > p > a
  section.partners-wrapper > ul > li > 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
Page has successful HTTP status code
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback