Skip to content
Audit Complete

Results for https://nypl.org

Visit site
United States United States · Santa Clara Completed: Apr 21, 2026 22:34 UTC
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)
C77

Site Health

Score: 77 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

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.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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 · 669 peers
You 77
·
Avg 72
At average
0 50 100
Better than 88% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Apple · 822 peers
You 77
·
Avg 73
At average
0 50 100
Better than 85% 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

No Content-Security-Policy header found

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

Security › Content Security Policy
3

2 button(s) with no accessible text

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

Accessibility › Link & Button Quality
4

Soft 404: server returns HTTP 200 for non-existent pages

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

Accessibility › 404 Error Page
5

16 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

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%2Fnypl.org)](https://beavercheck.com/results/f5196f64-0231-4cd0-b60f-6b0d8d612d33)
<a href="https://beavercheck.com/results/f5196f64-0231-4cd0-b60f-6b0d8d612d33"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnypl.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fnypl.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. The 1 performance issue below shapes how fast users perceive your page. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
1 performance issue — Akamai's research found 53% of mobile users abandon pages over 3s.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

3 warning

3 barrier(s) likely increasing bounce by ~6%.

Trust (2)

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 (1)

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, …)

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

Return on Investment

$600 investment → $0.17/month returns + USD 7,500 risk avoided

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

Investment

$600

6h · 5 findings

Monthly returns

$0.17 /mo

~$2.00 / year

  • Bandwidth savings $0.17

Regulatory risk avoided

USD 7,500

if kept compliant

  • CCPA/CPRA USD 7,500

$100 — 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

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 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

$625 / month at risk

~$7,502 / year if left unfixed

Compliance Risk

$7,500

CCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 1 advertising/retargeting trackers detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+1 more

Bandwidth Waste

$0.17 /mo

2080.8 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~208 KB per page load
    Saves $0.17/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

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.

0
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
45
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
45
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.

0 ms

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

0 ms

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

0 ms

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

0.000

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

0 ms

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

0 ms

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

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
js.hcaptcha.com/1/api.js300.0 s86.0 KiB

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

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.

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.

Diagnostics

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.

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.

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.

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

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

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
Forced reflow
Improve image delivery
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Avoids enormous network payloads Total size was 677 KiB
JavaScript execution time 0.3 s
Minimizes main-thread work 0.6 s
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 10 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 10 ms
INP breakdown
LCP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
45

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

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > iframe#main-iframe body > iframe#main-iframe

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
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 use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
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
`[role]` values are valid
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
Background and foreground colors have a sufficient contrast ratio
`<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
Heading elements appear in a sequentially-descending order
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
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.
73

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Fledge
js.hcaptcha.com/1/api.js line 3, col 47111
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
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
Page has valid source maps
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
45

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 are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
head > meta

To appear in search results, crawlers need access to your app.

Content Best Practices

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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.

Structured data is valid
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Image elements have `[alt]` attributes
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

68
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
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.
100
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.09 s

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

1.25 s

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

688 ms

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

0.000

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

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

5.00 s

Detailed Report

Audit breakdown by category with detailed findings.

68

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

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: REGISTER TODAY On Now: NYPL's World Literature & Arts Festival Celebrate the c…
path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,0,MAIN,0,DIV,0,DIV
selector: div.scout__homepage > main#mainContent > div#content-header > div.css-1kk6jc9
snippet: <div class="css-1kk6jc9">

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.

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
Large amount of books sprawled across a red table. div#card-image-d0bc1d2d-c8e0-4e21-955b-403875565c86 > a#card-image-link-d0bc1d2d-c8e0-4e21-955b-403875565c86 > div#nextjsImage-card-image-84bcafa5-af9e-4a64-b266-719c559ec44a > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...161.8 KiB151.1 KiB
Lion statue in front of the Stephen A. Schwarzman Building with two red banners… div#card-image-c2e2c0b4-c8de-49ae-9f60-30407217c662 > a#card-image-link-c2e2c0b4-c8de-49ae-9f60-30407217c662 > div#nextjsImage-card-image-c72959ec-5280-48af-86ce-2c092a046c39 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...109.6 KiB98.9 KiB
Librarian in a black dress reads a colorful picture book to a group of children… div#card-image-257e6845-aafd-4888-8338-bd20438e51e9 > a#card-image-link-257e6845-aafd-4888-8338-bd20438e51e9 > div#nextjsImage-card-image-a134c858-8cf7-4a46-8f98-e35b741b7a8d > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...87.7 KiB77.0 KiB
4 side-by-side headshots: Edwin Santana, Dr. Shana Russell, Tamara Santibañez, … div.css-ys3583 > a#event-card-image-link-0e711f69-5e47-44f7-98e4-6ed166b099fe > div#nextjsImage-event-image-0e711f69-5e47-44f7-98e4-6ed166b099fe-68764dbc-1483-4173-b0bc-041d459cda01 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...67.7 KiB66.3 KiB
Author headshots on either side of Umrigar's book, "Missing Sam." div.css-ys3583 > a#event-card-image-link-featured-dee218d6-1ec2-4edd-8520-8a412af1d4b1 > div#nextjsImage-event-image-featured-dee218d6-1ec2-4edd-8520-8a412af1d4b1-df723cbb-51dc-4781-bf35-ef753638ca3c > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...91.2 KiB65.8 KiB
Headshots of Bethany Crystal, Saadiq Rodgers-King, and Peta-Gay Clarke alongsid… div.css-ys3583 > a#event-card-image-link-ae5a83b8-a5e3-43e7-ac46-c6a3227eebb4 > div#nextjsImage-event-image-ae5a83b8-a5e3-43e7-ac46-c6a3227eebb4-276eca99-6478-4c6e-9c52-44b7123f9598 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...62.2 KiB60.9 KiB
A man and a young girl read from a book in braille while sitting at a colorful … div#card-image-2d5a16e8-04cc-4477-b322-25367b2d8e7e > a#card-image-link-2d5a16e8-04cc-4477-b322-25367b2d8e7e > div#nextjsImage-card-image-4727dc8c-1140-4ce1-8c8b-16f396e53b84 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...69.0 KiB59.2 KiB
2 side-by-side headshots: Lloyd Blankfein, Hortense le Gentil div.css-ys3583 > a#event-card-image-link-fe513ce0-e808-4d00-95e3-088bc9e91ac1 > div#nextjsImage-event-image-fe513ce0-e808-4d00-95e3-088bc9e91ac1-5a2b9b13-e969-43c5-94d5-9dd45831e5f0 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...58.3 KiB57.1 KiB
Stack of books on a wooden desk, with bookshelves in the background. div#card-image-340f7a72-51f0-4f27-b740-11c535f337d7 > a#card-image-link-340f7a72-51f0-4f27-b740-11c535f337d7 > div#nextjsImage-card-image-9f684063-4524-47b2-ad66-391fcf663520 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...63.2 KiB54.2 KiB
Woman holding iPad in library setting. div#card-image-9b700650-d2f3-47d8-a2ce-35ef29ab5fcc > a#card-image-link-9b700650-d2f3-47d8-a2ce-35ef29ab5fcc > div#nextjsImage-card-image-05d4e2ed-034e-4236-a894-0dea2079ea6f > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...61.9 KiB53.0 KiB
A woman with glasses and a scarf behind a librarian's desk hands a book to a pa… div#card-image-af552fd5-be7f-4b69-93a6-6946b918a54e > a#card-image-link-af552fd5-be7f-4b69-93a6-6946b918a54e > div#nextjsImage-card-image-450862c7-9099-4ed3-adb5-4d67e7a768e6 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...57.5 KiB49.3 KiB
In the foreground a stack of old books partially obscures three people research… div#card-image-9d8525ca-1d2e-404a-b524-b7f39cea9bf2 > a#card-image-link-9d8525ca-1d2e-404a-b524-b7f39cea9bf2 > div#nextjsImage-card-image-8054cb29-7544-4a4c-9d56-26c1b9b49184 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...54.7 KiB46.9 KiB
Two kids at a desk with notebooks open and pens in hand. div#card-image-67214b72-ed49-4011-8a69-ddecc8611e2f > a#card-image-link-67214b72-ed49-4011-8a69-ddecc8611e2f > div#nextjsImage-card-image-4361a84b-b3ed-40e2-9072-526cf2c21e65 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...54.5 KiB46.7 KiB
Colorful graphic featuring the word Welcome in many languages, including Englis… div#card-image-e4e245e8-1172-4a1f-96c7-e89b8be756ac > a#card-image-link-e4e245e8-1172-4a1f-96c7-e89b8be756ac > div#nextjsImage-card-image-bde3b5bb-a710-4f20-8367-df6569a478d2 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...53.4 KiB45.7 KiB
Messy pile of NYPL cards with one standing up and in focus in the middle of the… div#card-image-1c1ee9c8-8d91-42b4-b596-249b294c4745 > a#card-image-link-1c1ee9c8-8d91-42b4-b596-249b294c4745 > div#nextjsImage-card-image-7f6785ad-20ac-44d2-b643-9acae9d0dd9c > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...48.3 KiB41.4 KiB
White text reads "Get Lit!" next to the cover of the book "Lake Effect." div#card-image-28f4c815-e5be-41bf-bfeb-2249823995cb > a#card-image-link-28f4c815-e5be-41bf-bfeb-2249823995cb > div#nextjsImage-card-image-3473f0d4-1336-469c-a148-64d7eba838c1 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...39.9 KiB34.2 KiB
Schomburg Centennial '100' logo in red, green, and purple on a black background. div#card-image-9ab2eaa2-866d-42f6-ad35-ffc07058e842 > a#card-image-link-9ab2eaa2-866d-42f6-ad35-ffc07058e842 > div#nextjsImage-card-image-2b037ca0-fa65-4f78-bc39-086759840a14 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...30.6 KiB26.3 KiB
Teal text-based graphic reads: National Poetry Month, The New York Public Libra… div#card-image-49fb4a50-c79a-4daf-9c0e-c12a7e23b10e > a#card-image-link-49fb4a50-c79a-4daf-9c0e-c12a7e23b10e > div#nextjsImage-card-image-aaff1550-a208-4b5b-8cdb-780af93393bb > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...21.8 KiB18.7 KiB
painting the cosmos a#staff-pick-card-link-7e0057e5-9e4c-4d6c-a167-073b9138950f > div.css-13k02e6 > div#nextjsImage-3234a3dc-7192-45cf-a121-c99a14a8fd1a > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...26.5 KiB17.1 KiB
Haven by Ani Katz div.css-ys3583 > a#slideshow-card-image-link-120a4b57-5c4f-45ee-8bf8-33a880606f90 > div#nextjsImage-slideshow-a0e3e293-88ec-4e7b-a6dc-09d63379ea96 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...32.7 KiB15.7 KiB
Dark blue rectangle with gold and white Treasures exhibition logo in the center. div#card-image-ab52dbbd-b47f-4988-a9a9-393afbf39def > a#card-image-link-ab52dbbd-b47f-4988-a9a9-393afbf39def > div#nextjsImage-card-image-c2eac3ca-8a4e-4d1d-9c7a-e68fae1d9528 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...17.8 KiB15.3 KiB
Metropolitans: New York Baseball, Class Struggle, and the People's Team div.css-ys3583 > a#slideshow-card-image-link-44d78fe7-4008-41e8-9a1d-1e2809e62aa5 > div#nextjsImage-slideshow-4b5aefec-07d2-43bd-b4f4-2d5502ccb326 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...31.9 KiB14.6 KiB
Teal text-based graphic reads: Arab American Heritage Month. div#card-image-65883ef2-2354-4365-92e4-13584c4c8cea > a#card-image-link-65883ef2-2354-4365-92e4-13584c4c8cea > div#nextjsImage-card-image-0405d297-1e6b-4ee3-9cf2-ab51e5ca565f > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...14.7 KiB12.6 KiB
the black hunger a#staff-pick-card-link-a63a4bf1-5f5c-44b6-9f7a-deb982807923 > div.css-13k02e6 > div#nextjsImage-7d3d690d-2bab-4e95-867c-133f24fd4df0 > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...29.2 KiB11.9 KiB
Days of Love and Rage: A Story of Ordinary People Forging a Revolution div.css-ys3583 > a#slideshow-card-image-link-c67f573b-8007-4536-b79f-fd06bf2b6abe > div#nextjsImage-slideshow-ef5e6951-1d89-4887-a8bd-18b8bc5fbfdc > img
/scout/_next/image?url=https%3A%2F%2Fdrupal.nypl.org%2Fsi...28.8 KiB11.7 KiB

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.0 s
URLTime Spent
nypl.org/229 ms
www.nypl.org/801 ms
www.nypl.org/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

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 Evaluation2.0 s
Other367 ms
Script Parsing & Compilation304 ms
Style & Layout197 ms
Rendering67 ms
Garbage Collection52 ms
Parse HTML & CSS31 ms

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 15.3 KiB
URLTransfer SizeEst Savings
www.nypl.org/scout/_next/static/css/324bf731318319c7.css15.5 KiB15.3 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

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
NYPL Main Building Facade div.css-125sda2 > div.css-0 > div.css-0 > img.css-1uyh2tv
cdn-d8.nypl.org/s3fs-public/2020-05/NYPL_MainFacadeRev2Cam2.png

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

Layout shift culprits
Document request latency
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 20 user timings
Avoid long main-thread tasks 13 long tasks found
Avoid non-composited animations 85 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 560 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 380 ms
INP breakdown
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
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
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[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 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.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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 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
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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
Unload event listeners are deprecated and will be removed.
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

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.

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
Redirects HTTP traffic to HTTPS
100

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.

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
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback