ascendpinegrove.com

1 of the 2 audits in this goal falls short: Avoid multiple page redirects: the page is sent through a detour. Chrome says each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds.

• Redirects to https://www.olympuspinegrove.com/: https://ascendpinegrove.com/

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

A page that does not exist answers 404. Google treats content behind a 404 or 410 as gone, and flags empty pages that answer 200 (success) as soft 404s.

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.

1 of the 4 audits in this goal falls short: List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements. 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.

• Fix any of the following: List item does not have a <ul>, <ol> parent element: <li index="0" class="photoGalleryThumbs asymetric-big-image" data-index="0">: https://ascendpinegrove.com/

The page as your server sends it holds its text; scripts add 41 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 WebSite, LocalBusiness, ApartmentComplex, GeoCoordinates, LocationFeatureSpecification, and OpeningHoursSpecification. 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.

Image elements have [alt] attributes 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 3 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.

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

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

• ARIA commands must have an accessible name: <a data-dm-multisize-attr="href" data-image-url="https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa99-d2f2-715b-9ace…" style="" role="button" tabindex="0">: https://ascendpinegrove.com/

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://ascendpinegrove.com/

1 of the 3 audits in this goal falls short: button, link, and menuitem elements do not have accessible names. 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.

• 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: <a data-dm-multisize-attr="href" data-image-url="https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa99-d2f2-715b-9ace…" style="" role="button" tabindex="0">: https://ascendpinegrove.com/

Form elements have associated labels WCAG requires every form field to have a label or instructions, and the axe rule label checks for it.

All 11 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 3 audits in this goal pass. WCAG requires text to contrast with its background by at least 4.5 to 1, and the axe rule color-contrast checks for it.

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.

<frame> or <iframe> elements have a title WCAG, the web accessibility standard most laws point to, requires captions for the audio in prerecorded video.

Total Blocking Time (760 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 (760 ms): https://ascendpinegrove.com/
• Reduce JavaScript execution time (6.3 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 (9.6 s): https://ascendpinegrove.com/

1 of the 3 audits in this goal falls short: Speed Index (13.4 s). Measured from real visitors of your whole site, last 28 days; the rest is a lab test on a phone. 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.

• Speed Index (13.4 s): https://ascendpinegrove.com/
• Render-blocking requests (Est savings of 1,000 ms), from cdn-website.com: https://static.cdn-website.com/mnlt/production/6862/_dm/s/rt/dist/scripts/d-js-one-runtime-unified-mobile.min.js
• Network dependency tree: https://ascendpinegrove.com/

Cumulative Layout Shift is 0.22 for real visitors of your whole site, last 28 days, which Google rates needs improvement. 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 is 0.22 for real visitors of your whole site, last 28 days, which Google rates needs improvement.: https://ascendpinegrove.com/
• Layout shift culprits: https://ascendpinegrove.com/
• Avoid large layout shifts (15 layout shifts found): <div class="dmRespColsWrapper" id="1517396738">: https://ascendpinegrove.com/

1 of the 4 audits in this goal falls short: Improve image delivery (Est savings of 47,128 KiB). 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 47,128 KiB): <img src="https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa9b-91ab-72ca-96d9…" alt="Fenced-in dog park with agility equipment and a playground in the backgrou…">, from cdn-website.com: https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa9b-91ab-72ca-96d9-a9dc58417465.webp

7 of the 7 audits in this goal fall short: Avoid enormous network payloads (Total size was 54,797 KiB), Reduce unused JavaScript (Est savings of 1,291 KiB), Reduce unused CSS (Est savings of 91 KiB), Minify JavaScript (Est savings of 54 KiB), Minify CSS (Est savings of 3 KiB), Duplicated JavaScript (Est savings of 6 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 54,797 KiB), from cdn-website.com: https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa9b-91ab-72ca-96d9-a9dc58417465.webp
• Reduce unused JavaScript (Est savings of 1,291 KiB), from eliseai.com: https://cdn.eliseai.com/@meetelise/chat
• Reduce unused CSS (Est savings of 91 KiB), from cdn-website.com: https://irp.cdn-website.com/d4191897/files/d4191897_withFlex_0.min.css?v=118

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

• Use efficient cache lifetimes (Est savings of 292 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.js
• Use efficient cache lifetimes (Est savings of 292 KiB), from Facebook: https://connect.facebook.net/en_US/bundle/sdk.js/
• Use efficient cache lifetimes (Est savings of 292 KiB), from repli360.com: https://app.repli360.com/admin/rrac-website-script/eyJpdiI6IkxsTDlrVDBnQUU0dlpuN0VEcGp6ZGc9PSIsInZhbHVlIjoiN2NxS2ZBU2JYTW5LSUxiSkc2MEtjdz09IiwibWFjIjoiM2YwNTE4MDg1YTJiOTQ1OGUxOGI0N2RkODNlY2U1MWE0NTE4ZWJlMTk3YzEwOTE4OGJmODBiNmViYTlhM2Y5ZSJ9

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

• SyntaxError: Unexpected token '-': https://ascendpinegrove.com/
• Uses deprecated APIs (1 warning found): https://ascendpinegrove.com/

1 of the 3 audits in this goal falls short: Document request latency (Est savings of 120 ms). Chrome says a CDN (a network of servers near your visitors) reduces the network latency that slows a server's first response.

• Document request latency (Est savings of 120 ms): https://ascendpinegrove.com/
• Network Round Trip Times (10 ms): https://ascendpinegrove.com/
• Server Backend Latencies (40 ms): https://ascendpinegrove.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.