Platform: wordpress
Archetype: community
Run ID: 2026-04-19T06-18-18-831Z
Scanned: 2026-04-19T07:23:24.758Z
Duration: 673s
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 | 47 | Full sitemap + linked pages |
| P0 (critical) | 1 | Site-down or compliance-breaking |
| P1 (urgent) | 10 | Significant revenue / SEO / UX impact |
| P2 (high) | 48 | Quality / ranking / trust degradation |
| P3 (medium) | 138 | Polish + optimization |
| "Do first" items | 8 | AI-flagged top priorities |
| Quick wins (< 30 min) | 41 | Fastest ROI items |
If you only have time for ten things this month, do these — in this order.
Page: https://cityleafnj.com/wp-login.php
Effort: Moderate (1-3 hours)
Page: https://cityleafnj.com/
Effort: Moderate (1-3 hours)
Page: https://cityleafnj.com/
Effort: Quick win (< 30 min)
Page: https://cityleafnj.com/
Effort: Moderate (1-3 hours)
Page: https://cityleafnj.com/
Effort: Quick win (< 30 min)
Page: https://cityleafnj.com/
Effort: Moderate (1-3 hours)
Page: https://cityleafnj.com/
Effort: Quick win (< 30 min)
Page: https://cityleafnj.com/
Effort: Moderate (1-3 hours)
Page: https://cityleafnj.com/
Effort: Moderate (1-3 hours)
Page: https://cityleafnj.com/
Effort: Moderate (1-3 hours)
tier5.exposed.artifactWhat it means (plain English)
Your WordPress login page (/wp-login.php) is publicly accessible and returns a success response. This is a security risk because attackers can attempt to guess passwords or use automated tools to break into your site. While WordPress login pages are standard, exposing them without protection makes your site an easier target for hackers.
Why it matters for your business: An unauthorized login could allow attackers to modify your inventory, patient data, compliance documents, or age-gate settings—potentially violating cannabis regulations and losing customer trust.
Technical root cause: WordPress /wp-login.php is enabled by default and not blocked by a firewall rule (WAF) or .htaccess restriction. Your web server is not configured to require additional authentication or hide this endpoint from public access.
Recommended fix — step by step
tier1.js.page-errorWhat it means (plain English)
Your website's homepage is throwing a JavaScript error that breaks interactive features. When a visitor loads the page, a script is trying to modify an HTML element that doesn't exist or hasn't loaded yet, causing the entire interaction layer to fail. This means buttons, forms, menus, and other interactive elements may not work properly.
Why it matters for your business: Customers cannot navigate your menu, place orders, or interact with age-gate verification—directly blocking sales and creating compliance risk if the age gate fails to function.
Technical root cause: A JavaScript plugin or custom code is calling setAttribute() on a DOM element (HTML object) that is null—either because it doesn't exist on the page, or it's being referenced before the page finishes loading.
Recommended fix — step by step
tier9.a11y.aria-dialog-nameWhat it means (plain English)
Your age-gate dialog—the overlay that appears to verify visitor age before accessing the site—is missing a label that screen readers can announce. Screen reader users won't know what the dialog is for or how to interact with it. This is a serious accessibility issue under WCAG 2.1 Level AA standards.
Why it matters for your business: Screen reader users (including visually impaired customers) cannot understand or navigate your age-verification gate, effectively blocking them from your site and creating legal liability under the ADA.
Technical root cause: The #baag3-gate div has role="dialog" but lacks aria-label, aria-labelledby, or title attributes. Screen readers require one of these to announce the dialog's purpose.
Recommended fix — step by step
tier9.a11y.aria-required-childrenWhat it means (plain English)
Your homepage has a container marked as a 'list' in the accessibility code, but it contains child elements (images, subheadings, links) that aren't properly structured as list items. Screen reader users and people navigating via keyboard will encounter confusing or broken navigation because the list structure doesn't match its contents. This is a fundamental accessibility violation that blocks compliant browsing.
Why it matters for your business: Inaccessible sites expose you to ADA legal risk, exclude disabled customers from purchasing, and signal poor professionalism to search engines—harming both compliance standing and organic traffic.
Technical root cause: The Elementor page builder (likely a carousel, grid, or product loop) was assigned role="list" but its child elements don't follow the required list structure (each child should be a <li> or have role="listitem"). This mismatch typically happens when Elementor's loop container is used without proper semantic wrapping.
Recommended fix — step by step
tier9.a11y.color-contrastWhat it means (plain English)
A button on your homepage (the age-gate 'Yes' button) has white text (#ffffff) on a yellow-green background (#b4be0e) that creates a contrast ratio of only 2.03:1. WCAG accessibility standards require a minimum of 4.5:1 for text this size to be readable by people with low vision or color blindness. This fails a legal accessibility requirement.
Why it matters for your business: Cannabis retailers are subject to heightened scrutiny on compliance; accessibility violations expose you to ADA lawsuits and state regulatory penalties, especially on a critical compliance gate like age verification.
Technical root cause: The age-gate button uses inline CSS styling that pairs a light background color with white text, creating insufficient contrast. This likely originated from a theme or plugin template that wasn't tested against WCAG 2 AA standards.
Recommended fix — step by step
tier9.a11y.link-nameWhat it means (plain English)
Your website has 5 image gallery links that keyboard and screen reader users cannot identify or interact with properly. These links have no visible text, no hidden labels (aria-label), and no title attributes—so assistive technology can't tell users what these links do. This makes your site unusable for people with vision disabilities.
Why it matters for your business: You are exposed to WCAG 2.1 Level A compliance risk (legal liability in NJ), and you're excluding customers who use screen readers or keyboard navigation from exploring your product galleries.
Technical root cause: Elementor's gallery lightbox links are rendering as clickable anchors with only decorative background images and no accessible text alternative. The data-elementor-lightbox-title attribute is metadata, not accessible text.
Recommended fix — step by step
tier9.a11y.role-img-altWhat it means (plain English)
Your gallery images on the homepage have the accessibility role of 'image' but lack descriptive text that screen readers can read aloud. This means visitors using screen readers (software that reads web pages aloud for blind or low-vision users) cannot understand what these images show. You have 5 images missing this required description.
Why it matters for your business: Inaccessible galleries reduce traffic from users with disabilities, expose you to ADA litigation risk, and hurt your search rankings because Google cannot index unlabeled images.
Technical root cause: Elementor gallery elements are set to role='img' but the aria-label attributes are empty or missing. The plugin is not auto-populating alt text from image metadata.
Recommended fix — step by step
tier8.lighthouse.bestPractices-desktopWhat it means (plain English)
Your site's Lighthouse Best Practices score is 56 out of 100, which is well below the healthy threshold of 90. This score reflects issues like outdated libraries, missing security headers, or browser compatibility problems that erode user trust and can harm search rankings. The full details are in your Lighthouse HTML report, which lists each specific violation.
Why it matters for your business: A low Best Practices score signals to search engines and visitors that your site may have security or reliability issues—especially critical for a cannabis retailer where compliance and customer trust directly affect sales and legal standing.
Technical root cause: Best Practices violations typically stem from outdated WordPress plugins, missing HTTP security headers (like Content-Security-Policy or X-Frame-Options), unpatched dependencies, or third-party scripts that lack proper security configuration.
Recommended fix — step by step
tier11.browser.webkit-js-errorsWhat it means (plain English)
Your website has a JavaScript error that appears in Safari and other Apple browsers (WebKit) but not in Chrome. The error occurs when code tries to modify an HTML element (the mobile viewport tag) that doesn't exist or hasn't loaded yet. This causes features or page behavior to break for Safari users, particularly on iPhones and iPads.
Why it matters for your business: Safari represents ~25-30% of mobile traffic for most cannabis retail sites; broken functionality for these users directly reduces conversions, user engagement, and compliance form submissions.
Technical root cause: JavaScript is attempting to call setAttribute() on a null object, likely because the mobile viewport meta tag isn't present in the DOM when the script executes, or a script is running before the DOM is fully parsed. Safari's error handling differs slightly from Chrome, exposing the issue.
Recommended fix — step by step
tier11.browser.firefox-js-errorsWhat it means (plain English)
Your site has a JavaScript error that appears in Firefox but not Chrome. The code is trying to call a method (setAttribute) on something that doesn't exist (null). This usually happens when a script looks for an HTML element on the page before that element has loaded, or the element doesn't exist at all. Firefox reports this differently than Chrome, which is why you're seeing it only in Firefox.
Why it matters for your business: Firefox users may experience broken interactive features, missing buttons, or site elements that don't respond correctly, leading to lost sales and customers switching to competitors.
Technical root cause: A JavaScript file is attempting to access or modify an HTML element (likely with an id or class selector) that either doesn't exist on the page or hasn't finished loading when the script runs. The script references a variable called 'mvp' which is null.
Recommended fix — step by step
mvp.setAttribute(...) to if (mvp) { mvp.setAttribute(...) } or mvp?.setAttribute(...) if using modern JavaScript.tier5.mixed-contentWhat it means (plain English)
Your website is served over HTTPS (secure), but some code references are pointing to HTTP (non-secure) URLs. These are Schema.org markup references—structured data that helps search engines understand your site. Browsers may flag or downgrade trust, though in this case the actual resources are schema definitions (not loaded assets), so the practical risk is low.
Why it matters for your business: While these specific schema.org references are safe, mixed-content warnings can erode customer trust and may marginally impact search rankings; for a cannabis retailer where compliance perception matters, clean security signals are important.
Technical root cause: WordPress or a theme/plugin is hardcoding http://www.schema.org/ URIs in JSON-LD structured data blocks. Schema.org URIs are namespace definitions (not fetched assets) and work over HTTP or HTTPS interchangeably, but best practice is to use https:// to avoid any browser warnings.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 37 images without alternative text descriptions. Alt text is hidden text that describes what an image shows — it helps screen readers (used by people who are blind or have low vision) understand images, and it also helps search engines understand your content. Right now, over 90% of your images are missing these descriptions.
Why it matters for your business: Missing alt text reduces your search visibility for product images and dispensary photos, and it creates legal risk under accessibility laws (ADA); customers using assistive technology cannot understand your product catalog.
Technical root cause: Images were likely uploaded to WordPress or added via Elementor without filling in the Alt Text field during upload or insertion. This is a common oversight when bulk-uploading product photos or hero images.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 37 images out of 41 total that lack alt text — the descriptive label that tells screen readers and search engines what an image shows. This means visually impaired customers cannot understand product photos or store information, and Google cannot index those images for search results. It's a double hit: accessibility barrier + lost SEO opportunity.
Why it matters for your business: Customers using screen readers (including legally blind patients) cannot identify products or navigate your dispensary info; you're also losing image search traffic for strain names, product types, and cannabis-related queries that could drive new customers.
Technical root cause: Images were uploaded to WordPress without alt text filled in during upload, or alt text fields were left blank. WordPress doesn't enforce alt text, so it defaults to missing.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Nine images on your blog post about recreational cannabis lack alt text — descriptive labels that screen readers read aloud to blind/low-vision visitors. Search engines also use alt text to understand image content, so missing it weakens your SEO for image search and topic relevance.
Why it matters for your business: Missing alt text blocks accessibility for disabled customers (legal risk in NJ + bad optics for a wellness brand), and costs you search ranking points on a high-intent wellness article that could drive traffic.
Technical root cause: Images were inserted into the WordPress post without filling in the Alt Text field in the image block or media library; WordPress allows this by default.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Five images on your Newark cannabis guide page don't have alt text — descriptive labels that explain what each image shows. Search engines and screen readers (tools that help blind/low-vision visitors navigate your site) can't understand unlabeled images, so they miss important content.
Why it matters for your business: Missing alt text reduces your SEO ranking for cannabis keywords, blocks accessibility compliance, and means some of your visitors literally can't see or understand your product/guide content.
Technical root cause: Images were uploaded to WordPress without filling in the Alt Text field in the media library during insertion, or the image blocks were added without the alt attribute populated.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Five images on your Cannabis Concentrates Guide page don't have alt text—descriptive text that explains what the image shows. Screen readers (used by blind and low-vision visitors) can't describe these images, and search engines can't understand what they depict. This makes your content less accessible and less discoverable.
Why it matters for your business: Visitors using assistive technology will miss critical product or educational information, reducing engagement and potential sales. Google also uses alt text to rank image search results, so missing alt text means you're losing organic search traffic for cannabis product images.
Technical root cause: Images were likely uploaded or embedded in the WordPress editor without filling in the Alt Text field during upload, or alt text was removed during a content migration or theme update.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Six images on your blog page lack alternative text (alt text) — descriptive labels that screen readers announce to visually impaired visitors and that search engines use to understand image content. This creates barriers for accessibility and reduces your blog's visibility in image search results.
Why it matters for your business: Visitors using screen readers cannot understand your blog content, limiting your audience reach; additionally, search engines rank blog posts partly on image optimization, so missing alt text directly harms your SEO traffic and discovery.
Technical root cause: Images were inserted into WordPress posts without filling the 'Alt Text' field in the image block or media library settings, leaving the alt attribute empty.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your Harrison, NJ page has 11 images without alt text—alternative text that describes what's in the image. Screen readers (tools blind and low-vision visitors use) can't tell users what those images show. Search engines also can't read images without alt text, so you're missing keyword opportunities that could bring traffic from image search.
Why it matters for your business: Customers using assistive technology may leave your site frustrated; you're also losing SEO value in Google Images and missing compliance with accessibility law (ADA), which cannabis retailers are increasingly expected to follow.
Technical root cause: Images were uploaded to WordPress without filling in the Alt Text field in the Media Library or the image block settings. WordPress doesn't auto-generate alt text, so images default to missing or empty alt attributes.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your website has 11 images without alt text (descriptive text read aloud by screen readers and used by search engines). This prevents visually impaired customers from understanding what those images show, and it signals to Google that you're missing SEO signals. On the Kearny, NJ page specifically, 11 of 14 images lack this description.
Why it matters for your business: Visually impaired customers cannot navigate your site or learn about your products/locations, reducing accessibility and potentially violating ADA compliance. Search engines also rank pages with complete alt text higher, which directly affects local SEO for your "areas we serve" content.
Technical root cause: Images were uploaded to WordPress without filling in the Alt Text field in the media editor, or were inserted via HTML without the alt attribute. WordPress stores alt text in the media library, but it only displays in the frontend if explicitly set during upload or via the image block editor.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Eleven images on your Newark service page are missing alt text — a brief description that screen readers announce to visually impaired visitors and that search engines use to understand image content. This creates both an accessibility barrier (some customers cannot use your site) and a missed SEO opportunity (Google can't index what those images show).
Why it matters for your business: Visually impaired customers cannot navigate your service areas, and you're losing search traffic for location-based queries like 'cannabis dispensary near Newark' because Google doesn't know what those images depict.
Technical root cause: Images were likely uploaded to WordPress without filling in the 'Alt Text' field in the Media Library, or alt attributes were stripped during theme/plugin updates.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your Bloomfield page has 11 images missing alt text — short descriptions that explain what each image shows. Screen readers (tools blind customers use to browse the web) can't tell visitors what these images are, and search engines can't understand them either. This means you're invisible to both accessibility tools and search rankings for image-related queries.
Why it matters for your business: Blind and low-vision customers can't navigate your dispensary pages, potentially creating legal exposure under ADA compliance rules; you also lose SEO credit for product photos and location images that could drive local search traffic.
Technical root cause: Images were uploaded to WordPress without alt text filled in during the media upload process, or the image blocks in the page editor weren't configured with descriptions.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Eleven images on your East Orange service area page are missing alt text — short descriptions that screen readers read aloud and search engines use to understand image content. This makes your page harder for visually impaired customers to navigate and signals incomplete content to Google.
Why it matters for your business: Missing alt text reduces your search ranking for local cannabis keywords (especially important for 'East Orange' + product discovery) and excludes potential customers using screen readers or visiting on slow connections where images don't load.
Technical root cause: Images were uploaded to WordPress without filling in the 'Alt Text' field in the Media Library, or the alt attributes were left blank when images were inserted into the page.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your Jersey City page has 11 images without alt text — short descriptions that explain what each image shows. Search engines and screen readers (used by people with vision loss) can't understand images without these descriptions. This hurts both your accessibility and your search ranking.
Why it matters for your business: Customers using assistive technology can't navigate your location pages, and Google ranks sites with complete alt text higher in local search results — critical for a dispensary competing on geographic keywords.
Technical root cause: Images were uploaded to WordPress without alt text filled in during upload, or alt fields were left blank in the media library or image blocks.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Eleven images on your Hoboken service page are missing alt text — descriptive labels that screen readers use to describe images to blind and low-vision visitors. These missing labels also prevent search engines from understanding what your images show, which weakens SEO for image search and general ranking.
Why it matters for your business: Missing alt text blocks potential customers using screen readers from understanding your dispensary locations and product photos, and reduces your visibility in Google Images — a significant traffic source for local cannabis searches.
Technical root cause: Images were uploaded to WordPress without filling in the Alt Text field in the Media Library, or the field was left blank during initial page creation.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your delivery page has 9 images that lack alt text — a short description that appears if an image fails to load and that search engines read to understand your content. This makes the page harder for people using screen readers and reduces your visibility in image search results.
Why it matters for your business: Customers with visual impairments may struggle to navigate your delivery service page, and you're missing opportunities to rank in Google Images and attract new customers searching for cannabis delivery in Jersey City.
Technical root cause: Images were uploaded to WordPress without alt text filled in during the media upload process, or images were added via HTML/theme code without alt attributes.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Nine images on your Hoboken delivery page don't have alt text—descriptive labels that screen readers read aloud to blind or low-vision visitors. Search engines also use alt text to understand what images show, which helps your pages rank for image searches and reinforces topic relevance.
Why it matters for your business: Missing alt text locks out customers using assistive technology, exposes you to accessibility complaints, and wastes SEO opportunity—especially important for a local dispensary where image-rich product pages drive organic traffic.
Technical root cause: Images were likely uploaded to WordPress media library and inserted into the page without filling in the 'Alt Text' field, or a theme template is generating images (like hero banners or product thumbnails) without programmatic alt attributes.
Recommended fix — step by step
<img> tag includes alt="your description".tier2.a11y.img-missing-altWhat it means (plain English)
Nine images on your Kearny delivery page don't have alt text—descriptions that tell search engines and screen readers what each image shows. This hurts both accessibility (people using screen readers can't understand the images) and SEO (Google can't index them properly).
Why it matters for your business: Customers using assistive technology get a degraded experience, and you're losing SEO value on a key local service page that should rank for 'cannabis delivery Kearny NJ' and similar queries.
Technical root cause: WordPress images were uploaded or embedded without filling in the Alt Text field in the image block settings, or were added via HTML without an alt attribute.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Nine images on your Newark delivery page don't have alt text — a short description that describes what the image shows. Search engines and screen readers (used by people with vision loss) can't understand unlabeled images, which means you're losing SEO value and excluding a portion of your audience.
Why it matters for your business: Missing alt text hurts your Google rankings for delivery-related searches and makes your site inaccessible to customers using assistive technology, reducing trust and potential sales.
Technical root cause: Images were uploaded or added to the page without filling in the 'Alt Text' field in the WordPress media editor, leaving the alt attribute blank or missing entirely.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Nine images on your East Orange delivery page don't have alt text—descriptions that explain what each image shows. Screen readers (software that helps blind and low-vision customers browse your site) can't tell users what these images are. Search engines also can't index the content, so you're losing a ranking opportunity.
Why it matters for your business: Potential customers using assistive technology can't understand your product images, reducing accessibility and limiting your audience. Missing alt text also hurts SEO for dispensary pages, making it harder for customers searching for 'cannabis delivery near me' to find you.
Technical root cause: Images were uploaded to WordPress without filling in the Alt Text field during upload or in the image settings. WordPress doesn't auto-generate useful alt text.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Nine images on your Bloomfield delivery page are missing alt text — a brief text description that screen readers use to understand images, and that search engines use to index them. This means customers using screen readers cannot understand what those images show, and Google cannot learn what your products or location look like.
Why it matters for your business: Missing alt text reduces organic search visibility for product images and location photos, and excludes customers with visual impairments or those using assistive technology — a legal accessibility risk for a retail site.
Technical root cause: Images were uploaded to WordPress without entering alt text in the media library, or image blocks/galleries were inserted without alt attributes populated during publishing.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Nine images on your Harrison delivery page don't have alt text—descriptive labels that screen readers read aloud and search engines use to understand what's in the image. This blocks visually impaired customers from knowing what products or information they're seeing, and Google penalizes pages with poor accessibility.
Why it matters for your business: Customers using screen readers can't identify your products or dispensary features on that page, reducing trust and repeat visits. Google also ranks pages with complete alt text higher in search results, so fixing this helps your delivery pages show up when local customers search for dispensaries.
Technical root cause: Images were uploaded to WordPress without alt text filled in during upload or via the Media Library. WordPress allows images to be added without the alt field populated.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your About Us page has 13 images without alternative text descriptions. Alt text is invisible text attached to images that describes what they show. Search engines and screen readers (used by people with vision impairments) rely on alt text to understand images, since they can't see them directly.
Why it matters for your business: Missing alt text reduces your search ranking potential for image-based queries, limits your reach to customers using accessibility tools, and may expose you to ADA compliance risk if a visitor with a disability cannot access your content.
Technical root cause: Images were uploaded to WordPress without filling in the Alt Text field in the image block or media library. WordPress allows images to be published without alt text, but best practice requires it for every image.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your website has 11 images without alt text (descriptive text that appears if an image fails to load). This prevents visually impaired customers using screen readers from understanding what those images show, and it also means search engines can't "read" those images to rank your pages higher. On the Belleville, NJ page, 11 out of 14 images are missing this description.
Why it matters for your business: Visually impaired customers can't navigate your dispensary locations or products, reducing accessibility compliance risk and limiting your market reach; Google also ranks pages with properly described images higher in local search results for 'cannabis near me' queries.
Technical root cause: Images were uploaded to WordPress without filling in the 'Alt Text' field in the media library, or alt attributes were left blank in the image blocks.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Seven images on your Weed Delivery page lack alt text — a description that screen readers announce to blind/low-vision visitors and that search engines use to understand image content. This blocks accessibility compliance and leaves SEO value on the table, since Google can't index what those images show.
Why it matters for your business: Missing alt text reduces your ranking for image-based search queries (e.g., 'cannabis strains Jersey City'), locks out customers using assistive technology, and increases legal risk under accessibility lawsuits common in cannabis retail.
Technical root cause: Images were uploaded to WordPress without alt text filled in the Media Library, or alt fields were left blank when images were inserted into the post/page editor.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Seven images on your Newark delivery page don't have alt text — descriptive labels that screen readers use to understand images, and that search engines use to index them. This means visually impaired customers can't understand what those images show, and Google can't properly catalog them for search results.
Why it matters for your business: Missing alt text hurts both accessibility (excluding disabled customers) and SEO rankings for product/strain imagery, which is critical for a dispensary site where visual appeal drives purchasing decisions.
Technical root cause: Images were uploaded to WordPress without filling in the Alt Text field during upload or in the Media Library, or they were embedded via HTML/code without alt attributes.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Nine images on your Belleville delivery page don't have alt text—descriptions that tell screen readers (and search engines) what each image shows. This means visually impaired customers can't understand what those images are, and Google has a harder time indexing them. It's a quick fix that improves both accessibility and search ranking.
Why it matters for your business: Customers using screen readers abandon pages they can't navigate; Google ranks pages with proper alt text higher in search results, directly affecting your ability to be found by customers searching for cannabis delivery in Belleville.
Technical root cause: Images were uploaded to WordPress without alt text filled in during the upload/edit process, or the theme's image block doesn't enforce alt text as required.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 37 images without alternative text (alt text) — a brief description that appears when an image fails to load and is read aloud by screen readers for visually impaired visitors. This breaks accessibility for customers who rely on assistive technology and also signals to search engines that your content may be incomplete or lower quality.
Why it matters for your business: Customers using screen readers cannot understand product photos, strains, or dispensary visuals, reducing sales from disabled visitors; search engines also rank pages with missing alt text lower, hurting your organic visibility for product and location searches.
Technical root cause: Images were likely added via Elementor (WordPress page builder) without filling in the Alt Text field during upload, or bulk-imported content skipped alt text entirely.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 37 images without alt text — descriptive labels that tell search engines and visitors using screen readers what the image shows. This hurts both accessibility (people using assistive technology can't understand your product photos) and SEO (Google can't index what's in those images, missing ranking opportunities).
Why it matters for your business: Customers with visual impairments can't browse your menu or products, and you're losing organic search traffic because Google doesn't know what those product photos depict — particularly damaging for a dispensary where product images drive discovery and trust.
Technical root cause: Images in your Elementor-built pages (the page builder WordPress uses) are missing the alt attribute. This typically happens when images are uploaded and inserted without filling in the alt text field during upload or when legacy content wasn't retrofitted.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 37 images without alt text — descriptive text that explains what each image shows. This text is read aloud by screen readers (tools visually impaired customers use to browse the web) and also helps search engines understand your images. Without it, those images are invisible to both people and Google.
Why it matters for your business: Visually impaired customers cannot understand product images or dispensary photos, reducing accessibility and potential sales; search engines cannot index your images, costing you visibility in Google Image Search where cannabis product searches are common.
Technical root cause: Images in Elementor (your page builder) were added without filling in the 'Alt Text' field. WordPress stores alt text in the image's alt attribute, which is empty on these 37 images.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 37 images without alt text — short descriptions that explain what each image shows. Search engines and assistive technologies (used by visually impaired visitors) rely on this text to understand images. Without it, you're losing ranking signals and excluding customers who use screen readers.
Why it matters for your business: Missing alt text reduces your SEO visibility for product and strain images, and it creates compliance risk under accessibility laws (ADA / WCAG 2.1 AA), which cannabis retailers face increasing scrutiny on.
Technical root cause: Elementor (your page builder) allows images to be inserted without requiring alt text entry. The loop-item template in your library likely has untagged product or menu images that were bulk-imported or created without alt fields being populated.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 37 images without alt text — descriptive text that explains what the image shows. Search engines and assistive technology (software that helps people with vision loss) can't understand image content without it. This hurts both accessibility for customers and your visibility in Google Images.
Why it matters for your business: Customers using screen readers or with slow connections won't know what products you're showing; you're also missing keyword signals in Google Images, which drives discovery traffic to dispensaries.
Technical root cause: Images uploaded to WordPress and embedded via Elementor likely lack the alt text field filled in during upload or insertion. Elementor allows alt text but it wasn't populated when these images were added.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
37 images on your site lack alternative text (alt text) — a short description that search engines and assistive technology (used by people with vision impairments) read when they can't see the image. This hurts both discoverability and accessibility compliance, especially for product images and license/compliance graphics that customers and regulators need to understand.
Why it matters for your business: Missing alt text reduces your SEO rankings for product pages, blocks access for customers using screen readers, and creates compliance risk if license or age-gate imagery isn't described for regulators auditing your site.
Technical root cause: Images uploaded to Elementor (your page builder) or WordPress media library were added without alt text filled in at the time of upload. Elementor doesn't require alt text, so editors skip it.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your site has 37 images without alt text — short descriptions that tell screen readers and search engines what each image shows. This blocks customers using assistive technology from understanding your product photos and violates accessibility standards. It also loses SEO value because search engines can't index what's in those images.
Why it matters for your business: Customers with visual impairments can't shop your products effectively, and you're missing keyword opportunities that image alt text provides to Google — especially important for cannabis product discovery and local SEO.
Technical root cause: Images were likely added via Elementor (WordPress page builder) or media uploads without completing the alt text field, which is optional by default in WordPress and Elementor.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your website has 37 images without alt text — alternative text that describes what the image shows. Search engines and screen readers (used by people with vision disabilities) can't understand images without this description. This means potential customers using assistive technology can't navigate your site, and Google can't index your product images or cannabis strains properly.
Why it matters for your business: Missing alt text reduces search visibility for product images, blocks accessibility (a legal risk under ADA), and frustrates customers who rely on screen readers — shrinking your addressable market and exposing you to compliance complaints.
Technical root cause: Images were likely added via Elementor or the WordPress media library without alt-text fields being filled in during upload. Elementor's visual editor makes it easy to drop images without requiring the alt field, leaving it blank by default.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Your website has 37 images without alt text — descriptive labels that screen readers use to tell blind/low-vision visitors what an image shows, and that search engines use to understand your content. Right now, nearly 90% of your images are invisible to both assistive technology users and search bots.
Why it matters for your business: Missing alt text locks out customers using screen readers, exposes you to accessibility complaints, and prevents Google from indexing product photos and dispensary imagery — directly reducing organic search visibility for strain names, products, and 'cannabis near me' queries.
Technical root cause: Elementor (the page builder) allows images to be uploaded without requiring alt text entry. Most images on the site, particularly in the footer and product galleries, were inserted without the alt field populated.
Recommended fix — step by step
tier2.links.brokenWhat it means (plain English)
Your site has 2 broken internal links that point to email-protection pages (these are Cloudflare email obfuscation URLs). When search engines or visitors click these links, they hit a 404 error page instead of landing on valid content. This wastes crawl budget and creates a poor user experience when someone tries to contact you.
Why it matters for your business: Broken contact links on your About Us and legal pages prevent potential customers from reaching out, directly harming customer acquisition for your dispensary.
Technical root cause: Cloudflare's email protection feature (Flexible SSL) generates these cdn-cgi URLs automatically. However, they're being indexed as internal links instead of remaining as obfuscated email text in the page source. This typically happens when the email addresses are wrapped in anchor tags (<a> elements) rather than being protected as plain text.
Recommended fix — step by step
tier3.perf.mobile-failWhat it means (plain English)
The performance testing tool timed out while trying to load your homepage on a mobile device, meaning the page took longer than 60 seconds to fully load. This suggests either a slow server response, large unoptimized images or scripts, or external services (ads, analytics, maps) that are blocking page completion.
Why it matters for your business: Slow mobile load times cause visitors to leave before seeing your inventory, compliance info, or contact details—directly reducing foot traffic and online orders, especially since most cannabis shoppers search on mobile.
Technical root cause: WordPress sites often load render-blocking JavaScript, unoptimized media, or unresponsive plugins. The 'networkidle' wait condition requires all network requests to finish, which fails if any external service (tracking pixel, ad network, third-party map) hangs or never completes.
Recommended fix — step by step
tier5.header.strict-transport-securityWhat it means (plain English)
Your site is missing an HTTP security header called Strict-Transport-Security (HSTS), which tells browsers to always use encrypted HTTPS connections when visiting your domain. Without it, a visitor's first request to your site could be intercepted and redirected to a fake copy. Since you're hosted on WP Engine and fronted by Cloudflare, this header is easy to add.
Why it matters for your business: For a cannabis retailer handling age verification, payment info, and customer data, missing HSTS increases the risk of man-in-the-middle attacks that could expose customer information or redirect visitors to phishing sites, damaging trust and compliance.
Technical root cause: The HSTS header is not being set by your WordPress hosting (WP Engine) or Cloudflare edge configuration. It must be explicitly configured at one of those two layers.
Recommended fix — step by step
tier5.header.x-frame-optionsWhat it means (plain English)
Your website is missing the X-Frame-Options security header, which tells browsers whether your site can be embedded inside iframes on other websites. Without it, attackers could potentially embed your site in a malicious page to trick users or steal information. This is a standard security practice that most sites implement.
Why it matters for your business: Missing this header weakens your site's security posture, potentially exposing customers to clickjacking attacks and damaging trust in your brand—especially critical for a cannabis retailer handling age-gated content and customer data.
Technical root cause: The header is not being set by your WordPress hosting environment (WP Engine) or Cloudflare configuration. It must be explicitly added either in your server config, Cloudflare rules, or WordPress security plugin.
Recommended fix — step by step
tier5.header.content-security-policyWhat it means (plain English)
Your website is missing a Content Security Policy (CSP) header — a security directive that tells browsers which sources of content (scripts, images, stylesheets) are trusted. Without it, attackers could inject malicious code more easily. This is a common WordPress gap, especially on WP Engine hosting where CSP must be explicitly configured.
Why it matters for your business: A CSP breach could expose customer data, compromise your age-gate compliance, or deface your site — damaging trust and triggering regulatory scrutiny in the heavily-monitored cannabis industry.
Technical root cause: WP Engine does not set a default CSP header; it must be configured either via WordPress plugin, .htaccess rules, or WP Engine's own control panel. The current setup has Cloudflare in front, but no CSP policy is being sent from the origin.
Recommended fix — step by step
tier5.fortress.spf-missingWhat it means (plain English)
Your domain cityleafnj.com does not have an SPF (Sender Policy Framework) record published in DNS. SPF is a simple text record that tells email providers which servers are authorized to send mail from your domain. Without it, emails from your business (order confirmations, newsletters, password resets) are likely flagged as spam or rejected entirely.
Why it matters for your business: Customers won't receive order confirmations, account notifications, or marketing emails, leading to lost revenue, support tickets, and damaged trust.
Technical root cause: No SPF record (v=spf1) has been added to the DNS zone for cityleafnj.com. You have a DMARC policy in place but no SPF mechanism to enforce sender authentication.
Recommended fix — step by step
tier6.a11y.small-targetsWhat it means (plain English)
Your site has 36 buttons, links, and other clickable elements that are smaller than 44×44 pixels on mobile phones. This is below the Web Content Accessibility Guidelines (WCAG) standard, which means visitors with motor impairments or anyone using a phone one-handed will struggle to tap them accurately. Many will miss and tap the wrong element, creating frustration and abandoned visits.
Why it matters for your business: Users with accessibility needs or poor dexterity abandon sites with tiny tap targets—you lose potential customers and expose the business to accessibility complaints; this is especially important in the cannabis industry where compliance scrutiny is high.
Technical root cause: Interactive elements (buttons, menu items, links, form inputs) are styled with CSS widths and heights below 44px, or padding is insufficient. This often happens when desktop designs are not adapted for mobile screens, or when CSS frameworks set small default sizes.
Recommended fix — step by step
tier6.a11y.small-targetsWhat it means (plain English)
Your website has 38 interactive buttons, links, and form fields that are smaller than 44×44 pixels on mobile devices. This makes them difficult to tap accurately, especially for people with motor impairments, arthritis, or those using a phone in one hand. The Web Content Accessibility Guidelines (WCAG) require a minimum 44×44 pixel target size to meet accessibility standards.
Why it matters for your business: Customers with accessibility needs may abandon your site due to frustration with small tap targets, reducing conversion on product pages and age verification. You also risk legal liability under the ADA if accessibility complaints are filed.
Technical root cause: The theme or custom CSS is applying font sizes, padding, or button dimensions that render below the 44px minimum on mobile viewports. This is often caused by overly aggressive responsive scaling or insufficient mobile padding in button/link styling.
Recommended fix — step by step
button, a, input[type='button'], .menu-item { min-height: 44px; min-width: 44px; padding: 12px 16px; }tier6.a11y.small-targetsWhat it means (plain English)
Your website has 38 interactive buttons, links, and form fields that are smaller than 44×44 pixels when viewed on mobile phones. This makes them hard to tap accurately—especially for people with less precise fine motor control, older adults, or anyone using a phone one-handed. WCAG 2.5.5 (Web Content Accessibility Guidelines) is the accessibility standard that requires touch targets be at least 44×44 pixels.
Why it matters for your business: Visitors—including older cannabis customers and those with accessibility needs—will have friction completing age-gate verification, product searches, or checkout, leading to abandoned visits and lower conversion rates. Accessibility lawsuits in the cannabis vertical are rising.
Technical root cause: WordPress theme or custom CSS is likely using small buttons, link padding, or form inputs without mobile-specific size rules. Navigation menus, product filters, and call-to-action buttons are often cramped on mobile by default.
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 a tablet. This makes them hard to tap accurately, especially for people with motor control challenges or using touchscreens. WCAG 2.5.5 is an accessibility standard that requires interactive elements to meet a minimum size so all visitors can use your site comfortably.
Why it matters for your business: Visitors on tablets—including older customers and those with dexterity challenges—may struggle to add products to cart, click age-gate buttons, or navigate menus, leading to abandoned browsals and lost sales. Poor accessibility also signals unprofessionalism and may trigger complaints or scrutiny from disability advocacy groups.
Technical root cause: The theme or custom CSS is using padding-poor button styling, narrow menu links, or icon-only navigation elements that don't meet the 44×44 minimum. This often happens when designs are optimized for desktop-sized fingers (large pointers) and not tested on actual touch devices.
Recommended fix — step by step
button, a.button, .menu a { min-height: 44px; min-width: 44px; padding: 12px 16px; } to set a baseline.tier10.journey.page-errorsWhat it means (plain English)
Your homepage is encountering two JavaScript errors after the age gate loads and the menu becomes visible. These errors occur when the browser tries to interact with HTML elements that either don't exist or haven't loaded yet — specifically, code is trying to set an attribute on an element (setAttribute) and check if an element contains something (contains) but finding nothing instead. While visitors may not see obvious breakage, these errors can prevent interactive features from working properly.
Why it matters for your business: JavaScript errors on your homepage can break the age-gate experience, menu navigation, or add-to-cart functionality, causing potential customers to leave before completing a purchase.
Technical root cause: A WordPress plugin or custom theme script is attempting to manipulate DOM elements (likely related to age verification or menu functionality) before those elements are fully rendered in the page, or the selectors used to find those elements are incorrect and return null.
Recommended fix — step by step
tier2.meta.no-descriptionWhat it means (plain English)
Your blog category page (/category/blog/) doesn't have a meta description — the 150-160 character summary that appears below your page title in Google search results. Without it, Google generates a random snippet from your page content, which often looks unprofessional and may not encourage clicks.
Why it matters for your business: Missing meta descriptions reduce click-through rates from search results; potential customers see a poorly formatted preview instead of your curated message, directly impacting blog traffic and brand perception.
Technical root cause: WordPress doesn't automatically generate meta descriptions for category archive pages. You likely have a plugin (Yoast SEO, Rank Math, etc.) installed but haven't filled in the description field for this specific category.
Recommended fix — step by step
tier9.a11y.landmark-uniqueWhat it means (plain English)
Your main navigation menu doesn't have a unique name that screen readers can use to distinguish it from other navigation areas on the page. Right now, it's labeled generically as "Menu," which creates confusion for visitors using assistive technology who may hear multiple identical landmark announcements. This is a best-practice accessibility issue that doesn't block functionality but does reduce usability for disabled visitors.
Why it matters for your business: Visitors relying on screen readers may struggle to navigate your site efficiently, potentially reducing time-on-site and conversions; this also exposes you to accessibility compliance risk in a regulated industry.
Technical root cause: The nav element has aria-label="Menu" but no additional distinguishing attribute. WordPress/Elementor's default menu landmark lacks a unique accessible name; if multiple navigation regions exist (e.g., main menu + footer menu), they become indistinguishable to assistive technology.
Recommended fix — step by step
tier4.schema.missing-coreDetail
Every site should emit Organization + LocalBusiness + WebSite JSON-LD.
tier2.robots.no-sitemapWhat it means (plain English)
Your robots.txt file (a plain-text file that tells search engines what pages to crawl) doesn't include a link to your XML sitemap. The sitemap is like a master map of every page on your site that you want Google and Bing to index. Without this pointer, search engines have to discover your pages the slow way—by following links. For a dispensary site with product pages, locations, and info pages that might not be heavily cross-linked, this slows down search visibility.
Why it matters for your business: Slower indexing of your product inventory and menu pages means slower appearance in local search results, which directly impacts customers finding you online.
Technical root cause: WordPress doesn't automatically add the Sitemap directive to robots.txt. An SEO plugin like Yoast, Rankmath, or All in One SEO usually does this, but it requires configuration or the plugin may not be active.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Three images on your articles page lack alt text — the hidden description that screen readers (used by blind and low-vision visitors) read aloud, and that search engines use to understand what images show. This means some of your audience cannot access the content, and Google gets less context to rank your pages.
Why it matters for your business: Missing alt text reduces your search visibility for image-based queries (e.g., product photos, strain reviews) and excludes disabled customers from browsing your content — both legal and commercial risks.
Technical root cause: Images were uploaded to WordPress without filling in the Alt Text field in the media library, or they were added via HTML without an alt attribute.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
OpenGraph tags are snippets of code that control how your site preview appears when someone shares a link on Facebook, Instagram, or other social platforms. Without them, shared links show a generic or broken preview, which looks unprofessional and discourages clicks. This is especially important for cannabis retailers, where word-of-mouth and social sharing drive foot traffic.
Why it matters for your business: Missing OpenGraph metadata reduces click-through rates when customers share your dispensary location or product pages on social media, directly impacting foot traffic and online visibility.
Technical root cause: The WordPress site's theme or SEO plugin is not outputting og:title and og:image meta tags in the page <head>. This is typically a configuration gap in the site's SEO settings or theme defaults.
Recommended fix — step by step
tier2.meta.title-lengthWhat it means (plain English)
Your page title is 90 characters long, but search engines like Google typically display only 50–65 characters in search results before truncating with an ellipsis (…). When your title is too long, the important part of your message gets cut off, making it less compelling to potential customers clicking through from search results.
Why it matters for your business: Truncated titles in search results reduce click-through rates from customers searching for cannabis wellness information, directly impacting traffic and foot traffic to your dispensary.
Technical root cause: The WordPress page title (set via Yoast SEO, All in One SEO, or the theme's title tag) exceeds the recommended 50–65 character range that renders fully in most search engine results.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
Open Graph tags are metadata snippets that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your page when someone shares it. Without them, your posts appear bland—no custom title, description, or image—which reduces click-through rates and looks unprofessional.
Why it matters for your business: When customers share your wellness or product content on social media, missing Open Graph tags cause poor previews, discouraging friends from clicking through, which means lost foot traffic and repeat customer referrals.
Technical root cause: The WordPress page or post lacks og:title, og:image, and related Open Graph meta tags in the <head> section. This typically happens when an SEO plugin is not installed, not configured, or the theme doesn't inject these tags automatically.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your blog post isn't configured to display nicely when shared on social media platforms like Twitter/X. Without a Twitter card meta tag, when someone shares your post, it will show only plain text and a generic thumbnail instead of an attractive preview with your chosen image, headline, and description.
Why it matters for your business: Missing social card metadata reduces click-through rates on social shares, limiting organic traffic from Twitter/X where cannabis education and community engagement drive awareness and foot traffic to your dispensary.
Technical root cause: The page is missing the <meta name="twitter:card"> tag and related Open Graph meta tags (og:image, og:title, og:description) in the page header, which social platforms use to render rich previews.
Recommended fix — step by step
tier2.meta.title-lengthWhat it means (plain English)
Your page title (the text that appears in browser tabs and search results) is 76 characters long, but search engines typically truncate titles longer than 60 characters on desktop and 55 on mobile. This means visitors searching Google won't see your full title — it'll be cut off mid-sentence, which looks unprofessional and may reduce click-through rates.
Why it matters for your business: Truncated titles in search results lower click-through rates from potential customers searching for cannabis consumption methods, directly reducing qualified traffic to your articles and product pages.
Technical root cause: The WordPress page or post title, or the SEO plugin's custom title field, contains 76 characters. Most search engines display 50–60 characters before truncating with an ellipsis (…).
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares your articles page on Facebook, Instagram, or other social platforms, those sites pull in a title and image to display in the preview. Without OpenGraph metadata (special HTML tags that tell social platforms what to show), your link will display generically or incorrectly, making it less likely people will click through.
Why it matters for your business: Poor social sharing preview reduces click-through rates on shared posts, losing potential customers who discover you through social media word-of-mouth or your own team's promotional posts.
Technical root cause: The page's HTML header is missing og:title and og:image meta tags. WordPress doesn't add these automatically; they must be configured via a plugin (like Yoast SEO, All in One SEO, or Rank Math) or manually inserted into the theme template.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When this article is shared on Facebook, Instagram, or other social platforms, those sites can't pull a custom title or image to display in the preview. Instead, users see whatever generic fallback the platform provides—usually just the page URL and a bland thumbnail. This makes your content look less professional and less clickable when shared.
Why it matters for your business: Lower click-through rates on social shares means fewer visitors from social traffic, and reduced brand credibility when your content appears in newsfeeds alongside competitors who have polished previews.
Technical root cause: The WordPress page is missing og:title, og:image, og:description, and og:url meta tags in the <head> section. Most WordPress SEO plugins (like Yoast or Rank Math) auto-generate these, but they may not be configured or enabled for blog posts.
Recommended fix — step by step
tier2.a11y.img-missing-altWhat it means (plain English)
Four images on your blog post about cannabis and creativity don't have alt text — brief descriptions that explain what the image shows. Alt text serves two purposes: it helps people using screen readers understand the image, and it tells search engines what the image contains so it can appear in image search results.
Why it matters for your business: Missing alt text reduces your visibility in Google Images (a source of organic traffic) and makes your content inaccessible to visitors using assistive technology, which can expose you to accessibility complaints.
Technical root cause: Images were likely uploaded to WordPress without filling in the Alt Text field during upload or insertion, or the field was left blank when the post was created.
Recommended fix — step by step
tier2.meta.no-ogWhat it means (plain English)
When someone shares your blog post on Facebook, LinkedIn, or other social platforms, those sites look for OpenGraph tags (special metadata) to know what headline and image to display in the preview. Without og:title and og:image, the share card will look broken or use generic fallbacks, which hurts click-through rates and makes your content look unprofessional.
Why it matters for your business: Blog posts about your dispensary's story and community involvement are key trust-builders; broken social previews reduce shares and referral traffic, cutting the reach of your earned credibility.
Technical root cause: The WordPress theme or Yoast SEO plugin (if installed) is not automatically generating or allowing manual entry of og:title and og:image meta tags for this post.
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 small code snippet that tells Twitter (X) how to display a preview when someone shares your link on that platform. Without it, Twitter shows a plain text link instead of an attractive preview with your image and description, making shared posts less engaging.
Why it matters for your business: Missed social sharing engagement means fewer clicks from Twitter back to your site when customers or staff share your dispensary information, product updates, or promotions on social media.
Technical root cause: The WordPress theme or a custom header configuration is not outputting the <meta name="twitter:card" content="summary_large_image"> tag in the page's 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 how to display your content when someone shares a link to your site on Twitter/X. Without it, Twitter uses a generic preview instead of your custom image, headline, and description.
Why it matters for your business: Shared articles from your site will appear less professional and engaging on social media, reducing click-through rates and brand presence among customers who discover you through Twitter/X.
Technical root cause: The WordPress theme or a custom header.php template is not including the Open Graph and Twitter Card meta tags in the <head> section of the page.
Recommended fix — step by step
tier2.meta.no-twitter-cardWhat it means (plain English)
Your blog posts don't have Twitter card tags—special metadata that tells Twitter (now X) how to display your content when someone shares a link. Without them, X shows a plain text preview instead of a formatted card with your title, description, and image. This is a cosmetic issue; the content still appears and is still shareable.
Why it matters for your business: Shared blog posts look less professional on social media, which reduces click-through rates and brand presence when customers discuss your content on X.
Technical root cause: The WordPress theme or SEO plugin is not generating twitter:card meta tags (specifically, the og:image fallback is missing). Most sites use Yoast SEO or All in One SEO to automate this; if neither is active, the tags are absent.
Recommended fix — step by step
tier2.meta.title-lengthDetail
Title should be 20-65 chars. Got: "Cannabis and Creativity: How It Can Enhance Your Artistic Side | CityLeaf Dispensary"
tier2.meta.title-lengthDetail
Title should be 20-65 chars. Got: "New Minority-Owned Cannabis Shop in Newark Comes to Budding Industry | CityLeaf Dispensary"
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: "The Ultimate Guide to Cannabis in Newark, NJ | CityLeaf Dispensary"
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: "A Connoisseur's Guide to Cannabis Concentrates | CityLeaf Dispensary"
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
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.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
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.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
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: "NJ Cannabis Flower Delivery: Premium Weed Strains Delivered to Your Door | CityLeaf Dispensary"
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: "NJ Vape Delivery: Premium Cannabis Vape Pens & Cartridges Delivered | CityLeaf Dispensary"
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: "NJ Pre-Roll Delivery: Premium, Ready-to-Enjoy Joints Delivered | CityLeaf Dispensary"
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.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.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
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.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
tier2.meta.no-ogDetail
Page missing og:title and/or og:image.
tier2.meta.no-twitter-cardDetail
No twitter:card meta tag.
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.js-desktopDetail
JavaScript transfer exceeds 250KB budget.
tier3.weight.total-desktopDetail
Total transfer exceeds 2500KB budget.
tier4.h1.multipleDetail
Only one H1 per page.
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.dkim-missingDetail
Tried selectors: google, default, selector1, selector2, s1, k1 — none matched at cityleafnj.com. DKIM improves deliverability + anti-spoofing.
tier8.lighthouse.mobile-failedDetail
The "start lh:driver:navigate" performance mark has not been set
tier8.lighthouse.perf-desktopDetail
Score 80 is below target 90. See HTML report for details.
tier8.lighthouse.a11y-desktopDetail
Score 85 is below target 95. See HTML report for details.
tier8.lighthouse.seo-desktopDetail
Score 92 is below target 95. See HTML report for details.
tier8.lh-opportunity.offscreen-images-desktopDetail
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. https://developer.chrome.com/docs/lighthouse/performance/offscreen-images/" target="_blank" rel="noreferrer">Learn how to defer offscreen images.
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-css-desktopDetail
Minifying CSS files can reduce network payload sizes. https://developer.chrome.com/docs/lighthouse/performance/unminified-css/" target="_blank" rel="noreferrer">Learn how to minify CSS.
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.
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.
_46 findings on this page_
Your website's homepage is throwing a JavaScript error that breaks interactive features. When a visitor loads the page, a script is trying to modify an HTML element that doesn't exist or hasn't loaded
Your website is served over HTTPS (secure), but some code references are pointing to HTTP (non-secure) URLs. These are Schema.org markup references—structured data that helps search engines understand
Your site's Lighthouse Best Practices score is 56 out of 100, which is well below the healthy threshold of 90. This score reflects issues like outdated libraries, missing security headers, or browser
Your age-gate dialog—the overlay that appears to verify visitor age before accessing the site—is missing a label that screen readers can announce. Screen reader users won't know what the dialog is for
Your homepage has a container marked as a 'list' in the accessibility code, but it contains child elements (images, subheadings, links) that aren't properly structured as list items. Screen reader use
A button on your homepage (the age-gate 'Yes' button) has white text (#ffffff) on a yellow-green background (#b4be0e) that creates a contrast ratio of only 2.03:1. WCAG accessibility standards require
Your website has 5 image gallery links that keyboard and screen reader users cannot identify or interact with properly. These links have no visible text, no hidden labels (aria-label), and no title at
Your gallery images on the homepage have the accessibility role of 'image' but lack descriptive text that screen readers can read aloud. This means visitors using screen readers (software that reads w
Your website has a JavaScript error that appears in Safari and other Apple browsers (WebKit) but not in Chrome. The error occurs when code tries to modify an HTML element (the mobile viewport tag) tha
Your site has a JavaScript error that appears in Firefox but not Chrome. The code is trying to call a method (setAttribute) on something that doesn't exist (null). This usually happens when a script l
Your site has 37 images out of 41 total that lack alt text — the descriptive label that tells screen readers and search engines what an image shows. This means visually impaired customers cannot under
Your site has 2 broken internal links that point to email-protection pages (these are Cloudflare email obfuscation URLs). When search engines or visitors click these links, they hit a 404 error page i
The performance testing tool timed out while trying to load your homepage on a mobile device, meaning the page took longer than 60 seconds to fully load. This suggests either a slow server response, l
Your site is missing an HTTP security header called Strict-Transport-Security (HSTS), which tells browsers to always use encrypted HTTPS connections when visiting your domain. Without it, a visitor's
Your website is missing the X-Frame-Options security header, which tells browsers whether your site can be embedded inside iframes on other websites. Without it, attackers could potentially embed your
Your website is missing a Content Security Policy (CSP) header — a security directive that tells browsers which sources of content (scripts, images, stylesheets) are trusted. Without it, attackers cou
Your domain cityleafnj.com does not have an SPF (Sender Policy Framework) record published in DNS. SPF is a simple text record that tells email providers which servers are authorized to send mail from
Your site has 36 buttons, links, and other clickable elements that are smaller than 44×44 pixels on mobile phones. This is below the Web Content Accessibility Guidelines (WCAG) standard, which means v
Your website has 38 interactive buttons, links, and form fields that are smaller than 44×44 pixels on mobile devices. This makes them difficult to tap accurately, especially for people with motor impa
Your website has 38 interactive buttons, links, and form fields that are smaller than 44×44 pixels when viewed on mobile phones. This makes them hard to tap accurately—especially for people with less
Your website has 38 buttons, links, and interactive elements that are smaller than 44×44 pixels when viewed on a tablet. This makes them hard to tap accurately, especially for people with motor contro
Your main navigation menu doesn't have a unique name that screen readers can use to distinguish it from other navigation areas on the page. Right now, it's labeled generically as "Menu," which creates
Your homepage is encountering two JavaScript errors after the age gate loads and the menu becomes visible. These errors occur when the browser tries to interact with HTML elements that either don't ex
OpenGraph tags are snippets of code that control how your site preview appears when someone shares a link on Facebook, Instagram, or other social platforms. Without them, shared links show a generic o
Your website is missing a Twitter Card meta tag, which is a small code snippet that tells Twitter (X) how to display a preview when someone shares your link on that platform. Without it, Twitter shows
_4 findings on this page_
Nine images on your blog post about recreational cannabis lack alt text — descriptive labels that screen readers read aloud to blind/low-vision visitors. Search engines also use alt text to understand
Your page title is 90 characters long, but search engines like Google typically display only 50–65 characters in search results before truncating with an ellipsis (…). When your title is too long, the
Open Graph tags are metadata snippets that tell social media platforms (Facebook, Instagram, LinkedIn) how to display your page when someone shares it. Without them, your posts appear bland—no custom
Your blog post isn't configured to display nicely when shared on social media platforms like Twitter/X. Without a Twitter card meta tag, when someone shares your post, it will show only plain text and
_4 findings on this page_
Your page title (the text that appears in browser tabs and search results) is 76 characters long, but search engines typically truncate titles longer than 60 characters on desktop and 55 on mobile. Th
When someone shares your articles page on Facebook, Instagram, or other social platforms, those sites pull in a title and image to display in the preview. Without OpenGraph metadata (special HTML tags
Your website 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/X. Without it, Twitter uses a generic preview instea
Three images on your articles page lack alt text — the hidden description that screen readers (used by blind and low-vision visitors) read aloud, and that search engines use to understand what images
_4 findings on this page_
When this article is shared on Facebook, Instagram, or other social platforms, those sites can't pull a custom title or image to display in the preview. Instead, users see whatever generic fallback th
Your blog posts don't have Twitter card tags—special metadata that tells Twitter (now X) how to display your content when someone shares a link. Without them, X shows a plain text preview instead of a
Four images on your blog post about cannabis and creativity don't have alt text — brief descriptions that explain what the image shows. Alt text serves two purposes: it helps people using screen reade
_4 findings on this page_
When someone shares your blog post on Facebook, LinkedIn, or other social platforms, those sites look for OpenGraph tags (special metadata) to know what headline and image to display in the preview. W
_4 findings on this page_
Five images on your Newark cannabis guide page don't have alt text — descriptive labels that explain what each image shows. Search engines and screen readers (tools that help blind/low-vision visitors
_4 findings on this page_
Five images on your Cannabis Concentrates Guide page don't have alt text—descriptive text that explains what the image shows. Screen readers (used by blind and low-vision visitors) can't describe thes
_4 findings on this page_
Six images on your blog page lack alternative text (alt text) — descriptive labels that screen readers announce to visually impaired visitors and that search engines use to understand image content. T
_4 findings on this page_
_4 findings on this page_
_4 findings on this page_
_4 findings on this page_
Your blog category page (/category/blog/) doesn't have a meta description — the 150-160 character summary that appears below your page title in Google search results. Without it, Google generates a ra
_3 findings on this page_
Your Harrison, NJ page has 11 images without alt text—alternative text that describes what's in the image. Screen readers (tools blind and low-vision visitors use) can't tell users what those images s
_3 findings on this page_
Your website has 11 images without alt text (descriptive text read aloud by screen readers and used by search engines). This prevents visually impaired customers from understanding what those images s
_3 findings on this page_
Eleven images on your Newark service page are missing alt text — a brief description that screen readers announce to visually impaired visitors and that search engines use to understand image content.
_3 findings on this page_
Your Bloomfield page has 11 images missing alt text — short descriptions that explain what each image shows. Screen readers (tools blind customers use to browse the web) can't tell visitors what these
_3 findings on this page_
Eleven images on your East Orange service area page are missing alt text — short descriptions that screen readers read aloud and search engines use to understand image content. This makes your page ha
_3 findings on this page_
Your Jersey City page has 11 images without alt text — short descriptions that explain what each image shows. Search engines and screen readers (used by people with vision loss) can't understand image
_3 findings on this page_
Eleven images on your Hoboken service page are missing alt text — descriptive labels that screen readers use to describe images to blind and low-vision visitors. These missing labels also prevent sear
_3 findings on this page_
_3 findings on this page_
_3 findings on this page_
Your delivery page has 9 images that lack alt text — a short description that appears if an image fails to load and that search engines read to understand your content. This makes the page harder for
_3 findings on this page_
Nine images on your Hoboken delivery page don't have alt text—descriptive labels that screen readers read aloud to blind or low-vision visitors. Search engines also use alt text to understand what ima
_3 findings on this page_
Nine images on your Kearny delivery page don't have alt text—descriptions that tell search engines and screen readers what each image shows. This hurts both accessibility (people using screen readers
_3 findings on this page_
Nine images on your Newark delivery page don't have alt text — a short description that describes what the image shows. Search engines and screen readers (used by people with vision loss) can't unders
_3 findings on this page_
Nine images on your East Orange delivery page don't have alt text—descriptions that explain what each image shows. Screen readers (software that helps blind and low-vision customers browse your site)
_3 findings on this page_
Nine images on your Bloomfield delivery page are missing alt text — a brief text description that screen readers use to understand images, and that search engines use to index them. This means custome
_3 findings on this page_
Nine images on your Harrison delivery page don't have alt text—descriptive labels that screen readers read aloud and search engines use to understand what's in the image. This blocks visually impaired
_3 findings on this page_
_3 findings on this page_
_3 findings on this page_
_3 findings on this page_
Your About Us page has 13 images without alternative text descriptions. Alt text is invisible text attached to images that describes what they show. Search engines and screen readers (used by people w
_3 findings on this page_
_3 findings on this page_
Your website has 11 images without alt text (descriptive text that appears if an image fails to load). This prevents visually impaired customers using screen readers from understanding what those imag
_3 findings on this page_
Seven images on your Weed Delivery page lack alt text — a description that screen readers announce to blind/low-vision visitors and that search engines use to understand image content. This blocks acc
_3 findings on this page_
Seven images on your Newark delivery page don't have alt text — descriptive labels that screen readers use to understand images, and that search engines use to index them. This means visually impaired
_3 findings on this page_
Nine images on your Belleville delivery page don't have alt text—descriptions that tell screen readers (and search engines) what each image shows. This means visually impaired customers can't understa
_3 findings on this page_
Your site has 37 images without alternative text (alt text) — a brief description that appears when an image fails to load and is read aloud by screen readers for visually impaired visitors. This brea
_3 findings on this page_
Your site has 37 images without alt text — descriptive labels that tell search engines and visitors using screen readers what the image shows. This hurts both accessibility (people using assistive tec
_3 findings on this page_
Your site has 37 images without alt text — descriptive text that explains what each image shows. This text is read aloud by screen readers (tools visually impaired customers use to browse the web) and
_3 findings on this page_
Your site has 37 images without alternative text descriptions. Alt text is hidden text that describes what an image shows — it helps screen readers (used by people who are blind or have low vision) un
_3 findings on this page_
Your site has 37 images without alt text — short descriptions that explain what each image shows. Search engines and assistive technologies (used by visually impaired visitors) rely on this text to un
_3 findings on this page_
Your site has 37 images without alt text — descriptive text that explains what the image shows. Search engines and assistive technology (software that helps people with vision loss) can't understand i
_3 findings on this page_
37 images on your site lack alternative text (alt text) — a short description that search engines and assistive technology (used by people with vision impairments) read when they can't see the image.
_3 findings on this page_
Your site has 37 images without alt text — short descriptions that tell screen readers and search engines what each image shows. This blocks customers using assistive technology from understanding you
_3 findings on this page_
Your website has 37 images without alt text — alternative text that describes what the image shows. Search engines and screen readers (used by people with vision disabilities) can't understand images
_3 findings on this page_
Your website has 37 images without alt text — descriptive labels that screen readers use to tell blind/low-vision visitors what an image shows, and that search engines use to understand your content.
_1 finding on this page_
Your robots.txt file (a plain-text file that tells search engines what pages to crawl) doesn't include a link to your XML sitemap. The sitemap is like a master map of every page on your site that you
_1 finding on this page_
Your WordPress login page (/wp-login.php) is publicly accessible and returns a success response. This is a security risk because attackers can attempt to guess passwords or use automated tools to brea
_Generated by Apex Sentinel Monthly Audit · 2026-04-19T07:34:37.911Z · Powered by Bud Authority._
Generated by Apex Sentinel · © 2026 Bud Authority