Website review, no card needed

thepharmaz.com logo

thepharmaz.com website review

Visit site (opens in a new tab)Reviewed 22 October 202631 issues · 78 checks

This review found 31 issues worth fixing on thepharmaz.com, 7 of them high impact, across 78 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

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

How it loaded on a phone

  1. thepharmaz.com at 0.4 s0.4 s
  2. thepharmaz.com at 0.9 s0.9 s
  3. thepharmaz.com at 1.3 s1.3 s
  4. thepharmaz.com at 1.7 s1.7 s
  5. thepharmaz.com at 2.1 s2.1 s
  6. thepharmaz.com at 2.6 s2.6 s
  7. thepharmaz.com at 3.0 s3.0 s
  8. thepharmaz.com at 3.4 s3.4 s

Speed

9 to fix60
  • Render-blocking requests

    1.9 s

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

  • Improve image delivery

    500 ms · 4.3 MB

    12 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Mobile performance score: 60

    60/100

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

  • Reduce unused CSS

    750 ms · 75 KiB

    About 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused JavaScript

    150 ms · 361 KiB

    About 361 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Google Tag Manager adds 324 ms

    324 ms

    Google Tag Manager costs a phone 324 ms of main-thread work and 536 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.

  • Legacy JavaScript

    350 ms · 17 KiB

    Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • Main-thread work: 2.3 s

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

  • 1,597 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and SiteScout and others), adding 601 KiB and 475 ms of main-thread time.

  • Minify CSS

    150 ms · 18 KiB

    18 KiB could be saved by minifying CSS.

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    22 KiB

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

  • 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: 26 ms

    26 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 7.4 s

    7.4 s

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

  • Time to Interactive: 12.8 s

    12.8 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • 3 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 163 ms

    163 ms

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

2 to fix69
  • Page weight: 6.9 MB in 93 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 93 requests on a phone: images 5.4 MB (26), scripts 1.2 MB (37) and stylesheets 124 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Dusties-Sour-Strike-Menu-Image-Full-Fam-Colored-BG-600x600.j is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images in older formats

    3 images (232 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 (45 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    1.97 g

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

1 checks passed
  • 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 9093
  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 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 → h6, h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 97 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is short (16 characters)

    Your title is only 16 characters: “Home – The Pharm”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 H1 headlines

    There are 5 <h1> headlines (“DUSTIES SOUR STRIKE”, “We are the source” and “Our Products”). One clear main headline is easier for people and search engines.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • 81 internal links, 6 external

    The homepage links to 81 pages on thepharmaz.com and 6 external pages.

6 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “Sun soaked, quality cannabis available at rad prices across Arizona. For our people, our planet and our shared love of …”.

  • Canonical URL set

    The canonical URL is https://thepharmaz.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://thepharmaz.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://thepharmaz.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.

3 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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 13 pages without a meta description

    https://thepharmaz.com/life-on-the-pharm, https://thepharmaz.com/product/sweet-blend, https://thepharmaz.com/product/diesel-blend, https://thepharmaz.com/product/citrus-blend, https://thepharmaz.com/product/herbal-blend and https://thepharmaz.com/product/pineapple-splash and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Unexpected identifier 'Promise'”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    10 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix72
  • Local business without LocalBusiness data

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 234 words

    The homepage has only about 234 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “JOIN” and “Shop”.

  • 3 short forms

    3 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, HubSpot and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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.

  • 2 cookies set on arrival

    2

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 thepharmaz.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2022.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
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 31 issues on thepharmaz.com, including 14 speed issues, 3 SEO issues and 5 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