amli.com

The page has no title. 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 of its own keeps your wording in front of searchers.

• No title text: https://www.amli.com/

The page lacks a favicon. Open Graph tags decide the title, description and image a link shows when shared; Google shows your icon in results.

• No a favicon: https://www.amli.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.

The page answers, no tag or header keeps it out of search results, and robots.txt lets search crawlers read it. 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.amli.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 3 audits in this goal pass. Google says the vast majority of the new pages it finds each day come through links. A page that links onward gives search another path to the next page.

The description is 148 characters, which fits a search result. Google sets no length limit and cuts a title or description to the device's width. SEO tools measure a title in pixels, since 60 characters run from 267 to 1,133 pixels, and count a description in characters. A cut loses the last words.

All 2 audits in this goal pass. Google uses one canonical address per page, recommends readable words rather than long ID numbers, and can show a breadcrumb trail in desktop results when the page marks one up.

Avoid multiple page redirects: the page only switches to https or adds or drops www. Chrome says each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds.

The structured data lacks the business type, apartment, and blog on /blog, and gives the business no keywords. The page does not state the business's address, latitude, longitude, number of bedrooms, pets allowed, and telephone. 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.

• The structured data names Organization, ImageObject, and WebSite: https://www.amli.com/
• Not in the page's structured data: https://www.amli.com/
• Not in the page's structured data: https://www.amli.com/blog

Scripts add 29 pieces of text your server does not send, and none of it is what visitors come to the page for. 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 description is the page's own and reads as a summary. 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. It asks for descriptive file names.

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://amli.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.

Select elements have associated label elements. 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 2 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 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.

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

• Use efficient cache lifetimes (Est savings of 294 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.js
• Use efficient cache lifetimes (Est savings of 294 KiB), from Facebook: https://connect.facebook.net/signals/config/273600943000144?v=2.9.426&r=stable&domain=www.amli.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 294 KiB), from Optanon: https://cdn.cookielaw.org/scripttemplates/202309.1.0/otBannerSdk.js

1 of the 3 audits in this goal falls short: Speed Index (5.8 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 (5.8 s): https://amli.com/
• LCP breakdown: https://amli.com/
• Render-blocking requests (Est savings of 150 ms): https://www.amli.com/_next/static/chunks/bf8f6ab9ddd182e7.css

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

• Interaction to Next Paint is 336 ms for real visitors of this page, last 28 days, which Google rates needs improvement.: https://amli.com/
• Reduce JavaScript execution time (2.8 s): https://www.amli.com/_next/static/chunks/c49f2eaa76e9fd53.js
• Minimize main-thread work (3.6 s): https://amli.com/

1 of the 4 audits in this goal falls short: Improve image delivery (Est savings of 31 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 31 KiB): <img alt="" width="2560" height="1440" decoding="async" data-nimg="1" class="h-full w-full bg-[75%_40%] object-cover" style="color:transparent" sizes="100vw" srcset="https://images.prismic.io/amli-website/adfadde8-169e-4043-ab9f-89b2221f20a…" src="https://images.prismic.io/amli-website/adfadde8-169e-4043-ab9f-89b2221f20a…">, from prismic.io: https://images.prismic.io/amli-website/adfadde8-169e-4043-ab9f-89b2221f20a7_FountainPlace_amenity_sky+lounge_lifestyle.jpg?auto=compress%2Cformat&rect=0%2C211%2C2560%2C1440&w=750&fit=max

3 of the 8 audits in this goal fall short: Reduce unused JavaScript (Est savings of 441 KiB), Reduce unused CSS (Est savings of 19 KiB), and Legacy JavaScript (Est savings of 55 KiB). Chrome says large network payloads are highly correlated with long load times and cost visitors money on mobile data.

• Reduce unused JavaScript (Est savings of 441 KiB), from Google Tag Manager: https://www.googletagmanager.com/gtag/js?id=G-5E383R6HZL&cx=c&gtm=4e6ak0
• Reduce unused CSS (Est savings of 19 KiB): #onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …
• Legacy JavaScript (Est savings of 55 KiB): https://www.amli.com/_next/static/chunks/c49f2eaa76e9fd53.js

1 of the 7 audits in this goal falls short: Browser errors were logged to the console. Chrome says an error in the console means a problem on your page that you need to resolve.

• Failed to load resource: the server responded with a status of 404 (Not Found): https://amli.com/

1 of the 3 audits in this goal falls short: Requests the geolocation permission on page load. Users are mistrustful of or confused by pages that ask for their location as soon as they load.

• Requests the geolocation permission on page load: https://amli.com/

2 of the 5 audits in this goal fall short: Document request latency (Est savings of 1,330 ms) and Your site sends no Strict-Transport-Security header. A CDN keeps copies of your site on servers close to each visitor, so pages arrive sooner. Chrome says a CDN reduces the network latency that slows a server's first response.

• Document request latency (Est savings of 1,330 ms): https://amli.com/
• No Strict-Transport-Security header: https://www.amli.com/
• Network Round Trip Times (10 ms): https://amli.com/

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.

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