Website review, no card needed

hemptyful.com logo

hemptyful.com website review

Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 75 checks

This review found 41 issues worth fixing on hemptyful.com, 14 of them high impact, across 75 checks. The most urgent: main-thread work: 5.8 s. 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 hemptyful.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hemptyful.com at 1.2 s1.2 s
  2. hemptyful.com at 2.4 s2.4 s
  3. hemptyful.com at 3.6 s3.6 s
  4. hemptyful.com at 4.8 s4.8 s
  5. hemptyful.com at 6.0 s6.0 s
  6. hemptyful.com at 7.2 s7.2 s
  7. hemptyful.com at 8.4 s8.4 s
  8. hemptyful.com at 9.6 s9.6 s

Speed

11 to fix62
  • Main-thread work: 5.8 s

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

  • Improve image delivery

    750 ms · 952 KiB

    17 images could be 952 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, cashfree.com and popt.in and others), adding 2.0 MB and 811 ms of main-thread time.

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    310 ms · 460 KiB

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

  • Use efficient cache lifetimes

    674 KiB

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

  • Reduce unused CSS

    460 ms · 91 KiB

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

  • Shopify adds 320 ms

    320 ms

    Shopify costs a phone 320 ms of main-thread work and 1.1 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.

  • Render-blocking requests

    300 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • cashfree.com adds 246 ms

    246 ms

    cashfree.com costs a phone 246 ms of main-thread work and 520 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.

  • 2,157 HTML elements

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

  • 9 long tasks on the main thread

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Minify JavaScript

    32 KiB

    32 KiB could be saved by minifying JavaScript.

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

    11 ms

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

Core Web Vitals

5 to fix60
  • Largest Contentful Paint: 12.1 s

    12.1 s

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

  • Time to Interactive: 20.1 s

    20.1 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Total Blocking Time: 277 ms

    277 ms

    Scripts block taps and scrolling for 277 ms in total while the page loads. Good is under 200 ms.

  • 15 images without width and height

    15 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
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

3 to fix53
  • Page weight: 5.3 MB in 312 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 312 requests on a phone: images 2.9 MB (70), scripts 1.2 MB (62) and other files 947 KiB (150). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

    7 images further down the page (714 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    41 KiB

    1 image is downloaded at several times the size a phone draws it, for example Meet_The_Founder_Mobile_420_x520px.png at 1,260 px wide, shown at 378 px. Resized copies would save about 41 KiB.

  • About 1.5 g of CO₂ per visit

    1.51 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

11 to fixGoogle 7685
  • Invalid ARIA attributes

    16 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Hidden but focusable

    42 elements hidden from screen readers can still receive keyboard focus.

  • 38 text elements with low contrast

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 30 images without alt text

    30 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • 15 links without text

    15 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

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

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 9279
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Hemptyful Premium Hemp Seed Nutrition | Plant based Protein & Omega -3”.

  • 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 long (167 characters)

    Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 157 internal links, 14 external

    The homepage links to 157 pages on hemptyful.com and 14 external pages.

4 checks passed
  • Canonical URL set

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

  • 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://hemptyful.com/sitemap.xml.

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://hemptyful.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 (2,055 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

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

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://whatsapp-media-library.s3.ap-south-1.amazonaws.com/IMAGE/6523f0cf512dd00b0fdfd31c/63229_profilepicture1697089863817.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 1,265 words of copy

    The homepage carries about 1,265 words of visible text.

4 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “Shop by Category”, “Shop by Concern” and “Register”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 24 testimonial or review blocks and 1 trust badge.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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 Meta Pixel (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.

  • 15 cookies set on arrival

    15

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

  • 34 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on hemptyful.com, including 16 speed issues, 4 SEO 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