peterdobias.com website review

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

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

8 third-party services load with your homepage (YouTube, Convert Insights and Klaviyo and others), adding 1.5 MB and 1.2 s of main-thread time.

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

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

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

YouTube costs a phone 561 ms of main-thread work and 985 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.

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

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

11 KiB could be saved by minifying JavaScript.

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

About 128 KiB of CSS is downloaded but never applied on this page.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dr. Peter Dobias — natural dog health | Dr. Dobias”.

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

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

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

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

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

Your homepage downloads 3.6 MB in 320 requests on a phone: scripts 1.6 MB (99), other files 750 KiB (93) and images 671 KiB (90). Under 2 MB keeps phones on slow connections fast.

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

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

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

Some list items are not inside a list.

2 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: 7 elements on the page fail this check, rated moderate by axe-core.

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

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

Your title is 67 characters, so Google will cut it off around 60: “Dr. Peter Dobias - Holistic Veterinarian – Dr. Dobias International”.

The homepage links to 266 pages on peterdobias.com and 9 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://peterdobias.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://peterdobias.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://peterdobias.com/customer_authentication/redirect and https://peterdobias.com/pages/recipe-maker have no meta description, so Google writes the search snippet from whatever text it finds.

https://peterdobias.com/pages/customer-reviews, https://peterdobias.com/customer_authentication/redirect, https://peterdobias.com/collections/all, https://peterdobias.com/blogs/blog and https://peterdobias.com/blogs/article have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

Opening the homepage sets 27 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.