Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

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.

Request	Cache TTL	Transfer Size
/ESWChatBotMessageforwe1744836953484/webruntime/view/495b...	16224.0 s	383.4 KiB
/ESWChatBotMessageforwe1744836953484/assets/styles/salesf...	19.0 s	102.0 KiB
/signals/config/911375248086398?v=2.9.313&r=stable&domain...	1200.0 s	100.1 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	97.1 KiB
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	8907.0 s	77.1 KiB
/signals/config/171525100059628?v=2.9.313&r=stable&domain...	1200.0 s	46.5 KiB
js.hs-analytics.net/analytics/1778414400000/5016179.js	300.0 s	42.4 KiB
/ESWChatBotMessageforwe1744836953484/assets/js/bootstrap....	60.0 s	26.4 KiB
js.hscollectedforms.net/collectedforms.js	300.0 s	26.6 KiB
js.hs-banner.com/v2/5016179/banner.js	300.0 s	23.8 KiB
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	16224.0 s	29.9 KiB
www.redditstatic.com/ads/pixel.js?pixel_id=a2_ivqw7bocplbk	60.0 s	19.0 KiB
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	16224.0 s	27.8 KiB
tags.srv.stackadapt.com/events.js	5.0 s	7.7 KiB
static.hotjar.com/c/hotjar-2642245.js?sv=7	60.0 s	6.2 KiB
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	16223.0 s	8.7 KiB
storage.cloud.kargo.com/kds/kds-events-gtm.min.js	1800.0 s	6.2 KiB
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	16223.0 s	4.9 KiB
s2.adform.net/banners/scripts/st/trackpoint-async.js	604800.0 s	31.5 KiB
/ESWChatBotMessageforwe1744836953484/assets/styles/bootst...	60.0 s	3.0 KiB
/ESWChatBotMessageforwe1744836953484/assets/js/inert.min.js	60.0 s	2.9 KiB
/maps/api/js?key=AIzaSyDuAv3ndH3npJ9eQr90IE4P4bX8Gjrx4HU&...	1800.0 s	2.8 KiB
/ESWChatBotMessageforwe1744836953484/assets/js/sitecontex...	60.0 s	1.7 KiB
js.hs-scripts.com/5016179.js	90.0 s	1.3 KiB
js-na1.hs-scripts.com/5016179.js	0.0 ms	1.2 KiB
/ESWChatBotMessageforwe1744836953484/assets/styles/embedd...	19.0 s	1.0 KiB
/rp.gif?ts=1778416793109&id=a2_ivqw7bocplbk&event=PageVis...	0.0 ms	666 B
c.lytics.io/api/tag/ed11d***b0d6cb60f1a*d*df/latest.min.js	7200.0 s	648 B
insight.adsrvr.org/track/pxl/?adv=7s95dua&ct=0:edd2c1f&fmt=3	0.0 ms	149 B
insight.adsrvr.org/track/pxl/?adv=x6d8evf&ct=0:qfhdx43&fmt=3	0.0 ms	149 B
/tr/?id=171525100059628&ev=PageView&dl=https%3A%2F%2Fperr...	0.0 ms	19 B
/tr/?id=171525100059628&ev=PageView&dl=https%3A%2F%2Fperr...	0.0 ms	16 B
/tr/?id=911375248086398&ev=PageView&dl=https%3A%2F%2Fperr...	0.0 ms	16 B

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.

	URL	Resource Size	Est Savings
Galleries `div.pageAssembly > article.sm:w-[70.4339rem] > div.sm:max-h-[27.9026rem] > img.transition-opacity`	/perryhomes/image/upload/c_limit,w_750/dpr_auto/f_auto/q_...	32.3 KiB	23.4 KiB
Find Your New Home `main#main-content > header.w-full > div.relative > img.transition-opacity`	/perryhomes/image/upload/c_limit,w_750/f_auto/q_auto/PH.c...	32.2 KiB	19.0 KiB
Homebuying 101 `div.pageAssembly > article.sm:w-[70.4339rem] > div.sm:max-h-[27.9026rem] > img.transition-opacity`	/perryhomes/image/upload/c_limit,w_750/dpr_auto/f_auto/q_...	26.0 KiB	18.8 KiB
MyAccount `div.pageAssembly > article.sm:w-[70.4339rem] > div.sm:max-h-[27.9026rem] > img.transition-opacity`	/perryhomes/image/upload/c_limit,w_750/dpr_auto/f_auto/q_...	25.1 KiB	18.2 KiB
New Home Concierge `div.pageAssembly > article.sm:w-[70.4339rem] > div.sm:max-h-[27.9026rem] > img.transition-opacity`	/perryhomes/image/upload/c_limit,w_750/dpr_auto/f_auto/q_...	18.9 KiB	13.7 KiB

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:295.58 label:Time to first byte subpart:timeToFirstByte] map[duration:11.694 label:Resource load delay subpart:resourceLoadDelay] map[duration:148.79 label:Resource load duration subpart:resourceLoadDuration] map[duration:2747.065 label:Element render delay subpart:elementRenderDelay]]

lhId: page-1-IMG

nodeLabel: Find Your New Home

path: 1,HTML,1,BODY,3,MAIN,1,HEADER,0,DIV,0,IMG

selector: main#main-content > header.w-full > div.relative > img.transition-opacity

snippet: <img alt="Find Your New Home" fetchpriority="high" decoding="async" data-nimg="fill" class="transition-opacity object-cover duration-700 ease-linear" style="position: absolute; height: 100%; width: 100%; inset: 0px;" sizes="(min-width: 1600px) 1512px, calc(94.69vw + 16px)" srcset="https://res.cloudinary.com/perryhomes/image/upload/c_limit,w_16/f_auto/q_a…" src="https://res.cloudinary.com/perryhomes/image/upload/c_limit,w_750/f_auto/q_…">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
/ESWChatBotMessageforwe1744836953484/assets/js/bootstrap....	http/1.1
/ESWChatBotMessageforwe1744836953484/assets/styles/bootst...	http/1.1
/ESWChatBotMessageforwe1744836953484/assets/htdocs/siteco...	http/1.1
/ESWChatBotMessageforwe1744836953484/assets/js/sitecontex...	http/1.1
/ESWChatBotMessageforwe1744836953484/?lwc.mode=prod&lwr.l...	http/1.1
/ESWChatBotMessageforwe1744836953484/assets/js/inert.min.js	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/framework...	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/view/495b...	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/component...	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/component...	http/1.1
/ESWChatBotMessageforwe1744836953484/webruntime/view/d775...	http/1.1
/ESWChatBotMessageforwe1744836953484/assets/styles/embedd...	http/1.1
/ESWChatBotMessageforwe1744836953484/assets/styles/salesf...	http/1.1

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

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.

URL	Transfer Size	Duration
perryhomes.com/_next/static/css/05b21d21c0869782.css	1.3 KiB
perryhomes.com/_next/static/css/cf3231e9f5025ab4.css	26.6 KiB	451 ms

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.

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: 150 ms 23.6 KiB

URL	Transfer Size	Est Savings
perryhomes.com/_next/static/css/cf3231e9f5025ab4.css	26.5 KiB	23.6 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.

Estimated savings: 2.3 s 442.6 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-CNS7PNWGBC&cx=c&gtm=4e6562h1	174.5 KiB	67.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-KFQSKBWC&gtm_auth=aBbK6DdmcowGjYSN7B-aog	195.0 KiB	60.7 KiB
maps.googleapis.com/maps-api-v3/api/js/64/12d/main.js	83.1 KiB	54.0 KiB
perryhomes.com/_next/static/chunks/4027-9a9821c8af697fce.js	37.6 KiB	32.7 KiB
connect.facebook.net/en_US/fbevents.js	97.0 KiB	31.4 KiB
maps.googleapis.com/maps-api-v3/api/js/64/12d/common.js	36.7 KiB	26.9 KiB
/signals/config/911375248086398?v=2.9.313&r=stable&domain...	100.0 KiB	26.3 KiB
maps.googleapis.com/maps-api-v3/api/js/64/12d/util.js	69.4 KiB	26.1 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	25.7 KiB
perryhomes.com/_next/static/chunks/8566-ae821fa7e590a7ad.js	33.7 KiB	24.4 KiB
maps.googleapis.com/maps-api-v3/api/js/64/12d/map.js	25.3 KiB	22.8 KiB
s2.adform.net/banners/scripts/st/trackpoint-async.js	31.3 KiB	22.2 KiB
perryhomes.com/_next/static/chunks/6881-1f1791324eaa0b34.js	40.2 KiB	22.0 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	645 ms	46 ms	0.0 ms
perryhomes.com/	536 ms	36 ms	31 ms
www.googletagmanager.com/gtm.js?id=GTM-KFQSKBWC&gtm_auth=aBbK6DdmcowGjYSN7B-aog	517 ms	442 ms	53 ms
js.hs-analytics.net/analytics/1778414400000/5016179.js	488 ms	384 ms	10 ms
perryhomes.com/_next/static/chunks/7023-17c41caaeebda58d.js	459 ms	423 ms	8.9 ms
www.redditstatic.com/ads/pixel.js?pixel_id=a2_ivqw7bocplbk	356 ms	332 ms	6.7 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	337 ms	287 ms	22 ms
www.googletagmanager.com/gtag/js?id=G-CNS7PNWGBC&cx=c&gtm=4e6562h1	292 ms	237 ms	46 ms
/signals/config/911375248086398?v=2.9.313&r=stable&domain...	213 ms	178 ms	28 ms
perryhomes.com/_next/static/chunks/8566-ae821fa7e590a7ad.js	137 ms	129 ms	7.1 ms
/signals/config/171525100059628?v=2.9.313&r=stable&domain...	133 ms	119 ms	13 ms
perryhomes.com/_next/static/chunks/fd9d1056-462860166448dba8.js	129 ms	92 ms	11 ms
connect.facebook.net/en_US/fbevents.js	119 ms	92 ms	26 ms
maps.googleapis.com/maps-api-v3/api/js/64/12d/main.js	100 ms	70 ms	19 ms
js.hscollectedforms.net/collectedforms.js	88 ms	66 ms	4.7 ms
/ESWChatBotMessageforwe1744836953484/assets/js/bootstrap....	70 ms	45 ms	7.0 ms
tags.srv.stackadapt.com/events.js	67 ms	40 ms	1.5 ms
maps.googleapis.com/maps-api-v3/api/js/64/12d/common.js	58 ms	45 ms	12 ms
perryhomes.com/_next/static/chunks/webpack-eeda17d56c9aec07.js	53 ms	31 ms	0.9 ms

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.

Category	Time Spent
Script Evaluation	3.3 s
Other	859 ms
Script Parsing & Compilation	466 ms
Style & Layout	383 ms
Parse HTML & CSS	81 ms
Garbage Collection	76 ms
Rendering	38 ms

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 reason	Failure type
Pages with WebSocket cannot enter back/forward cache.	Pending browser support

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.

URL	Transfer Size
/ESWChatBotMessageforwe1744836953484/webruntime/view/495b...	383.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-KFQSKBWC&gtm_auth=aBbK6DdmcowGjYSN7B-aog	195.4 KiB
www.googletagmanager.com/gtag/js?id=G-CNS7PNWGBC&cx=c&gtm=4e6562h1	174.5 KiB
perryhomes.com/_next/static/media/36cdb93dc4fdf301-s.p.ttf	153.4 KiB
perryhomes.com/_next/static/media/1d8c655f89aebb8a-s.p.ttf	149.3 KiB
perryhomes.com/_next/static/media/c9c89127cf1e2b9d-s.p.ttf	144.3 KiB
perryhomes.com/_next/static/media/1fc0c74dec9a0f56-s.p.ttf	144.0 KiB
/ESWChatBotMessageforwe1744836953484/assets/styles/salesf...	102.0 KiB
/signals/config/911375248086398?v=2.9.313&r=stable&domain...	100.1 KiB
connect.facebook.net/en_US/fbevents.js	97.1 KiB

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

●Forced reflow

●LCP request discovery

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 1 user timing

●Avoid long main-thread tasks 18 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 140 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 220 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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

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.flex > iframe `body.flex > 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.

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
New Home Concierge `div.pageAssembly > article.sm:w-[70.4339rem] > div.sm:gap-y-[1.6254rem] > h3.sm:text-[1.6254rem]`
Become a Perry Insider! `body.flex > footer.flex > div.flex > h5#title-newsletter`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MOVE-IN READY `div.absolute > article.flex > div.relative > a.font-body`

○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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[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.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○`<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>`.

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

Best Practices

Trust and Safety

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source
perryhomes.com/_next/static/chunks/app/layout-1b320f9e95f3ca21.js

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 / Warning	Source
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 1126

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.

Source	Description
	`Error: Load error! at HTMLScriptElement.<anonymous> (<anonymous>:2:171)`
perryhomes.com/api/ip-geolocation	`Failed to load resource: the server responded with a status of 500 ()`
perryhomes.com/_next/static/chunks/7023-17c41caaeebda58d.js	`IP geolocation failed Error: IP geolocation failed at https://perryhomes.com/_next/static/chunks/app/layout-1b320f9e95f3ca21.js:1:32723`

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●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 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

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 destination	Link Text
perryhomes.com/tradition-excellence	Learn More
perryhomes.com/new-home-concierge	Learn More
perryhomes.com/about-my-account	Learn More
perryhomes.com/photo-gallery	Learn More
perryhomes.com/homebuying-101	Learn More
perryhomes.com/warranty	Learn More
perryhomes.com/homeowner-testimonials	Learn 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`