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

65

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.

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.

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: Member Management Software Manage Your Organization All in One Place Simplify,…
path: 1,HTML,1,BODY,3,DIV,3,DIV,0,DIV,0,DIV,0,MAIN,0,ARTICLE,0,DIV,1,DIV
selector: main#primary > article#post-422 > div.entry-content > div#homepage-hero
snippet: <div id="homepage-hero" class="block-wrapper">

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 Size
www.wildapricot.com/wp-content/themes/wildapricot/assets/css/style.css19.3 KiB
www.wildapricot.com/wp-content/themes/wildapricot/blocks/icon-list/style.css614 B
www.wildapricot.com/wp-content/themes/wildapricot/blocks/blog-posts/style.css2.5 KiB
/wp-content/themes/wildapricot/blocks/testimonial-block/s...1.9 KiB
/wp-content/themes/wildapricot/blocks/flexible-cards/card...689 B
/wp-content/themes/wildapricot/blocks/flexible-cards/styl...1.8 KiB

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

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

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.

Estimated savings: 895 ms
URLTime Spent
wildapricot.org/503 ms
wildapricot.com/190 ms
wildapricot.com/202 ms
www.wildapricot.com/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.

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.

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 171.5 KiB
URLTransfer SizeEst Savings
/WebUI/built9.14.0-fb981fc/scripts/shared/ui/shared-ui-co...230.5 KiB136.5 KiB
/BuiltTheme/transparent_vertical.v1.0/current/40761a09/Sc...139.0 KiB32.1 KiB
live-sf.wildapricot.org/WebUI/built9.14.0-fb981fc/General.js4.9 KiB2.9 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: 0.0 ms 12.7 KiB
URLTransfer SizeEst Savings
www.wildapricot.com/wp-content/themes/wildapricot/assets/css/style.css19.0 KiB12.7 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
www.wildapricot.com/wp-content/uploads/2025/05/Member-Database-2.svg455.5 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.9 KiB
/WebUI/built9.14.0-fb981fc/scripts/shared/ui/shared-ui-co...230.9 KiB
/WebUI/built9.14.0-fb981fc/scripts/public/react/index-84b...196.6 KiB
/BuiltTheme/transparent_vertical.v1.0/current/40761a09/Sc...139.6 KiB
/BuiltTheme/transparent_vertical.v1.0/current/40761a09/fo...96.4 KiB
/WebUI/built9.14.0-fb981fc/css/shared/ui/shared-ui-compil...92.6 KiB
/BuiltTheme/transparent_vertical.v1.0/current/40761a09/St...77.2 KiB
/WebUI/built9.14.0-fb981fc/scripts/shared/bonapagetop/bon...64.9 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
div.wildapricot-testimonial-block > div.testimonial-design2-container > div.testimonial-design2-right > img.testimonial-design2-tree div.wildapricot-testimonial-block > div.testimonial-design2-container > div.testimonial-design2-right > img.testimonial-design2-tree
/wp-content/themes/wildapricot/assets/images/backgrounds/...
div.wildapricot-testimonial-block > div.testimonial-design2-container > div.testimonial-design2-left > img.testimonial-design2-swirl div.wildapricot-testimonial-block > div.testimonial-design2-container > div.testimonial-design2-left > img.testimonial-design2-swirl
/wp-content/themes/wildapricot/assets/images/backgrounds/...
div.entry-content > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-8480 div.entry-content > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-8480
www.wildapricot.com/wp-content/uploads/2025/05/Member-Database-2.svg
div.entry-content > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-8481 div.entry-content > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-8481
www.wildapricot.com/wp-content/uploads/2025/05/Event-Management.svg
div.entry-content > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-8482 div.entry-content > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-8482
www.wildapricot.com/wp-content/uploads/2025/05/Artboard-1-1.svg
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-7019 div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-7019
www.wildapricot.com/wp-content/uploads/2025/05/Group-1436-1.svg
friendly apricot wearing a headset div.wp-block-image > figure.aligncenter > a > img.wp-image-7994
www.wildapricot.com/wp-content/uploads/2025/05/apricot-avatar-animated.svg
steep green mountain with a red flag at the top div.wp-block-image > figure.aligncenter > a > img.wp-image-7991
www.wildapricot.com/wp-content/uploads/2025/05/mountains-flag-animated.svg
waving hand div.wp-block-image > figure.aligncenter > a > img.wp-image-6970
www.wildapricot.com/wp-content/uploads/2024/09/waving-hand-svg.svg
div.col-xl-3 > div.newsletter-box > div.newsletter-mascot > img.img-fluid div.col-xl-3 > div.newsletter-box > div.newsletter-mascot > img.img-fluid
/wp-content/themes/wildapricot/assets/images/footer/sunny...

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

●Use efficient cache lifetimes
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Network dependency tree
●Optimize viewport for mobile
●Minify CSS
●Reduce unused JavaScript
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 160 ms
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 110 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
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
●`[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
●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 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
○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.
○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.
62

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
wildapricot.com/Allowed

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.
/WebUI/built9.14.0-fb981fc/scripts/shared/bonapagetop/bon... line 2, col 96240
●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
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