PXP · Site audit

Prepared by PXP — opens pxp.dev in a new tab

All pages

Homepage

https://pxp.dev/ , opens in a new tab

Scores

Performance
64 mobile
92 desktop
Accessibility
89 mobile
88 desktop
Best Practices
100 mobile
100 desktop
SEO
100 mobile
100 desktop
Agentic Browsing
1/2 mobile
1/2 desktop

Findings

Full-page screenshot of Homepage as rendered during the mobile scan.
Boxes mark elements that failed a check. Hover or focus an element in the lists below to highlight it here.

Accessibility — 4 failing checks

Finding 1: Background and foreground colors do not have a sufficient contrast ratio.

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

serious weight 7 3 elements How to fix , opens in a new tab

Show the 3 elements at fault
  • div.container > div.row > div.col-lg-6 > a.btn 
    <a href="/get-more-info" class="btn btn-lg btn-primary mt-3">

    Fix any of the following: Element has insufficient color contrast of 1.67 (foreground color: #ffffff, background color: #8bd4de, font size: 13.1pt (17.5px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.mt-4 > div.border-bottom > div.accordion-panel-title > span.h6 
    <span class="h6 mb-0">

    Fix any of the following: Element has insufficient color contrast of 3.19 (foreground color: #4e9d95, background color: #ffffff, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.row > div.col-xl-8 > p.lead > a 
    <a href="https://meetings.hubspot.com/wylie">

    Fix any of the following: Element has insufficient color contrast of 4.14 (foreground color: #e52525, background color: #f2f5f5, font size: 13.1pt (17.5px), font weight: normal). Expected contrast ratio of 4.5:1

Finding 2: Links do not have a discernible name

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.

serious weight 7 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • div.col-auto > ul.nav > li.nav-item > a.nav-link 
    <a href="#" class="nav-link">

    Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute

Finding 3: Heading elements are not in a sequentially-descending order

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.

moderate weight 3 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • div.col-lg-6 > div.card > div.card-body > h5.card-title 
    <h5 class="card-title mb-2">

    Fix any of the following: Heading order invalid

Finding 4: Document does not have a main landmark.

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

moderate weight 3 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • html 
    <html lang="en">

    Fix all of the following: Document does not have a main landmark

Agentic Browsing — 1 failing check

Finding 5: Accessibility tree is not well-formed

A well-formed accessibility tree helps AI agents to navigate and interact with the page.

unrated weight 1 0 elements How to fix , opens in a new tab

Lab metrics

Measured in a simulated mobile environment. These are readings, not checks — treat them as context for the performance score rather than defects to close.

3.2 s First Contentful Paint
8.7 s Largest Contentful Paint
70 ms Total Blocking Time
0 Cumulative Layout Shift
6.0 s Speed Index

Performance — 13 opportunities

Font display

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.

Est savings of 150 ms score 0 How to fix , opens in a new tab

Forced reflow

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.

score 0 How to fix , opens in a new tab

Image elements do not have explicit `width` and `height`

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

score 50 How to fix , opens in a new tab

Improve image delivery

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Est savings of 820 KiB score 50 How to fix , opens in a new tab

Legacy JavaScript

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

Est savings of 45 KiB score 0 How to fix , opens in a new tab

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Est savings of 9 KiB score 50 How to fix , opens in a new tab

Network dependency tree

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.

score 0 How to fix , opens in a new tab

Reduce unused CSS

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.

Est savings of 70 KiB score 0 How to fix , opens in a new tab

Reduce unused JavaScript

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

Est savings of 103 KiB score 0 How to fix , opens in a new tab

Render-blocking requests

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.

Est savings of 1,660 ms score 0 How to fix , opens in a new tab

Time to Interactive

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.

8.7 s score 36 How to fix , opens in a new tab

Use efficient cache lifetimes

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

Est savings of 5 KiB score 50 How to fix , opens in a new tab

Performance: 11 checks passed, 5 not applicable
  • Layout shift culprits
  • Document request latency
  • Optimize DOM size
  • Duplicated JavaScript
  • Optimize viewport for mobile
  • Max Potential First Input Delay
  • Avoids enormous network payloads
  • JavaScript execution time
  • Minimizes main-thread work
  • Avoid multiple page redirects
  • Initial server response time was short
  • INP breakdown (not applicable)
  • LCP request discovery (not applicable)
  • User Timing marks and measures (not applicable)
  • Avoid non-composited animations (not applicable)
  • Avoid large layout shifts (not applicable)
Accessibility: 20 checks passed, 41 not applicable
  • `[aria-*]` attributes match their roles
  • `button`, `link`, and `menuitem` elements have accessible names
  • ARIA attributes are used as specified for the element's role
  • Deprecated ARIA roles were not used
  • `[aria-hidden="true"]` is not present on the document `<body>`
  • Elements use only permitted ARIA attributes
  • `[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
  • Document has a `<title>` element
  • `<html>` element has a `[lang]` attribute
  • `<html>` element has a valid value for its `[lang]` attribute
  • Image elements have `[alt]` attributes
  • Links are distinguishable without relying on color.
  • Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
  • List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
  • `[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
  • Touch targets have sufficient size and spacing.
  • `[accesskey]` values are unique (not applicable)
  • Elements with `role="dialog"` or `role="alertdialog"` have accessible names. (not applicable)
  • `[aria-hidden="true"]` elements do not contain focusable descendents (not applicable)
  • ARIA input fields have accessible names (not applicable)
  • ARIA `meter` elements have accessible names (not applicable)
  • ARIA `progressbar` elements have accessible names (not applicable)
  • Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. (not applicable)
  • `[role]`s are contained by their required parent element (not applicable)
  • Elements with the `role=text` attribute do not have focusable descendents. (not applicable)
  • ARIA toggle fields have accessible names (not applicable)
  • ARIA `tooltip` elements have accessible names (not applicable)
  • ARIA `treeitem` elements have accessible names (not applicable)
  • The page contains a heading, skip link, or landmark region (not applicable)
  • `<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements. (not applicable)
  • Definition list items are wrapped in `<dl>` elements (not applicable)
  • ARIA IDs are unique (not applicable)
  • No form fields have multiple labels (not applicable)
  • `<frame>` or `<iframe>` elements have a title (not applicable)
  • `<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute. (not applicable)
  • Input buttons have discernible text. (not applicable)
  • `<input type="image">` elements have `[alt]` text (not applicable)
  • Form elements have associated labels (not applicable)
  • The document does not use `<meta http-equiv="refresh">` (not applicable)
  • `<object>` elements have alternate text (not applicable)
  • Select elements have associated label elements. (not applicable)
  • Skip links are focusable. (not applicable)
  • No element has a `[tabindex]` value greater than 0 (not applicable)
  • Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table. (not applicable)
  • `<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe. (not applicable)
  • `[lang]` attributes have a valid value (not applicable)
  • `<video>` elements contain a `<track>` element with `[kind="captions"]` (not applicable)
  • `autocomplete` attributes are used correctly (not applicable)
  • Elements with `role="none"` or `role="presentation"` do not have conflicts (not applicable)
  • SVG elements with an `img` role have an accessible text alternative (not applicable)
  • Tables have different content in the summary attribute and `<caption>`. (not applicable)
  • All heading elements contain content. (not applicable)
  • Uses ARIA roles only on compatible elements (not applicable)
  • Image elements do not have `[alt]` attributes that are redundant text. (not applicable)
  • Elements with visible text labels have matching accessible names. (not applicable)
  • Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption. (not applicable)
  • `<td>` elements in a large `<table>` have one or more table headers. (not applicable)
Best Practices: 13 checks passed, 1 not applicable
  • Uses HTTPS
  • Avoids requesting the geolocation permission on page load
  • Avoids requesting the notification permission on page load
  • Allows users to paste into input fields
  • Displays images with correct aspect ratio
  • Serves images with appropriate resolution
  • Page has the HTML doctype
  • Properly defines charset
  • Avoids deprecated APIs
  • Avoids third-party cookies
  • No browser errors logged to the console
  • Page has valid source maps
  • No issues in the `Issues` panel in Chrome Devtools
  • Redirects HTTP traffic to HTTPS (not applicable)
SEO: 9 checks passed, 1 not applicable
  • 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` (not applicable)
Agentic Browsing: 1 check passed, 4 not applicable
  • Cumulative Layout Shift
  • WebMCP form coverage (not applicable)
  • WebMCP tools registered (not applicable)
  • WebMCP schemas are valid (not applicable)
  • llms.txt follows recommendations (not applicable)

Scanned · Lighthouse 13.4.1