Skip to content
https://jstor.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.

33

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.

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:35.647 source:map[type:text value:[unattributed]]]]

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
Middle East Map ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/Midd...313.0 KiB305.1 KiB
Detail of 17th-century nautical chart depicting the English Channel and decorat… ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...292.1 KiB284.4 KiB
TRIANGULAR DYNAMICS: US RESPONSE TO CHINA’S ASSERTIVENESS IN THE MIDDLE EAST ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/Mont...235.3 KiB229.5 KiB
Cover and inside page from alternative publication Overthrow ul > li > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/new-avenues/alternativ...196.8 KiB180.6 KiB
Detail of a black and white photograph of Maya children lined up by a blackboard ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...144.1 KiB137.5 KiB
Golden figure of a scarab with bird’s wings ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...135.5 KiB129.4 KiB
US POLICY IN THE MIDDLE EAST: THIRD QUARTER 2025 REPORT CARD: A Quarterly Asses… ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/Katu...132.5 KiB126.2 KiB
Detail of a painting depicting the landscape of New Mexico with mountains in th… ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...118.0 KiB112.6 KiB
The U.S. Policy towards Post-Saddam Iraq: Implications for the Middle Eastern R… ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/Naqv...107.0 KiB101.7 KiB
Architectural details and art from the Alhambra palace ul > li > search-ui-pharos-image-card > img
www.jstor.org/assets/long-lived_20201006/images/new-avenues/work-with-images.jpg115.1 KiB98.9 KiB
Detail of a print depicting a woman’s face and decorative abstract patterns ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...92.9 KiB88.6 KiB
Do Campaign Speeches Predict Foreign Policy? An Operational Code and Leadership… ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/ZDAM...88.8 KiB83.5 KiB
Strained Ties: Saudi Arabia and the War in Yemen ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/LANT...87.6 KiB82.1 KiB
Metaphor, the Middle East, and the American Imagination ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/Fowl...85.5 KiB80.1 KiB
Vintage photograph of a woman looking through a picture frame ul > li > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/new-avenues/artstor-im...96.1 KiB79.9 KiB
KUWAIT. Gulf War Aftermath. KUWAIT. 1991. The Persian Gulf. ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/McCu...84.5 KiB78.3 KiB
search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img
/assets/long-lived_20201006/images/browse-by-collection-c...75.9 KiB73.1 KiB
search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img
/assets/long-lived_20201006/images/browse-by-collection-c...72.8 KiB69.2 KiB
Floundering Stability: US Foreign Policy in Egypt ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/Kame...58.3 KiB52.8 KiB
search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img
/assets/long-lived_20201006/images/browse-by-collection-c...42.3 KiB40.8 KiB
US Military Bases in the Gulf: Better Upset than Sorry? ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/Kuwa...42.3 KiB39.3 KiB
search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img
/assets/long-lived_20201006/images/browse-by-collection-c...38.9 KiB37.3 KiB
Calming the Red Sea’s Turbulent Waters ul.glide__slides > li.glide__slide > search-ui-pharos-image-card > img
/assets/long-lived_20201006/images/thematic-carousel/Grou...32.6 KiB30.3 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
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.

URLTransfer SizeDuration
cdn.cookielaw.org/scripttemplates/otSDKStub.js9.1 KiB817 ms

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.

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

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: 752 ms
URLTime Spent
jstor.org/752 ms
www.jstor.org/0.0 ms

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

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
Unattributable1.1 s169 ms0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-N6GDC22624 ms460 ms111 ms
www.jstor.org/537 ms10 ms4.5 ms
/mfe-copper-roof/header/0becc8f3/react-dom_19_2_4.57e05c9...469 ms336 ms13 ms
cdn.cookielaw.org/scripttemplates/202505.1.0/otBannerSdk.js395 ms257 ms37 ms
/mfe-copper-roof/footer/68fef919/src_initComponents_ts.d1...197 ms182 ms0.2 ms
www.jstor.org/assets/search-ui_20250818T182451/build/2443.js191 ms153 ms23 ms
/mfe-copper-roof/query-builder/0b448bab/src_initComponent...179 ms149 ms0.5 ms
www.jstor.org/assets/global_20251201T215504/build/global/js/global.min.js177 ms117 ms51 ms
/assets/long-lived_20201006/js/scoped-custom-element-regi...172 ms143 ms1.0 ms
/mfe-copper-roof/header/0becc8f3/ithaka-pharos_14_22_2.c5...150 ms137 ms11 ms
/mfe-copper-roof/query-builder/0b448bab/src_bootstrap_js....147 ms129 ms0.4 ms
/mfe-copper-roof/provider-designation-statement/f3b07e9a/...112 ms106 ms2.4 ms
/assets/search-ui_20250818T182451/build/search-ui/js/home...112 ms39 ms4.2 ms
www.jstor.org/mfe-copper-roof/header/0becc8f3/remoteEntry.js108 ms97 ms3.7 ms
/mfe-copper-roof/access-workflow/8e13cdaf/vueuse-core_14_...107 ms81 ms18 ms
/mfe-copper-roof/footer/68fef919/ithaka-sentry-monitoring...100 ms63 ms35 ms
/mfe-copper-roof/heads-up-display/663eec3c/graphql_16_12_...89 ms75 ms13 ms
/mfe-copper-roof/access-workflow/8e13cdaf/css-loader_7_1_...87 ms74 ms9.7 ms
/mfe-copper-roof/access-workflow/8e13cdaf/src_initCompone...85 ms82 ms0.4 ms
/mfe-copper-roof/prompt/6b866a17/css-loader_7_1_2.9a74589...75 ms61 ms11 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js72 ms62 ms3.0 ms
/mfe-copper-roof/prompt/6b866a17/src_initComponents_ts.74...72 ms71 ms0.2 ms
/mfe-copper-roof/query-builder/0b448bab/vue_3_5_13.f4a518...67 ms52 ms15 ms
/mfe-copper-roof/header/0becc8f3/ithaka-pharos_14_22_2.5f...58 ms29 ms1.4 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 Evaluation3.5 s
Other1.2 s
Script Parsing & Compilation663 ms
Style & Layout539 ms
Parse HTML & CSS137 ms
Rendering120 ms
Garbage Collection88 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 37.8 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
search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img search-ui-pharos-layout.negate-nav-bottom-margin > section.collection-showcase--browse > div.collection-showcase__images > img
/assets/long-lived_20201006/images/browse-by-collection-c...
Detail of a painting depicting the landscape of New Mexico with mountains in th… ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...
Detail of a print depicting a woman’s face and decorative abstract patterns ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...
Golden figure of a scarab with bird’s wings ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...
Detail of 17th-century nautical chart depicting the English Channel and decorat… ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...
Detail of a black and white photograph of Maya children lined up by a blackboard ul.glide__slides > li.glide__slide > picture > img
/assets/long-lived_20201006/images/hero/jstor_homepageher...
Google icon div.alternate-access-buttons > mfe-access-workflow-pharos-button > span.oauth-button-content > img
www.jstor.org/mfe-copper-roof/access-workflow/8e13cdaf/c85adc4a978057a34e43.svg
Microsoft icon div.alternate-access-buttons > mfe-access-workflow-pharos-button > span.oauth-button-content > img
www.jstor.org/mfe-copper-roof/access-workflow/8e13cdaf/b03ab40117b01c4a477c.svg
Search icon div.alternate-access-buttons > mfe-access-workflow-pharos-button > span.authentication-button-content > img
www.jstor.org/mfe-copper-roof/access-workflow/8e13cdaf/9e30a1c3e93948d22d3c.svg
Linked Institutions Icon div.mfe-provider-designation-statement > div.mfe-provider-designation-statement__provider-designation-statement > span.mfe-provider-designation-statement__has-uuid > img.mfe-provider-designation-statement-icon
/mfe-copper-roof/provider-designation-statement/f3b07e9a/...

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 76 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 30 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 210 ms
●Avoid large layout shifts 6 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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 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
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

●Uses HTTPS
●Avoids deprecated APIs
●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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.

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
a#link-element a#link-element

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