Skip to content
https://www.presentandperform.com

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.

75

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:2005.115 label:Time to first byte subpart:timeToFirstByte] map[duration:1244.806 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-LI
nodeLabel: Private Audition Coaching
path: 1,HTML,1,BODY,0,HEADER,0,DIV,1,DIV,0,NAV,0,UL,0,LI,1,UL,0,LI
selector: ul#menu-1-3877784c > li.menu-item > ul.sub-menu > li.menu-item
snippet: <li class="menu-item menu-item-type-post_type menu-item-object-page menu-item-6369">

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
value: No additional origins are good candidates for preconnecting

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
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.2 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.2 s

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 883 ms
URLTime Spent
presentandperform.com/983 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

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: 0.0 ms 256.0 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
Syracuse University div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/Syracuse-University.svg
NYFA div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/NYFA.svg
NYU div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/NYU.svg
UM div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/UM.png
UNCCH div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/UNCCH.svg
UUTAH div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/UUTAH.svg
Brokling College div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/Brokling-College.svg
The New School div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/The-New-School.png
Pace University div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/Pace-University.svg
UCONN div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/UCONN.svg
NTI div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/NTI-220x50.png
UF div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/UF.svg
Columbia div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/Columbia.svg
USC div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/USC.svg
NETC div.elementor-image-carousel > div.swiper-slide > figure.swiper-slide-inner > img.swiper-slide-image
presentandperform.com/wp-content/uploads/2025/09/NETC.svg

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Improve image delivery
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 60 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,388 KiB
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.5 s
●Avoid long main-thread tasks 1 long task found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 290 ms
●Server Backend Latencies 270 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
95

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.

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
Private Audition Coaching li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item
Conservatory Bound li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item
Workshops li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item
Video Acting Coach li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item
Monologue Services li.menu-item > ul.sub-menu > li.menu-item > a.elementor-sub-item
My Work nav.elementor-nav-menu--main > ul#menu-1-3877784c > li.menu-item > a.elementor-item
About nav.elementor-nav-menu--main > ul#menu-1-3877784c > li.menu-item > a.elementor-item
Resources nav.elementor-nav-menu--main > ul#menu-1-3877784c > li.menu-item > a.elementor-item
Work with Mariah div.e-con-inner > div.elementor-element > div.elementor-element > a.elementor-button
Services div.e-con-inner > div.elementor-element > div.elementor-element > a.elementor-button
Contact Mariah div.elementor-element > div.e-con-inner > div.elementor-element > a.elementor-button
Present & Perform logo div.e-con-inner > div.elementor-element > div.elementor-element > a
Contact div.e-con-inner > div.elementor-element > div.elementor-element > a.elementor-button
Services div.e-con-inner > div.elementor-element > div.elementor-element > a
Acting Coach nav.elementor-nav-menu--main > ul#menu-1-c4e9427 > li.menu-item > a.elementor-item
Conservatory Bound nav.elementor-nav-menu--main > ul#menu-1-c4e9427 > li.menu-item > a.elementor-item
Workshops nav.elementor-nav-menu--main > ul#menu-1-c4e9427 > li.menu-item > a.elementor-item
Video Acting Coach nav.elementor-nav-menu--main > ul#menu-1-c4e9427 > li.menu-item > a.elementor-item
Monologue Services nav.elementor-nav-menu--main > ul#menu-1-c4e9427 > li.menu-item > a.elementor-item
My Work nav.elementor-nav-menu--main > ul#menu-1-a61f736 > li.menu-item > a.elementor-item
Resources nav.elementor-nav-menu--main > ul#menu-1-a61f736 > li.menu-item > a.elementor-item

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-*]` 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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links 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
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○`<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
○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.
○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.
○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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
presentandperform.com/ line 736, col 6
ReferenceError: Swiper is not defined at https://presentandperform.com/:737:7 at NodeList.forEach (<anonymous>) at https://presentandperform.com/:728:15
presentandperform.com/ line 669, col 0
ReferenceError: wp is not defined at https://presentandperform.com/:670:1
●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 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
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Send Feedback