Big Red Jelly · Site audit

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

All pages

Services

https://bigredjelly.com/services/ , opens in a new tab

Scores

Performance
49 mobile
84 desktop
Accessibility
73 mobile
73 desktop
Best Practices
100 mobile
100 desktop
SEO
92 mobile
92 desktop
Agentic Browsing
2/3 mobile
2/3 desktop

Findings

Full-page screenshot of Services 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 — 8 failing checks

Finding 1: `[role]`s are not contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

critical weight 10 5 elements How to fix , opens in a new tab

Show the 5 elements at fault
  • div.wpb_wrapper > ul.wpb_tabs_nav > li.tab-item > a#tab-title-brand 
    <a role="tab" id="tab-title-brand" href="#tab-brand" aria-selected="true" tabindex="0" aria-controls="tab-brand" class="active-tab">

    Fix any of the following: Required ARIA parent role not present: tablist

  • div.wpb_wrapper > ul.wpb_tabs_nav > li.tab-item > a#tab-title-content 
    <a role="tab" id="tab-title-content" href="#tab-content" aria-selected="false" tabindex="-1" aria-controls="tab-content">

    Fix any of the following: Required ARIA parent role not present: tablist

  • div.wpb_wrapper > ul.wpb_tabs_nav > li.tab-item > a#tab-title-build 
    <a role="tab" id="tab-title-build" href="#tab-build" aria-selected="false" tabindex="-1" aria-controls="tab-build">

    Fix any of the following: Required ARIA parent role not present: tablist

  • div.wpb_wrapper > ul.wpb_tabs_nav > li.tab-item > a#tab-title-growth-strategy 
    <a role="tab" id="tab-title-growth-strategy" href="#tab-growth-strategy" aria-selected="false" tabindex="-1" aria-controls="tab-growth-strategy">

    Fix any of the following: Required ARIA parent role not present: tablist

  • div.wpb_wrapper > ul.wpb_tabs_nav > li.tab-item > a#tab-title-grow 
    <a role="tab" id="tab-title-grow" href="#tab-grow" aria-selected="false" tabindex="-1" aria-controls="tab-grow">

    Fix any of the following: Required ARIA parent role not present: tablist

Finding 2: Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

critical weight 10 1 element How to fix , opens in a new tab

Show the 1 element at fault
  • div.wpb_wrapper > div.wpb_content_element > div.wpb_wrapper > ul.wpb_tabs_nav 
    <ul class="wpb_tabs_nav ui-tabs-nav clearfix" role="tablist">

    Fix any of the following: Element has children which are not allowed: li

Finding 3: 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 20 elements How to fix , opens in a new tab

Show the 20 elements at fault
  • div.wpb_text_column > h4 > a > strong 
    <strong>

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-discovery/brand-discovery-ses…">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-discovery/dedicated-brand-str…">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-discovery/brand-blueprint-and…">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-research/brand-audit/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-research/ideal-customer-resea…">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-research/brand-and-market-res…">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-positioning/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-dna/brand-purpose/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-core/brand-core-values/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-core/mission-statements/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-core/vision-statement/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-core/brand-promise/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-core/brand-emotion-drivers/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-core/internal-brand-engagemen…">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-messaging/unique-value-and-se…">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-messaging/taglines/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-messaging/brand-voice/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • div.nectar-fancy-ul > ul > li > a 
    <a href="https://bigredjelly.com/services/brand/brand-visual-identity/logo-design/">

    Fix any of the following: Element has insufficient color contrast of 4.28 (foreground color: #e62525, background color: #f9f9fa, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

  • body.wp-singular > div#brj-privacy-bar > button#brj-pb-ok 
    <button class="brj-pb-btn brj-pb-ok" id="brj-pb-ok">

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

Finding 4: 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 6 elements How to fix , opens in a new tab

Show the 6 elements at fault
  • div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a 
    <a href="https://x.com/brj_marketing" target="_blank">

    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

  • div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a 
    <a href="https://www.facebook.com/bigredjelly/" target="_blank">

    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

  • div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a 
    <a href="https://www.linkedin.com/company/big-red-jelly/" target="_blank">

    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

  • div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a 
    <a href="https://www.youtube.com/channel/UC1zx9PH25X82MLdTMK6bkhQ/videos" target="_blank">

    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

  • div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a 
    <a href="https://www.instagram.com/bigredjelly/" target="_blank">

    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

  • div.wpb_wrapper > div.nectar_icon_wrap > div.nectar_icon > a 
    <a href="https://www.tiktok.com/@bigredjelly" target="_blank">

    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 5: List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

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

Show the 2 elements at fault
  • div.wpb_content_element > div.wpb_wrapper > ul.wpb_tabs_nav > li.tab-item 
    <li class="tab-item active-tab">

    Fix any of the following: List item parent element has a role that is not role="list"

  • div.wpb_content_element > div.wpb_wrapper > ul.wpb_tabs_nav > li.tab-item 
    <li class="tab-item">

    Fix any of the following: List item parent element has a role that is not role="list"

Finding 6: Touch targets do not have sufficient size or spacing.

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.

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

Show the 2 elements at fault
  • div.col > div.post-header > span.meta-category > a.build 
    <a class="build" href="https://bigredjelly.com/blog/category/build/">

    Fix any of the following: Target has insufficient size (32px by 20px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.

  • div.col > div.post-header > span.meta-category > a.marketing 
    <a class="marketing" href="https://bigredjelly.com/blog/category/marketing/">

    Fix any of the following: Target has insufficient size (67px by 20px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.

Finding 7: Links rely on color to be distinguishable.

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

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

Show the 1 element at fault
  • div.wpb_wrapper > div.wpb_text_column > h2 > a 
    <a href="https://bigredjelly.com/services/brand/">

    Fix any of the following: The link has insufficient color contrast of 2.15:1 with the surrounding text. (Minimum contrast is 3:1, link text: #e62525, surrounding text: #444444) The link has no styling (such as underline) to distinguish it from the surrounding text

Finding 8: 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 3 elements How to fix , opens in a new tab

Show the 3 elements at fault
  • div.vc_column-inner > div.wpb_wrapper > div.wpb_text_column > h4 
    <h4>

    Fix any of the following: Heading order invalid

  • div.nectar_hotspot_wrap > div.nttip > div.inner > h5 
    <h5>

    Fix any of the following: Heading order invalid

  • div.vc_column-inner > div.wpb_wrapper > div.wpb_text_column > h4 
    <h4 style="text-align: center;">

    Fix any of the following: Heading order invalid

SEO — 1 failing check

Finding 9: Links do not have descriptive text

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

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

Agentic Browsing — 1 failing check

Finding 10: 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.5 s First Contentful Paint
5.8 s Largest Contentful Paint
700 ms Total Blocking Time
0.018 Cumulative Layout Shift
6.4 s Speed Index

Performance — 15 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 40 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

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 248 KiB score 0 How to fix , opens in a new tab

LCP breakdown

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

score 0 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 12 KiB score 50 How to fix , opens in a new tab

Max Potential First Input Delay

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.

270 ms score 44 How to fix , opens in a new tab

Minimize main-thread work

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

3.3 s score 0 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 JavaScript execution time

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.

1.4 s 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 157 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 268 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 3,130 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.

11.4 s score 19 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 132 KiB score 50 How to fix , opens in a new tab

Performance: 9 checks passed, 3 not applicable
  • Document request latency
  • Duplicated JavaScript
  • LCP request discovery
  • Optimize viewport for mobile
  • Minify JavaScript
  • Avoids enormous network payloads
  • Image elements have explicit `width` and `height`
  • Avoid multiple page redirects
  • Initial server response time was short
  • INP breakdown (not applicable)
  • User Timing marks and measures (not applicable)
  • Avoid non-composited animations (not applicable)
Accessibility: 21 checks passed, 36 not applicable
  • `[aria-*]` attributes match their roles
  • 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>`
  • `[aria-hidden="true"]` elements do not contain focusable descendents
  • 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
  • Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
  • `[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
  • Skip links are focusable.
  • No element has a `[tabindex]` value greater than 0
  • Document has a main landmark.
  • Elements with `role="none"` or `role="presentation"` do not have conflicts
  • `[accesskey]` values are unique (not applicable)
  • `button`, `link`, and `menuitem` elements have accessible names (not applicable)
  • Elements with `role="dialog"` or `role="alertdialog"` have accessible names. (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 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)
  • 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)
  • 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
  • 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`
Agentic Browsing: 2 checks passed, 3 not applicable
  • Cumulative Layout Shift
  • llms.txt follows recommendations
  • WebMCP form coverage (not applicable)
  • WebMCP tools registered (not applicable)
  • WebMCP schemas are valid (not applicable)

Scanned · Lighthouse 13.4.1