D

Poor for AI agents

Speed: Fail (Google's lab run of this page)

Capped at D: assistants have trouble acting on your site (Act 54). Your checks earned 77.

94

Find

Does your site let search engines and assistants read and list your pages?

25% of your grade · 8 of 9 goals pass

  • Search engines and AI assistants are allowed to read your sitePass

    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.

    Overview of OpenAI crawlers, OpenAI
  • Search engines may list each pagePass

    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.

    AI features and your website, Google
  • Search results can show your pages' wordsPass

    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.

    Robots.txt Introduction and Guide, Google
  • Your pages are listed in a sitemapPass

    https://www.implantcenterofmiami.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.

    Build and submit a sitemap, Google
  • Pages that do not exist say soPass

    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.

    How Google Search handles HTTP status codes, Google
  • Every page has its own titlePass

    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.

    Influencing Title Links in Google Search, Google
  • Each page has one clear addressPass

    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.

    How to Specify a Canonical with rel="canonical" and Other Methods, Google
  • Pages open without detoursPass

    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.

    Avoid multiple page redirects, Chrome
88

Understand

Do they understand who you are and what you offer?

25% of your grade · 6 of 7 goals pass

  • Headings give each page an outlineFail

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

    • Fix any of the following: Heading order invalid: <h3 class="text-align-center">: https://www.implantcenterofmiami.com/
    • Fix any of the following: Heading order invalid: <h5 class="m-size-20 m-text-align-left">: https://www.implantcenterofmiami.com/

    What to do Ask the people who run your site to give each page one main heading and to put the headings under it in order.

    For your web team: Use h1 once, then h2 to h6 without skipping a level, and remove or fill any heading element that has no text.

    Optimizing your website for generative AI features on Google Search, Google
  • Your key facts are in the page itselfPass

    The page as your server sends it holds its text; scripts add 6 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.

    Understand JavaScript SEO basics, Google Search Central
  • Your business is described in structured dataPass

    The home page's structured data names WebSite, Dentist, PostalAddress, GeoCoordinates, 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.

    Intro to structured data, Google
  • A short guide to your site for AI assistantsPass

    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.

    Optimizing your website for generative AI features on Google Search, Google
  • Every page has its own summary for search resultsPass

    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.

    How to Write Meta Descriptions, Google
  • Images describe themselvesPass

    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.

    Image SEO Best Practices, Google
  • Pages say which language they are inPass

    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.

    Rule html-has-lang: <html> element must have a lang attribute, Deque axe
  • Lists and tables are built as lists and tablesPass

    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.

    Rule list: <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Deque axe
54

Act

Can they use your site for a shopper?

25% of your grade · 3 of 8 goals pass

  • Assistants can read your page's controlsMust haveFail

    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 input fields must have an accessible name: <div class="slick-track" style="opacity: 1; width: 2292px; transform: translate3d(-764px, 0px, 0px);" role="listbox">: https://www.implantcenterofmiami.com/
    • Links must have discernible text: <a dont-color-link="true" href="/root-canal-myths-vs-facts-debunking-common-misconceptions">: https://www.implantcenterofmiami.com/

    What to do Ask whoever runs your site to run Google's PageSpeed Insights on the home page and fix the accessibility problems it lists, which are mostly buttons and fields with no label.

    For your web team: 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.

    Accessibility for agents, Chrome
  • Your site offers tools to AI assistantsMust haveFail

    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.implantcenterofmiami.com/

    What to do Ask whoever runs your site to expose the main action on your site, such as booking or contacting you, as a WebMCP tool.

    For your web team: Call document.modelContext.registerTool({ name, description, inputSchema, execute }) as the home page loads, or add toolname and tooldescription attributes to the form. A name is 1 to 128 letters, digits, _, - or .

    WebMCP for developers, Chrome
  • Custom controls announce what they arePartial

    1 of the 2 audits in this goal falls short: ARIA input fields do not 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.

    • 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" style="opacity: 1; width: 2292px; transform: translate3d(-764px, 0px, 0px);" role="listbox">: https://www.implantcenterofmiami.com/

    What to do Ask the people who run your site to name every custom control, such as a date picker or a slider.

    For your web team: Give each element with an ARIA control role an accessible name through aria-label or aria-labelledby.

    Accessibility for agents, Chrome
  • Text is readablePartial

    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.33 (foreground color: #ffffff, background color: #3c93d2, font size: 11.3pt (15px), font weight: bold). Expected contrast ratio of 4.5:1: <span class="text" id="1785308425">: https://www.implantcenterofmiami.com/

    What to do Ask the people who run your site to darken pale text and to underline the links inside paragraphs.

    For your web team: Reach a contrast ratio of 4.5 to 1 for normal text, mark links in text with more than color, and leave user-scalable and maximum-scale out of the viewport tag.

    Rule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axe
  • Extra labels on controls are used correctlyPass

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

    Rule aria-roles: ARIA roles used must conform to valid values, Deque axe
  • Buttons and links are big enough to tapPass

    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.

    Accessible tap targets, Google
  • Visitors can move around the pagePass

    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 for agents, Chrome
73

Performance

Is it fast and sound for the person who clicks through?

Speed comes from real visitors of your page over the last 28 days when Google has their numbers, and from a test on a phone when it does not.

25% of your grade · 4 of 10 goals pass

  • The page responds as soon as it appearsFail

    Total Blocking Time (1,680 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 (1,680 ms): https://www.implantcenterofmiami.com/
    • Reduce JavaScript execution time (3.0 s): https://www.implantcenterofmiami.com/
    • Minimize main-thread work (6.0 s): https://www.implantcenterofmiami.com/

    What to do Ask the people who run your site to remove scripts it does not need, which keep the page busy.

    For your web team: Split long tasks and defer scripts that are not needed to start. PageSpeed lists the costliest scripts.

    Total Blocking Time (TBT), Google
  • The main content shows up quicklyPartial

    1 of the 3 audits in this goal falls short: Speed Index (3.9 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 (3.9 s): https://www.implantcenterofmiami.com/
    • Network dependency tree: https://www.implantcenterofmiami.com/
    • Font display (Est savings of 30 ms), from dwhitelabel.com: https://static-cdn.dwhitelabel.com/fonts/fontawesome-webfont.woff2?v=6

    What to do Ask the people who run your site to make the first screen load faster on phones, starting with its biggest image.

    For your web team: Serve the largest element early: preload it, avoid render-blocking scripts and styles, and cut server response time. PageSpeed lists what holds it back.

    Web Vitals, Google
  • Images are the right sizePartial

    3 of the 4 audits in this goal fall short: Improve image delivery (Est savings of 981 KiB), Serves images with low resolution, 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 981 KiB): <img src="https://irp.cdn-website.com/5fb3fd72/dms3rep/multi/Logo_Implant_Center_of_…" id="1933286430" class="" data-dm-image-path="https://irp.cdn-website.com/5fb3fd72/dms3rep/multi/Logo_Implant_Center_of_…" alt="Implant Center Of Miami logo" onerror="handleImageLoadError(this)" height="51.921875" width="171.0">, from cdn-website.com: https://irp.cdn-website.com/5fb3fd72/dms3rep/multi/Logo_Implant_Center_of_Miami_final_1EE.gif
    • Serves images with low resolution: <img src="https://irp.cdn-website.com/5fb3fd72/dms3rep/multi/opt/Screenshot+2023-02-…" alt="" id="1067708865" class="" data-dm-image-path="https://irp.cdn-website.com/5fb3fd72/dms3rep/multi/Screenshot+2023-02-23+a…" width="1280" height="996" onerror="handleImageLoadError(this)">, from cdn-website.com: https://irp.cdn-website.com/5fb3fd72/dms3rep/multi/opt/Screenshot+2023-02-23+at+4.40.27+PM-432w.png
    • Image elements do not have explicit width and height: <img src="https://irp.cdn-website.com/95237112/dms3rep/multi/opt/icoi-640w.jpg" alt="International Congress of Oral Implantologists" class="filmSlider-PanelSlider-Img" onerror="handleImageLoadError(this)" loading="lazy">, from cdn-website.com: https://irp.cdn-website.com/95237112/dms3rep/multi/opt/icoi-640w.jpg

    What to do Ask the people who run your site to resize and compress your images before they go on the page.

    For your web team: 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.

    Properly size images, Chrome
  • The page does not weigh muchPartial

    6 of the 7 audits in this goal fall short: Avoid enormous network payloads (Total size was 3,899 KiB), Reduce unused JavaScript (Est savings of 917 KiB), Reduce unused CSS (Est savings of 151 KiB), Minify JavaScript (Est savings of 3 KiB), Minify CSS (Est savings of 5 KiB), and Legacy JavaScript (Est savings of 21 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,899 KiB), from cdn-website.com: https://irp.cdn-website.com/5fb3fd72/dms3rep/multi/Logo_Implant_Center_of_Miami_final_1EE.gif
    • Reduce unused JavaScript (Est savings of 917 KiB), from Google Tag Manager: https://www.googletagmanager.com/gtm.js?id=GTM-TDFMLFR
    • Reduce unused CSS (Est savings of 151 KiB), from cdn-website.com: https://irp.cdn-website.com/fonts/css2?family=Nanum+Myeongjo:ital,wght@0,400;0,700;0,800&family=Abel:ital,wght@0,400&family=Cabin:ital,wght@0,400..700;1,400..700&family=Spinnaker:ital,wght@0,400&family=Amiko:ital,wght@0,400;0,600;0,700&family=Playball:ital,wght@0,400&family=Karla:ital,wght@0,200..800;1,200..800&family=Averia+Sans+Libre:ital,wght@0,300;0,400;0,700;1,300;1,400;1,700&family=Alegreya:ital,wght@0,400..900;1,400..900&family=Amiri:ital,wght@0,400;0,700;1,400;1,700&family=Barlow:ital,wght@0,100;0,200;0,300;0,400;0,500;0,600;0,700;0,800;0,900;1,100;1,200;1,300;1,400;1,500;1,600;1,700;1,800;1,900&family=Bebas+Neue:ital,wght@0,400&family=Be+Vietnam:ital,wght@0,100;0,200;0,300;0,400;0,600;0,700;0,800;0,900&family=Comfortaa:ital,wght@0,300..700;1,300..700&family=Dancing+Script:ital,wght@0,400..700;1,400..700&family=DM+Sans:ital,wght@0,100..1000;1,100..1000&family=DM+Serif+Display:ital,wght@0,400;1,400&family=Droid+Sans:ital,wght@0,400;0,700&family=Droid+Sans+Mono:ital,wght@0,400&family=Droid+Serif:ital,wght@0,400;0,700&family=Epilogue:ital,wght@0,100..900;1,100..900&family=Fjalla+One:ital,wght@0,400&family=Heebo:ital,wght@0,100..900;1,100..900&family=Inter:ital,wght@0,100..900;1,100..900&subset=latin-ext&display=swap

    What to do Ask the people who run your site to remove code and files the page does not use.

    For your web team: Minify scripts and styles, remove unused and duplicate code, and stop shipping legacy polyfills. PageSpeed lists the files by size.

    Avoid enormous network payloads, Chrome
  • Repeat visitors get a faster pagePartial

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

    • Use efficient cache lifetimes (Est savings of 157 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.js
    • Use efficient cache lifetimes (Est savings of 157 KiB), from Facebook: https://connect.facebook.net/signals/config/164608367643096?v=2.9.427&r=stable&domain=www.implantcenterofmiami.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 157 KiB), from elfsight.com: https://static.elfsight.com/platform/platform.js

    What to do Ask the people who run your site to let browsers keep images, scripts and styles between visits.

    For your web team: Send Cache-Control with a long max-age for fingerprinted static files, and revalidate the rest with ETag.

    Prevent unnecessary network requests with the HTTP Cache, Google
  • The page loads without errorsPartial

    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.

    • eapps.Platform throws: "Widget "8b04d04d-d889-4df9-b7c1-8acb2c1fa25a" can`t be initialized because WIDGET_NOT_FOUND" with -> div.elfsight-app-8b04d04d-d889-4df9-b7c1-8acb2c1fa25a: https://www.implantcenterofmiami.com/

    What to do Ask the people who run your site to open the page in a browser's developer tools and clear the errors it lists.

    For your web team: 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.

    Browser errors were logged to the console, Chrome
  • The page does not jump around while it loadsPass

    Cumulative Layout Shift is 0.00 for real visitors of your whole site, 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.

    Web Vitals, Google
  • Visitors are on a secure connectionPass

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

    Why HTTPS matters, Google
  • Visitors are not interrupted on arrivalPass

    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.

    Requests the geolocation permission on page load, Chrome
  • Served fastPass

    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.

    Reduce server response times (TTFB), Chrome

Watch an assistant search for this site

This scan graded the site on its own. The journey sends an assistant to search the way a shopper would, then shows where it got through and where it stopped.

Get a site that keeps itself ready

Get this site rebuilt in Clutch. It grades itself as assistants change and fixes what slips, so it stays ready on its own. You approve the new site before it goes live.

How we grade