fajitapetes.com

https://fajitapetes.com/sitemap.xml answers 404. 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.

• Status 404: https://fajitapetes.com/sitemap.xml

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.

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.

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.

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 WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, and PropertyValueSpecification. 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.

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

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

1 of the 2 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.48 (foreground color: #ffffff, background color: #739436, font size: 13.5pt (18px), font weight: normal). Expected contrast ratio of 4.5:1: <span>: https://fajitapetes.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.

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

1 of the 3 audits in this goal falls short: Speed Index (10.5 s). Measured from real visitors of this page, 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 (10.5 s): https://fajitapetes.com/
• Render-blocking requests (Est savings of 310 ms): https://fajitapetes.com/_next/static/chunks/6d526c946bbbb849.css

1 of the 4 audits in this goal falls short: Improve image delivery (Est savings of 10 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 10 KiB): <header class="styles-module__DxJPCa__clt_371_34 wrapper-80">: https://fajitapetes.com/pattern-red.png

3 of the 8 audits in this goal fall short: Avoid enormous network payloads (Total size was 3,336 KiB), Reduce unused JavaScript (Est savings of 212 KiB), and Legacy JavaScript (Est savings of 14 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,336 KiB), from Google Tag Manager: https://www.googletagmanager.com/gtag/js?id=AW-867189185
• Reduce unused JavaScript (Est savings of 212 KiB), from Google Tag Manager: https://www.googletagmanager.com/gtm.js?id=GTM-PLTCC98Z
• Legacy JavaScript (Est savings of 14 KiB): https://fajitapetes.com/_next/static/chunks/b618b5e673ac1932.js

Interaction to Next Paint is 138 ms for real visitors of this page, last 28 days, which Google rates good. 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.

Cumulative Layout Shift is 0.00 for real visitors of this page, last 28 days, which Google rates good. 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.

Use efficient cache lifetimes web.dev says fetching resources over the network is both slow and expensive.

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

All 7 audits in this goal pass. Chrome says an error in the console means a problem on your page that you need to resolve.

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.