Skip to content
http://www.lindaschlapfer.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

30

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 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:20.586 source:map[column:27235 line:3 type:source-location url:https://assets.squarespace.com/universal/scripts-compressed/common-17d77f470f291cd9-min.en-US.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:46.431 source:map[column:19 line:9 type:source-location url:reserveSpaceForHeader.js urlProvider:network]] map[reflowTime:77.956 source:map[type:text value:[unattributed]]] map[reflowTime:2.757 source:map[column:67473 line:1 type:source-location url:https://static1.squarespace.com/static/vta/5c5a519771c10ba3470d8101/scripts/site-bundle.9ad4428074df7afb73619ace1a54f3c9.js urlProvider:network]] map[reflowTime:0.117 source:map[column:72109 line:1 type:source-location url:https://static1.squarespace.com/static/vta/5c5a519771c10ba3470d8101/scripts/site-bundle.9ad4428074df7afb73619ace1a54f3c9.js urlProvider:network]] map[reflowTime:1.478 source:map[column:83688 line:1 type:source-location url:https://static1.squarespace.com/static/vta/5c5a519771c10ba3470d8101/scripts/site-bundle.9ad4428074df7afb73619ace1a54f3c9.js urlProvider:network]] map[reflowTime:2.725 source:map[column:78799 line:1 type:source-location url:https://static1.squarespace.com/static/vta/5c5a519771c10ba3470d8101/scripts/site-bundle.9ad4428074df7afb73619ace1a54f3c9.js urlProvider:network]] map[reflowTime:20.058 source:map[column:81970 line:1 type:source-location url:https://static1.squarespace.com/static/vta/5c5a519771c10ba3470d8101/scripts/site-bundle.9ad4428074df7afb73619ace1a54f3c9.js urlProvider:network]] map[reflowTime:9.432 source:map[column:56899 line:64 type:source-location url:https://assets.squarespace.com/universal/scripts-compressed/common-17d77f470f291cd9-min.en-US.js urlProvider:network]] map[reflowTime:0.656 source:map[column:58640 line:64 type:source-location url:https://assets.squarespace.com/universal/scripts-compressed/common-17d77f470f291cd9-min.en-US.js urlProvider:network]] map[reflowTime:0.312 source:map[column:58675 line:64 type:source-location url:https://assets.squarespace.com/universal/scripts-compressed/common-17d77f470f291cd9-min.en-US.js urlProvider:network]] map[reflowTime:5.298 source:map[column:121861 line:64 type:source-location url:https://assets.squarespace.com/universal/scripts-compressed/common-17d77f470f291cd9-min.en-US.js urlProvider:network]] map[reflowTime:4.321 source:map[column:16424 line:6 type:source-location url:https://assets.squarespace.com/universal/scripts-compressed/common-17d77f470f291cd9-min.en-US.js urlProvider:network]] map[reflowTime:0.567 source:map[column:117751 line:64 type:source-location url:https://assets.squarespace.com/universal/scripts-compressed/common-17d77f470f291cd9-min.en-US.js urlProvider:network]] map[reflowTime:0.628 source:map[column:25279 line:0 type:source-location url:https://definitions.sqspcdn.com/website-component-definition/static-assets/website.components.imageFluid/d529e0f6-8c71-4eec-89f2-7c230ec5a547_943/website.components.imageFluid.visitor.js urlProvider:network]] map[reflowTime:2.022 source:map[column:26156 line:0 type:source-location url:https://definitions.sqspcdn.com/website-component-definition/static-assets/website.components.imageFluid/d529e0f6-8c71-4eec-89f2-7c230ec5a547_943/website.components.imageFluid.visitor.js urlProvider:network]] map[reflowTime:2.44 source:map[column:22845 line:0 type:source-location url:https://definitions.sqspcdn.com/website-component-definition/static-assets/website.components.imageFluid/d529e0f6-8c71-4eec-89f2-7c230ec5a547_943/website.components.imageFluid.visitor.js urlProvider:network]]]

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
Illustration of a bright yellow sun with wavy rays extending outward. div.fluid-image-container > div.js-content-mode-element-wrapper > div.js-content-mode-element > img
/content/v1/5f2af28e914d6a1c9f401002/7d89ee43-1bef-45a0-9...158.8 KiB148.5 KiB
Marriage & Family Therapist div.header-title > div.header-title-logo > a > img
/content/v1/5f2af28e914d6a1c9f401002/1f65fe57-6f89-428e-a...8.2 KiB8.0 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-2-IMG
nodeLabel: A beige background featuring a black stylized logo with the letters 'LS' and th…
path: 1,HTML,1,BODY,0,DIV,2,MAIN,0,ARTICLE,0,SECTION,0,SECTION,1,DIV,0,DIV,0,DIV,1,DIV,5,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.fluid-image-container > div.js-content-mode-element-wrapper > div.js-content-mode-element > img
snippet: <img data-stretch="false" data-src="https://images.squarespace-cdn.com/content/v1/5f2af28e914d6a1c9f401002/9d8…" data-image="https://images.squarespace-cdn.com/content/v1/5f2af28e914d6a1c9f401002/9d8…" data-image-dimensions="407x407" data-image-focal-point="0.5,0.5" data-sqsp-image-block-image="" alt="A beige background featuring a black stylized logo with the letters 'LS' a…" data-licensed-asset-preview="false" data-load="false" elementtiming="system-image-block" src="https://images.squarespace-cdn.com/content/v1/5f2af28e914d6a1c9f401002/9d8…" …>

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.

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.

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: 630 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 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: 600 ms 88.0 KiB
URLTransfer SizeEst Savings
/static/versioned-site-css/5f2af28e914d6a1c9f401002/181/5...109.9 KiB88.0 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

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 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.8 s
Other2.0 s
Style & Layout960 ms
Script Parsing & Compilation655 ms
Parse HTML & CSS229 ms
Rendering109 ms
Garbage Collection52 ms

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
Marriage &amp; Family Therapist div.header-title > div.header-title-logo > a > img
/content/v1/5f2af28e914d6a1c9f401002/1f65fe57-6f89-428e-a...

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

●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,587 KiB
●Avoid long main-thread tasks 15 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 50 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
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
91

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.

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
Are you caught in the same arguments without resolution? div.sqs-text-block-container > div.sqs-html-content > h2 > span.sqsrte-text-color--black
Do you find yourselves avoiding each other? div.sqs-text-block-container > div.sqs-html-content > p > span.sqsrte-text-color--black
Has your communication turned mostly negative or critical? div.sqs-text-block-container > div.sqs-html-content > p > span.sqsrte-text-color--black
Every relationship faces challenges, but couples therapy can help you navigate … div.sqs-text-block-container > div.sqs-html-content > p > span.sqsrte-text-color--black
Couples Therapy can help to: li.accordion-item > h4.accordion-item__title-wrapper > button#button-yui_3_17_2_1_1745712717462_4953-1 > span.accordion-item__title
Issues that I can help with: li.accordion-item > h4.accordion-item__title-wrapper > button#button-yui_3_17_2_1_1745712717462_4953-2 > span.accordion-item__title
Couples therapy is a supportive, collaborative process. Most sessions will be t… div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > p
In our first session, we’ll talk about what brings you here and what you’re hop… div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > p
Every couple is unique, and I tailor my approach to fit your needs, drawing fro… div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > p
Sessions are 60 minutes and typically held once a week — either in person or ov… div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > p
Understanding each other’s vulnerabilities div.sqs-html-content > ul > li > p
Communicating openly and without defensiveness div.sqs-html-content > ul > li > p
Reconnecting with each other’s values and dreams div.sqs-html-content > ul > li > p
Moving past difficult impasses div.sqs-html-content > ul > li > p
Managing emotions with greater awareness div.sqs-html-content > ul > li > p
Creating lasting change through shared goals div.sqs-html-content > ul > li > p
In our sessions, we work together to explore challenges, build healthier patter… div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > h4
SCHEDULE A 15 MINUTE CONSULTATION div#block-680f7fed05d981ff71969907 > div#yui_3_17_2_1_1790974449724_69 > div#yui_3_17_2_1_1790974449724_68 > a.sqs-block-button-element--large

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
In our sessions, we work together to explore challenges, build healthier patter… div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sqs-text-block-container > div.sqs-html-content > h4 > a

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.

○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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
○`[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
○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.
○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>`.
○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.
81

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
www.lindaschlapfer.com/Allowed
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Redirects HTTP traffic to HTTPS
●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
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