Purple Buds

A third-party optimization script (dynamic_optimization.js from Bud Authority's dashboard) is being blocked by your website's security policy. This script is trying to load as base64-encoded data, which your Content Security Policy doesn't permit. The script never executes, breaking the homepage-to-menu user journey.

Action: Contact Bud Authority support to whitelist the dynamic_optimization.js script origin (https://dashboard.budauthority.com/scripts/) in your CSP header, or request they modify the script delivery method to avoid base64 data: URIs. Verify the fix by re-running the homepage-to-menu journey test.

A Bud Authority optimization script is being blocked by your site's security policy (CSP). The script tries to load from a data URL, which your current policy doesn't allow. This is preventing the contact page from fully loading and may affect user experience or optimization features.

Action: Work with your dev team to add 'data:' to the script-src CSP directive, or refactor the script loader to use a whitelisted external URL instead of an inline base64 blob. Verify with Bud Authority that dashboard.budauthority.com is intentionally being called.

Purple Buds has DMARC set up but is missing an SPF record on pbuds.com. This means emails from your domain (order confirmations, password resets, promotions) are likely being flagged as spam by Gmail, Outlook, and other providers—customers won't see them.

Action: Add an SPF record to pbuds.com's DNS with your email service provider (Mailchimp, SendGrid, etc.). Contact your email vendor for the exact SPF syntax, then add it as a TXT record. Test with a tool like MXToolbox.

Your website has 29 buttons, links, or touch elements that are too small for mobile users to tap accurately. At 320px width (common phone size), these fall below the 44x44 pixel standard that regulators and accessibility guidelines require. This causes friction and failed conversions.

Action: Audit the mobile site at 320px viewport using Chrome DevTools. Identify the 29 small targets (likely navigation, menu toggles, or add-to-cart buttons). Resize them to minimum 44x44px or add padding around them. Prioritize the Dutchie ordering flow and primary CTAs first.

Your website has 29 buttons, links, and interactive elements that are too small to tap easily on mobile phones. This violates accessibility standards and frustrates customers trying to browse your menu or make purchases on their phones.

Action: Audit the mobile layout at 375px width and increase all interactive elements to at least 44×44 pixels. Prioritize the Dutchie menu iframe and checkout buttons. Test with actual thumb-tap interaction on a mobile device.

Your website has 29 buttons, links, or clickable elements that are too small (under 44x44 pixels) on mobile phones. This makes them hard to tap accurately and violates accessibility law. Visitors—especially older customers or those on slower connections—will struggle to place orders or navigate your menu.

Action: Audit the mobile layout (414px viewport) and increase all interactive elements to at least 44x44 pixels. Prioritize the Dutchie menu iframe and checkout flow. Use browser DevTools or a mobile device to identify and resize each element.

Your website has 30 buttons, links, or clickable elements that are too small for users to easily tap on tablets. This creates friction for customers trying to browse your menu or make purchases, and it violates accessibility standards that cannabis retailers should follow.

Action: Audit the 30 undersized targets on tablet view—prioritize those in the Dutchie menu iframe and checkout flow. Resize to minimum 44x44px or increase padding around them. Test on actual tablets before deploying.

36 text elements on your menu page have color combinations that are too similar, making them hard for customers (especially those with vision impairment) to read. This includes your store status, menu labels, and buttons. It's a legal accessibility issue under WCAG standards.

Action: Audit the Dutchie embed styling: increase contrast by darkening text or lightening backgrounds. Priority fixes: 'Closed' status, 'Menu' label, and 'View All' links. Contact Dutchie support to confirm if this is a platform-side issue or if CSS customization is available.

Your website uses a definition list (<dl>) HTML element with incorrect child elements inside it. This breaks accessibility for screen reader users who rely on proper structure to understand content relationships. It's a structural HTML error, not a content problem.

Action: Audit the <dl> element at `.lg\:gap-12 > .lg\:col-span-2` on the homepage. Replace any <a> or improperly nested <div> tags with correct <dt>/<dd> pairs, or switch to a <div>-based layout if definition list semantics don't apply. Verify the fix with an accessibility checker before deploying.

Your menu page has three landmark regions (navigation, main content, and footer) that lack unique identifying labels. Screen reader users can't distinguish between them, making navigation confusing for disabled visitors and potentially exposing you to ADA compliance risk.

Action: Add unique aria-label attributes to the nav (.glass-nav), main, and the Dutchie footer contentinfo role. For example: aria-label="Main navigation", aria-label="Menu content", and aria-label="Footer information". The Dutchie footer is third-party—verify if you can override it via CSS or request a fix from Dutchie support.

The product menu on your /menu page has 8 list items that aren't properly wrapped in list containers (ul or ol tags). This breaks accessibility for screen readers and violates WCAG standards, which can expose you to legal risk and prevent customers with disabilities from browsing your menu.

Action: Contact Dutchie support to report that their embedded iframe carousel is generating improperly nested list items. Request they wrap the carousel items in a proper <ul> or <ol> element. If they cannot fix it, you may need to explore alternative menu embed solutions or add a JavaScript workaround to restructure the DOM after iframe load.

A login prompt inside the Dutchie menu iframe has keyboard navigation problems — screen readers and keyboard users may struggle to interact with it properly. This is a real accessibility issue that could block customers from ordering.

Action: Contact Dutchie support to report the nested interactive element in their login-nudge tooltip. If they cannot fix it, request a workaround (e.g., moving the login prompt outside the nested structure or removing the tooltip wrapper). Test with a keyboard and screen reader after any changes.

Seven sections of your homepage content (including the Purple Buds logo, tagline, and a canvas element) aren't wrapped in proper landmark regions like <header>, <main>, or <nav>. This makes your site harder to navigate for people using screen readers and assistive devices. It's a WCAG accessibility issue that could expose you to compliance risk.

Action: Wrap the homepage hero section (logo, tagline, canvas) in a <header> landmark, and ensure all other page content sits within <main>, <nav>, or <section> landmarks. This is auto-fixable by your developer—request they run the axe fix or manually restructure the HTML semantics.

Your menu page has content (like the Purple Buds header and other text) that isn't wrapped in proper structural landmarks (like <nav>, <main>, <header>). This makes it harder for people using screen readers to navigate your site, and it violates accessibility standards that cannabis retailers should follow to avoid compliance risk.

Action: Wrap the page header and main menu content in semantic HTML landmarks: put the Purple Buds logo and tagline inside a <header>, and the menu/Dutchie iframe inside a <main> tag. This is auto-fixable by your developer in under 30 minutes.

Seven pieces of content on your contact page (including the Purple Buds logo, tagline, and a canvas element) are floating outside of semantic page structure markers. This makes it harder for screen reader users and accessibility tools to navigate your site. It's a best-practice issue that won't block most visitors but signals incomplete accessibility setup.

Action: Wrap the logo, tagline, and canvas element in semantic HTML landmarks (e.g., <header>, <main>, <nav>) instead of leaving them as orphaned elements. This is a straightforward code fix—ask your developer to reorganize the contact page's HTML structure to nest all visible content inside proper landmark regions.

A button in the Dutchie menu iframe (the login popup close button) is too small at 20×20 pixels — it should be at least 24×24 pixels. This makes it hard for mobile users and people with dexterity issues to tap, and it violates accessibility standards that cannabis sites must follow.

Action: Contact Dutchie support to report the undersized close button in their login nudge component, or request they increase the button size to 24×24px minimum. If Dutchie won't fix it, explore whether the login nudge can be disabled or styled differently on your Purple Buds menu page.

A Bud Authority optimization script is being blocked by your site's security policy (Content Security Policy). This script tries to load from a data URL, which your current policy doesn't allow. The blocker is preventing the script from running, which could affect site performance and tracking.

Action: Add 'data:' to the script-src directive in your Content Security Policy header, or whitelist the specific domain (dashboard.budauthority.com) if that's preferred. Contact your Bud Authority account manager to confirm the script UUID (ef5c17dd-58da-436d-843b-629c08ccdd31) is legitimate before allowing it.

Your website has 29 buttons, links, or clickable elements that are too small (under 44x44 pixels) on mobile phones. This violates accessibility standards and makes it harder for customers to tap the right spot, especially on small screens.

Action: Audit the mobile menu, product filters, and checkout buttons. Increase touch targets to at least 44x44 pixels with adequate spacing. Prioritize elements in your cart flow and product selection menu first.

Your website has 29 buttons, links, or other clickable elements that are too small for mobile users to tap accurately. This violates accessibility standards and causes frustration on phones, leading to missed clicks and poor user experience.

Action: Audit the mobile menu, product filters, and checkout buttons on pbuds.com. Increase any tap targets under 44x44 pixels to at least 44x44 pixels, or add spacing between them. Prioritize the Dutchie ordering interface and any CTA buttons in the revenue path.

Your website has 29 buttons, links, or clickable elements that are too small for mobile users to tap comfortably. This violates accessibility standards and frustrates customers trying to browse or purchase on phones.

Action: Audit mobile navigation and menu buttons; resize tap targets to at least 44×44 pixels. Prioritize the Dutchie menu iframe and checkout path. Test on iPhone SE (414px width) after changes.

Your website has 30 buttons, links, and interactive elements that are too small to tap easily on tablets. This violates accessibility standards and frustrates customers trying to browse your menu or make purchases on mobile devices.

Action: Audit the tablet view of your site (especially the Dutchie menu integration and checkout buttons) and increase any interactive element smaller than 44x44 pixels. Prioritize buttons in the ordering flow and primary navigation.