URL: https://luxuryleafstl.com/
Platform: unknown
Archetype: premium
Run ID: 2026-04-19T06-18-18-831Z
Scanned: 2026-04-19T07:24:34.971Z
Duration: 581s
This is a monthly deep audit. The crawler performed a full-site scan including
Lighthouse performance, axe-core accessibility (WCAG 2.2 AA), cross-browser compatibility,
security headers, schema markup validation, and SEO best-practice checks.
Because this site is not a repository we control, Apex Sentinel **cannot automatically
apply fixes** — instead, each finding below includes an AI-generated plain-English
explanation + step-by-step recommended fix you can hand to a developer or execute
in your CMS directly.
Overall grade: F
| Dimension | Count | Meaning |
|---|---|---|
| Pages crawled | 23 | Full sitemap + linked pages |
| P0 (critical) | 1 | Site-down or compliance-breaking |
| P1 (urgent) | 5 | Significant revenue / SEO / UX impact |
| P2 (high) | 22 | Quality / ranking / trust degradation |
| P3 (medium) | 85 | Polish + optimization |
| "Do first" items | 5 | AI-flagged top priorities |
| Quick wins (< 30 min) | 55 | Fastest ROI items |
If you only have time for ten things this month, do these — in this order.
Page: https://luxuryleafstl.com/wp-login.php
Effort: Quick win (< 30 min)
Page: https://luxuryleafstl.com/
Effort: Quick win (< 30 min)
Page: https://luxuryleafstl.com/
Effort: Quick win (< 30 min)
Page: https://luxuryleafstl.com/
Effort: Quick win (< 30 min)
Page: https://luxuryleafstl.com/
Effort: Moderate (1-3 hours)
Page: https://luxuryleafstl.com/
Effort: Moderate (1-3 hours)
Page: https://luxuryleafstl.com/
Effort: Moderate (1-3 hours)
Page: https://luxuryleafstl.com/about-us/
Effort: Moderate (1-3 hours)
Page: https://luxuryleafstl.com/deliver-service-area/
Effort: Moderate (1-3 hours)
Page: https://luxuryleafstl.com/areas-we-serve/
Effort: Quick win (< 30 min)
tier5.exposed.artifactWhat it means (plain English)
Your WordPress admin login page is publicly accessible at /wp-login.php. This means anyone on the internet can visit that URL and attempt to guess passwords or exploit known WordPress vulnerabilities. For a premium cannabis retailer, this is a critical security gap that should be closed immediately.
Why it matters for your business: Exposed login pages are a primary target for automated attacks that can lock you out of your own site, deface your storefront, or steal customer data — directly threatening sales, reputation, and compliance with state cannabis regulations.
Technical root cause: WordPress's default login path is not blocked by your firewall or web server configuration. The site is running WordPress (platform confirmed by the /wp-login.php endpoint), but no access restrictions are in place at the server or CDN level.
Recommended fix — step by step
tier9.a11y.aria-dialog-nameWhat it means (plain English)
Your age-gate dialog (the overlay that asks visitors to confirm they're 21+) doesn't have a label that screen readers can announce. Screen reader users won't know what the dialog is for, and they can't navigate it properly. This is a WCAG accessibility violation that could expose you to legal liability.
Why it matters for your business: Inaccessible age gates can result in ADA compliance complaints, blocked traffic from accessibility-checking crawlers, and exclusion of disabled customers who use assistive technology.
Technical root cause: The dialog element with id 'baag3-gate' has role='dialog' and aria-modal='true' but lacks an aria-label, aria-labelledby, or title attribute. Screen readers have no accessible name to announce.
Recommended fix — step by step
tier9.a11y.color-contrastWhat it means (plain English)
A button on your homepage has white text (#ffffff) on a light green background (#6fad54) that fails to meet accessibility standards. The contrast ratio is 2.69:1, but WCAG AA requires at least 3:1 for normal text. This means visitors with low vision or color blindness may struggle to read the button.
Why it matters for your business: Inaccessible buttons reduce conversion rates for customers with vision impairments, expose you to ADA compliance risk, and signal poor site quality to search engines, which may penalize rankings.
Technical root cause: The button's CSS uses a light green background color that is too close in brightness to white text. The contrast calculation shows the foreground and background colors do not meet the 3:1 minimum ratio required by WCAG 2 AA.
Recommended fix — step by step
tier9.a11y.link-nameWhat it means (plain English)
Your site has 6 links that screen readers cannot identify — they contain images or are completely empty. When a visually impaired customer uses a screen reader to navigate, these links will be announced as blank or inaccessible, preventing them from clicking through to product pages or key destinations.
Why it matters for your business: Cannabis retail sites must be legally accessible; inaccessible links violate WCAG 2.1 Level A compliance and expose you to ADA litigation risk, plus they lock out customers using assistive technology.
Technical root cause: Links are built as empty anchor tags or contain only images with no alt text or aria-label attribute. Screen readers have nothing to announce.
Recommended fix — step by step
tier9.a11y.scrollable-region-focusableWhat it means (plain English)
Your website has 11 scrollable sections (primarily in review carousels) that keyboard users cannot navigate. When someone uses Tab to move through your site with a keyboard or screen reader, they can't access or scroll through these review sections. This is a serious accessibility violation that locks out keyboard and assistive technology users from key content.
Why it matters for your business: Keyboard and screen reader users (including visually impaired customers and those with mobility disabilities) cannot read your customer reviews — a critical trust signal for a luxury dispensary — and you're at legal risk under ADA/WCAG compliance expectations.
Technical root cause: The scrollable divs (likely Swiper carousel containers with class .gr-inner-body inside review slides) lack tabindex and keyboard event handlers. Swiper carousels by default are touch/mouse-only unless explicitly configured with keyboard navigation and focus management.
Recommended fix — step by step
.swiper-container or .swiper-wrapper parent; note its ID or data attribute.<script> tag); search for new Swiper( or Swiper.use( in DevTools Console or your source.keyboard: { enabled: true } and a11y: { enabled: true } to the Swiper config object; if v6–7, use keyboard: true and a11y: true.tabindex="0" to the .swiper-wrapper div or each .swiper-slide to make them focusable.tier2.links.brokenWhat it means (plain English)
Your website has 12 broken internal links—URLs pointing to pages that no longer exist or return a 404 error. Most of these are email addresses obscured by Cloudflare's anti-spam protection (the cdn-cgi/l/email-protection URLs), but one is a genuine missing page: /luxeliteclub. Broken links frustrate visitors, damage search engine rankings, and waste crawl budget—the 'allowance' Google gives to index your site.
Why it matters for your business: Broken links reduce customer trust (they can't contact you or navigate to loyalty program pages), hurt your SEO visibility for local keywords like 'dispensary near Fox Theatre,' and may block conversions if those pages were meant to drive sales or sign-ups.
Technical root cause: The /luxeliteclub page has been deleted or moved without a redirect in place. The Cloudflare email protection links are false positives—they're obfuscated email addresses that audit tools misinterpret as broken URLs, not actual navigation problems.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 170 images without alt text — descriptive labels that screen readers use to tell visually-impaired visitors what an image shows. This makes your site harder to use for people with vision loss, and it also signals to Google that you haven't optimized images for search. When Google can't understand an image, it can't rank that page as highly for related searches.
Why it matters for your business: Missing alt text reduces your organic search visibility for product and lifestyle imagery, hurts accessibility compliance (legal risk in some jurisdictions), and excludes vision-impaired customers from your site — a growing demographic for premium e-commerce.
Technical root cause: Images were likely added to the site without alt attributes being filled in during upload or page creation. This is common when using page builders, galleries, or bulk image imports without enforcing alt text fields.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your website has 163 images without alt text—descriptions that screen readers use to understand images, and that search engines use to index visual content. This means blind and low-vision visitors cannot understand your product photos, and Google cannot index them for image search. Nearly every image on your site is affected.
Why it matters for your business: You're losing accessibility compliance (legal risk in some jurisdictions), missing image search traffic for your premium products, and excluding a customer segment that uses assistive technology.
Technical root cause: Images were uploaded to the site without descriptive alt attributes in the HTML. This is typically a content management or image upload workflow issue where alt text entry was never required or enforced.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Every image on your delivery service area page lacks descriptive text (called 'alt text'). This text is read aloud by screen readers for customers with visual impairments, and it also helps search engines understand what your images show. Right now, Google can't tell what's in these 16 images, and neither can visually impaired visitors.
Why it matters for your business: Missing alt text reduces your SEO visibility for image-based searches, limits your reach to customers using accessibility tools, and may expose you to legal risk under accessibility compliance standards (ADA).
Technical root cause: Images were added to the page without alt attribute values. This is commonly caused by CMS drag-and-drop image uploads that don't prompt for descriptive text, or direct HTML/code edits that omitted the alt attribute entirely.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Every image on your Areas We Serve page lacks alternative text (alt text) — a text description that screen readers speak aloud for visually impaired visitors. This also prevents search engines from understanding what's in those images, which weakens your ability to rank for visual search queries.
Why it matters for your business: You're excluding accessibility-conscious customers and losing SEO value from product/location images that could drive organic traffic to your service areas.
Technical root cause: Images were inserted into the page without alt attributes populated in the HTML. This is typically a content management or theme configuration issue where alt fields were left blank during upload.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Five images on your delivery areas page have no descriptive text attached to them. Alt text is a short description that helps both visually-impaired visitors (using screen readers) and search engines understand what an image shows. Without it, those visitors can't access the content, and Google has less information to rank your page.
Why it matters for your business: Missing alt text limits your SEO visibility for image-based searches (local customers looking for "luxury cannabis delivery near me") and excludes potential customers using accessibility tools.
Technical root cause: Images were uploaded to the page without alt attribute text being filled in during upload or page editing.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your website has 153 images that lack descriptive alt text (alternative text shown to screen readers and search engines when images don't load). This blocks visually impaired customers from understanding product photos and details, and tells Google's crawlers nothing about what those images contain—meaning they won't appear in image search results or contribute to page ranking.
Why it matters for your business: You're losing potential customers who use assistive technology, facing legal accessibility risk, and missing image search traffic that could drive discovery of your premium products and medical offerings.
Technical root cause: Images were likely uploaded without alt attributes populated in the image manager, or a page builder template was used without enforcing alt text during publication.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 170 images without alt text — descriptive labels that tell search engines and visually impaired visitors what an image shows. This is both an accessibility issue (some customers can't see your product photos) and an SEO miss (Google can't read those images to rank them or understand your page content).
Why it matters for your business: Missing alt text limits your visibility in Google Images for product searches, reduces time-on-site for customers using screen readers, and leaves SEO value on the table for high-intent product keywords like 'premium cannabis strains STL'.
Technical root cause: Images are likely inserted via Elementor (a page builder) or directly in HTML without the alt attribute populated. Elementor's media upload interface has an optional 'alt text' field that was skipped during content creation.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 170 images missing alt text—the text that describes an image to search engines and screen readers (software used by people with vision loss). This means search engines can't understand what those images show, and customers using assistive technology get a poor experience. Because cannabis retail is heavily visual, this is a significant miss.
Why it matters for your business: Missing alt text reduces your SEO visibility for product images, strains, and dispensary photos, and excludes customers with disabilities—both a compliance risk and a lost revenue opportunity.
Technical root cause: Images were likely added to pages (especially via page builders like Elementor) without the alt attribute being filled in during upload or page creation.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your website has 170 images without alt text—descriptive text that explains what's in each image. This matters for two reasons: customers using screen readers (accessibility software) can't understand those images, and search engines can't index what's in them either. When Google can't read an image, it can't help your site rank for relevant searches.
Why it matters for your business: Missing alt text costs you SEO visibility for product photos and lifestyle imagery, and excludes customers with vision impairments—both of which reduce sales and risk legal exposure under accessibility laws.
Technical root cause: Most likely cause is bulk image uploads (especially through Elementor or a page builder) without filling in the alt text field during or after upload. If images are added via a gallery or slider plugin, the default behavior is to leave alt text blank unless manually populated.
Recommended fix — step by step
tier4.h1.missingWhat it means (plain English)
Your homepage is missing an H1 tag, which is the main headline that tells search engines (and visitors) what your page is about. Think of it like the title of a newspaper article—every article has one, and yours doesn't. This makes it harder for Google to understand what your site does.
Why it matters for your business: Without a clear H1, search engines struggle to rank your homepage for key phrases like 'luxury cannabis dispensary St. Louis' or 'premium weed delivery STL,' which directly reduces organic traffic and new customer discovery.
Technical root cause: The homepage HTML either lacks an <h1> tag entirely, or uses only lower-level headings (h2, h3, etc.). This is often caused by design-first builds where headlines are styled as images or divs instead of semantic HTML.
Recommended fix — step by step
tier4.schema.missing-coreWhat it means (plain English)
Your site includes structured data (a machine-readable format search engines use to understand your business) for Organization and WebSite, but is missing LocalBusiness schema. LocalBusiness tells Google key details like your physical address, phone number, hours, and ratings in a standardized format. For a dispensary with a physical location, this is a significant gap.
Why it matters for your business: Without LocalBusiness schema, Google is less likely to display your business prominently in local search results and Google Maps, directly reducing foot traffic and phone inquiries from customers searching 'cannabis dispensary near me' or 'luxury dispensaries in STL.'
Technical root cause: The site's JSON-LD markup was configured to include Organization and WebSite but omitted LocalBusiness, which is the schema type specifically designed for businesses with physical locations. This is a configuration oversight in the structured data implementation.
Recommended fix — step by step
tier5.header.strict-transport-securityWhat it means (plain English)
Your site is missing the Strict-Transport-Security (HSTS) header, which tells browsers to always use encrypted HTTPS connections when visiting your domain. Without it, visitors could accidentally connect via unencrypted HTTP, exposing their data to interception. This is especially critical for a cannabis retailer handling customer data and payments.
Why it matters for your business: Missing HSTS weakens your security posture, increases vulnerability to data theft during checkout, and signals to search engines and security auditors that your site has gaps—potentially hurting trust and SEO ranking.
Technical root cause: The HTTP response headers from your server (or Cloudflare intermediary) do not include the Strict-Transport-Security directive. This is a server/hosting configuration that must be explicitly enabled; it is not set by default.
Recommended fix — step by step
tier5.header.x-frame-optionsWhat it means (plain English)
Your site is missing the X-Frame-Options security header, which tells browsers whether your pages can be embedded inside frames on other websites. Without it, attackers could potentially wrap your site in a hidden frame to trick users into clicking on malicious content (called clickjacking). This header is a basic security control that takes seconds to enable.
Why it matters for your business: A clickjacking attack could redirect customers to phishing sites or unauthorized retailers, damaging trust, compliance standing, and exposing the business to legal liability in a regulated industry.
Technical root cause: The server (LiteSpeed cache engine behind Cloudflare) is not configured to send the X-Frame-Options header in HTTP responses. This is a server/hosting configuration issue, not a code problem.
Recommended fix — step by step
tier5.header.content-security-policyWhat it means (plain English)
Your site is missing a Content Security Policy (CSP) header — a security directive that tells browsers which sources of code and content are trusted. Without it, attackers could inject malicious scripts or load dangerous resources. This is especially important for a cannabis retail site handling customer data and payments.
Why it matters for your business: A missing CSP increases risk of data breaches, payment fraud, and customer trust erosion — critical vulnerabilities for a premium dispensary handling sensitive transactions and customer information.
Technical root cause: The server (LiteSpeed cache + Cloudflare) is not configured to emit a Content-Security-Policy HTTP response header. WordPress itself does not set CSP by default; it must be added via server config, a security plugin, or Cloudflare rules.
Recommended fix — step by step
tier6.a11y.small-targetsWhat it means (plain English)
Your website has 44 interactive buttons, links, and touch elements that are smaller than the minimum recommended size of 44×44 pixels when viewed on mobile devices at 320px width (like older iPhones or small Android phones). This makes them hard to tap accurately, especially for customers with larger fingers or accessibility needs. When users miss their target, they either tap the wrong link or abandon the interaction entirely.
Why it matters for your business: Mobile visitors—particularly older adults or those with dexterity challenges—will struggle to browse products, navigate menus, or complete age-verification steps, directly reducing completed purchases and increasing cart abandonment on phones.
Technical root cause: The page uses interactive elements (buttons, navigation links, product filters, checkout controls) with widths or heights below 44 pixels, either from tight CSS sizing or inadequate padding around touch targets. At narrow mobile viewports, the layout compresses these further.
Recommended fix — step by step
tier6.a11y.small-targetsWhat it means (plain English)
Your website has 45 interactive buttons, links, and form fields that are smaller than 44×44 pixels on mobile phones. This makes them hard to tap accurately, especially for customers with larger fingers, arthritis, or vision impairments. It's a legal accessibility standard (WCAG 2.5.5) that most modern sites are expected to meet.
Why it matters for your business: Customers on mobile devices—your largest traffic segment—may abandon checkout, age verification, or menu browsing due to frustration with tiny tap targets, directly reducing sales and increasing cart abandonment.
Technical root cause: The site's CSS likely sets button and link padding/sizing for desktop (where they appear larger) without responsive breakpoints that increase touch targets for mobile viewports below 600px width.
Recommended fix — step by step
@media (max-width: 600px) { button, a, input[type='button'], .tap-target { min-height: 44px; min-width: 44px; padding: 12px 16px; } } to ensure all interactive elements meet the 44×44 minimumtier6.a11y.small-targetsWhat it means (plain English)
Your website has 45 interactive buttons, links, and form fields that are smaller than 44×44 pixels when viewed on mobile phones. This violates WCAG accessibility guidelines because users—especially those with tremors, vision impairments, or large fingers—struggle to tap such small targets accurately.
Why it matters for your business: Customers on mobile devices (likely 50%+ of your traffic) experience frustration during checkout, age verification, or menu navigation, leading to abandoned carts and lost sales; you may also face ADA liability complaints.
Technical root cause: The site's responsive design either inherits desktop button sizes on mobile without scaling, or uses CSS/HTML that sets fixed pixel dimensions too small for touch interfaces.
Recommended fix — step by step
tier6.a11y.small-targetsWhat it means (plain English)
Your website has 38 buttons, links, and interactive elements that are smaller than 44×44 pixels when viewed on tablets. This makes them hard to tap accurately, especially for customers with limited dexterity or on touchscreens. WCAG 2.5.5 is an accessibility standard that requires interactive elements to meet a minimum touch-friendly size.
Why it matters for your business: Customers using tablets or mobile devices may struggle to complete purchases, navigate your menu, or access age verification—directly affecting conversion rates and potentially frustrating your demographic.
Technical root cause: Interactive elements (buttons, product links, navigation items) were likely designed for desktop and not resized responsively for tablet viewports, or padding/margin around clickable areas is insufficient.
Recommended fix — step by step
tier8.lighthouse.perf-mobileWhat it means (plain English)
Your mobile site takes about 32 seconds for the largest visual element (like a hero image or product card) to appear on screen. Industry standard is under 2.5 seconds. This delay happens because images, scripts, or stylesheets are loading slowly or are too large. Visitors on phones will see a blank or incomplete page, frustrating the buying experience.
Why it matters for your business: Mobile shoppers abandon sites that take longer than 3 seconds to load; slow mobile performance directly reduces conversion rates and harms search ranking visibility for cannabis product searches.
Technical root cause: The Largest Contentful Paint (LCP) metric of 31.9 seconds indicates unoptimized or render-blocking resources—likely uncompressed hero images, critical CSS/JavaScript loaded synchronously, or slow server response times on mobile networks.
Recommended fix — step by step
tier9.a11y.regionWhat it means (plain English)
Your site has 111 pieces of content (headings, text blocks, etc.) that aren't wrapped in semantic landmark regions like <main>, <nav>, <aside>, or <section> tags. Screen reader users rely on landmarks to navigate and understand page structure — without them, they have to read through every element linearly. This is an accessibility issue that may expose you to compliance complaints.
Why it matters for your business: Screen reader users (including disabled customers and employees) cannot efficiently navigate your dispensary site, reducing inclusivity and creating potential ADA liability — especially important for a luxury brand positioning itself as customer-centric.
Technical root cause: Elementor page builder is wrapping content in generic <div> elements instead of semantic HTML landmarks. The page likely has no <main> wrapper, and content sections lack proper <article>, <section>, or role="region" attributes.
Recommended fix — step by step
tier3.cwv.cls-desktopWhat it means (plain English)
Your homepage is experiencing cumulative layout shift (CLS) of 0.082, meaning elements on the page are moving around after they initially load. This happens when images, ads, or fonts load after the page structure is already rendered, pushing content down. While it's only slightly above Google's 0.05 threshold, users notice this jank—especially on slower connections or mobile devices.
Why it matters for your business: Layout shift frustrates customers browsing your product menu and age gate, potentially causing accidental clicks on wrong items or abandonment before they even see your menu.
Technical root cause: Your page is likely missing explicit dimensions on images or relying on web fonts that load asynchronously after layout is computed. With 1.65 MB of image data and 91 requests, unoptimized asset loading is the culprit.
Recommended fix — step by step
tier9.a11y.heading-orderWhat it means (plain English)
Your site has a heading hierarchy problem: an H5 (smallest heading level) is being used without proper H2, H3, or H4 headings above it first. Screen readers and search engines expect headings to follow a logical ladder—like an outline in a document. When you skip levels, it confuses assistive technology users and weakens your content structure for search engines.
Why it matters for your business: Visitors using screen readers may struggle to navigate your location pages, reducing accessibility compliance and potentially exposing you to ADA legal risk; search engines also use heading hierarchy to understand page topics, which can slightly diminish SEO for location-based queries.
Technical root cause: The Elementor page builder (detected from the HTML class) is rendering an H5 element without preceding H2, H3, or H4 levels. This typically happens when a template or section is reused without adjusting the heading hierarchy for the page context.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your Fox Theatre location page lack descriptive text (called 'alt text'). Screen readers—software that reads web pages aloud for blind or low-vision customers—cannot describe these images. Search engines also cannot understand what the images show, missing an SEO opportunity.
Why it matters for your business: Customers using assistive technology cannot see product photos or location details; you're also leaving search ranking power on the table for location-based queries like 'cannabis near Fox Theatre.'
Technical root cause: Images were inserted into the page without alt attributes—HTML metadata that describes the image content to machines and accessibility tools.
Recommended fix — step by step
<img src='photo.jpg'> to <img src='photo.jpg' alt='descriptive text here'>.tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your Botanical Garden location page lack alt text—descriptive labels that search engines and screen readers use to understand what images show. Without alt text, search engines can't index the image content, and customers using screen readers miss important visual information about your products or store.
Why it matters for your business: Missing alt text reduces your search ranking for image-based queries (customers searching 'cannabis near botanical garden st louis' with Google Images won't find you) and creates accessibility barriers that may violate ADA compliance expectations for retail sites.
Technical root cause: Images were inserted into the page without the alt attribute populated. This is typically an oversight during content upload or page creation, where the CMS or HTML editor allows images to be added without requiring alt text.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Four product or lifestyle images on your dispensary location page lack alt text—descriptive labels that search engines and assistive technology (screen readers used by blind/low-vision customers) rely on. Without these labels, Google cannot understand what those images show, and customers using screen readers get no context.
Why it matters for your business: Missing alt text reduces your page's relevance for image search (a key discovery channel for cannabis products) and excludes accessibility-conscious customers who use assistive devices—both harmful to traffic and brand reputation.
Technical root cause: Images were uploaded or embedded without manually adding alt attributes in the HTML code, or the CMS failed to auto-populate them during upload.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your dispensary location page don't have alt text—descriptive labels that screen readers use to tell blind and low-vision customers what the image shows. Google also uses alt text to understand your images for search results, so missing it costs you SEO visibility.
Why it matters for your business: Customers using assistive technology can't see what your products or dispensary look like, and search engines can't index these images—losing potential local SEO traffic from 'cannabis near St. Louis' searches.
Technical root cause: Images were added to the page without the HTML alt attribute being populated, either during initial build or through a CMS that didn't enforce alt text on upload.
Recommended fix — step by step
tier2.robots.no-sitemapWhat it means (plain English)
Your robots.txt file (the instruction manual you give to Google's crawlers) doesn't tell them where to find your sitemap—an organized list of all your pages. Without this pointer, search engines have to discover pages more slowly and may miss some content, especially if your site structure is complex or pages are buried deep.
Why it matters for your business: Missing the sitemap reference in robots.txt slows down how quickly Google indexes your product pages, menus, and compliance information, delaying when customers can find you in local search results.
Technical root cause: The robots.txt file exists but lacks a 'Sitemap:' line pointing to your XML sitemap URL. This is a simple configuration omission—the sitemap likely exists, but robots.txt isn't advertising it.
Recommended fix — step by step
tier2.meta.title-lengthWhat it means (plain English)
Your homepage title—the text that appears in browser tabs and search results—is only 18 characters long. Search engines prefer titles between 20 and 65 characters because longer titles give potential customers more context about what your site offers. Your current title is just barely under the minimum and doesn't mention key details like your location or that you're a cannabis dispensary.
Why it matters for your business: A weak title reduces click-through rate from search results; customers searching for 'cannabis dispensary near me' or 'luxury cannabis STL' are less likely to click your link if the preview doesn't clearly tell them what you offer.
Technical root cause: The title tag in your HTML head contains only 'Home | Luxury Leaf' without descriptive keywords or location information. Search engines use this to rank and display your site in results.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
Your homepage is missing OpenGraph tags — special code that tells Facebook, Instagram, and other social platforms how to display your site when someone shares a link. Without these tags, social shares show generic or broken previews, which damages trust and click-through rates.
Why it matters for your business: When customers share your products or promotions on social media, a missing or ugly preview reduces click-throughs and makes your brand look unprofessional compared to competitors.
Technical root cause: The page's HTML <head> section is missing og:title, og:image, og:description, and og:url meta tags that social platforms use to generate preview cards.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When this page is shared on Facebook, Instagram, or other social platforms, those sites won't know what title or image to display. Instead of showing your dispensary name and a professional photo, the link will appear as a generic, unattractive preview. This looks unprofessional and reduces click-through rates from social traffic.
Why it matters for your business: Missing social preview images directly reduce engagement and sharing of your content on platforms where your customers discover local dispensaries and promotions.
Technical root cause: The page HTML is missing OpenGraph meta tags (og:title, og:image, og:description, og:url) in the <head> section, which social platforms use to generate rich preview cards when links are shared.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your site is missing Twitter Card meta tags, which are small code snippets that tell Twitter how to display your content when someone shares a link. Without them, Twitter shows a plain text preview instead of a rich card with your image, headline, and description. For a premium cannabis retailer, this means missed opportunities to make your brand look polished when customers or influencers share your posts on social.
Why it matters for your business: Weak social sharing appearance reduces click-through rates and brand perception when customers share your product pages or blog content on Twitter/X, directly impacting traffic and brand authority.
Technical root cause: The page is missing the <meta name="twitter:card" content="summary_large_image"> tag and related Twitter-specific meta tags (twitter:title, twitter:description, twitter:image) in the HTML head section.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image"> to the page head<meta name="twitter:title" content="Your Page Title"> using the actual page headline<meta name="twitter:description" content="Brief description"> (160 characters max)<meta name="twitter:image" content="https://luxuryleafstl.com/path-to-image.jpg"> pointing to a high-quality image (minimum 200x200px, recommended 1200x628px)tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your blog post page lack descriptive alt text — the hidden labels that screen readers use to describe images to visually impaired visitors, and that search engines use to understand image content. This means some customers cannot access your content, and search engines cannot index those images.
Why it matters for your business: Missing alt text reduces your site's accessibility compliance risk, harms your ability to rank in Google Images (a source of premium cannabis retail traffic), and creates a poor experience for customers using assistive technology.
Technical root cause: Images were uploaded to the page without filling in the alt text field during upload or post editing. This is a common oversight when content is added quickly without an accessibility checklist.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares your 'About Us' page on Facebook, Instagram, or other social platforms, those sites need specific metadata tags to know what image and text to display in the preview card. Without these tags, the preview looks unprofessional or blank, and visitors are less likely to click through.
Why it matters for your business: Poor social media preview cards reduce click-through rates on shares, limiting word-of-mouth discovery and brand perception among potential customers who encounter your content on social platforms.
Technical root cause: The page is missing og:title and og:image meta tags in the HTML head section. Social platforms read these tags to generate rich preview cards; without them, they fall back to generic or missing content.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your About Us page doesn't have a Twitter Card meta tag — a small piece of code that tells Twitter (now X) how to display a preview when someone shares your link on that platform. Without it, the link appears as plain text rather than a rich preview with your logo, headline, and description.
Why it matters for your business: Missing Twitter Cards reduce click-through rates on social shares and make your brand look less polished compared to competitors; for a luxury cannabis retailer, this undermines perceived professionalism and discourages engagement on a key social platform.
Technical root cause: The page's HTML head section lacks the <meta name="twitter:card" content="summary_large_image"> tag and related Open Graph properties (og:image, og:title, og:description) that Twitter uses to construct rich previews.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:site" content="@YourTwitterHandle">, <meta property="og:title" content="About Luxury Leaf STL">, <meta property="og:description" content="[Your 160-char description]">, and <meta property="og:image" content="[URL to 1200x630px brand image]".tier2.meta.no-ogWhat it means (plain English)
When someone shares your delivery service area page on social media (Facebook, Instagram, etc.), the platform doesn't know what title or image to display. Instead of showing your branded content, it falls back to a generic preview. This is especially visible on dispensary reviews and word-of-mouth sharing.
Why it matters for your business: Missing social preview images and titles reduce click-through rates on shared links and weaken brand consistency when customers recommend your delivery area to friends on social platforms.
Technical root cause: The page is missing the Open Graph meta tags (og:title, og:image, og:description) in the HTML <head> section that social networks use to generate link previews.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your website is missing a Twitter Card meta tag, which is a snippet of code that tells Twitter how to display your page when someone shares the link on that platform. Without it, Twitter will show a generic preview instead of a custom one with your branding, product images, or key information — making shared links less appealing and less likely to drive clicks.
Why it matters for your business: Missing Twitter Cards reduce click-through rates on social shares, especially important for a premium dispensary building brand awareness and driving delivery orders through social channels.
Technical root cause: The page lacks the <meta name="twitter:card"> tag and related Twitter Card meta properties (twitter:title, twitter:description, twitter:image) in the HTML head section.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When your page is shared on Facebook, Instagram, or other social platforms, those sites look for Open Graph tags—special metadata that tells them what image and title to display in the preview. Without them, social platforms show a generic or broken preview, which looks unprofessional and reduces click-through rates from social traffic.
Why it matters for your business: Missing Open Graph tags lower engagement when customers share your service area pages on social media, reducing organic referral traffic and brand perception among potential customers discovering you through social shares.
Technical root cause: The page's HTML <head> section is missing og:title and og:image meta tags that social platforms use to generate rich previews when the URL is shared.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When your delivery page is shared on Facebook, Instagram, or other social platforms, those sites use special metadata tags (called OpenGraph tags) to display a preview—title, image, description. Without these tags, the preview looks broken or generic, which discourages clicks and makes your brand appear unprofessional.
Why it matters for your business: Missing preview images on social shares reduces click-through rates from social traffic and weakens brand perception when customers share your delivery service area with friends.
Technical root cause: The page HTML does not include og:title and og:image meta tags in the <head> section, so social platforms cannot extract rich preview data and fall back to generic or missing visuals.
Recommended fix — step by step
tier2.meta.title-lengthWhat it means (plain English)
The page title — the text that appears in browser tabs and search results — is only 19 characters long. Search engines and users expect titles between 20 and 65 characters. A longer, more descriptive title helps search engines understand the page and encourages clicks from potential customers browsing results.
Why it matters for your business: A weak title on your Deals page means fewer clicks from Google search results, directly reducing traffic to your promotions and damaging conversion opportunities.
Technical root cause: The current title 'Deals | Luxury Leaf' is truncated and lacks keyword context that would describe what deals are available (e.g., discounts, products, location).
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares your deals page on social media (Facebook, Instagram, LinkedIn), the platform doesn't have a custom image or title to display—so it falls back to a generic preview or shows nothing appealing. OpenGraph tags are snippets of code in your page header that tell social networks exactly what image and headline to show when your link is shared.
Why it matters for your business: Shared deals pages get fewer clicks and engagement on social media, reducing foot traffic from word-of-mouth promotion and organic social discovery.
Technical root cause: The page HTML is missing <meta property="og:title"> and <meta property="og:image"> tags in the <head> section, so social platforms have no instruction on how to present the content.
Recommended fix — step by step
<meta property="og:title" content="Current Deals | Luxury Leaf STL"> with your actual deals headline<meta property="og:image" content="https://luxuryleafstl.com/path-to-deals-image.jpg"> pointing to a 1200×630px image of your best current deal or storefront<meta property="og:description" content="..."> and <meta property="og:url" content="https://luxuryleafstl.com/deals/"> for completenesstier2.a11y.img-missing-altWhat it means (plain English)
Four images on your Deals page have no alternative text descriptions. Alt text is read aloud by screen readers (tools that help blind and low-vision visitors navigate your site) and also helps search engines understand what images show. Without it, those images are invisible to both assistive technology users and search algorithms.
Why it matters for your business: Missing alt text reduces your Deals page's search visibility for image-based queries, excludes disabled customers from accessing promotions, and creates legal accessibility liability under ADA/WCAG standards—especially risky for a retail site.
Technical root cause: The four images on the Deals page were added without descriptive alt attributes in the HTML. This is a common content gap when images are uploaded via CMS without populating the alt field.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares a link to your medical card page on social media or messaging apps, it won't display a custom preview image or headline — instead, it shows a generic or blank card. OpenGraph tags are snippets of code that tell Facebook, Twitter, LinkedIn, and other platforms exactly what image and text to display when your page is shared.
Why it matters for your business: Reduced click-through rates on social shares; patients discovering your dispensary through word-of-mouth social posts are less likely to click through if the preview looks unprofessional or unclear.
Technical root cause: The page's HTML header is missing og:title and og:image meta tags, which are optional but strongly recommended for shareability and brand control.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When your contact page is shared on social media (Facebook, LinkedIn, etc.), there's no custom preview—no branded image or headline. Instead, social platforms show a generic or broken preview, which looks unprofessional and reduces click-through rates from social traffic.
Why it matters for your business: Lost social media referral traffic and weakened brand presentation when customers or partners share your contact page; particularly damaging for a premium dispensary relying on word-of-mouth and social proof.
Technical root cause: The contact page HTML is missing og:title, og:description, and og:image meta tags in the <head> section. Social platforms rely on these tags to generate attractive preview cards.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your contact page don't have alt text—descriptive text that explains what each image shows. Search engines and screen readers (used by people with vision impairments) can't understand these images without it. This means you're missing SEO signals and excluding potential customers.
Why it matters for your business: Missing alt text reduces your search ranking for product/strain images, and visitors using assistive technology can't understand your product photos—shrinking your addressable audience.
Technical root cause: Images were inserted into the HTML without an 'alt' attribute, or the alt attribute is empty. This is common in page builders and CMS systems when media is uploaded without description fields being filled in.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares a link to your dispensary page on social media or messaging apps, the platforms don't know what image or title to display. Instead of showing your branded cannabis product photo and store name, they show a generic preview or nothing at all. This makes shared links look unprofessional and reduces click-through rates from social traffic.
Why it matters for your business: Lost social media visibility and referral traffic; when customers share your location or product pages, they generate weak previews that hurt engagement and brand perception among peers.
Technical root cause: The page is missing og:title, og:image, og:url, and og:description meta tags in the HTML head. Social platforms rely on these Open Graph tags to know what to display when content is shared.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares your dispensary page on Facebook, Instagram, or other social platforms, the preview that appears is generated from special HTML tags called OpenGraph metadata. Without og:title and og:image tags, social shares show a generic preview instead of an attractive, branded one that encourages clicks.
Why it matters for your business: Poor social media previews reduce click-through rates on shares, which means fewer customers discovering your location and products through word-of-mouth sharing on social platforms.
Technical root cause: The page HTML is missing the og:title and og:image meta tags in the <head> section. These are required by social platforms to generate rich preview cards.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages are missing Twitter Card meta tags—a snippet of code that tells Twitter how to display your content when someone shares a link. Without it, Twitter shows a plain text preview instead of an attractive card with your image, headline, and description. This reduces click-through rates from social media.
Why it matters for your business: Lost social sharing visibility and engagement; customers sharing your dispensary location or product pages on Twitter will see a less compelling preview, reducing traffic from that channel.
Technical root cause: The page HTML lacks the <meta name="twitter:card" content="summary_large_image"> tag and related Open Graph meta properties (og:image, og:description) that social platforms use to generate rich previews.
Recommended fix — step by step
<head> section: <meta name="twitter:card" content="summary_large_image">, <meta name="twitter:site" content="@YourTwitterHandle">, and <meta property="og:image" content="https://luxuryleafstl.com/image.jpg"> (replace with actual image URL)tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your Gateway Arch location page lack alt text — descriptive captions that screen reader users and search engines use to understand what an image shows. Without alt text, customers using assistive technology cannot see product or location photos, and search engines cannot index that visual content to help people find you.
Why it matters for your business: Missing alt text reduces your page's search ranking for location-based queries (especially important for a dispensary competing in a local market) and blocks visually impaired customers from experiencing your storefront and product photos.
Technical root cause: Images were added to the page without alt text attributes in the HTML, or the CMS/site builder did not require or capture alt text during upload.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares a link to your dispensary page on social media (Facebook, LinkedIn, etc.), the platform doesn't know what title or image to show. Instead of your professional branding, it defaults to a plain link or generic preview. This looks unprofessional and reduces click-through rates from social referrals.
Why it matters for your business: Lost social media traffic and weak brand presentation when customers share your location pages with friends or post about visiting your dispensary.
Technical root cause: The page is missing og:title and og:image meta tags in the HTML <head> section. These tags tell social platforms exactly what text and image to display when the page is shared.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When this page is shared on Facebook, Instagram, or other social platforms, those platforms don't have a preview image or custom title to display. Instead, they show a generic or broken preview, making your post look unprofessional and less likely to be clicked.
Why it matters for your business: Social sharing is a key driver of foot traffic to cannabis dispensaries; a poor preview reduces click-through rates and brand perception when customers share your location or products on social media.
Technical root cause: The page is missing og:title and og:image meta tags in the HTML <head> section. These Open Graph tags tell social platforms exactly what title and image to show when the page is shared.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages lack Twitter Card markup—special HTML tags that tell Twitter how to display your content when someone shares a link. Without this, Twitter shows only a plain text preview instead of an attractive card with your image and description.
Why it matters for your business: Lost opportunity to drive traffic and brand awareness from social sharing; competitors with rich Twitter cards get more clicks from social feeds.
Technical root cause: The page is missing the <meta name="twitter:card" content="summary_large_image"> tag and related open graph meta tags in the HTML <head> section.
Recommended fix — step by step
<head> section.</head> tag: <meta name="twitter:card" content="summary_large_image"><meta name="twitter:title" content="[PAGE_TITLE]"><meta name="twitter:description" content="[PAGE_META_DESCRIPTION]"><meta name="twitter:image" content="[URL_TO_HIGH_QUALITY_IMAGE]"> (replace bracketed values with your actual content).<meta property="og:title" content="[PAGE_TITLE]"><meta property="og:description" content="[PAGE_META_DESCRIPTION]"><meta property="og:image" content="[URL_TO_IMAGE]"><meta property="og:type" content="website">.tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your dispensary location page lack alt text—descriptive text that tells search engines and screen readers what each image shows. This means visually impaired customers using assistive technology can't understand those images, and search engines can't index them for image search results.
Why it matters for your business: Missing alt text reduces discoverability in Google Images (lost organic traffic), limits accessibility for disabled visitors (legal/reputation risk), and signals to Google that your page is less high-quality.
Technical root cause: Images are embedded in HTML without the 'alt' attribute populated. This is likely a content upload oversight rather than a technical architecture problem.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares a link to your dispensary page on social media or messaging apps, platforms like Facebook and Instagram don't know what title or image to display. Instead of showing your dispensary name and a professional photo, they might show a generic preview or nothing at all. This metadata (called OpenGraph tags) is read by social platforms to create rich, clickable previews.
Why it matters for your business: Poor social sharing appearance reduces click-through rates when customers share your location pages with friends, lowering foot traffic and online visibility among your target audience.
Technical root cause: The page HTML is missing og:title and og:image meta tags in the <head> section. These tags are not being generated automatically by the platform or template.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your St. Louis Science Center location page lack alt text — descriptive text that screen readers use to understand images, and that search engines use to index image content. This means visually impaired customers cannot understand what those images show, and Google cannot properly rank them in image search results.
Why it matters for your business: Customers using screen readers or assistive technology cannot experience your product photography, reducing accessibility and potentially losing sales; also, you're missing ranking opportunities in Google Images, which drives traffic to local dispensary pages.
Technical root cause: The images were added to the page without alt attributes in their HTML code, a common oversight when uploading images via a CMS editor without explicitly filling in the alt text field.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
OpenGraph metadata tells social media platforms (Facebook, Instagram, Twitter) how to display your content when someone shares a link. Without og:title and og:image tags, your dispensary page will show a generic preview instead of an attractive, branded snapshot. This matters especially for Instagram and Facebook, where cannabis dispensaries often run ads and share promotions.
Why it matters for your business: Missing social preview metadata reduces click-through rates on paid social campaigns and organic shares, potentially costing revenue on promotions or new customer acquisition.
Technical root cause: The page <head> section lacks og:title, og:image, og:description, and og:url meta tags that social platforms scrape to generate rich previews.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages lack a Twitter card meta tag, which is a snippet of code that tells Twitter (now X) how to display your content when someone shares a link. Without it, social shares appear plain and unbranded, reducing click-through rates from social media.
Why it matters for your business: Missed social sharing amplification—when customers or influencers share your dispensary location pages on X, the posts look generic instead of showcasing your premium brand, products, or location details, reducing traffic from social referrals.
Technical root cause: The page is missing the <meta name="twitter:card" content="summary_large_image"> tag (and related twitter:title, twitter:description, twitter:image tags) in the HTML head section.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="[page title]">, <meta name="twitter:description" content="[page description]">, and <meta name="twitter:image" content="[image URL]"> in the page head.tier2.meta.no-ogWhat it means (plain English)
When this page is shared on Facebook, Instagram, or other social platforms, those sites don't have a preview image or headline to display. Instead, visitors see a generic or broken preview, making your post look unprofessional and reducing click-through rates. OpenGraph tags are snippets of code in the page header that tell social platforms what to show.
Why it matters for your business: Premium cannabis retailers rely on word-of-mouth and social sharing; a broken social preview signals carelessness and reduces traffic from social referrals, especially damaging for a luxury brand positioning.
Technical root cause: The page is missing og:title and og:image meta tags in the HTML <head> section. Social platforms fall back to generic extraction, which rarely looks polished.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages don't have Twitter card tags, which are snippets of code that tell Twitter (now X) how to display your link when someone shares it. Without them, shared links appear as plain text instead of showing your product image, description, and brand name—missing an opportunity to make shares look professional and drive clicks back to your site.
Why it matters for your business: When customers share your dispensary location or product pages on social media, missing cards result in ugly, text-only posts that get fewer clicks and lower engagement, reducing free word-of-mouth traffic.
Technical root cause: The page is missing the <meta name="twitter:card" content="summary_large_image"> and related OpenGraph/Twitter meta tags in the HTML head section.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="[Page Title]">, <meta name="twitter:description" content="[Product/Location Description]">, and <meta name="twitter:image" content="[URL to high-quality image]"> (use a 1200×630px product or storefront photo).tier2.meta.no-ogWhat it means (plain English)
OpenGraph metadata tells social media platforms (Facebook, Instagram, LinkedIn) how to display your page when someone shares a link. Without og:title and og:image tags, your dispensary page will show a generic preview instead of an attractive branded image and headline — making shared links less compelling and lowering click-through rates.
Why it matters for your business: Lost social media engagement and reduced referral traffic; when customers share your location page on Facebook or Instagram, it won't display your logo or a professional photo, making your dispensary look less credible than competitors.
Technical root cause: The page's HTML head section is missing <meta property="og:title" content="..."> and <meta property="og:image" content="..."> tags that social platforms use to generate rich previews.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages are missing Twitter Card markup — metadata that tells Twitter how to display your content when someone shares a link. Without it, Twitter shows a plain text preview instead of a rich card with your image, headline, and description. This reduces click-through rates from social sharing.
Why it matters for your business: Lost social traffic and weaker brand presence when customers share your dispensary pages on Twitter/X; competitors with rich cards get better engagement and more clicks back to their sites.
Technical root cause: The page HTML is missing the <meta name="twitter:card" content="summary_large_image"> tag and related twitter: meta tags (twitter:title, twitter:description, twitter:image) in the document head.
Recommended fix — step by step
<meta property="og: tags — these often power Twitter cards if twitter: tags are missing.<meta name="twitter:card" content="summary_large_image"> to the head; Twitter will auto-populate from og: tags.tier2.meta.no-twitter-cardWhat it means (plain English)
Your homepage doesn't have a Twitter Card meta tag, which is a small piece of code that tells Twitter how to display your link when someone shares it on that platform. Without it, Twitter uses basic information and may not show your branding, product images, or custom description—making shared links look generic and less inviting to click.
Why it matters for your business: When customers or influencers share your dispensary's link on Twitter/X, the preview will be bland instead of showcasing your premium brand identity, potentially reducing click-through rates and brand recall on social platforms.
Technical root cause: The page HTML is missing the <meta name="twitter:card" content="summary_large_image"> tag and related Twitter Open Graph tags (twitter:title, twitter:description, twitter:image) in the <head> section.
Recommended fix — step by step
<head> section: <meta name="twitter:card" content="summary_large_image">, <meta name="twitter:site" content="@YourTwitterHandle">, <meta name="twitter:title" content="Your Homepage Title">, <meta name="twitter:description" content="Your brand description">, and <meta name="twitter:image" content="https://luxuryleafstl.com/path-to-high-res-logo-or-hero-image.jpg">tier2.meta.no-twitter-cardWhat it means (plain English)
Your site is missing a Twitter Card meta tag, which tells Twitter how to display your content when someone shares a link on that platform. Without it, Twitter shows a generic preview that may not showcase your products or branding effectively.
Why it matters for your business: Shared links to your product pages and service areas on Twitter get less visual appeal, reducing click-through rates and brand recognition among potential customers on social media.
Technical root cause: The page lacks the <meta name="twitter:card" content="summary_large_image"> tag in its HTML head section, and likely missing associated og:image or twitter:image tags for preview images.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your pages are missing Twitter Card meta tags, which are snippets of code that tell Twitter how to display your content when someone shares a link. Without them, Twitter shows a basic preview instead of a rich, branded one with your image and description — making shared posts look less professional.
Why it matters for your business: When customers share your delivery areas or product pages on Twitter/X, they appear generic instead of branded, reducing click-through rates and perceived legitimacy for a luxury cannabis brand.
Technical root cause: The page HTML lacks <meta name="twitter:card" content="summary_large_image"> and related Twitter Card meta tags in the document head.
Recommended fix — step by step
<head> section of your page template (or every page if hand-coded): <meta name="twitter:card" content="summary_large_image">, <meta name="twitter:site" content="@YourTwitterHandle">, <meta name="twitter:title" content="Page Title">, <meta name="twitter:description" content="Brief description">, <meta name="twitter:image" content="https://luxuryleafstl.com/path-to-image.jpg">twitter:image URL points to a high-quality image at least 1200×630 pixels for the summary_large_image card typetier2.meta.no-twitter-cardWhat it means (plain English)
Your /deals/ page is missing a Twitter Card meta tag — a snippet of code that tells Twitter how to display your content when someone shares the link. Without it, Twitter will generate a generic preview instead of showing your curated product image, headline, and description, making shared links less eye-catching.
Why it matters for your business: Fewer clicks and engagement when customers share your deals on social media, reducing organic reach and traffic to your promotions.
Technical root cause: The page's HTML head section lacks the <meta name="twitter:card" content="summary_large_image"> tag and related Open Graph properties needed for social preview optimization.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="Luxury Leaf STL Deals">, <meta name="twitter:description" content="[your deal description]">, and <meta name="twitter:image" content="[URL to a 1200x630px image]">.tier2.meta.no-twitter-cardWhat it means (plain English)
Your site is missing a Twitter Card meta tag, which tells Twitter how to display your content when someone shares a link to your site on Twitter or X. Without this tag, Twitter shows a plain text preview instead of a rich preview with your brand imagery and description, making shared links less visually appealing and less likely to drive clicks.
Why it matters for your business: Missing Twitter Cards reduce social media engagement and click-through rates when customers share your product pages or medical card information on social platforms, limiting organic reach.
Technical root cause: The page lacks the meta tag <meta name="twitter:card" content="summary_large_image"> (or another valid Twitter Card type) in the HTML head section.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your contact page is missing a Twitter Card meta tag, which tells Twitter how to display your page when someone shares the link on that platform. Without it, Twitter will use a generic preview that may not show your branding or the most relevant information.
Why it matters for your business: Lost opportunity to control how your dispensary appears when customers or industry partners share your contact page on Twitter/X, potentially reducing click-through rates and brand consistency.
Technical root cause: The page's HTML head section lacks the <meta name="twitter:card" tag, which is a standardized but optional enhancement that social platforms check for when generating link previews.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image"> and optionally add <meta name="twitter:title" content="Contact Luxury Leaf STL"> and <meta name="twitter:description" content="Reach out to our premium cannabis dispensary"> and <meta name="twitter:image" content="[URL to 1200x630px brand logo or hero image]">tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages don't include Twitter Card meta tags, which are small code snippets that tell Twitter how to display your content when someone shares a link on that platform. Without them, Twitter shows a plain text preview instead of an attractive card with your image and description, making shared links less engaging.
Why it matters for your business: Missing Twitter Cards reduce click-through rates when customers or advocates share your dispensary location pages on Twitter/X, limiting organic social discovery and foot traffic referrals.
Technical root cause: The page HTML is missing the <meta name="twitter:card" content="summary_large_image"> tag and related Twitter-specific meta tags (twitter:title, twitter:description, twitter:image) in the document head.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image"> to the <head> of your dispensary location pages.<meta name="twitter:title" content="[Page Title]"> and <meta name="twitter:description" content="[Meta Description]"> matching your OG tags.<meta name="twitter:image" content="[URL to 1200x630px image]"> pointing to a high-quality product or storefront photo.tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages lack Twitter Card metadata, which tells Twitter how to display your content when someone shares a link on that platform. Without this, Twitter shows a plain text preview instead of an attractive card with your image and description, reducing click-through rates from social sharing.
Why it matters for your business: Missed social amplification opportunity—customers sharing your dispensary location or product pages on Twitter/X will generate less engaging previews, lowering traffic from social referrals.
Technical root cause: The page is missing the <meta name="twitter:card" content="summary_large_image"> tag and related Twitter meta tags (twitter:title, twitter:description, twitter:image) in the HTML head section.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="[Page Title]">, <meta name="twitter:description" content="[Page Description]">, <meta name="twitter:image" content="[URL to 1200x630px image]"> — use the same image and description as your Open Graph tags if they existtier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages are missing Twitter Card metadata—special HTML tags that control how your content looks when shared on Twitter/X. Without these tags, your links appear as plain text without preview images or formatted descriptions, making them less likely to be clicked or shared.
Why it matters for your business: Missing Twitter Cards reduce click-through rates on social shares and make your dispensary look less professional compared to competitors when customers share your product pages on social media.
Technical root cause: The page lacks <meta name="twitter:card"> and related tags (twitter:title, twitter:description, twitter:image) in the HTML head section. These are optional but improve social sharing appearance.
Recommended fix — step by step
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier2.meta.title-lengthDetail
Title should be 20-65 chars. Got: "Home | Luxury Leaf"
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.title-lengthDetail
Title should be 20-65 chars. Got: "Home | Luxury Leaf"
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.title-lengthDetail
Title should be 20-65 chars. Got: "Home | Luxury Leaf"
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.title-lengthDetail
Title should be 20-65 chars. Got: "Blog | Luxury Leaf"
tier2.meta.description-lengthDetail
Description should be 80-160 chars.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier3.weight.total-mobileDetail
Total transfer exceeds 2500KB budget.
tier3.weight.total-desktopDetail
Total transfer exceeds 2500KB budget.
tier5.header.x-content-type-optionsDetail
x-content-type-options not present on homepage response. Affects fortress score and CSP posture.
tier5.header.referrer-policyDetail
referrer-policy not present on homepage response. Affects fortress score and CSP posture.
tier5.header.permissions-policyDetail
permissions-policy not present on homepage response. Affects fortress score and CSP posture.
tier5.fortress.ssl-gradeDetail
Qualys SSL Labs: SSL Labs HTTP 400. Aim for A+ via strong TLS 1.3, HSTS, CAA, and preload.
tier5.fortress.dnssec-missingDetail
DNSSEC adds cryptographic verification to DNS responses. Consider enabling via your registrar.
tier5.fortress.caa-missingDetail
CAA records restrict which CAs may issue certs for your domain, preventing rogue issuance. Add CAA for letsencrypt.org / digicert.com / etc.
tier5.fortress.dmarc-weakDetail
DMARC published at p=none — monitoring mode only. After 2-4 weeks of clean reports, tighten to p=quarantine → p=reject.
tier8.lighthouse.a11y-mobileDetail
Score 89 is below target 95. See HTML report for details.
tier8.lighthouse.seo-mobileDetail
Score 85 is below target 95. See HTML report for details.
tier8.lh-opportunity.uses-rel-preconnect-mobileDetail
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/" target="_blank" rel="noreferrer">Learn how to preconnect to required origins.
tier8.lh-opportunity.render-blocking-resources-mobileDetail
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources/" target="_blank" rel="noreferrer">Learn how to eliminate render-blocking resources.
tier8.lh-opportunity.unminified-javascript-mobileDetail
Minifying JavaScript files can reduce payload sizes and script parse time. https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript/" target="_blank" rel="noreferrer">Learn how to minify JavaScript.
tier8.lh-opportunity.unused-css-rules-mobileDetail
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/" target="_blank" rel="noreferrer">Learn how to reduce unused CSS.
tier8.lh-opportunity.unused-javascript-mobileDetail
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/" target="_blank" rel="noreferrer">Learn how to reduce unused JavaScript.
tier-revenue.dutchie.iframe-absentDetail
No Dutchie iframe detected. If this client uses a different menu provider, add it to clients.yaml dutchieSlug=null + we'll stop flagging.
Grouped by URL — useful when working through the site one page at a time.
_39 findings on this page_
Your website has 12 broken internal links—URLs pointing to pages that no longer exist or return a 404 error. Most of these are email addresses obscured by Cloudflare's anti-spam protection (the cdn-cg
Your age-gate dialog (the overlay that asks visitors to confirm they're 21+) doesn't have a label that screen readers can announce. Screen reader users won't know what the dialog is for, and they can'
A button on your homepage has white text (#ffffff) on a light green background (#6fad54) that fails to meet accessibility standards. The contrast ratio is 2.69:1, but WCAG AA requires at least 3:1 for
Your site has 6 links that screen readers cannot identify — they contain images or are completely empty. When a visually impaired customer uses a screen reader to navigate, these links will be announc
Your website has 11 scrollable sections (primarily in review carousels) that keyboard users cannot navigate. When someone uses Tab to move through your site with a keyboard or screen reader, they can'
Your site has 170 images without alt text — descriptive labels that screen readers use to tell visually-impaired visitors what an image shows. This makes your site harder to use for people with vision
Your homepage is experiencing cumulative layout shift (CLS) of 0.082, meaning elements on the page are moving around after they initially load. This happens when images, ads, or fonts load after the p
Your homepage is missing an H1 tag, which is the main headline that tells search engines (and visitors) what your page is about. Think of it like the title of a newspaper article—every article has one
Your site includes structured data (a machine-readable format search engines use to understand your business) for Organization and WebSite, but is missing LocalBusiness schema. LocalBusiness tells Goo
Your site is missing the Strict-Transport-Security (HSTS) header, which tells browsers to always use encrypted HTTPS connections when visiting your domain. Without it, visitors could accidentally conn
Your site is missing the X-Frame-Options security header, which tells browsers whether your pages can be embedded inside frames on other websites. Without it, attackers could potentially wrap your sit
Your site is missing a Content Security Policy (CSP) header — a security directive that tells browsers which sources of code and content are trusted. Without it, attackers could inject malicious scrip
Your website has 44 interactive buttons, links, and touch elements that are smaller than the minimum recommended size of 44×44 pixels when viewed on mobile devices at 320px width (like older iPhones o
Your website has 45 interactive buttons, links, and form fields that are smaller than 44×44 pixels on mobile phones. This makes them hard to tap accurately, especially for customers with larger finger
Your website has 45 interactive buttons, links, and form fields that are smaller than 44×44 pixels when viewed on mobile phones. This violates WCAG accessibility guidelines because users—especially th
Your website has 38 buttons, links, and interactive elements that are smaller than 44×44 pixels when viewed on tablets. This makes them hard to tap accurately, especially for customers with limited de
Your mobile site takes about 32 seconds for the largest visual element (like a hero image or product card) to appear on screen. Industry standard is under 2.5 seconds. This delay happens because image
Your site has a heading hierarchy problem: an H5 (smallest heading level) is being used without proper H2, H3, or H4 headings above it first. Screen readers and search engines expect headings to follo
Your site has 111 pieces of content (headings, text blocks, etc.) that aren't wrapped in semantic landmark regions like <main>, <nav>, <aside>, or <section> tags. Screen reader users rely on landmarks
Your homepage title—the text that appears in browser tabs and search results—is only 18 characters long. Search engines prefer titles between 20 and 65 characters because longer titles give potential
Your homepage is missing OpenGraph tags — special code that tells Facebook, Instagram, and other social platforms how to display your site when someone shares a link. Without these tags, social shares
Your homepage doesn't have a Twitter Card meta tag, which is a small piece of code that tells Twitter how to display your link when someone shares it on that platform. Without it, Twitter uses basic i
_5 findings on this page_
_4 findings on this page_
The page title — the text that appears in browser tabs and search results — is only 19 characters long. Search engines and users expect titles between 20 and 65 characters. A longer, more descriptive
When someone shares your deals page on social media (Facebook, Instagram, LinkedIn), the platform doesn't have a custom image or title to display—so it falls back to a generic preview or shows nothing
Your /deals/ page is missing a Twitter Card meta tag — a snippet of code that tells Twitter how to display your content when someone shares the link. Without it, Twitter will generate a generic previe
Four images on your Deals page have no alternative text descriptions. Alt text is read aloud by screen readers (tools that help blind and low-vision visitors navigate your site) and also helps search
_4 findings on this page_
Your site has 170 images without alt text — descriptive labels that tell search engines and visually impaired visitors what an image shows. This is both an accessibility issue (some customers can't se
_4 findings on this page_
Your site has 170 images missing alt text—the text that describes an image to search engines and screen readers (software used by people with vision loss). This means search engines can't understand w
_4 findings on this page_
Your website has 170 images without alt text—descriptive text that explains what's in each image. This matters for two reasons: customers using screen readers (accessibility software) can't understand
_3 findings on this page_
When this page is shared on Facebook, Instagram, or other social platforms, those sites won't know what title or image to display. Instead of showing your dispensary name and a professional photo, the
Your site is missing Twitter Card meta tags, which are small code snippets that tell Twitter how to display your content when someone shares a link. Without them, Twitter shows a plain text preview in
Four images on your blog post page lack descriptive alt text — the hidden labels that screen readers use to describe images to visually impaired visitors, and that search engines use to understand ima
_3 findings on this page_
Your website has 163 images without alt text—descriptions that screen readers use to understand images, and that search engines use to index visual content. This means blind and low-vision visitors ca
When someone shares your 'About Us' page on Facebook, Instagram, or other social platforms, those sites need specific metadata tags to know what image and text to display in the preview card. Without
Your About Us page doesn't have a Twitter Card meta tag — a small piece of code that tells Twitter (now X) how to display a preview when someone shares your link on that platform. Without it, the link
_3 findings on this page_
Every image on your delivery service area page lacks descriptive text (called 'alt text'). This text is read aloud by screen readers for customers with visual impairments, and it also helps search eng
When someone shares your delivery service area page on social media (Facebook, Instagram, etc.), the platform doesn't know what title or image to display. Instead of showing your branded content, it f
Your website is missing a Twitter Card meta tag, which is a snippet of code that tells Twitter how to display your page when someone shares the link on that platform. Without it, Twitter will show a g
_3 findings on this page_
Every image on your Areas We Serve page lacks alternative text (alt text) — a text description that screen readers speak aloud for visually impaired visitors. This also prevents search engines from un
When your page is shared on Facebook, Instagram, or other social platforms, those sites look for Open Graph tags—special metadata that tells them what image and title to display in the preview. Withou
Your site is missing a Twitter Card meta tag, which tells Twitter how to display your content when someone shares a link on that platform. Without it, Twitter shows a generic preview that may not show
_3 findings on this page_
Five images on your delivery areas page have no descriptive text attached to them. Alt text is a short description that helps both visually-impaired visitors (using screen readers) and search engines
When your delivery page is shared on Facebook, Instagram, or other social platforms, those sites use special metadata tags (called OpenGraph tags) to display a preview—title, image, description. Witho
Your pages are missing Twitter Card meta tags, which are snippets of code that tell Twitter how to display your content when someone shares a link. Without them, Twitter shows a basic preview instead
_3 findings on this page_
Your website has 153 images that lack descriptive alt text (alternative text shown to screen readers and search engines when images don't load). This blocks visually impaired customers from understand
When someone shares a link to your medical card page on social media or messaging apps, it won't display a custom preview image or headline — instead, it shows a generic or blank card. OpenGraph tags
Your site is missing a Twitter Card meta tag, which tells Twitter how to display your content when someone shares a link to your site on Twitter or X. Without this tag, Twitter shows a plain text prev
_3 findings on this page_
When your contact page is shared on social media (Facebook, LinkedIn, etc.), there's no custom preview—no branded image or headline. Instead, social platforms show a generic or broken preview, which l
Your contact page is missing a Twitter Card meta tag, which tells Twitter how to display your page when someone shares the link on that platform. Without it, Twitter will use a generic preview that ma
Four images on your contact page don't have alt text—descriptive text that explains what each image shows. Search engines and screen readers (used by people with vision impairments) can't understand t
_3 findings on this page_
When someone shares a link to your dispensary page on social media or messaging apps, the platforms don't know what image or title to display. Instead of showing your branded cannabis product photo an
Your product pages don't include Twitter Card meta tags, which are small code snippets that tell Twitter how to display your content when someone shares a link on that platform. Without them, Twitter
Four images on your Fox Theatre location page lack descriptive text (called 'alt text'). Screen readers—software that reads web pages aloud for blind or low-vision customers—cannot describe these imag
_3 findings on this page_
When someone shares your dispensary page on Facebook, Instagram, or other social platforms, the preview that appears is generated from special HTML tags called OpenGraph metadata. Without og:title and
Your product pages are missing Twitter Card meta tags—a snippet of code that tells Twitter how to display your content when someone shares a link. Without it, Twitter shows a plain text preview instea
Four images on your Gateway Arch location page lack alt text — descriptive captions that screen reader users and search engines use to understand what an image shows. Without alt text, customers using
_3 findings on this page_
When someone shares a link to your dispensary page on social media (Facebook, LinkedIn, etc.), the platform doesn't know what title or image to show. Instead of your professional branding, it defaults
Your product pages lack Twitter Card metadata, which tells Twitter how to display your content when someone shares a link on that platform. Without this, Twitter shows a plain text preview instead of
Four images on your Botanical Garden location page lack alt text—descriptive labels that search engines and screen readers use to understand what images show. Without alt text, search engines can't in
_3 findings on this page_
When this page is shared on Facebook, Instagram, or other social platforms, those platforms don't have a preview image or custom title to display. Instead, they show a generic or broken preview, makin
Your product pages lack Twitter Card markup—special HTML tags that tell Twitter how to display your content when someone shares a link. Without this, Twitter shows only a plain text preview instead of
Four images on your dispensary location page lack alt text—descriptive text that tells search engines and screen readers what each image shows. This means visually impaired customers using assistive t
_3 findings on this page_
When someone shares a link to your dispensary page on social media or messaging apps, platforms like Facebook and Instagram don't know what title or image to display. Instead of showing your dispensar
Your product pages are missing Twitter Card metadata—special HTML tags that control how your content looks when shared on Twitter/X. Without these tags, your links appear as plain text without preview
Four images on your St. Louis Science Center location page lack alt text — descriptive text that screen readers use to understand images, and that search engines use to index image content. This means
_3 findings on this page_
OpenGraph metadata tells social media platforms (Facebook, Instagram, Twitter) how to display your content when someone shares a link. Without og:title and og:image tags, your dispensary page will sho
Your product pages lack a Twitter card meta tag, which is a snippet of code that tells Twitter (now X) how to display your content when someone shares a link. Without it, social shares appear plain an
Four product or lifestyle images on your dispensary location page lack alt text—descriptive labels that search engines and assistive technology (screen readers used by blind/low-vision customers) rely
_3 findings on this page_
When this page is shared on Facebook, Instagram, or other social platforms, those sites don't have a preview image or headline to display. Instead, visitors see a generic or broken preview, making you
Your product pages don't have Twitter card tags, which are snippets of code that tell Twitter (now X) how to display your link when someone shares it. Without them, shared links appear as plain text i
Four images on your dispensary location page don't have alt text—descriptive labels that screen readers use to tell blind and low-vision customers what the image shows. Google also uses alt text to un
_3 findings on this page_
OpenGraph metadata tells social media platforms (Facebook, Instagram, LinkedIn) how to display your page when someone shares a link. Without og:title and og:image tags, your dispensary page will show
Your product pages are missing Twitter Card markup — metadata that tells Twitter how to display your content when someone shares a link. Without it, Twitter shows a plain text preview instead of a ric
_3 findings on this page_
_3 findings on this page_
_1 finding on this page_
Your robots.txt file (the instruction manual you give to Google's crawlers) doesn't tell them where to find your sitemap—an organized list of all your pages. Without this pointer, search engines have
_1 finding on this page_
Your WordPress admin login page is publicly accessible at /wp-login.php. This means anyone on the internet can visit that URL and attempt to guess passwords or exploit known WordPress vulnerabilities.
_Generated by Apex Sentinel Monthly Audit · 2026-04-19T07:34:15.791Z · Powered by Bud Authority._
Generated by Apex Sentinel · © 2026 Bud Authority