Website review, no card needed

shopharborside.com logo

shopharborside.com website review

Visit site (opens in a new tab)Reviewed 22 October 202627 issues · 81 checks

This review found 27 issues worth fixing on shopharborside.com, 8 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.3 s618 msMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 2026987 ms
May 9, 20261.0 s
May 16, 20261.0 s
May 23, 2026995 ms
May 30, 2026948 ms
Jun 6, 2026932 ms
Jun 13, 2026973 ms
Jun 20, 20261.0 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.1 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20262.3 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
472 ms24 msMay 2Oct 17396 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202677 ms
May 9, 202679 ms
May 16, 202679 ms
May 23, 202680 ms
May 30, 202682 ms
Jun 6, 202683 ms
Jun 13, 202687 ms
Jun 20, 202686 ms
Jun 27, 202687 ms
Jul 4, 202679 ms
Jul 11, 202678 ms
Jul 18, 202676 ms
Jul 25, 202678 ms
Aug 1, 202679 ms
Aug 8, 202682 ms
Aug 15, 202683 ms
Aug 22, 202684 ms
Aug 29, 202683 ms
Sep 5, 202679 ms
Sep 12, 2026283 ms
Sep 19, 2026361 ms
Sep 26, 2026409 ms
Oct 3, 2026420 ms
Oct 10, 2026405 ms
Oct 17, 2026396 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of shopharborside.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shopharborside.com at 0.6 s0.6 s
  2. shopharborside.com at 1.3 s1.3 s
  3. shopharborside.com at 1.9 s1.9 s
  4. shopharborside.com at 2.5 s2.5 s
  5. shopharborside.com at 3.2 s3.2 s
  6. shopharborside.com at 3.8 s3.8 s
  7. shopharborside.com at 4.4 s4.4 s
  8. shopharborside.com at 5.1 s5.1 s

Speed

7 to fix65
  • Reduce unused JavaScript

    1.1 s · 536 KiB

    About 536 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Wix, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 2.6 MB and 840 ms of main-thread time.

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 56). Pages that score under 90 lose visitors before the first paint.

  • Wix adds 379 ms

    379 ms

    Wix costs a phone 379 ms of main-thread work and 1.7 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Tag Manager adds 297 ms

    297 ms

    Google Tag Manager costs a phone 297 ms of main-thread work and 509 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 2.5 s

    A phone's processor spends 2.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,621 HTML elements

    The page has 1,621 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.

  • Improve image delivery

    140 KiB

    13 images could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    71 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (71 KiB).

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    27 KiB

    27 KiB JavaScript is shipped twice across bundles.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 24 ms

    24 ms

    Your server sent the HTML in 24 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “HS Background.png”.

  • Time to Interactive: 14.6 s

    14.6 s

    The page becomes fully interactive after 14.6 s. Good is under 3.8 s.

  • First Contentful Paint: 3.3 s

    3.3 s

    The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

  • Tap response (INP) got 413% slower for real visitors

    +413%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 77 ms to 396 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 203% slower for real visitors

    +203%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 4.0 s

    4.0 s

    Visually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 359 ms

    359 ms

    Real visitors wait 359 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 199 ms

    199 ms

    Scripts block the page for only 199 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.3 MB in 222 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 222 requests on a phone: scripts 1.7 MB (104), other files 656 KiB (67) and images 570 KiB (45). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.93 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8391
  • ARIA commands must have an accessible name (16 elements)

    ARIA commands must have an accessible name: 16 elements on the page fail this check, rated serious by axe-core.

  • 8 text elements with low contrast

    8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 39 internal links, 6 external

    The homepage links to 39 pages on shopharborside.com and 6 external pages.

8 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Harborside, trusted for 20 years, is a premium recreational cannabis dispensary near me. Join now for exclusive deals a…”.

  • One H1 headline

    Your main headline reads: “HARBORSIDE IS ONE OF THE OLDEST, LARGEST AND MOST RESPECTED CANNABIS DISPENSARIES IN CALIFORNIA”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Harborside | Recreational Dispensary Near Me”.

  • Canonical URL set

    The canonical URL is https://www.shopharborside.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.shopharborside.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (426 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.shopharborside.com/llms.txt (7 KiB, 25 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.shopharborside.com/membership is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.shopharborside.com/join-our-team, https://www.shopharborside.com/medical-card and https://www.shopharborside.com/membership have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.shopharborside.com/deals, https://www.shopharborside.com/join-our-team, https://www.shopharborside.com/medical-card, https://www.shopharborside.com/stash-rewards, https://www.shopharborside.com/we-make-it-right-policy and https://www.shopharborside.com/delivery and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

    11 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 394 words of copy

    The homepage carries about 394 words of visible text.

5 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “JOIN OUR TEAM”, “CONTACT” and “SHOP NOW”.

  • Social proof on the page

    Social proof on the homepage: a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 15 other companies contacted

    Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at shopharborside.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Wix
Framework
React
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on shopharborside.com, including 13 speed issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25