Website review, no card needed

heliopet.com logo

heliopet.com website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 78 checks

This review found 36 issues worth fixing on heliopet.com, 15 of them high impact, across 78 checks. The most urgent: avoid multiple page redirects. 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
2.3 s1.8 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
201 ms158 msMay 16Oct 31163 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026181 ms
May 23, 2026178 ms
May 30, 2026182 ms
Jun 6, 2026186 ms
Jun 13, 2026187 ms
Jun 20, 2026189 ms
Jun 27, 2026189 ms
Jul 4, 2026192 ms
Jul 11, 2026188 ms
Jul 18, 2026182 ms
Jul 25, 2026180 ms
Aug 1, 2026178 ms
Aug 8, 2026184 ms
Aug 15, 2026195 ms
Aug 22, 2026187 ms
Aug 29, 2026181 ms
Sep 5, 2026180 ms
Sep 12, 2026179 ms
Sep 19, 2026178 ms
Sep 26, 2026192 ms
Oct 3, 2026195 ms
Oct 10, 2026196 ms
Oct 17, 2026181 ms
Oct 24, 2026163 ms
Oct 31, 2026163 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 heliopet.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. heliopet.com at 0.8 s0.8 s
  2. heliopet.com at 1.7 s1.7 s
  3. heliopet.com at 2.5 s2.5 s
  4. heliopet.com at 3.4 s3.4 s
  5. heliopet.com at 4.2 s4.2 s
  6. heliopet.com at 5.1 s5.1 s
  7. heliopet.com at 5.9 s5.9 s
  8. heliopet.com at 6.8 s6.8 s

Speed

11 to fix37
  • Avoid multiple page redirects

    10.4 s

    The page goes through 2 redirects before it starts loading, costing about 10.4 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    2.9 s · 470 KiB

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

  • Improve image delivery

    1.1 s · 301 KiB

    6 images could be 301 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.

  • Minify JavaScript

    1.1 s · 71 KiB

    71 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (avada.io, Facebook and Klaviyo and others), adding 14.3 MB and 926 ms of main-thread time.

  • Shopify adds 60 ms

    60 ms

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

  • Use efficient cache lifetimes

    442 KiB

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

  • Facebook adds 203 ms

    203 ms

    Facebook costs a phone 203 ms of main-thread work and 339 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.

  • 1,843 HTML elements

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

  • Document request latency

    250 ms

    The HTML itself could arrive about 250 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • 20 long tasks on the main thread

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

  • Duplicated JavaScript

    44 KiB

    44 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    38 KiB

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

  • Reduce unused CSS

    19 KiB

    About 19 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.

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

    17 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 19.9 s

    19.9 s

    Your largest element takes 19.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Help your pet from home & Reduce their Pain Meet HelioPet™!…”.

  • Time to Interactive: 25.8 s

    25.8 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

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

    1.4 s

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

  • Real-user INP: 186 ms

    186 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 643 ms

    643 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix33
  • Page weight: 17.7 MB in 412 requests

    17.7 MB

    Your homepage downloads 17.7 MB in 412 requests on a phone: media 12.8 MB (7), scripts 2.1 MB (177) and images 1.0 MB (27). Under 2 MB keeps phones on slow connections fast.

  • About 5.0 g of CO₂ per visit

    5.02 g

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

Accessibility

6 to fixGoogle 8683
  • 4 images without alt text

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

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

  • 7 text elements with low contrast

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

  • 3 tap targets too small

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

1 checks passed
  • 14 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Meta description is long (309 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 48 internal links, 2 external

    The homepage links to 48 pages on heliopet.com and 2 external pages.

6 checks passed
  • Title: 60 characters

    Your title is a healthy 60 characters: “Helio Pet | Reduce Pain for Pets at Home | Helio Pet Website”.

  • Canonical URL set

    The canonical URL is https://www.heliopet.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.heliopet.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

4 to fix81
  • 5 linked pages hidden from search

    https://www.heliopet.com/products/low-level-laser-therapy-for-pets, https://www.heliopet.com/products/helio-mobilitymax-drops, https://www.heliopet.com/products/nail-grinder, https://www.heliopet.com/products/air-filter and https://www.heliopet.com/products/laser-glasses are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 7 pages without a meta description

    https://www.heliopet.com/pages/contact-us, https://www.heliopet.com/pages/science-page, https://www.heliopet.com/pages/technology, https://www.heliopet.com/products/helio-mobilitymax-drops, https://www.heliopet.com/products/nail-grinder and https://www.heliopet.com/policies/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.heliopet.com/products/pet-device and https://www.heliopet.com/products/low-level-laser-therapy-for-pets use the same meta description. A description written for each page earns more clicks.

  • 11 pages without an H1

    https://www.heliopet.com/pages/contact-us, https://www.heliopet.com/pages/science-page, https://www.heliopet.com/pages/technology, https://www.heliopet.com/pages/reviews, https://www.heliopet.com/products/pet-device and https://www.heliopet.com/products/helio-calm-collar and 5 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 20 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 11 words

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

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

3 checks passed
  • 19 calls to action

    The homepage has 19 calls to action, for example “Contact Us”, “shop now” and “Shop Now”.

  • 12 short forms

    12 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 4 mores (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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 28 of them by other companies (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.

  • 54 other companies contacted

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

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Nabu For Fb Pixel · Gempages Builder · Kilatech Currency Converter · Feedapis For Bing Shopping Ms · Simprosys Google Shopping Feed · Klaviyo Email Marketing Sms · Gempages Cro · Stape Remix · Avada Cookie Bar · stamped.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on heliopet.com, including 17 speed issues, 2 SEO issues and 4 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