Website review, no card needed

petdesk.com logo

petdesk.com website review

Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 78 checks

This review found 26 issues worth fixing on petdesk.com, 5 of them high impact, across 78 checks. The most urgent: page weight: 4.6 MB in 146 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.3 s1.1 sMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
107 ms82 msMay 16Oct 3185 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026103 ms
May 23, 2026100 ms
May 30, 202697 ms
Jun 6, 202696 ms
Jun 13, 202695 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 202696 ms
Jul 11, 202697 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202698 ms
Aug 22, 2026102 ms
Aug 29, 2026103 ms
Sep 5, 2026104 ms
Sep 12, 2026104 ms
Sep 19, 2026104 ms
Sep 26, 2026103 ms
Oct 3, 202696 ms
Oct 10, 202692 ms
Oct 17, 202687 ms
Oct 24, 202686 ms
Oct 31, 202685 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 petdesk.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix94
  • 3,177 HTML elements

    The page has 3,177 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 (Framer CDN, Google Tag Manager and Hubspot and others), adding 4.5 MB and 1.0 s of main-thread time.

  • Framer CDN adds 684 ms

    684 ms

    Framer CDN costs a phone 684 ms of main-thread work and 3.7 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.

  • Reduce unused JavaScript

    475 KiB

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

  • Improve image delivery

    373 KiB

    18 images could be 373 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Main-thread work: 3.6 s

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

  • Google Tag Manager adds 269 ms

    269 ms

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

  • 10 long tasks on the main thread

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

  • Use efficient cache lifetimes

    149 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (149 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.

2 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94. That is in Google's “good” band (90 and up).

  • Server response: 59 ms

    59 ms

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

Core Web Vitals

2 to fix100
  • Time to Interactive: 17.4 s

    17.4 s

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

  • Total Blocking Time: 253 ms

    253 ms

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

11 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.0 s

    1.0 s

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

  • Real-user INP: 90 ms

    90 ms

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

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (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.

  • Real-user TTFB: 466 ms

    466 ms

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

  • Speed Index: 3.1 s

    3.1 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.008

    0.008

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

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Save 25-30 hours per week & grow clinic revenue by 25%”.

Images and page weight

2 to fix63
  • Page weight: 4.6 MB in 146 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 146 requests on a phone: other files 1.5 MB (17), images 1.4 MB (62) and scripts 1.4 MB (57). Under 2 MB keeps phones on slow connections fast.

  • 12 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.30 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8792
  • Elements must only use permitted ARIA attributes (4 elements)

    Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

  • 4 text elements with low contrast

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

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

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

  • 11 form fields without a label

    11 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 6 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 228 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

5 to fixGoogle 9279
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Veterinary Software Built to Reclaim Time and Connect With Clients”.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Save 25-30 hours per week& grow clinic revenue by…”, “Save 25-30 hours per week& grow clinic revenue by…” and “Save 25-30 hours per week & grow clinic revenue b…”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Organization, SoftwareApplication and WebSite) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

  • No social preview image

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

  • 10 links crawlers can't follow

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

  • 159 internal links, 18 external

    The homepage links to 159 pages on petdesk.com and 18 external pages.

4 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Veterinary software built to easily grow your clinic through communication tools, integrated phones, direct booking, AI…”.

  • Canonical URL set

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

  • 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://petdesk.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,028 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without an H1

    https://petdesk.com/book-a-demo has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://petdesk.com/product-tours/full-platform and https://petdesk.com/download-app-for-pet-health have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 10093
  • 4 small tap targets

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

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 fix75
  • Thin social proof

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

  • No analytics detected

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

  • A 12-field form

    Your longest form asks for 12 fields (1 required). Every extra field lowers completion.

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

    The homepage carries about 852 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 26 calls to action

    The homepage has 26 calls to action, for example “Get a demo”, “Download now” and “Get a Demo”.

  • Direct contact links

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

Privacy and tracking

  • 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). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 petdesk.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
Framer
Hosting
Framer

Hiring

Hiring
10 open roles
Teams
Engineering (5), Customer Experience (4), Marketing (1)
Job board
lever

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on petdesk.com, including 9 speed issues, 5 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