livevici.com

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages link to each other in a way search engines can follow What the grader found: Links are not crawlable. Links do not have descriptive text (1 link found). Details: - Links are not crawlable: <a class="btn close"> The fix, for a developer: Give each link an <a> element with an href instead of a script-only click handler, and link text that describes the destination rather than "click here". Source: SEO Link Best Practices for Google, Google: https://developers.google.com/search/docs/crawling-indexing/links-crawlable; Understanding Success Criterion 2.4.4: Link Purpose (In Context), W3C: https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site says when a page does not exist (404) What the grader found: An address that does not exist answers 200 with a normal page. Details: - Status 200 The fix, for a developer: Return 404 (or 410 for a page that is gone) for unknown routes. A single-page app needs its server to answer unknown paths with the not-found page and a 404 status, since a redirect to the home page makes every address look real. Source: How Google Search handles HTTP status codes, Google: https://developers.google.com/crawling/docs/troubleshooting/http-status-codes; RFC 9110, section 15.5.5 404 Not Found, IETF: https://www.rfc-editor.org/rfc/rfc9110#section-15.5.5 Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages open without unnecessary redirects What the grader found: Your home page is sent through a detour to another page before it opens. Details: - Redirects to /vici-san-diego-ca The fix, for a developer: Link to the final address, and make each redirect reach its destination in one hop, such as one rule that sends http and non-www straight to the final https address. Source: Avoid multiple page redirects, Chrome: https://developer.chrome.com/docs/lighthouse/performance/redirects Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site tells AI agents what your business is (structured data) What the grader found: Your home page has no structured data with a type. Details: - Your home page has no structured data with a type The fix, for a developer: Add a JSON-LD script to the home page whose "@type" is the most specific schema.org type that fits the business. schema.org lists every type and its subtypes. Source: Intro to structured data, Google: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data; JSON-LD 1.1, W3C: https://www.w3.org/TR/json-ld11/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can tell what your images show (alt text) What the grader found: Image elements do not have [alt] attributes Details: - Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation": <img src="/themes/hgfenton/prop/main/vici/images/dare-to-live-tagline.png"> The fix, for a developer: Give each meaningful img an alt attribute that says what it shows, an empty alt="" to decorative images, and a text name to image buttons, svg graphics and objects. Source: Image SEO Best Practices, Google: https://developers.google.com/search/docs/appearance/google-images; Understanding Success Criterion 1.1.1: Non-text Content, W3C: https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site has a short guide for AI agents (llms.txt) What the grader found: llms.txt does not follow recommendations The fix, for a developer: Serve a Markdown file at /llms.txt with a 200, and keep it clear of any rule that sends unknown paths to the home page or a firewall page. Start it with an H1 naming the site, then sections of links to key pages, as llmstxt.org describes. Source: llms.txt audit, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site tells AI agents everything they can do with it, in one place (ARD catalog) What the grader found: ARD manifest is invalid The fix, for a developer: Serve JSON at /.well-known/ard.json with an entries list that follows the ARD schema: each entry has a urn:air: identifier, a displayName, a type and a url. An MCP server's entry has the type application/mcp-server-card+json and points at its server card, at /mcp/server-card. Link it from every page with <link rel="ard" href="/.well-known/ard.json">. Lighthouse warns about a catalog found only at the older /.well-known/ai-catalog.json. Source: Lighthouse agentic browsing scoring, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/scoring; Agentic Resource Discovery specification, agenticresourcediscovery.org: https://agenticresourcediscovery.org/spec/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site sends AI agents a plain-text version of each page (Markdown) What the grader found: Cloudflare's scan asked your home page for Markdown and got none back. Details: - Site does not support Markdown for Agents The fix, for a developer: Answer a request whose Accept header names text/markdown with the page's content as Markdown and Content-Type: text/markdown. Cloudflare can convert pages at its edge, or the server can render the Markdown itself. Source: Markdown for Agents, Cloudflare: https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site says how AI may use its content (Content Signals) What the grader found: Cloudflare found no Content-Signal line in your robots.txt. Details: - Cannot check Content Signals without robots.txt The fix, for a developer: Add a Content-Signal line to robots.txt under the user agents it covers, such as Content-Signal: search=yes, ai-input=yes, ai-train=no. Source: Content Signals, Content Signals: https://contentsignals.org/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your lists and tables are built so agents can read them What the grader found: List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements. Details: - Fix any of the following: List item parent element has a role that is not role="list". Ensure the parent element has role="list", or move the <li> inside a <ul> or <ol>.: <li class="accordion-item" data-accordion-item=""> The fix, for a developer: Use ul, ol and dl with li, dt and dd children, and table markup with th header cells for tabular data, rather than line breaks and styled divs. Source: Rule list: <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Deque axe: https://dequeuniversity.com/rules/axe/4.13/list; Understanding Success Criterion 1.3.1: Info and Relationships, W3C: https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can see your site's buttons and fields (accessibility tree) What the grader found: Accessibility tree is not well-formed Details: - ARIA input fields must have an accessible name: <div class="slick-track" role="listbox" style="opacity: 1; width: 3690px; transform: translate3d(-410px, 0px, 0px);"> - Certain ARIA roles must contain particular children: <ul class="accordion" data-accordion="n7k73u-accordion" data-allow-all-closed="true" role="tablist"> - Certain ARIA roles must be contained by particular parents: <a class="accordion-title" href="#" aria-controls="ormwge-accordion" role="tab" id="ormwge-accordion-label" aria-expanded="false" aria-selected="false"> The fix, for a developer: Give every button, link and field an accessible name, associate each field with a label, and remove invalid ARIA roles and attributes. PageSpeed lists the elements that fail. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can complete tasks when they visit your site (WebMCP) What the grader found: Your home page offers agents no tasks to complete through WebMCP. The fix, for a developer: Register a WebMCP tool for every task a customer can do as the page loads: call document.modelContext.registerTool() with a name, a description, an input schema and an execute function, or add toolname and tooldescription attributes to the form. A name is 1 to 128 letters, digits, _, - or . Source: WebMCP for developers, Chrome: https://developer.chrome.com/docs/ai/webmcp; WebMCP, Draft Community Group Report, W3C Web Machine Learning Community Group: https://webmachinelearning.github.io/webmcp/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can complete tasks without visiting your site (MCP server) What the grader found: Google's Lighthouse finds your ARD catalog invalid, so agents cannot rely on it to find your MCP server. Details: - Lighthouse's ard-schema audit fails The fix, for a developer: Serve the MCP server card at /mcp/server-card, as the server card extension places it, and list it in /.well-known/ard.json as an entry with a urn:air: identifier, a displayName, the type application/mcp-server-card+json and the card's URL. Source: SEP-2127: MCP Server Cards, Model Context Protocol: https://modelcontextprotocol.io/seps/2127-mcp-server-cards; Agentic Resource Discovery specification, agenticresourcediscovery.org: https://agenticresourcediscovery.org/spec/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can tell what every button and link does What the grader found: Links do not have a discernible name. Details: - 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: <a class="scroll-btn" href="#luxury"> The fix, for a developer: Give each button, link and input button visible text or an aria-label, keep the accessible name containing the visible text, and make links to different places read differently. Source: Rule button-name: Buttons must have discernible text, Deque axe: https://dequeuniversity.com/rules/axe/4.13/button-name; Understanding Success Criterion 4.1.2: Name, Role, Value, W3C: https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can tell what every form field asks for What the grader found: Select elements do not have associated label elements. Details: - Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> 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 Element's default semantics were not overridden with role="none" or role="presentation": <select id="contact_bedrooms" name="contact[bedrooms]"> The fix, for a developer: Associate each input and select with one label element through for and id, and use valid autocomplete values on fields for names, addresses and payment details. Source: Rule label: Form elements must have labels, Deque axe: https://dequeuniversity.com/rules/axe/4.13/label; Understanding Success Criterion 3.3.2: Labels or Instructions, W3C: https://www.w3.org/WAI/WCAG22/Understanding/labels-or-instructions.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can tell what custom controls are, such as date pickers What the grader found: ARIA input fields do not have accessible names. ARIA toggle fields do not have accessible names. Details: - Fix any of the following: 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 class="slick-track" role="listbox" style="opacity: 1; width: 3690px; transform: translate3d(-410px, 0px, 0px);"> The fix, for a developer: Give each element with an ARIA control role an accessible name through aria-label or aria-labelledby. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents; Understanding Success Criterion 4.1.2: Name, Role, Value, W3C: https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Hidden labels on your buttons and fields are accurate (ARIA) What the grader found: Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. [role]s are not contained by their required parent element. Details: - Fix any of the following: Element has children which are not allowed: li: <ul class="accordion" data-accordion="n7k73u-accordion" data-allow-all-closed="true" role="tablist"> - Fix any of the following: Required ARIA parent role not present: tablist: <a class="accordion-title" href="#" aria-controls="ormwge-accordion" role="tab" id="ormwge-accordion-label" aria-expanded="false" aria-selected="false"> The fix, for a developer: Use native elements first, give each ARIA role its required attributes and children, remove attributes the role does not allow, and keep ids unique. Source: Rule aria-roles: ARIA roles used must conform to valid values, Deque axe: https://dequeuniversity.com/rules/axe/4.13/aria-roles; Accessible Rich Internet Applications (WAI-ARIA) 1.2, W3C: https://www.w3.org/TR/wai-aria-1.2/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site tells AI agents about its other services What the grader found: Your home page sends no Link headers that point agents to these files. Your site has no API catalog. Your site has no Agent Skills index. Your site has no A2A agent card. Details: - No Link headers found on target page - API Catalog returned HTML instead of JSON - Agent Skills index returned HTML instead of JSON The fix, for a developer: Publish the files that fit: an API catalog at /.well-known/api-catalog, an Agent Skills index, an A2A agent card at /.well-known/agent-card.json, and Link headers on the home page that point to them. Source: RFC 8288, Web Linking, IETF: https://www.rfc-editor.org/rfc/rfc8288; RFC 9727, api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs, IETF: https://www.rfc-editor.org/rfc/rfc9727 Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your main content shows up quickly on phones What the grader found: Largest Contentful Paint is 7.2 s for real visitors of this page, last 28 days, which Google rates poor. First Contentful Paint is 6.6 s for real visitors of this page, last 28 days, which Google rates poor. Speed Index (8.9 s). Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone. Details: - LCP request discovery - LCP breakdown - Render-blocking requests (Est savings of 1,300 ms) The fix, for a developer: Serve the largest element early: preload it, avoid render-blocking scripts and styles, and cut server response time. PageSpeed lists what holds it back. Source: Web Vitals, Google: https://web.dev/articles/vitals; Largest Contentful Paint (LCP), Google: https://web.dev/articles/lcp Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site responds quickly to taps and clicks What the grader found: Interaction to Next Paint is 524 ms for real visitors of this page, last 28 days, which Google rates poor. Details: - Reduce JavaScript execution time (3.9 s), from Google CDN - Minimize main-thread work (5.4 s) - Forced reflow The fix, for a developer: Split long tasks and defer scripts that are not needed to start. PageSpeed lists the costliest scripts. Source: Total Blocking Time (TBT), Google: https://web.dev/articles/tbt; Lighthouse performance scoring, Chrome: https://developer.chrome.com/docs/lighthouse/performance/performance-scoring Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages stay still while they load What the grader found: Cumulative Layout Shift is 0.37 for real visitors of this page, last 28 days, which Google rates poor. Details: - Layout shift culprits - Avoid large layout shifts (2 layout shifts found): <main role="main"> The fix, for a developer: Set width and height on images and embeds, reserve space for late content, and use font-display with a matching fallback font. Source: Web Vitals, Google: https://web.dev/articles/vitals; Cumulative Layout Shift (CLS), Google: https://web.dev/articles/cls Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Return visits load faster What the grader found: Use efficient cache lifetimes (Est savings of 18,776 KiB) The fix, for a developer: Send Cache-Control with a long max-age for fingerprinted static files, and revalidate the rest with ETag. Source: Prevent unnecessary network requests with the HTTP Cache, Google: https://web.dev/articles/http-cache Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your server answers quickly What the grader found: Document request latency (Est savings of 660 ms). Your home page is served over HTTP/1.1. Details: - Network Round Trip Times (20 ms) - Server Backend Latencies (40 ms) The fix, for a developer: Serve the page through a CDN or edge network over HTTP/2 or HTTP/3, compress text with gzip or Brotli, cache the document at the edge, and avoid redirects. Source: Reduce server response times (TTFB), Chrome: https://developer.chrome.com/docs/lighthouse/performance/server-response-time Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Images are sent at the size they are shown What the grader found: Improve image delivery (Est savings of 1,019 KiB). Image elements do not have explicit width and height. Details: - Improve image delivery (Est savings of 1,019 KiB): <img class="location-preview-img lazy" src="/uploads/images/images/original/242734/bike-with-v-flat.png?1496965151"> - Image elements do not have explicit width and height: <img alt="VICI logo" class="logo-img" src="/uploads/images/images/original/236852/Vici_updated_logo_sect2.png?1493931…"> The fix, for a developer: Serve several sizes with srcset and sizes, use a modern format such as WebP or AVIF, and keep each image's width and height in the proportion it is shown. Source: Properly size images, Chrome: https://developer.chrome.com/docs/lighthouse/performance/uses-responsive-images Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages are light to download What the grader found: Avoid enormous network payloads (Total size was 25,068 KiB). Reduce unused JavaScript (Est savings of 1,742 KiB). Reduce unused CSS (Est savings of 37 KiB). Minify JavaScript (Est savings of 8 KiB). Legacy JavaScript (Est savings of 9 KiB). Details: - Reduce unused JavaScript (Est savings of 1,742 KiB), from Google CDN - Minify JavaScript (Est savings of 8 KiB), from Cloudflare CDN - Legacy JavaScript (Est savings of 9 KiB), from Unpkg The fix, for a developer: Minify scripts and styles, remove unused and duplicate code, and stop shipping legacy polyfills. PageSpeed lists the files by size. Source: Avoid enormous network payloads, Chrome: https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11

My website https://www.livevici.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages load without errors What the grader found: Browser errors were logged to the console. Details: - Failed to load resource: net::ERR_CONNECTION_FAILED The fix, for a developer: Fix each console error and browser issue, replace deprecated APIs, publish source maps for your scripts, and start the document with a doctype and a charset. Source: Browser errors were logged to the console, Chrome: https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livevici-com/2026-11-11