Latitude Movement

Your website's homepage is returning a 404 error, meaning visitors and search engines cannot access it. This completely blocks traffic and revenue.

Action: Immediately check Netlify deployment status and verify the build succeeded. Confirm the correct homepage file (index.html) is in the root directory. If recently deployed, rollback to the last working version.

A critical user journey is breaking during the age-gate-to-menu flow. A 404 error (missing resource) is preventing customers from viewing your menu after age verification, which directly blocks sales.

Action: Identify which resource is returning 404 in the age gate → menu transition (check network logs in browser DevTools). Likely culprits: missing asset, broken API endpoint, or misconfigured Dutchie iframe reference. Rebuild/redeploy if needed.

Your website's root domain (https://latitude-movement.netlify.app) is returning a 404 error, meaning visitors and search engines can't access it. This breaks the entire user journey and severely damages SEO.

Action: Immediately verify the Netlify deployment status and check that index.html exists and is properly configured as the default page. Test the root URL in a browser and review Netlify build logs for deployment errors.

Search engines can't find your site instructions. Without a robots.txt file, Google and other search engines may crawl inefficiently or miss important pages, hurting your visibility in search results.

Action: Create and deploy a robots.txt file at the root of your domain. Use the auto-fix plan 'write-default-robots' to generate a standard version, then verify it returns HTTP 200 at https://latitude-movement.netlify.app/robots.txt.

Search engines can't find all your pages because your sitemap is missing or empty. This slows down how quickly Google discovers and ranks your content, hurting organic traffic over time.

Action: Generate and deploy a sitemap.xml file listing all your key pages (home, services, about, contact, pricing). For a wellness site like yours, prioritize high-traffic pages. Deploy it to your root directory and submit to Google Search Console.

Your website is missing a Content Security Policy (CSP) header, which is a security safeguard that tells browsers which content sources are trusted. Without it, your site is more vulnerable to malicious script injection attacks.

Action: Add a Content Security Policy header to your Netlify site. Since this is auto-fixable, apply the recommended CSP configuration through Netlify's headers settings (usually via netlify.toml or the dashboard).

Your website is missing a security header (x-frame-options) that tells browsers whether your site can be embedded in iframes on other websites. This leaves you vulnerable to clickjacking attacks where bad actors could trick users into clicking hidden elements on your page.

Action: Add the x-frame-options header with value 'SAMEORIGIN' or 'DENY' to your Netlify site configuration (via _headers file or netlify.toml). This is a one-line fix that blocks unauthorized embedding.

Your website is completely inaccessible to people using screen readers, keyboard navigation, or other assistive devices. This blocks customers with disabilities from browsing your wellness services, exposes you to legal liability under ADA compliance rules, and harms your search ranking.

Action: Open the Lighthouse HTML report immediately to identify the specific barriers (missing alt text, broken form labels, poor color contrast, etc.). Prioritize fixing semantic HTML structure and ARIA labels. This is a business-critical issue requiring developer attention within 48 hours.

Your website is completely inaccessible to people using assistive technologies (screen readers, voice control, etc.) and fails basic web accessibility standards. This means visitors with disabilities cannot navigate your site, and you're exposed to legal compliance risk under ADA/AODA regulations—particularly serious in the cannabis/wellness space where customers often include those with disabilities.

Action: Open the Lighthouse HTML report linked in the evidence and prioritize fixes for: missing alt text on images, poor color contrast, missing form labels, and broken keyboard navigation. Start with the most common issues (alt text, headings) which typically account for 60% of accessibility failures. Consider a professional accessibility audit if in-house fixes don't reach 85+.

Your website is failing Google's best practices audit across the board (0/100 score), indicating serious technical issues like outdated dependencies, insecure libraries, browser compatibility problems, or broken third-party integrations. This damages user trust and may block conversions.

Action: Download the full Lighthouse HTML report and prioritize fixing critical issues: update all npm/library dependencies, remove or replace any deprecated packages, ensure HTTPS everywhere, and audit third-party scripts (tracking, embeds, ads) for security warnings. Start with the top 3 flagged items.

Your mobile site is failing Google's core quality checks—all Lighthouse scores are at 0/100, meaning critical issues are blocking basic functionality, accessibility, and search visibility on phones. This is a site-breaking problem, not just a polish issue.

Action: Open the Lighthouse HTML report immediately and fix the blocking errors listed under 'Best Practices' first (typically: unsecured iframes, outdated libraries, broken console errors). Then rebuild and re-audit. Do not launch or promote this URL until scores exceed 80.

Your website is extremely slow on desktop—Lighthouse measures it at 0/100 performance. This means pages likely take 10+ seconds to load, causing visitors to leave before seeing your content and hammering your SEO ranking.

Action: Open the HTML report at the evidence path immediately and identify the biggest offenders (unoptimized images, render-blocking JavaScript, or oversized assets). Start by compressing images and deferring non-critical scripts. If you're on Netlify, enable their built-in image optimization.

Your website is loading extremely slowly on mobile devices (0/100 performance score), which means visitors are experiencing significant delays. This directly impacts user experience and search engine ranking, especially since most cannabis dispensary visitors browse on phones.

Action: Review the Lighthouse HTML report at the provided path to identify the top blocking issues (likely images, JavaScript, or server response time). Prioritize fixing the largest contentful paint and cumulative layout shift metrics. Consider image optimization, lazy loading, and reducing unused JavaScript as immediate wins.

Your website is scoring 0/100 on Google's SEO quality metrics, meaning search engines can't properly index and rank your pages. This directly blocks organic traffic and visibility for potential customers searching for wellness services.

Action: Immediately review the Lighthouse HTML report to identify missing critical SEO elements (meta tags, structured data, mobile responsiveness, page speed). Prioritize: add title tags, meta descriptions, H1 headers, and ensure site loads in under 3 seconds. If the site is still in development/staging, move to production first.

Your mobile site is scoring 0/100 on Google's SEO audit, meaning search engines cannot properly crawl and index your pages. This directly kills organic search visibility and prevents potential customers from finding you.

Action: Review the Lighthouse HTML report immediately to identify blocking issues (likely: missing meta tags, poor heading structure, or crawlability problems). Prioritize fixing mobile indexability and basic SEO metadata before next audit.

Your website's page structure is missing a main content landmark, which makes it harder for people using screen readers to navigate and find the primary content. Search engines also use these landmarks to better understand your page structure.

Action: Wrap your main content in a <main> HTML tag (or add role="main" to an existing container). This is a quick fix that improves accessibility and SEO without changing how the site looks.

Some content on your page isn't wrapped in proper landmark regions (like <main>, <nav>, <header>). This makes it harder for screen reader users to navigate your site, and it's a best practice that affects accessibility compliance.

Action: Wrap the content in the '.main' div with a proper <main> landmark element. This is a quick fix that improves both accessibility and compliance scoring.

Your website homepage is returning a 404 error, which means visitors and search engines cannot access it. This completely blocks customer access and damages your online presence.

Action: Immediately verify the Netlify deployment is live and the correct build artifact is published. Check that the site's root path serves index.html properly. If recently deployed, rollback to the last working version.

A critical user journey is breaking during the age-gate-to-menu flow due to a missing resource (404 error). This prevents customers from completing the purchase funnel, directly blocking revenue.

Action: Identify which asset failed to load by checking browser DevTools on the live site during the age gate → menu transition. Verify all Dutchie iframe dependencies and static assets are deployed and accessible. Re-run the journey test after fixes to confirm the 404 is resolved.

Your website's root domain is returning a 404 error, meaning visitors and search engines can't access your main page. This is a critical visibility problem that blocks traffic and harms search rankings.

Action: Immediately verify the Netlify deployment is active and the root index file is properly configured. Check Netlify build logs for deployment failures and redeploy if necessary. Confirm DNS settings point to the correct Netlify domain.

Search engines can't find your robots.txt file, which tells them which pages to crawl and index. Without it, Google may waste resources crawling pages you don't want indexed, or miss important ones entirely.

Action: Create and deploy a robots.txt file at the root of your domain. Use the auto-fix plan 'write-default-robots' to generate a standard template, then customize it to block any sensitive paths (e.g., /admin, /cart) if needed.

Your website doesn't have a sitemap file that search engines use to discover and index your pages. Without it, Google and other search engines may miss content on your site, hurting your visibility in search results.

Action: Generate and deploy a sitemap.xml file (list all public pages) and submit it to Google Search Console. For a Netlify site, use a static sitemap generator or plugin—this is a one-time setup that takes 15 minutes.

Your website is missing a Content Security Policy (CSP) header, which is a security rule that tells browsers what content is safe to load. This leaves the site more vulnerable to injection attacks and reduces your overall security score.

Action: Enable the auto-fix plan 'add-csp' to inject a standard CSP header into your Netlify site configuration. Verify the policy allows your essential third-party services (analytics, payment processors, etc.) to function correctly after deployment.

Your website is missing a security header (x-frame-options) that tells browsers whether your site can be embedded in iframes on other websites. This is a standard security best practice that protects against clickjacking attacks and strengthens your overall security posture.

Action: Add x-frame-options header set to 'DENY' or 'SAMEORIGIN' via Netlify configuration (netlify.toml or headers file). This is auto-fixable and takes 5 minutes.

Your website's homepage is returning a 404 error, meaning visitors and search engines cannot access it. This completely blocks traffic and revenue.

Action: Immediately check Netlify deployment status and verify the build succeeded. Confirm the correct index.html exists in the root directory and redeploy if necessary. Test the URL in a browser to confirm resolution.

A critical resource (likely an asset or API) is returning a 404 error during the age gate → menu flow. This breaks the customer journey at a revenue-critical point—users cannot see your menu after passing age verification.

Action: Check browser console (F12 → Console tab) on the live site to identify which specific resource is missing (image, script, or API endpoint). Verify it exists on your server or CDN and fix the path or re-deploy if needed.

Your website's main page is returning a 404 error, meaning visitors and search engines can't access it. This breaks the entire user experience and blocks organic search traffic from reaching your site.

Action: Immediately check your Netlify deployment — verify the build succeeded, the index.html file exists in the publish directory, and routing is configured correctly. If using a custom domain, confirm DNS settings point to Netlify.