Website review, no card needed

petscy.com logo

petscy.com website review

Visit site (opens in a new tab)Reviewed 20 November 202648 issues · 97 checks

This review found 48 issues worth fixing on petscy.com, 14 of them high impact, across 97 checks. The most urgent: audioeye.com adds 5.5 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

Real-visitor load time (LCP)75th percentile, phones
3.1 s2.0 sMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.8 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.2 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
214 ms165 msMay 30Nov 14187 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026175 ms
Jun 6, 2026171 ms
Jun 13, 2026179 ms
Jun 20, 2026186 ms
Jun 27, 2026195 ms
Jul 4, 2026193 ms
Jul 11, 2026194 ms
Jul 18, 2026196 ms
Jul 25, 2026198 ms
Aug 1, 2026206 ms
Aug 8, 2026208 ms
Aug 15, 2026205 ms
Aug 22, 2026205 ms
Aug 29, 2026204 ms
Sep 5, 2026205 ms
Sep 12, 2026204 ms
Sep 19, 2026203 ms
Sep 26, 2026202 ms
Oct 3, 2026181 ms
Oct 10, 2026177 ms
Oct 17, 2026179 ms
Oct 24, 2026178 ms
Oct 31, 2026196 ms
Nov 7, 2026197 ms
Nov 14, 2026187 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 petscy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. petscy.com at 2.4 s2.4 s
  2. petscy.com at 4.8 s4.8 s
  3. petscy.com at 7.2 s7.2 s
  4. petscy.com at 9.6 s9.6 s
  5. petscy.com at 11.9 s11.9 s
  6. petscy.com at 14.3 s14.3 s
  7. petscy.com at 16.7 s16.7 s
  8. petscy.com at 19.1 s19.1 s

Speed

13 to fix58
  • audioeye.com adds 5.5 s

    5.5 s

    audioeye.com costs a phone 5.5 s of main-thread work and 342 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 15.5 s

    A phone's processor spends 15.5 s on main-thread work while loading, 10.5 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 (audioeye.com, alia-prod.com and Clarity and others), adding 2.5 MB and 6.7 s of main-thread time.

  • Use efficient cache lifetimes

    550 ms · 666 KiB

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

  • Improve image delivery

    250 ms · 953 KiB

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

  • Mobile performance score: 58

    58/100

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

  • Reduce unused JavaScript

    300 ms · 665 KiB

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

  • Render-blocking requests

    600 ms

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

  • alia-prod.com adds 384 ms

    384 ms

    alia-prod.com costs a phone 384 ms of main-thread work and 1.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.

  • Clarity adds 352 ms

    352 ms

    Clarity costs a phone 352 ms of main-thread work and 29 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 CSS

    300 ms · 46 KiB

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

  • 2,972 HTML elements

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

  • Google Tag Manager adds 149 ms

    149 ms

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    50 ms · 57 KiB

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

  • Font display

    100 ms

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

  • Duplicated JavaScript

    50 ms · 17 KiB

    17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 43 ms

    43 ms

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

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 16.0 s

    16.0 s

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

  • Speed Index: 28.1 s

    28.1 s

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

  • Time to Interactive: 38.2 s

    38.2 s

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

  • Real-user CLS: 0.13

    0.13

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

  • 53 images without width and height

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

  • Total Blocking Time: 248 ms

    248 ms

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

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

    +11%

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

7 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 170 ms

    170 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 715 ms

    715 ms

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

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

    -22%

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

  • Cumulative Layout Shift: 0.089

    0.089

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

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

Images and page weight

3 to fix53
  • Page weight: 22.1 MB in 709 requests

    22.1 MB

    Your homepage downloads 22.1 MB in 709 requests on a phone: media 13.7 MB (2), images 3.9 MB (140) and scripts 2.1 MB (98). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

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

  • 2 images far larger than shown

    46 KiB

    2 images are downloaded at several times the size a phone draws them, for example happy_dog_cat.jpg at 1,332 px wide, shown at 390 px. Resized copies would save about 46 KiB.

  • About 6.3 g of CO₂ per visit

    6.27 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.27 g of CO₂e: 752.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

8 to fixGoogle 8490
  • 27 tap targets too small

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

  • 18 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 81 images without alt text

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 17 links without text

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • ARIA role should be appropriate for the element (5 elements)

    ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 54 automated accessibility rules passed

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

SEO

3 to fixGoogle 8583
  • No H1 headline

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

  • Meta description is long (169 characters)

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 182 internal links, 8 external

    The homepage links to 182 pages on petscy.com and 8 external pages.

6 checks passed
  • Title: 57 characters

    Your title is a healthy 57 characters: “Pet Supplements for Dogs & Cats | Vet-Formulated | PetScy”.

  • Canonical URL set

    The canonical URL is https://petscy.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://petscy.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix79
  • 13 linked pages hidden from search

    https://petscy.com/products/itch-allergy-plus-chews, https://petscy.com/collections/allergy-itch/products/itch-allergy-plus-chews, https://petscy.com/products/itch-relief-chews, https://petscy.com/collections/allergy-itch/products/itch-relief-chews, https://petscy.com/products/fish-oil and https://petscy.com/collections/allergy-itch/products/fish-oil and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 12 pages share 6 titles

    https://petscy.com/products/itch-allergy-plus-chews and https://petscy.com/collections/allergy-itch/products/itch-allergy-plus-chews all use the title “Itch & Allergy Plus Chews for Dogs | PetScy”, and 5 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages share a meta description

    https://petscy.com/products/itch-allergy-plus-chews and https://petscy.com/collections/allergy-itch/products/itch-allergy-plus-chews use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://petscy.com/collections/allergy-itch, https://petscy.com/products/itch-allergy-plus-chews, https://petscy.com/collections/allergy-itch/products/itch-allergy-plus-chews, https://petscy.com/products/itch-relief-chews, https://petscy.com/collections/allergy-itch/products/itch-relief-chews and https://petscy.com/products/fish-oil and 9 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 74 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5469
  • 1 broken image

    1 image failed to load on a phone, for example https://fyvxii.petscy.com/g/uids?pld=eKgTQXUEdahti2BgcS3aYcxlzrP2i7PFPokkxFVeTbMykw3ibLmvzn9d-XDgeKAt606BUofRCsETVLOPCrg6ImmOvuhNqYm2fTKqzbAUbSUKREunCt_SLyKAgEdnNTf8S8cYjxL1FX-4zkK4EE71JTmIVrQbJdkHUsQ.

  • 36 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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 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.

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

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,758 words of copy

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

5 checks passed
  • 23 calls to action

    The homepage has 23 calls to action, for example “Shop Now.cls-1{fill:#231f20}”, “Shop Now” and “Track My Order”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks, a star rating and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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
  • 8 trackers load before any consent

    8

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

  • 35 cookies set on arrival

    35

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

  • 66 other companies contacted

    Loading the homepage contacts 66 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 petscy.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 48 issues on petscy.com, including 20 speed issues, 3 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