Website review, no card needed

liveparallel.com logo

liveparallel.com website review

Visit site (opens in a new tab)Reviewed 26 October 202629 issues · 74 checks

This review found 29 issues worth fixing on liveparallel.com, 9 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
1.2 s605 msMay 9Oct 24705 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 2026957 ms
Jun 13, 2026957 ms
Jun 20, 2026921 ms
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 2026899 ms
Jul 25, 2026784 ms
Aug 1, 2026714 ms
Aug 8, 2026694 ms
Aug 15, 2026724 ms
Aug 22, 2026744 ms
Aug 29, 2026738 ms
Sep 5, 2026707 ms
Sep 12, 2026672 ms
Sep 19, 2026701 ms
Sep 26, 2026737 ms
Oct 3, 2026757 ms
Oct 10, 2026774 ms
Oct 17, 2026757 ms
Oct 24, 2026705 ms
Real-visitor tap response (INP)75th percentile, phones
86 ms67 msMay 9Oct 2473 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202676 ms
May 16, 202678 ms
May 23, 202680 ms
May 30, 202676 ms
Jun 6, 202676 ms
Jun 13, 202677 ms
Jun 20, 202675 ms
Jun 27, 202678 ms
Jul 4, 202677 ms
Jul 11, 202671 ms
Jul 18, 202684 ms
Jul 25, 202679 ms
Aug 1, 202669 ms
Aug 8, 202672 ms
Aug 15, 202670 ms
Aug 22, 202670 ms
Aug 29, 202672 ms
Oct 10, 202671 ms
Oct 17, 202670 ms
Oct 24, 202673 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 liveparallel.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. liveparallel.com at 0.4 s0.4 s
  2. liveparallel.com at 0.8 s0.8 s
  3. liveparallel.com at 1.1 s1.1 s
  4. liveparallel.com at 1.5 s1.5 s
  5. liveparallel.com at 1.9 s1.9 s
  6. liveparallel.com at 2.3 s2.3 s
  7. liveparallel.com at 2.6 s2.6 s
  8. liveparallel.com at 3.0 s3.0 s

Speed

5 to fix80
  • Render-blocking requests

    2.2 s

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.

  • Improve image delivery

    1.1 s · 193 KiB

    4 images could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 80

    80/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Google Analytics and others), adding 1.5 MB and 249 ms of main-thread time.

  • website-files.com adds 14 ms

    14 ms

    website-files.com costs a phone 14 ms of main-thread work and 924 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.

  • Reduce unused JavaScript

    136 KiB

    About 136 KiB of JavaScript is downloaded but never used on this page.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 95 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    16 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).

  • Reduce unused CSS

    16 KiB

    About 16 KiB of CSS is downloaded but never applied on this page.

  • 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 276 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Well-being reimagined.”.

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Time to Interactive: 7.2 s

    7.2 s

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

  • 9 images without width and height

    9 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -7%

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

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: 0.9 s

    0.9 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Largest content (LCP) got 33% faster for real visitors

    -33%

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

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 23 ms

    23 ms

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

Images and page weight

100
  • 5 images in older formats

    5 images (456 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.4 g of CO₂ per visit

    0.42 g

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

2 checks passed
  • Page weight: 1.5 MB in 41 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 41 requests on a phone: images 709 KiB (17), scripts 418 KiB (11) and fonts 332 KiB (7). That is a lean page.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9294
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 elements on the page fail 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.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

6 to fixGoogle 10070
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (57 characters)

    Your meta description is only 57 characters: “Cannabis, CBD and hemp brands focused on your well-being.”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.liveparallel.com/sitemap.xml, so Google discovers your pages only by following links.

  • 10 internal links, 19 external

    The homepage links to 10 pages on liveparallel.com and 19 external pages.

2 checks passed
  • Title: 37 characters

    Your title is a healthy 37 characters: “Parallel – Cannabis, CBD, Hemp Brands”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.liveparallel.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 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.

  • Text is in the HTML

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

Other pages

4 to fix81
  • 3 pages share a title

    https://www.liveparallel.com/news-media/surterra-wellness-x-wana-brands, https://www.liveparallel.com/news-media/parallel-partners-with-mcba-on-new-wave-of-cannabis-social-equity and https://www.liveparallel.com/news-media/goodblend-tm-texas-announces-educational-goodblend-cannabus-tm-tour-across-texas all use the title “LiveParallel.com”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.liveparallel.com/blog, https://www.liveparallel.com/news-media/surterra-wellness-x-wana-brands, https://www.liveparallel.com/news-media/parallel-partners-with-mcba-on-new-wave-of-cannabis-social-equity and https://www.liveparallel.com/news-media/goodblend-tm-texas-announces-educational-goodblend-cannabus-tm-tour-across-texas have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://www.liveparallel.com/about, https://www.liveparallel.com/news-media, https://www.liveparallel.com/careers, https://www.liveparallel.com/terms and https://www.liveparallel.com/privacy use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.liveparallel.com/about, https://www.liveparallel.com/news-media, https://www.liveparallel.com/blog, https://www.liveparallel.com/careers, https://www.liveparallel.com/terms and https://www.liveparallel.com/privacy have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10082
  • 2 broken images

    2 images failed to load on a phone, for example https://www.liveparallel.com/.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 417 words of copy

    The homepage carries about 417 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 liveparallel.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
Webflow
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Webflow

Hiring

Hiring
24 open roles
Teams
700 - Retail (11), 610 - Cultivation (4), 100 - Corporate (1), 180 - Construction / Facilities (1)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on liveparallel.com, including 9 speed issues, 6 SEO issues and 3 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