Skip to content
https://idealist.org

Lighthouse Desktop

· 0 checks — Desktop 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.

87

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
cdn.mxpnl.com/libs/mixpanel-2-latest.min.js600.0 s31.7 KiB
/usage.gif?token=fa14a315de3b412494c88f1d3a5803a3&correla...0.0 ms273 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:62.658 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
Join Idealist to Volunteer or Find a Nonprofit Job Continue with Google Continu… div.sc-tue1gi-0 > div > div > div.sc-yg6q43-0
/images/no_metadata/output=format:webp/resize=w:1280,fit:...134.0 KiB23.0 KiB
Idealist logo section.sc-7ycbp3-9 > a.sc-7ycbp3-10 > div.sc-d0smry-0 > img.sc-d0smry-1
www.idealist.org/static/images/logos/logo-mark.webp8.0 KiB7.5 KiB

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: Join Idealist to Volunteer or Find a Nonprofit Job Continue with Google Continu…
path: 1,HTML,1,BODY,2,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV
selector: div.sc-tue1gi-0 > div > div > div.sc-yg6q43-0
snippet: <div class="sc-yg6q43-0 hpmnur">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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: 413 ms
URLTime Spent
idealist.org/203 ms
www.idealist.org/210 ms
www.idealist.org/en0.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.

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

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 210 ms 463.9 KiB
URLTransfer SizeEst Savings
/assets/horizon-6c248c9b5705554fdde47a81c30970b644e330c0/...472.7 KiB275.5 KiB
www.googletagmanager.com/gtag/js?id=G-3R33VTSGJC&cx=c&gtm=4e64k0171.8 KiB66.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-TMDWTM2153.4 KiB63.4 KiB
www.googletagmanager.com/gtag/destination?id=AW-750399708&cx=c&gtm=4e64k0137.3 KiB58.3 KiB

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
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 13.5 KiB
URLTransfer SizeEst Savings
.doNQKz { background: currentcolor; display: inline-flex; flex-shrink: 0; pointer-events: none; … } …14.1 KiB13.5 KiB

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
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,646 KiB
●User Timing marks and measures 10 user timings
●JavaScript execution time 1.0 s
●Minimizes main-thread work 1.6 s
●Avoid long main-thread tasks 6 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 70 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 200 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
76

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.sc-5ujv3e-0 > div.sc-d43i1s-0 > input#page-header-desktop-search-location div > div.sc-5ujv3e-0 > div.sc-d43i1s-0 > input#page-header-desktop-search-location

These are opportunities to improve the usage of ARIA in your application which 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
Jobs Internships Volunteer Opportunities Events Organizations div.sc-aqbc4c-1 > div.sc-4bnqsq-0 > div.sc-6c47g9-0 > select.sc-08v8hu-0
English footer.sc-7ycbp3-0 > div.sc-7ycbp3-13 > div.sc-mcnu3u-0 > div.sc-a7mdfo-1
Volunteer in Seattle footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in San Jose footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Boston footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in San Francisco footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Denver footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Austin footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Virginia Beach footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Chicago footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Madison footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Miami footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Nashville footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Long Beach footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Minneapolis footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in New Orleans footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in New York City footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Phoenix footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in Washington DC footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3
Volunteer in San Diego footer.sc-7ycbp3-0 > div.sc-46k99j-0 > div.sc-46k99j-2 > a.sc-46k99j-3

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
VolunteerMatch div.sc-6c47g9-0 > div.sc-bbhosc-0 > p > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
VOLUNTEER RESOURCES div.sc-6c47g9-0 > div.sc-6c47g9-0 > div.sc-6c47g9-0 > h5.sc-3d9sk2-0
Bristol Hospice Austin a.sc-gaqjo1-0 > div.sc-6c47g9-0 > div.sc-6c47g9-0 > h5.sc-3d9sk2-0
Innocence Project a.sc-gaqjo1-0 > div.sc-6c47g9-0 > div.sc-6c47g9-0 > h5.sc-3d9sk2-0
Volunteer div.sc-7ycbp3-2 > div.sc-7ycbp3-3 > section.sc-7ycbp3-4 > h4.sc-7ycbp3-5

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Default Radius 5 miles 10 miles 15 miles 25 miles 60 miles 100 miles Entire Sta… form#layout-desktop-search-bar > div.sc-aqbc4c-1 > div.sc-e8efb5-0 > select.sc-e8efb5-1

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0
nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0 nav > div.sc-s4lzb9-0 > div.sc-s4lzb9-1 > button.sc-4w4j31-0

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-*]` 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 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 use only permitted ARIA attributes
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●No form fields have multiple labels
●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-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○`<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
○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
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.idealist.org/en/days/get-involvedLearn More

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Send Feedback