thebraxtonapts.com

A page that does not exist answers 200 with a normal page, so every guessed address looks real. Google treats content behind a 404 or 410 as gone, and flags empty pages that answer 200 (success) as soft 404s.

• Status 200: https://www.thebraxtonapts.com/grader-no-such-page-8f3a1c

Every AI search crawler and agent we grade is allowed. Training crawlers are allowed. A crawler is a robot that reads sites for a search engine or assistant, and one that is blocked cannot recommend you. Bing lists blocking Bingbot among the things to avoid, because content it cannot crawl may not be indexed or used in Copilot's answers.

Page isn’t blocked from indexing Google leaves out a page marked noindex, and a page its crawler cannot read cannot be listed or used as a supporting link in its AI features.

All 2 audits in this goal pass. A page whose text is kept out of results leaves a search engine or assistant nothing to quote. Google's AI features follow nosnippet and max-snippet, and Bing keeps content marked noarchive out of Copilot and limits nocache pages to their address, title and snippet.

https://www.thebraxtonapts.com/sitemap.xml is a sitemap. Google and Bing use an XML sitemap named in robots.txt to find your pages, and neither promises to index every page in it. A page must be indexed to appear in Google's AI answers.

All 2 audits in this goal pass. Google says the vast majority of the new pages it finds each day come through links, and it follows only links that are real <a> elements with an address.

Document has a <title> element Google builds the title link in search results from the page's title, and may change one that is missing, vague, boilerplate or repeated. A title keeps your wording in front of searchers.

All 2 audits in this goal pass. Google uses one canonical address per page, and uses hreflang to send searchers to the version of the page in their language.

All 2 audits in this goal pass. Chrome says each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds.

ai-catalog.json schema is invalid The Agentic Resource Discovery (ARD) draft is a format that helps assistants discover what a site offers, such as tools and agents; the standards are still emerging.

• ai-catalog.json schema is invalid: https://www.thebraxtonapts.com/

The page as your server sends it holds its text; scripts add 19 pieces of text. Claude's web fetch tool does not support pages that fill in their text with JavaScript, and Google reads such a page only after its first HTML, once it reaches the rendering queue. A page whose first response is empty waits or looks empty.

The home page's structured data names ApartmentComplex, LocalBusiness, QuantitativeValue, PostalAddress, GeoCoordinates, OpeningHoursSpecification, AggregateRating, Review, Person, Rating, LocationFeatureSpecification, and ImageObject. Structured data spares an assistant from guessing what a page means. Google says it gives explicit clues about a page; Bing says it may support clearer grounding and promises nothing.

llms.txt follows recommendations llmstxt.org proposes the file so assistants find what they need and follow its links. Lighthouse calls it an emerging convention and Google Search does not use it, so it is a bonus.

Document has a meta description Google can show a page's meta description as its snippet and asks for a different one on every page. It is less likely to show a list of keywords, so a specific summary has the best chance of being used.

Heading elements appear in a sequentially-descending order Google's guide to AI features says headings give a page a clear structure.

All 2 audits in this goal pass. Alt text is a short written description of an image. Google calls it the most important attribute for adding metadata about an image, and it also uses computer vision on the picture.

All 2 audits in this goal pass. WCAG requires the language of each page to be set in its code, so software reads it with the right rules and voice.

All 2 audits in this goal pass. WCAG, the web accessibility standard most laws point to, requires the structure a page shows on screen to be in its markup as well, and the axe rules check lists and tables for it.

Your home page offers no tools to AI assistants. WebMCP lets an assistant book or reserve through a site's own code instead of guessing its way around the screen.

A must have. While it fails, your letter stays at B or lower.

• PageSpeed's "WebMCP tools registered" audit lists no tool: https://www.thebraxtonapts.com/

1 of the 3 audits in this goal falls short: Background and foreground colors do not have a sufficient contrast ratio. WCAG requires text to contrast with its background by at least 4.5 to 1, and the axe rule color-contrast checks for it.

• Fix any of the following: Element has insufficient color contrast of 3.93 (foreground color: #ffffff, background color: #0b9444, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1: <p class="font-body text-sm text-[var(--vibe-color-text-on-primary)] mb-3 tracking-w…">: https://www.thebraxtonapts.com/

All 2 audits in this goal pass. WCAG requires every button and link to expose a name that says its purpose, and the axe rules button-name and link-name check for it.

Elements with role="dialog" or role="alertdialog" have accessible names. WCAG, the web accessibility standard most laws point to, requires every control to expose its name and role to assistive technology and software.

All 10 audits in this goal pass. Wrong ARIA tells an assistant a control is something it is not. WAI-ARIA defines the roles and attributes that are valid, and the axe rules check them.

All 2 audits in this goal pass. web.dev recommends tap targets of around 48 pixels, and WCAG sets a minimum of 24 by 24 pixels.

All 3 audits in this goal pass. WCAG, the web accessibility standard most laws point to, requires every function of a page to work from a keyboard.

Accessibility tree is well-formed (All audits passed) Chrome says agents review the accessibility tree to find what they can click or fill in, and missing labels can block them.

3 of the 3 audits in this goal fall short: Largest Contentful Paint (14.9 s), First Contentful Paint (3.8 s), and Speed Index (6.2 s). Lab test on a phone: too few real visitors to measure it. LCP is how long the main picture or text takes to appear, and visitors leave slow pages. web.dev says 2.5 seconds or less is good, one of Google's three Core Web Vitals.

• Largest Contentful Paint (14.9 s): https://www.thebraxtonapts.com/
• First Contentful Paint (3.8 s): https://www.thebraxtonapts.com/
• Speed Index (6.2 s): https://www.thebraxtonapts.com/

Use efficient cache lifetimes (Est savings of 330 KiB) web.dev says fetching resources over the network is both slow and expensive.

• Use efficient cache lifetimes (Est savings of 330 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.js
• Use efficient cache lifetimes (Est savings of 330 KiB), from Facebook: https://connect.facebook.net/signals/config/724003515637386?v=2.9.427&r=stable&domain=www.thebraxtonapts.com&im=1&hme=766752a074f0cb0756dd3275a46fdecbcfe3de1ab8f573546734b619e44d384f&ex_m=118%2C241%2C171%2C27%2C82%2C83%2C162%2C78%2C77%2C11%2C181%2C102%2C20%2C153%2C141%2C46%2C85%2C90%2C149%2C176%2C183%2C8%2C4%2C5%2C7%2C6%2C3%2C103%2C115%2C32%2C17%2C31%2C18%2C33%2C34%2C35%2C37%2C55%2C163%2C87%2C126%2C22%2C24%2C51%2C47%2C49%2C48%2C95%2C104%2C108%2C124%2C160%2C164%2C53%2C125%2C29%2C26%2C133%2C79%2C43%2C166%2C165%2C167%2C157%2C155%2C30%2C42%2C66%2C123%2C178%2C80%2C21%2C128%2C93%2C76%2C23%2C97%2C98%2C130%2C96%2C151%2C150%2C154%2C109%2C177%2C180%2C41%2C56%2C127%2C54%2C161%2C72%2C185%2C110%2C184%2C210%2C255%2C84%2C274%2C273%2C272%2C14%2C25%2C28%2C40%2C62%2C117%2C68%2C10%2C73%2C111%2C112%2C113%2C119%2C144%2C38%2C36%2C146%2C147%2C148%2C143%2C142%2C172%2C86%2C175%2C173%2C174%2C57%2C69%2C67%2C137%2C19%2C179%2C52%2C324%2C325%2C326%2C323%2C340%2C362%2C248%2C237%2C70%2C238%2C236%2C365%2C356%2C59%2C249%2C121%2C145%2C92%2C135%2C61%2C134%2C140%2C139%2C65%2C74%2C168%2C88%2C89%2C129%2C44%2C39%2C60%2C63%2C114%2C182%2C1%2C138%2C16%2C136%2C12%2C2%2C64%2C105%2C15%2C75%2C71%2C132%2C101%2C100%2C187%2C188%2C106%2C107%2C9%2C116%2C186%2C58%2C158%2C99%2C91%2C81%2C131%2C120%2C169%2C50%2C159%2C0%2C94%2C152%2C156%2C170%2C45%2C122%2C13%2C189
• Use efficient cache lifetimes (Est savings of 330 KiB), from Amazon Web Services: https://betterbot-media-files.s3.amazonaws.com/api/public/your_brand/avatars/standard_bee_bee2024.png

Total Blocking Time (330 ms) INP is the wait between a tap and the page responding, and under 200 milliseconds is good. Total Blocking Time, the lab test's stand-in, has the same bar.

• Total Blocking Time (330 ms): https://www.thebraxtonapts.com/
• Reduce JavaScript execution time (2.6 s), from audioeye-services.com: https://wsv3cdn.audioeye-services.com/static-scripts/m/audioeye-scanner-esm/v11.2.45/audioeye-scanner-esm.js
• Minimize main-thread work (4.2 s): https://www.thebraxtonapts.com/

Cumulative Layout Shift (0.187) CLS measures how much the page jumps while it loads, which makes people tap the wrong thing. web.dev names it one of three Core Web Vitals, and 0.1 or less is good.

• Cumulative Layout Shift (0.187): https://www.thebraxtonapts.com/
• Layout shift culprits: https://www.thebraxtonapts.com/
• Avoid large layout shifts (11 layout shifts found): <section class="relative w-full h-[65vh] md:h-[70vh] min-h-[420px] max-h-[780px] overflow-…">: https://www.thebraxtonapts.com/

2 of the 4 audits in this goal fall short: Improve image delivery (Est savings of 701 KiB) and Image elements do not have explicit width and height. Chrome says serving images larger than the version rendered on screen results in wasted bytes and slows page load.

• Improve image delivery (Est savings of 701 KiB): <img src="https://media.multihub.io/cdn-cgi/image/format=auto,w=960/property/5687098…" srcset="https://media.multihub.io/cdn-cgi/image/format=auto,w=160/property/5687098…" sizes="100vw" alt="A fenced-in dog park area with green grass and palm trees, featuring a ben…" loading="lazy" fetchpriority="auto" class="absolute inset-0 w-full h-full object-cover transition-opacity duration-[6…">, from multihub.io: https://media.multihub.io/cdn-cgi/image/format=auto,w=960/property/5687098786971648/019e89ca-4857-726e-83a7-eeb92cf62cb1.webp
• Image elements do not have explicit width and height: <img src="https://media.multihub.io/cdn-cgi/image/format=auto,w=960/property/5687098…" srcset="https://media.multihub.io/cdn-cgi/image/format=auto,w=160/property/5687098…" sizes="100vw" alt="Special offer" loading="eager" fetchpriority="high" class="alpp-image">, from multihub.io: https://media.multihub.io/cdn-cgi/image/format=auto,w=960/property/5687098786971648/019f6d50-4152-7606-adea-1e36583cfb3f.webp

7 of the 7 audits in this goal fall short: Avoid enormous network payloads (Total size was 3,141 KiB), Reduce unused JavaScript (Est savings of 453 KiB), Reduce unused CSS (Est savings of 39 KiB), Minify JavaScript (Est savings of 8 KiB), Minify CSS (Est savings of 12 KiB), Duplicated JavaScript (Est savings of 3 KiB), and Legacy JavaScript (Est savings of 29 KiB). Chrome says large network payloads are highly correlated with long load times and cost visitors money on mobile data.

• Avoid enormous network payloads (Total size was 3,141 KiB): https://www.thebraxtonapts.com/assets/index-g6Cf8kcC.js
• Reduce unused JavaScript (Est savings of 453 KiB): https://www.thebraxtonapts.com/assets/index-g6Cf8kcC.js
• Reduce unused CSS (Est savings of 39 KiB), from betterbot.com: https://thebraxton.engine.betterbot.com/style.css

1 of the 7 audits in this goal falls short: Uses deprecated APIs (1 warning found). Chrome says an error in the console means a problem on your page that you need to resolve.

• Uses deprecated APIs (1 warning found): https://www.thebraxtonapts.com/

Uses HTTPS web.dev says a secure connection helps prevent intruders tampering with traffic between your site and its visitors.

All 3 audits in this goal pass. Users are mistrustful of or confused by pages that ask for their location as soon as they load.

All 3 audits in this goal pass. Chrome says a CDN (a network of servers near your visitors) reduces the network latency that slows a server's first response.