URL: https://litmospheres.com/
Platform: unknown
Archetype: fun
Run ID: 2026-04-19T06-18-18-831Z
Scanned: 2026-04-19T06:46:48.878Z
Duration: 728s
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 | 18 | Full sitemap + linked pages |
| P0 (critical) | 1 | Site-down or compliance-breaking |
| P1 (urgent) | 3 | Significant revenue / SEO / UX impact |
| P2 (high) | 25 | Quality / ranking / trust degradation |
| P3 (medium) | 74 | Polish + optimization |
| "Do first" items | 4 | AI-flagged top priorities |
| Quick wins (< 30 min) | 54 | Fastest ROI items |
If you only have time for ten things this month, do these — in this order.
Page: https://litmospheres.com/wp-login.php
Effort: Moderate (1-3 hours)
Page: https://litmospheres.com/
Effort: Quick win (< 30 min)
Page: https://litmospheres.com/
Effort: Quick win (< 30 min)
Page: https://litmospheres.com/
Effort: Moderate (1-3 hours)
Page: https://litmospheres.com/services/
Effort: Quick win (< 30 min)
Page: https://litmospheres.com/contact/
Effort: Quick win (< 30 min)
Page: https://litmospheres.com/about-us/
Effort: Quick win (< 30 min)
Page: https://litmospheres.com/dispensary-schodack-ny/
Effort: Moderate (1-3 hours)
Page: https://litmospheres.com/dispensary-near-east-greenbush-ny/
Effort: Moderate (1-3 hours)
Page: https://litmospheres.com/?elementor_library=default-kit
Effort: Quick win (< 30 min)
tier5.exposed.artifactWhat it means (plain English)
Your WordPress login page is publicly accessible at /wp-login.php. This is a common attack target where hackers try to break into your site by guessing usernames and passwords. While WordPress is installed on your server, exposing this path makes it easier for automated attacks to find and attempt to breach your admin area.
Why it matters for your business: An unauthorized login compromise could allow attackers to inject malware, deface your site, steal customer data including age-verification records, or take your dispensary offline—directly threatening sales and compliance.
Technical root cause: WordPress login pages are enabled by default. Your server is not blocking or redirecting this sensitive path at the edge (CDN/firewall level), leaving it openly accessible to the internet.
Recommended fix — step by step
tier5.mixed-contentWhat it means (plain English)
Your website is served over HTTPS (secure), but it's trying to load a resource from an HTTP URL (insecure). Modern browsers block or warn about this, which can degrade trust and break functionality. In this case, it's a reference to http://oasas.ny.gov/HOPELine — likely a link to New York's addiction helpline resource.
Why it matters for your business: Mixed-content warnings erode customer trust, especially critical in cannabis retail where compliance and legitimacy are already under scrutiny. It may also trigger browser security warnings that discourage purchases.
Technical root cause: A link or resource embed in your page points to the HTTP version of a domain instead of HTTPS. The external domain (oasas.ny.gov) may not support HTTPS, or the link was simply copy-pasted with http:// instead of https://.
Recommended fix — step by step
tier9.a11y.aria-dialog-nameWhat it means (plain English)
Your age-gate dialog (the overlay that appears when visitors first land on your site) doesn't have a label that screen readers can announce. Screen reader users don't know what the dialog is for or how to interact with it. This is a critical accessibility barrier that may prevent some users from even entering your site.
Why it matters for your business: Screen reader users—including those with visual disabilities—cannot navigate your age gate, effectively locking them out of your site and exposing you to ADA/AODA compliance risk.
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 to announce its purpose to assistive technology.
Recommended fix — step by step
tier10.journey.failedWhat it means (plain English)
Your site is trying to load a JavaScript module (a .js file imported with type="module") but the server is sending back an HTML page instead. This breaks the age gate and menu functionality on the homepage. Modern browsers strictly enforce this check for security reasons, so the module refuses to load and the page becomes non-functional.
Why it matters for your business: Visitors cannot proceed past the age gate or access your menu, preventing sales and creating a broken user experience that damages trust and compliance appearance.
Technical root cause: A JavaScript import statement (likely import { ... } from 'path/to/file.js') is pointing to a URL that returns an HTML 404 error page instead of the actual JavaScript file. This usually happens when a script path is wrong, the file is in the wrong location, or the server isn't configured to serve .js files with the correct MIME type (application/javascript).
Recommended fix — step by step
/js/module.js vs /assets/js/module.js)..js files with Content-Type: application/javascript header.tier2.a11y.img-missing-altWhat it means (plain English)
Seven images on your Services page don't have alt text — short descriptive labels that explain what the image shows. Screen readers used by visually impaired customers can't describe these images, and search engines can't index them properly. This creates a barrier for accessibility and loses a small but real SEO signal.
Why it matters for your business: Visitors using screen readers get a worse experience, potentially leaving your site; Google also ranks pages with complete alt text slightly higher, affecting your visibility in search results.
Technical root cause: Images were likely added to the HTML or CMS without the alt attribute populated, or the alt attribute was left blank.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your contact page has 5 out of 6 images missing alt text — short descriptions that explain what each image shows. Search engines can't read images, so they rely on alt text to understand your content. Screen reader users (people with vision loss) also depend on alt text to know what's on the page.
Why it matters for your business: Missing alt text on your contact page hurts SEO ranking for image search, reduces accessibility for customers using assistive technology, and may expose you to accessibility compliance complaints under ADA/AODA standards.
Technical root cause: Images in HTML are missing the 'alt' attribute, or the attribute is empty. This is typically a template or CMS oversight during page creation.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Seven images on your About Us 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 unlabeled images, so they get skipped entirely. This means lost SEO value and a worse experience for accessible browsing.
Why it matters for your business: Missing alt text hurts your search ranking for image-related queries (like 'cannabis dispensary team' or 'local weed shop staff') and excludes customers using assistive technology — a legal accessibility concern for cannabis retailers in many jurisdictions.
Technical root cause: Images were uploaded to the page without alt attribute metadata. Most CMS platforms provide an 'alt text' field during image upload that was left blank.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Twelve images on your Schodack dispensary page are missing alt text — descriptive labels that screen readers announce to visually impaired visitors and that search engines read to understand image content. This creates a barrier for accessibility and reduces the page's search visibility for image-based queries.
Why it matters for your business: Visitors using screen readers cannot understand product photos or location visuals, lowering trust and accessibility compliance risk; Google also ranks pages with properly described images higher, especially important for cannabis retail where product imagery drives conversions.
Technical root cause: Images were added to the page without the alt attribute populated. This is often due to manual image uploads without a content management workflow that enforces alt text entry.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Twelve images on your East Greenbush dispensary page don't have alt text—descriptive labels that screen readers announce to blind and low-vision visitors, and that search engines use to understand image content. This creates a barrier for accessibility and misses an SEO opportunity, since Google can't index what those images contain.
Why it matters for your business: You're losing potential customers who use screen readers, and search engines can't index your product photos, strains, or store imagery—reducing your local search visibility for 'cannabis near me' queries.
Technical root cause: Images were inserted into the page without the HTML alt attribute populated, likely during content management or bulk image uploads where alt text wasn't filled in.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Eleven images on your site are missing alt text — a text description that explains what each image shows. Screen readers used by visually impaired customers can't describe these images, and search engines can't understand what they depict, which reduces your visibility in Google Images and general search results.
Why it matters for your business: Missing alt text blocks accessibility compliance (risking legal issues in some jurisdictions) and costs you organic traffic, especially from image search where cannabis lifestyle and product imagery drive discovery.
Technical root cause: Images were added to the site without filling in the alt text field during upload or page editing. Most likely, the Elementor page builder's image blocks were inserted without alt attributes populated.
Recommended fix — step by step
tier3.perf.mobile-failWhat it means (plain English)
Our automated performance testing tool timed out while trying to load your homepage on a mobile connection — it waited 60 seconds and never received a signal that the page had finished loading all resources. This suggests either the homepage is taking extremely long to load, or something is blocking the page from signaling it's ready (such as a script that never completes or a third-party service that's stalled).
Why it matters for your business: Customers visiting on mobile — likely a significant portion of dispensary traffic — may experience a blank or slow-loading page, leading to abandonment before they can browse products or check your hours; search engines also penalize slow mobile sites in rankings.
Technical root cause: The page is either genuinely slow to load (large unoptimized images, render-blocking scripts, or heavy third-party embeds), or a JavaScript or tracking service is hung and preventing the browser from finishing its load cycle.
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 HTTPS when connecting to your domain. Without it, visitors could be vulnerable to man-in-the-middle attacks if they accidentally visit via HTTP first. This is especially critical for a cannabis retailer handling age verification and customer data.
Why it matters for your business: Missing HSTS weakens customer trust and data security, and can negatively impact search rankings—Google favors sites with strong security headers.
Technical root cause: The server (hosted on Bluehost via Cloudflare) is not configured to send the Strict-Transport-Security header in HTTP responses. This is a server-side configuration issue, not a code problem.
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 or iframes on other websites. Without this header, malicious sites could embed your content in a hidden frame to trick users or steal data — a technique called clickjacking. This is a standard security control that takes minutes to add.
Why it matters for your business: A clickjacking attack could trick customers into unknowingly authorizing transactions, sharing payment info, or completing unintended actions while they think they're interacting with your dispensary site, directly exposing you to liability and customer trust damage.
Technical root cause: The X-Frame-Options header is not being set in your server or WordPress configuration. Your site runs on WordPress (evidenced by wp-json links in headers) hosted on Bluehost (via Cloudflare), and the header needs to be added either at the WordPress level or via your hosting control panel.
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 rule that tells browsers which external resources (scripts, images, fonts) are allowed to load. Without it, attackers could inject malicious code more easily. This is a standard security best practice for all websites, especially those handling customer data.
Why it matters for your business: A missing CSP weakens your site's defenses against code injection attacks, which could compromise customer data, payment information, or your reputation — critical for a retail business handling transactions.
Technical root cause: The HTTP response headers from your server do not include a Content-Security-Policy directive. Your site is hosted on Bluehost (via Cloudflare), and CSP must be set either in your WordPress site settings, .htaccess file, or via your hosting control panel.
Recommended fix — step by step
tier5.cookie.no-secureWhat it means (plain English)
Your website sets a cookie (nfd-enable-cf-opt) without the Secure flag. This flag tells browsers to only send the cookie over encrypted HTTPS connections, not unencrypted HTTP. Without it, if a visitor's connection is downgraded or intercepted, that cookie data could be exposed to attackers.
Why it matters for your business: A compromised cookie could allow attackers to impersonate customers, access their accounts, or tamper with their orders — damaging trust and exposing you to payment fraud and compliance violations.
Technical root cause: The Set-Cookie HTTP response header for nfd-enable-cf-opt is missing the Secure attribute. This is typically set by your hosting/CDN layer (Cloudflare appears involved) or server-side code that generates cookies.
Recommended fix — step by step
tier5.fortress.dmarc-missingWhat it means (plain English)
Your domain has a valid SPF record (which helps prevent email spoofing) but is missing a DMARC policy—a set of instructions that tell email providers how to handle emails claiming to be from your domain. Without DMARC, bad actors can more easily send fake emails that appear to come from Litmosphere, damaging trust with customers and potentially landing legitimate emails in spam folders.
Why it matters for your business: Missing DMARC increases the risk that your marketing emails, order confirmations, and customer communications land in spam or are spoofed by scammers, eroding customer trust and reducing engagement on time-sensitive compliance or promotional messages.
Technical root cause: DMARC is published as a DNS text record at _dmarc.litmospheres.com; this record does not exist. Many sites skip DMARC initially because it requires DNS changes and can appear technical, but it is a standard email authentication layer that takes minimal effort to deploy.
Recommended fix — step by step
tier6.a11y.small-targetsWhat it means (plain English)
Your homepage has 57 buttons, links, and interactive elements that are smaller than 44×44 pixels when viewed on a mobile phone at 320px width. This makes them hard to tap accurately—especially for customers with larger fingers, tremors, or vision impairments. WCAG 2.5.5 is an accessibility standard that requires touch targets to be at least 44×44 pixels.
Why it matters for your business: Small tap targets frustrate mobile shoppers (which likely include many cannabis customers browsing on their phones), leading to cart abandonment, missed age-gate confirmations, and reduced conversion rates. It also exposes you to accessibility complaints or legal risk.
Technical root cause: Interactive elements (buttons, links, product thumbnails, filters, or navigation items) are likely styled with padding or font-size values too small, or are crowded together without adequate spacing. Mobile-specific CSS may be missing or incorrectly calculated.
Recommended fix — step by step
tier6.a11y.small-targetsWhat it means (plain English)
Your site has 56 interactive buttons and links that are smaller than 44×44 pixels when viewed on a mobile phone (375px width). This makes them hard to tap accurately, especially for people with limited motor control or larger fingers. It's a recognized accessibility standard (WCAG 2.5.5) that most tap targets should be at least 44×44 pixels.
Why it matters for your business: Customers on mobile devices — your primary traffic source for a cannabis retailer — will struggle to tap menu items, product filters, and checkout buttons, leading to cart abandonment and lost sales. It also signals poor UX to search engines and accessibility-conscious visitors.
Technical root cause: The site's CSS or HTML uses small font sizes and padding on buttons, links, and interactive elements. Mobile viewport scaling may also be compressing clickable areas. Navigation menus, product page links, or filter buttons are likely not padded with enough whitespace around their text.
Recommended fix — step by step
button { min-width: 44px; min-height: 44px; } in your CSS.tier6.a11y.small-targetsWhat it means (plain English)
Your website has 57 interactive buttons, links, and input fields that are smaller than 44×44 pixels on mobile phones. This makes them hard to tap accurately—especially for customers with larger fingers, vision impairments, or motor control challenges. Apple and Google both recommend 44×44 as the minimum touch target size.
Why it matters for your business: Customers struggle to complete purchases, sign up for loyalty programs, or navigate your menu on mobile devices, leading to cart abandonment and lost sales.
Technical root cause: Interactive elements were likely sized for desktop viewing (often 32px or smaller) without scaling up for touch interfaces, or CSS padding/margins are insufficient around clickable areas.
Recommended fix — step by step
tier6.a11y.small-targetsWhat it means (plain English)
Your website has 25 buttons, links, and interactive elements that are smaller than 44x44 pixels when viewed on tablets. This makes them hard to tap accurately—especially for people with motor control challenges, older users, or anyone on a small screen. WCAG 2.5.5 is an accessibility standard that requires tap targets to be at least 44×44 pixels to be reliably clickable.
Why it matters for your business: Small tap targets create friction for mobile and tablet customers trying to navigate your menu, add products to cart, or access age verification—directly reducing conversion and risking compliance complaints or legal exposure under accessibility laws.
Technical root cause: Interactive elements are likely styled with padding or dimensions below 44px, or are closely spaced together without adequate padding. This often happens when desktop designs (which tolerate smaller clicks) are directly shrunk for mobile/tablet without adjustment.
Recommended fix — step by step
tier8.lighthouse.perf-mobileWhat it means (plain English)
Your mobile site takes over 31 seconds for the largest visual element (like a hero image or product photo) to appear. That's roughly 6× slower than Google's recommended 2.5 seconds. Most visitors will bounce or leave before seeing your menu, products, or age-gate content.
Why it matters for your business: Slow mobile load times cost cannabis retailers direct revenue: customers abandon carts, search engines rank you lower, and you miss age-gated visitor conversions during peak browsing times (mobile traffic dominates retail).
Technical root cause: The LCP (Largest Contentful Paint) metric of 31.5 seconds indicates oversized or unoptimized images, render-blocking JavaScript, or missing lazy-loading directives on the critical path. Common culprits: hero images not served in next-gen formats (WebP), slow third-party scripts (analytics, ads), or unminified CSS/JS.
Recommended fix — step by step
loading='lazy' attribute to all <img> tags that aren't above the fold.async or defer in HTML.tier9.a11y.heading-orderWhat it means (plain English)
Your homepage uses heading level 5 (h5) tags as primary section headers without proper hierarchy. Screen readers and search engines expect headings to follow a logical order—typically starting with h1, then h2, h3, and so on. Skipping directly to h5 confuses assistive technology and weakens the semantic structure of your page.
Why it matters for your business: Visitors using screen readers (including many with visual impairments, a significant portion of online traffic) cannot navigate your site's structure effectively, reducing accessibility and potentially limiting conversions. Search engines also use heading hierarchy to understand page topic relevance.
Technical root cause: The Elementor page builder is outputting h5 tags for what should be primary headings. This typically happens when template or theme defaults are set to h5, or when headings are styled to look small visually while remaining semantically as h5.
Recommended fix — step by step
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier2.a11y.img-missing-altDetail
Images without alt fail a11y + hurt SEO.
tier4.schema.missing-coreDetail
Every site should emit Organization + LocalBusiness + WebSite JSON-LD.
tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your Castleton-on-Hudson location page don't have alt text—descriptive labels that screen readers use to tell visually impaired visitors what an image shows. This means those visitors get no information from those images, and search engines can't understand what they depict either.
Why it matters for your business: Missing alt text reduces your SEO rankings for image searches and location-specific queries, and excludes customers using assistive technology from seeing product photos or dispensary visuals.
Technical root cause: Images were uploaded to the page without alt attributes populated in the HTML img tags, or the CMS failed to prompt for alt text during upload.
Recommended fix — step by step
tier2.robots.no-sitemapWhat it means (plain English)
Your robots.txt file (the instruction file that tells search engines how to crawl your site) doesn't point to your XML sitemap. A sitemap is a roadmap of all your pages that helps search engines find and index content faster, especially new product pages or promotions you add.
Why it matters for your business: Without a sitemap reference, search engines may miss indexing new strains, product updates, or location pages, reducing organic traffic and delaying visibility for new inventory or promotions.
Technical root cause: The robots.txt file is missing a 'Sitemap:' directive. This directive is optional but recommended; without it, search engines must discover your sitemap through other methods (like a meta tag), which is slower and less reliable.
Recommended fix — step by step
tier2.meta.title-lengthWhat it means (plain English)
Your homepage title tag (the text that appears in browser tabs and search results) is only 18 characters long. Search engines prefer titles between 20–65 characters because longer, descriptive titles help people understand what your page is about before clicking. A short title wastes an opportunity to include keywords and context that could improve click-through rates from Google.
Why it matters for your business: Underutilized real estate in search results means fewer clicks from potential customers searching for cannabis dispensaries or products in your area.
Technical root cause: The title tag in the page's HTML head section is minimal ('Home | Litmosphere'). It should include descriptive keywords—like location, product category, or brand differentiator—to fill the 20–65 character window that Google displays.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When your website is shared on Facebook, Instagram, or other social platforms, these pages pull in a preview image and title automatically. Without OpenGraph metadata, social posts show a generic or broken preview, making your content look unprofessional and reducing click-through rates from social traffic.
Why it matters for your business: Social sharing is a key discovery channel for cannabis retailers; a weak preview discourages customers from clicking through to your menu, promotions, or product pages.
Technical root cause: The page HTML is missing og:title, og:image, og:url, and og:description meta tags in the <head> section, so social platforms cannot extract rich preview data.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
Your blog post page is missing Open Graph tags—special metadata that tells Facebook, Instagram, LinkedIn, and other social platforms how to display your content when someone shares it. Without these tags, social posts default to basic text and may not show your cannabis products or branding visually, making shares less engaging.
Why it matters for your business: Lost opportunity to drive traffic from social sharing; posts about your products won't display with images or custom titles, reducing click-through rates from social platforms where cannabis customers discover dispensaries.
Technical root cause: The page HTML lacks <meta property="og:title"> and <meta property="og:image"> tags in the document head, so social platforms have no instruction on how to preview the page.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your site is missing a Twitter Card meta tag, which is a small code snippet that tells Twitter (X) how to display your content when someone shares a link. Without it, Twitter shows a plain link with minimal information instead of an attractive preview with your image, headline, and description.
Why it matters for your business: When customers share your products or blog posts on Twitter/X, missing cards result in low-engagement, plain-text previews that don't drive clicks back to your site or showcase your brand.
Technical root cause: The page lacks the <meta name="twitter:card" content="summary_large_image"> tag and related Twitter Card 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="[Your Page Title]"><meta name="twitter:description" content="[Your Page Description]"><meta name="twitter:image" content="[URL to high-quality image, 1200×630px]">tier2.a11y.img-missing-altWhat it means (plain English)
Three images on your 'Hello World' page don't have alt text — a short text description that tells screen readers and search engines what the image shows. This makes those images invisible to people using assistive technology and signals to Google that you haven't optimized for accessibility.
Why it matters for your business: Missing alt text reduces SEO value for image search (many cannabis customers search for product photos), and it excludes customers with visual impairments or slow connections from understanding your content.
Technical root cause: Images were inserted into the page without the 'alt' HTML attribute, which is required for accessibility compliance and search engine indexing.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
Your Services page doesn't include Open Graph tags — special metadata that tells social media platforms (Facebook, Instagram, LinkedIn) what image and headline to display when someone shares your link. Without these tags, social shares show a generic preview instead of your chosen branding.
Why it matters for your business: When customers share your services page on social media, it will display a generic or broken preview instead of a professional image and headline, reducing click-through rates and brand consistency in social feeds.
Technical root cause: The HTML <head> section is missing og:title and og:image meta tags. Social platforms fall back to page title and the first image they find, which is unpredictable and often unflattering.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When your product pages are shared on social media (Facebook, Instagram, LinkedIn), those platforms look for special metadata tags called OpenGraph tags to display a preview with your page title and image. Without og:title and og:image, social shares show a generic preview that doesn't represent your products or brand, making the link less attractive to click.
Why it matters for your business: Poor social media previews reduce click-through rates when customers share your products with friends, directly limiting organic word-of-mouth traffic and product discovery for your dispensary.
Technical root cause: The page HTML is missing <meta property="og:title"> and <meta property="og:image"> tags in the document head. When absent, platforms cannot fetch rich preview data and fall back to generic defaults.
Recommended fix — step by step
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 it. Without og:title and og:image, your contact page will show a generic preview instead of your branded message, making shared links look unprofessional.
Why it matters for your business: When customers share your contact page on social media, it won't display your dispensary name or a compelling image, reducing click-through rates and brand recognition in social feeds.
Technical root cause: The contact page's HTML <head> section is missing <meta property="og:title"> and <meta property="og:image"> tags that social platforms use to generate rich previews.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When people share your in-store pickup page on social media (Facebook, Instagram, etc.), those platforms don't have a nice preview card to display. Instead, they show a generic or broken-looking snippet. OpenGraph tags are special HTML codes that tell social platforms what image and headline to show when your page is shared.
Why it matters for your business: Poor social sharing previews reduce click-through rates when customers share your dispensary's pickup option with friends, directly limiting organic word-of-mouth traffic and brand awareness.
Technical root cause: The page's HTML <head> section is missing og:title and og:image meta tags that social platforms require to generate rich preview cards.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your website is missing Twitter Card tags, which are special metadata that tell Twitter (now X) how to display your pages when someone shares a link. Without them, the platform shows a plain, unformatted preview instead of your custom title, description, and image. For a cannabis retailer, this means social shares look unprofessional and miss the chance to drive traffic.
Why it matters for your business: Missing Twitter Cards reduce click-through rates on social media shares and make your in-store pickup and product pages appear less trustworthy when customers share them, directly impacting foot traffic and online visibility.
Technical root cause: The <meta name="twitter:card"> tag and related Twitter Card meta tags (twitter:title, twitter:description, twitter:image) are not present in the HTML <head> of this page.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Three images on your in-store pickup page don't have alt text—descriptive labels that screen readers use to tell visually impaired visitors what an image shows. This hurts both accessibility (people using screen readers can't understand those images) and SEO (search engines can't index image content without descriptions).
Why it matters for your business: Customers using assistive technology may skip your page or leave frustrated; you're also losing potential search traffic from image searches and missing SEO ranking signals.
Technical root cause: The HTML img tags lack alt attributes, or the attributes are empty (alt=""). Without these, browsers and search engines have no text description of the images.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
OpenGraph (OG) tags are snippets of code that control how your pages look when shared on Facebook, Instagram, LinkedIn, and other social platforms. Without og:title and og:image tags, when someone shares your online ordering page, it shows up as a generic, unappealing preview instead of a branded image with your business name and a clear call-to-action.
Why it matters for your business: Missing OG tags reduce click-through rates on social shares, making it less likely that potential customers will visit your site when your content is shared by staff or existing customers on social media.
Technical root cause: The /online-ordering/ page does not include <meta property="og:title" content="..."> or <meta property="og:image" content="..."> tags in its HTML <head> section, so social platforms fall back to generic parsing of page content.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your site is missing a Twitter Card meta tag, which is a snippet of code that tells Twitter how to display your page when someone shares it on that platform. Without it, Twitter shows a plain, unformatted preview instead of a rich card with your brand imagery and product details.
Why it matters for your business: Social sharing is free marketing; a missing Twitter Card means fewer people will click through from Twitter, reducing organic traffic and brand visibility when customers share your products or promotions.
Technical root cause: The HTML page lacks a <meta name="twitter:card" content="summary_large_image"> tag and related Twitter meta tags (twitter:image, twitter:title, twitter:description) in the page head.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Three images on your online ordering page lack alt text — descriptive text that screen readers announce to visitors with visual impairments, and that search engines use to understand what images show. This makes the page harder for people using accessibility tools and slightly reduces image visibility in search results.
Why it matters for your business: Missing alt text blocks disabled customers from understanding product images and ordering, and leaves SEO value on the table for product images that could rank in Google Image Search.
Technical root cause: Images were added to the page without alt attributes in the HTML, either during page build or via a CMS that didn't require alt text at upload.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When your Education & Community page is shared on social media (Facebook, Instagram, LinkedIn), those platforms need specific metadata tags to know what title and image to display in the preview. Without these tags, social shares show generic or broken previews, which looks unprofessional and discourages clicks.
Why it matters for your business: Poor social media previews reduce click-through rates on shared content, limiting organic reach and community engagement — especially critical for a cannabis brand building trust through educational content.
Technical root cause: The page is missing og:title and og:image meta tags in the HTML head. Social platforms fall back to page title and favicon, which rarely create compelling previews.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
Your About Us page is missing OpenGraph metadata—special tags that control how your page appears when shared on Facebook, Instagram, or other social platforms. Without these tags, when someone shares your link, it won't show a custom title or image, making the share look unprofessional and reducing click-through rates.
Why it matters for your business: Missed social media visibility and engagement; shared links appear generic instead of branded, reducing traffic from social platforms where many cannabis consumers discover dispensaries.
Technical root cause: The page HTML lacks og:title and og:image meta tags in the <head> section. These tags are not automatically generated by most website builders and must be explicitly added.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
Your /accessibility/ page is missing OpenGraph tags — special HTML code that tells social media platforms (Facebook, Instagram, LinkedIn) what to display when someone shares the link. Without these tags, the share preview looks generic and unattractive, which reduces click-through rates on social posts.
Why it matters for your business: When customers try to share your accessibility page on social media, it won't show a branded preview with your logo or a compelling image, making the share less likely to drive traffic back to your site.
Technical root cause: The page's HTML <head> section lacks og:title and og:image meta tags. Social platforms fall back to generic defaults when these are missing.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your accessibility page contains 2 images that lack descriptive alt text — the hidden labels that screen readers announce to visually impaired visitors and that search engines use to understand image content. This creates barriers for both customers and search ranking.
Why it matters for your business: Visually impaired customers cannot understand what those images show, reducing trust and compliance; search engines also rank pages with properly labeled images higher, so this is costing you SEO points on a page meant to showcase your commitment to accessibility.
Technical root cause: The images were added to the HTML without alt attributes, either during initial page build or a recent CMS content update.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares your dispensary location page on Facebook, Instagram, or other social platforms, those platforms pull in a preview image and headline. Without OpenGraph metadata (special tags that tell social platforms what to display), your page shows a generic or broken preview, making the shared link look unprofessional and less clickable.
Why it matters for your business: Poor social previews reduce click-through rates when customers share your dispensary location with friends, directly hurting foot traffic and online visibility in a competitive market.
Technical root cause: The page is missing og:title and og:image meta tags in the HTML <head> section. Social platforms default to generic fallbacks when these tags are absent.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages are missing Twitter Card meta tags — special HTML code that tells Twitter how to display your content when someone shares a link to your site on Twitter/X. Without this, your posts appear as plain text links instead of attractive preview cards with your logo, product image, and description.
Why it matters for your business: Missing Twitter Cards reduce click-through rates on social shares, making your cannabis products less visually appealing when staff, customers, or influencers post about Litmosphere on Twitter/X.
Technical root cause: The page HTML does not include <meta name="twitter:card" content="summary_large_image"> and related open graph meta tags (og:image, og:title, og:description) in the <head> section.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="[Product/Page Title]">, <meta name="twitter:description" content="[Product description]">, <meta name="twitter:image" content="[Image URL]"> (and also add equivalent og:* tags for all social platforms)tier2.meta.no-ogWhat it means (plain English)
Open Graph tags are snippets of code that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your page when someone shares it. Without og:title and og:image, your dispensary's location page will show up as a generic, unattractive preview when customers share it—missing your branding, location info, and a compelling image.
Why it matters for your business: Missing Open Graph tags reduce the likelihood that shared content drives traffic back to your site; potential customers see bland previews instead of professional branding, hurting word-of-mouth social sharing and local visibility.
Technical root cause: The page's HTML head section lacks og:title, og:image, and related Open Graph meta tags that social platforms parse when generating share previews.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages are missing Twitter Card tags, which are small code snippets that tell Twitter how to display your link when someone shares it on that platform. Without them, Twitter shows a plain, generic preview instead of your product image, name, and description—making your posts look less professional and less clickable.
Why it matters for your business: Missed social sharing engagement: customers who share your dispensary location or products on Twitter will see a bland preview, reducing click-through rates and brand visibility on a platform where cannabis enthusiasts and advocates are active.
Technical root cause: The page's HTML head section lacks <meta name="twitter:card"> and related tags (twitter:image, twitter:title, twitter:description). These are optional meta tags that enhance social sharing but are not generated by default.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="[Product/Location Name]">, <meta name="twitter:description" content="[Brief description]">, <meta name="twitter:image" content="[URL to product image]">, and <meta name="twitter:site" content="@YourTwitterHandle"> (if you have one).tier2.meta.no-ogWhat it means (plain English)
Open Graph tags are snippets of code that tell social platforms (Facebook, Instagram, LinkedIn) what image and text to display when someone shares your link. Without them, your dispensary page shows up as a plain link with no preview, making it less likely people will click through from social media.
Why it matters for your business: Social sharing is a free marketing channel for dispensaries; without OG tags, shared links look unprofessional and get fewer clicks, reducing foot traffic and online visibility.
Technical root cause: The page's HTML header is missing <meta property="og:title"> and <meta property="og:image"> tags, so social platforms have no instruction on what to display when the URL is shared.
Recommended fix — step by step
<head> section of https://litmospheres.com/dispensary-near-east-greenbush-ny/</head> tag: <meta property="og:title" content="Litmosphere Dispensary Near East Greenbush, NY">, <meta property="og:description" content="[Your 160-character description]">, <meta property="og:image" content="[Full URL to 1200x630px image]">, and <meta property="og:url" content="https://litmospheres.com/dispensary-near-east-greenbush-ny/">tier2.meta.no-twitter-cardWhat it means (plain English)
Your product pages are missing Twitter card metadata — special HTML tags that tell Twitter (now X) how to display your content when someone shares a link. Without them, the platform shows a plain, generic preview instead of your product photo, description, and branding. This makes shared links less compelling and less likely to drive clicks.
Why it matters for your business: Missing Twitter cards reduce click-through rates on social shares, which cuts organic traffic from X and limits brand visibility among cannabis consumers who discover dispensaries through social channels.
Technical root cause: The page HTML lacks <meta name="twitter:card">, twitter:image, twitter:title, and twitter:description tags in the document head. Without these, X defaults to a minimal text-only preview.
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 dispensary/product photo, 1200×630px]">, <meta name="twitter:site" content="@[your X handle]"> (if you have one).tier2.meta.title-lengthWhat it means (plain English)
Your homepage title tag (the text that appears in browser tabs and search results) is only 18 characters long. Search engines prefer titles between 20–65 characters because longer, descriptive titles help customers understand what your page is about before clicking. Your current title is too short to take full advantage of search visibility.
Why it matters for your business: A weak title tag reduces click-through rates from Google search results and fails to communicate your dispensary's key offerings (location, products, promotions) to potential customers searching for cannabis products nearby.
Technical root cause: The title tag in your page's HTML head section was likely set to a generic default during theme setup. It does not include descriptive keywords like your location, product categories, or brand differentiators that would naturally extend the character count.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
OpenGraph tags are snippets of code that control how your website appears when shared on social media platforms like Instagram, Facebook, and Twitter. Without these tags, your pages show up with generic or broken previews, making shared links look unprofessional and less clickable.
Why it matters for your business: Poor social media previews reduce click-through rates when customers share your products or promotions, directly impacting traffic and brand perception in a visual-first industry like cannabis retail.
Technical root cause: The affected page (an Elementor library template page) lacks og:title and og:image meta tags in its HTML head section, likely because it's an internal template not designed for social sharing but is still indexable.
Recommended fix — step by step
tier2.meta.title-lengthWhat it means (plain English)
Your homepage title tag (the text that appears in browser tabs and search results) is only 18 characters long. Search engines and users prefer titles between 20 and 65 characters because longer titles give more context about what the page offers. Right now, your title is too short to fully explain what Litmosphere does.
Why it matters for your business: A weak title reduces click-through rates from Google search results and misses an opportunity to include relevant keywords (like your location or product category) that help customers find you.
Technical root cause: The title tag in your site's HTML <head> section is set to a generic 'Home | Litmosphere' without descriptive keywords or value proposition.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
Open Graph tags are invisible snippets of code that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your content when someone shares a link. Without them, your posts will show a generic preview instead of your brand's logo, product photo, or custom headline—making social shares look unprofessional and getting fewer clicks.
Why it matters for your business: Cannabis retailers rely heavily on social media to drive traffic and build community; missing OG tags mean your Instagram and Facebook shares look broken, reducing click-through rates from social traffic by 20–40% and hurting brand perception.
Technical root cause: The Elementor page template (default-kit) lacks og:title and og:image meta tags in its <head> section. This is likely a theme/builder configuration gap rather than a site-wide issue, since only this specific URL was detected.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your site is missing a Twitter card meta tag, which is a small piece of code that tells Twitter how to display your page when someone shares a link on that platform. Without it, Twitter shows a plain text preview instead of an attractive card with your image, headline, and description.
Why it matters for your business: Cannabis products shared on Twitter/X reach fewer people and look unprofessional compared to competitors who have Twitter cards set up, reducing organic social reach and brand perception.
Technical root cause: The meta tag <meta name="twitter:card" content="summary_large_image"> and related Twitter card properties (twitter:title, twitter:description, twitter:image) are not present in your page's HTML head section.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:site" content="@YourTwitterHandle">, <meta name="twitter:title" content="Your Page Title">, <meta name="twitter:description" content="Your page description">, <meta name="twitter:image" content="https://litmospheres.com/path-to-product-image.jpg"><meta property="og:image" content="https://litmospheres.com/path-to-product-image.jpg"> if not already presenttier2.meta.title-lengthWhat it means (plain English)
Your homepage title tag is only 18 characters long, falling slightly short of the recommended minimum of 20 characters. Title tags are the headline that appears in browser tabs and search results, so this one is too brief to fully communicate what your site offers to potential customers and search engines.
Why it matters for your business: A weak title tag reduces click-through rates from Google search results and misses an opportunity to reinforce your brand and product offering (cannabis retail) in a prime real estate that influences both customers and search ranking.
Technical root cause: The title tag in your page's HTML <head> section reads only 'Home | Litmosphere' — it lacks descriptive keywords about your business type, location, or unique value proposition that search engines and users expect.
Recommended fix — step by step
tier2.meta.title-lengthWhat it means (plain English)
Your homepage title is only 18 characters long, falling short of Google's recommended 20–65 character range. Search engines use this title to display your site in results, and a very short title wastes the opportunity to include keyword phrases that tell customers what you offer.
Why it matters for your business: A weak title reduces click-through rates from search results and misses the chance to rank for keywords like 'cannabis dispensary' or your location—potential customers may skip your listing for competitors with clearer, more descriptive titles.
Technical root cause: The page title is set to a generic 'Home | Litmosphere' without descriptive keywords. Most page title templates default to minimal branding when custom SEO titles aren't specified.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
OpenGraph tags are metadata snippets that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your site when someone shares a link. Without them, your posts appear plain and generic instead of showing a custom title, description, and image. This affects how professional and trustworthy your brand looks when customers share your products on social.
Why it matters for your business: When customers share your dispensary's product pages or promotions on social media, missing OpenGraph tags cause plain, unattractive previews—reducing click-through rates and brand perception compared to competitors with rich social cards.
Technical root cause: The site either lacks og:title and og:image meta tags in the <head> section, or they are not being dynamically generated for template/library URLs. The affected URL is an Elementor library endpoint, which may not have proper OpenGraph templates configured.
Recommended fix — step by step
tier2.meta.title-lengthWhat it means (plain English)
Your blog category page has a page title (the text that appears in browser tabs and search results) that's only 18 characters long. Search engines prefer titles between 20–65 characters because longer titles give potential customers more context about what they'll find. A slightly longer title will help searchers understand the page better and may improve click-through rates from Google.
Why it matters for your business: A weak page title means fewer clicks from search results, which reduces traffic to your blog content—a key channel for building trust and driving repeat visits to your dispensary site.
Technical root cause: The page's HTML <title> tag contains only "Blog | Litmosphere," which is below the recommended minimum. Expanding it with descriptive keywords (e.g., "Cannabis Blog | Litmosphere Dispensary") will meet guidelines without exceeding the 65-character limit.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your homepage doesn't include a Twitter Card meta tag, which tells Twitter how to display your site when someone shares a link. Without it, Twitter shows a generic preview instead of a branded, engaging one with your logo, description, and image.
Why it matters for your business: Missed opportunity to drive traffic and build brand recognition when customers share your dispensary on social media—a plain preview converts far fewer clicks than a rich, visually appealing one.
Technical root cause: The meta tag <meta name="twitter:card" content="summary_large_image"> and related Twitter Card directives (og:image, og:description, etc.) are not present in the HTML head section.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your website is missing a Twitter Card meta tag, which tells Twitter (X) how to display your page when someone shares a link. Without it, Twitter shows a generic preview instead of your custom headline, description, and image. This is cosmetic but affects how professional your brand looks on social media.
Why it matters for your business: When customers share your product pages or services on Twitter/X, you miss the chance to control the visual impression and drive click-throughs with a branded preview.
Technical root cause: The page lacks 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="Your Page Title">, <meta name="twitter:description" content="Your Page Description">, <meta name="twitter:image" content="https://litmospheres.com/path-to-image.jpg">tier2.meta.no-twitter-cardWhat it means (plain English)
Your website is missing Twitter Card tags, which are special HTML instructions that tell Twitter (now X) how to display your pages when someone shares a link. Without them, social shares look plain and generic instead of showing your product photo, brand colors, and compelling description.
Why it matters for your business: Fewer clicks from social media shares; dispensary deals and new product announcements get less engagement when shared by staff or customers on X/Twitter.
Technical root cause: The page HTML lacks the meta tags twitter:card, twitter:title, twitter:description, and twitter:image in the <head> section.
Recommended fix — step by step
<head> of your page template (or each page if platform doesn't support templating): <meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="[Page Title]">, <meta name="twitter:description" content="[Brief description]">, <meta name="twitter:image" content="[URL to 1200x630px image]">tier2.meta.no-twitter-cardWhat it means (plain English)
Your website doesn't have Twitter card markup, which means when someone shares a link to your site on Twitter/X, it won't display a nice preview with your image and description. Instead, Twitter will pull whatever it can find, and the result looks unprofessional and incomplete.
Why it matters for your business: Missing Twitter cards reduce click-through rates on social shares and hurt brand perception when customers share your products or promotions on social media.
Technical root cause: The page lacks the <meta name="twitter:card" content="summary_large_image"> tag and related Twitter metadata in the HTML head section.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image"> to the head of your page template<meta name="twitter:site" content="@YourTwitterHandle"> (replace with your actual handle)<meta name="twitter:title" content="Page Title"> matching your page's main heading<meta name="twitter:description" content="Brief description of page content"> (50–160 characters)<meta name="twitter:image" content="https://litmospheres.com/path/to/image.jpg"> pointing to a 1200×630px imagetier2.meta.no-twitter-cardWhat it means (plain English)
Your website is missing a Twitter card meta tag, which is a small code snippet that tells Twitter how to display your content when someone shares a link on that platform. Without it, Twitter uses generic fallback formatting, which may not show your product images or brand messaging as intended.
Why it matters for your business: Missing Twitter cards reduce click-through rates from social shares and make your cannabis education content look less professional or appealing when shared on Twitter/X, potentially limiting organic reach and brand visibility.
Technical root cause: The page HTML does not include the Open Graph meta tag <meta name="twitter:card" content="summary_large_image"> or equivalent, which is optional but recommended for social sharing optimization.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image"><meta name="twitter:image" content="[full URL to your logo or key image]"> to specify which image displays when shared<meta name="twitter:title" content="[your page title]"> and <meta name="twitter:description" content="[your page description]"> for consistencytier2.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 (now X) how to display a preview when someone shares your About Us page. Without it, X shows a plain, generic preview instead of a branded one with your chosen image, title, and description.
Why it matters for your business: When customers share your About Us page on X, a weak preview reduces click-through rates and brand perception compared to competitors who have polished social previews.
Technical root cause: The <meta name="twitter:card" content="summary_large_image"> tag and related Open Graph meta tags are not present in the page's HTML head section.
Recommended fix — step by step
<head> section of the page<meta name="twitter:card" content="summary_large_image"><meta name="twitter:site" content="@YourTwitterHandle"><meta name="twitter:title" content="About Litmosphere"><meta name="twitter:description" content="[Your 2-sentence brand description]"><meta name="twitter:image" content="[URL to 1200x630px branded image]">tier2.meta.no-twitter-cardWhat it means (plain English)
Your site is missing a Twitter Card meta tag, which tells Twitter (now X) how to display your content when someone shares a link. Without it, X shows a plain text preview instead of a rich preview with your brand imagery and product details. This is purely cosmetic on social sharing—it doesn't affect your core site functionality.
Why it matters for your business: When customers share your product pages or promotions on X, the post looks generic and less engaging, reducing click-through rates and brand presence in social conversations.
Technical root cause: The page HTML is missing the <meta name="twitter:card" content="summary_large_image"> tag (or variant) in the document head, and no corresponding Open Graph tags that Twitter can fall back to.
Recommended fix — step by step
<head> section (or header template if using a CMS): <meta name="twitter:card" content="summary_large_image"><meta name="twitter:site" content="@YourXHandle"><meta name="twitter:image" content="https://litmospheres.com/path-to-brand-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 to your site on that platform. Without it, Twitter shows a plain text preview instead of a rich preview with your brand colors, images, and product details.
Why it matters for your business: When customers share your products or promotions on Twitter/X, the posts look generic instead of branded and eye-catching, reducing click-through rates and social engagement for your cannabis retail.
Technical root cause: The meta tag <meta name="twitter:card" content="summary_large_image"> is not present in the HTML head section. This is a simple metadata addition that most site builders support but isn't set by default.
Recommended fix — step by step
<meta name="twitter:card" content="summary_large_image"> in the head section.<meta name="twitter:image" content="[your-brand-logo-or-product-image-url]"> to specify which image displays.tier2.meta.no-ogWhat it means (plain English)
Your site is missing OpenGraph tags, which are snippets of code that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your content when someone shares a link. Without them, social shares show up as plain links with no image or description, making them look unprofessional and reducing click-through rates.
Why it matters for your business: Poor social media presentation hurts word-of-mouth and paid social campaigns, especially important for a fun cannabis brand where visual appeal and shareability drive customer acquisition.
Technical root cause: The affected URL is an Elementor library page (a backend template page, not a public-facing page). These pages typically don't need OpenGraph tags, but the scanner flagged it because the tags are absent. This is likely a false positive—the URL shouldn't be indexed or shared publicly in the first place.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your website is missing Twitter card metadata — a snippet of code that tells Twitter (X) how to display your content when someone shares a link. Without it, Twitter shows a plain, generic preview instead of your brand colors, images, and description. This is a cosmetic issue that doesn't block sharing.
Why it matters for your business: Shared links to your dispensary's products or promotions will appear less visually appealing on Twitter, reducing click-through rates and brand recall when customers share your site on social media.
Technical root cause: The <meta name="twitter:card"> tag and related Twitter Open Graph tags (twitter:title, twitter:description, twitter:image) are not present in the page's <head> section.
Recommended fix — step by step
<head> section<meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="Your Brand Name">, <meta name="twitter:description" content="Your dispensary description">, <meta name="twitter:image" content="[URL to your logo or product image]">tier2.meta.no-twitter-cardWhat it means (plain English)
Your site is missing a Twitter Card meta tag, which is a small code snippet that tells Twitter (now X) how to display your pages when someone shares a link. Without it, shared links appear plain and less engaging. This is a social media visibility feature, not a search engine requirement.
Why it matters for your business: When customers or influencers share your dispensary's product pages or promotions on Twitter/X, they'll display as plain text instead of rich cards with images and descriptions, reducing click-through rates and social engagement.
Technical root cause: The page's HTML header is missing the <meta name="twitter:card" content="summary_large_image"> tag (or equivalent variant). This is often overlooked when Elementor-based sites don't have a social sharing plugin configured.
Recommended fix — step by step
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.perf.desktop-failDetail
page.goto: Timeout 60000ms exceeded.
Call log:
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.cookie.no-samesiteDetail
Cookies should declare SameSite=Lax or Strict.
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.dkim-missingDetail
Tried selectors: google, default, selector1, selector2, s1, k1 — none matched at litmospheres.com. DKIM improves deliverability + anti-spoofing.
tier8.lighthouse.bestPractices-mobileDetail
Score 79 is below target 90. 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.
tier8.lighthouse.perf-desktopDetail
Score 76 is below target 90. See HTML report for details.
tier8.lighthouse.bestPractices-desktopDetail
Score 78 is below target 90. See HTML report for details.
tier8.lighthouse.seo-desktopDetail
Score 85 is below target 95. See HTML report for details.
tier8.lh-opportunity.uses-rel-preconnect-desktopDetail
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.prioritize-lcp-image-desktopDetail
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. https://web.dev/articles/optimize-lcp#optimize_when_the_resource_is_discovered" target="_blank" rel="noreferrer">Learn more about preloading LCP elements.
tier8.lh-opportunity.render-blocking-resources-desktopDetail
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-desktopDetail
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-desktopDetail
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.
Grouped by URL — useful when working through the site one page at a time.
_44 findings on this page_
Your website is served over HTTPS (secure), but it's trying to load a resource from an HTTP URL (insecure). Modern browsers block or warn about this, which can degrade trust and break functionality. I
Your age-gate dialog (the overlay that appears when visitors first land on your site) doesn't have a label that screen readers can announce. Screen reader users don't know what the dialog is for or ho
Your site is trying to load a JavaScript module (a .js file imported with type="module") but the server is sending back an HTML page instead. This breaks the age gate and menu functionality on the h
Our automated performance testing tool timed out while trying to load your homepage on a mobile connection — it waited 60 seconds and never received a signal that the page had finished loading all res
Your site is missing the Strict-Transport-Security (HSTS) header, which tells browsers to always use HTTPS when connecting to your domain. Without it, visitors could be vulnerable to man-in-the-middle
Your site is missing the X-Frame-Options security header, which tells browsers whether your pages can be embedded inside frames or iframes on other websites. Without this header, malicious sites could
Your site is missing a Content Security Policy (CSP) header — a security rule that tells browsers which external resources (scripts, images, fonts) are allowed to load. Without it, attackers could inj
Your website sets a cookie (nfd-enable-cf-opt) without the Secure flag. This flag tells browsers to only send the cookie over encrypted HTTPS connections, not unencrypted HTTP. Without it, if a visito
Your domain has a valid SPF record (which helps prevent email spoofing) but is missing a DMARC policy—a set of instructions that tell email providers how to handle emails claiming to be from your doma
Your homepage has 57 buttons, links, and interactive elements that are smaller than 44×44 pixels when viewed on a mobile phone at 320px width. This makes them hard to tap accurately—especially for cus
Your site has 56 interactive buttons and links that are smaller than 44×44 pixels when viewed on a mobile phone (375px width). This makes them hard to tap accurately, especially for people with limite
Your website has 57 interactive buttons, links, and input 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 25 buttons, links, and interactive elements that are smaller than 44x44 pixels when viewed on tablets. This makes them hard to tap accurately—especially for people with motor control
Your mobile site takes over 31 seconds for the largest visual element (like a hero image or product photo) to appear. That's roughly 6× slower than Google's recommended 2.5 seconds. Most visitors will
Your homepage uses heading level 5 (h5) tags as primary section headers without proper hierarchy. Screen readers and search engines expect headings to follow a logical order—typically starting with h1
Your homepage title tag (the text that appears in browser tabs and search results) is only 18 characters long. Search engines prefer titles between 20–65 characters because longer, descriptive titles
When your website is shared on Facebook, Instagram, or other social platforms, these pages pull in a preview image and title automatically. Without OpenGraph metadata, social posts show a generic or b
Your homepage doesn't include a Twitter Card meta tag, which tells Twitter how to display your site when someone shares a link. Without it, Twitter shows a generic preview instead of a branded, engagi
_5 findings on this page_
Your blog category page has a page title (the text that appears in browser tabs and search results) that's only 18 characters long. Search engines prefer titles between 20–65 characters because longer
_4 findings on this page_
Your homepage title tag (the text that appears in browser tabs and search results) is only 18 characters long. Search engines prefer titles between 20–65 characters because longer, descriptive titles
OpenGraph tags are snippets of code that control how your website appears when shared on social media platforms like Instagram, Facebook, and Twitter. Without these tags, your pages show up with gener
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 that platform. Without it, Twitter shows a plain text preview i
_4 findings on this page_
Eleven images on your site are missing alt text — a text description that explains what each image shows. Screen readers used by visually impaired customers can't describe these images, and search eng
Your homepage title tag (the text that appears in browser tabs and search results) is only 18 characters long. Search engines and users prefer titles between 20 and 65 characters because longer titles
Open Graph tags are invisible snippets of code that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your content when someone shares a link. Without them, your posts will sh
Your site is missing a Twitter card meta tag, which is a small piece of code that tells Twitter how to display your page when someone shares a link on that platform. Without it, Twitter shows a plain
_4 findings on this page_
Your homepage title tag is only 18 characters long, falling slightly short of the recommended minimum of 20 characters. Title tags are the headline that appears in browser tabs and search results, so
Your site is missing OpenGraph tags, which are snippets of code that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your content when someone shares a link. Without them, s
Your website is missing Twitter card metadata — a snippet of code that tells Twitter (X) how to display your content when someone shares a link. Without it, Twitter shows a plain, generic preview inst
_4 findings on this page_
Your homepage title is only 18 characters long, falling short of Google's recommended 20–65 character range. Search engines use this title to display your site in results, and a very short title waste
OpenGraph tags are metadata snippets that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your site when someone shares a link. Without them, your posts appear plain and gen
Your site is missing a Twitter Card meta tag, which is a small code snippet that tells Twitter (now X) how to display your pages when someone shares a link. Without it, shared links appear plain and l
_3 findings on this page_
Your blog post page is missing Open Graph tags—special metadata that tells Facebook, Instagram, LinkedIn, and other social platforms how to display your content when someone shares it. Without these t
Your site is missing a Twitter Card meta tag, which is a small code snippet that tells Twitter (X) how to display your content when someone shares a link. Without it, Twitter shows a plain link with m
Three images on your 'Hello World' page don't have alt text — a short text description that tells screen readers and search engines what the image shows. This makes those images invisible to people us
_3 findings on this page_
Seven images on your Services page don't have alt text — short descriptive labels that explain what the image shows. Screen readers used by visually impaired customers can't describe these images, and
Your Services page doesn't include Open Graph tags — special metadata that tells social media platforms (Facebook, Instagram, LinkedIn) what image and headline to display when someone shares your link
Your website is missing a Twitter Card meta tag, which tells Twitter (X) how to display your page when someone shares a link. Without it, Twitter shows a generic preview instead of your custom headlin
_3 findings on this page_
When your product pages are shared on social media (Facebook, Instagram, LinkedIn), those platforms look for special metadata tags called OpenGraph tags to display a preview with your page title and i
Your website is missing Twitter Card tags, which are special HTML instructions that tell Twitter (now X) how to display your pages when someone shares a link. Without them, social shares look plain an
Four images on your Castleton-on-Hudson location page don't have alt text—descriptive labels that screen readers use to tell visually impaired visitors what an image shows. This means those visitors g
_3 findings on this page_
Your contact page has 5 out of 6 images missing alt text — short descriptions that explain what each image shows. Search engines can't read images, so they rely on alt text to understand your content.
OpenGraph metadata tells social media platforms (Facebook, Instagram, LinkedIn) how to display your page when someone shares it. Without og:title and og:image, your contact page will show a generic pr
Your website doesn't have Twitter card markup, which means when someone shares a link to your site on Twitter/X, it won't display a nice preview with your image and description. Instead, Twitter will
_3 findings on this page_
When people share your in-store pickup page on social media (Facebook, Instagram, etc.), those platforms don't have a nice preview card to display. Instead, they show a generic or broken-looking snipp
Your website is missing Twitter Card tags, which are special metadata that tell Twitter (now X) how to display your pages when someone shares a link. Without them, the platform shows a plain, unformat
Three images on your in-store pickup page don't have alt text—descriptive labels that screen readers use to tell visually impaired visitors what an image shows. This hurts both accessibility (people u
_3 findings on this page_
OpenGraph (OG) tags are snippets of code that control how your pages look when shared on Facebook, Instagram, LinkedIn, and other social platforms. Without og:title and og:image tags, when someone sha
Your site is missing a Twitter Card meta tag, which is a snippet of code that tells Twitter how to display your page when someone shares it on that platform. Without it, Twitter shows a plain, unforma
Three images on your online ordering page lack alt text — descriptive text that screen readers announce to visitors with visual impairments, and that search engines use to understand what images show.
_3 findings on this page_
When your Education & Community page is shared on social media (Facebook, Instagram, LinkedIn), those platforms need specific metadata tags to know what title and image to display in the preview. With
Your website is missing a Twitter card meta tag, which is a small code snippet that tells Twitter how to display your content when someone shares a link on that platform. Without it, Twitter uses gene
_3 findings on this page_
Seven images on your About Us 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 understa
Your About Us page is missing OpenGraph metadata—special tags that control how your page appears when shared on Facebook, Instagram, or other social platforms. Without these tags, when someone shares
Your website is missing a Twitter Card meta tag, which is a snippet of code that tells Twitter (now X) how to display a preview when someone shares your About Us page. Without it, X shows a plain, gen
_3 findings on this page_
Your /accessibility/ page is missing OpenGraph tags — special HTML code that tells social media platforms (Facebook, Instagram, LinkedIn) what to display when someone shares the link. Without these ta
Your site is missing a Twitter Card meta tag, which tells Twitter (now X) how to display your content when someone shares a link. Without it, X shows a plain text preview instead of a rich preview wit
Your accessibility page contains 2 images that lack descriptive alt text — the hidden labels that screen readers announce to visually impaired visitors and that search engines use to understand image
_3 findings on this page_
When someone shares your dispensary location page on Facebook, Instagram, or other social platforms, those platforms pull in a preview image and headline. Without OpenGraph metadata (special tags that
Your product pages are missing Twitter Card meta tags — special HTML code that tells Twitter how to display your content when someone shares a link to your site on Twitter/X. Without this, your posts
_3 findings on this page_
Twelve images on your Schodack dispensary page are missing alt text — descriptive labels that screen readers announce to visually impaired visitors and that search engines read to understand image con
Open Graph tags are snippets of code that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your page when someone shares it. Without og:title and og:image, your dispensary's
Your product pages are missing Twitter Card tags, which are small code snippets that tell Twitter how to display your link when someone shares it on that platform. Without them, Twitter shows a plain,
_3 findings on this page_
Twelve images on your East Greenbush dispensary page don't have alt text—descriptive labels that screen readers announce to blind and low-vision visitors, and that search engines use to understand ima
Open Graph tags are snippets of code that tell social platforms (Facebook, Instagram, LinkedIn) what image and text to display when someone shares your link. Without them, your dispensary page shows u
Your product pages are missing Twitter card metadata — special HTML tags that tell Twitter (now X) how to display your content when someone shares a link. Without them, the platform shows a plain, gen
_1 finding on this page_
Your robots.txt file (the instruction file that tells search engines how to crawl your site) doesn't point to your XML sitemap. A sitemap is a roadmap of all your pages that helps search engines find
_1 finding on this page_
Your WordPress login page is publicly accessible at /wp-login.php. This is a common attack target where hackers try to break into your site by guessing usernames and passwords. While WordPress is inst
_Generated by Apex Sentinel Monthly Audit · 2026-04-19T06:58:56.639Z · Powered by Bud Authority._
Generated by Apex Sentinel · © 2026 Bud Authority