napo.pet website review

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

8 third-party services load with your homepage (framerusercontent.com, Google Tag Manager and TikTok and others), adding 1.9 MB and 992 ms of main-thread time.

Your mobile performance score is 71 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

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

framerusercontent.com costs a phone 441 ms of main-thread work and 934 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.

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

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

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

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

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

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

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

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

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

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 3 <h1> headlines (“Turns out pet insurance can be excellent.”, “Turns out pet insurance can be excellent.” and “Turns out pet insurance can be excellent.”). One clear main headline is easier for people and search engines.

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

The homepage links to 94 pages on napo.pet and 27 external pages.

There is no https://www.napo.pet/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.

https://www.napo.pet/app/policy-docs/wording/latest has no <title>, so Google invents the link text in results.

https://www.napo.pet/stories/piper-s-story, https://www.napo.pet/stories/nuggy-s-story, https://www.napo.pet/stories/mocca-s-story, https://www.napo.pet/events, https://www.napo.pet/complaints and https://www.napo.pet/privacy and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://www.napo.pet/events all use the title “Napo Pet Insurance: Lifetime cover for dogs and cats”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.napo.pet/app/policy-docs/wording/latest has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.napo.pet/blog, https://www.napo.pet/events and https://www.napo.pet/complaints use the same meta description. A description written for each page earns more clicks.

https://www.napo.pet/blog, https://www.napo.pet/stories/piper-s-story, https://www.napo.pet/stories/nuggy-s-story, https://www.napo.pet/stories/mocca-s-story, https://www.napo.pet/complaints and https://www.napo.pet/app/policy-docs/wording/latest and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.napo.pet/app/quote has 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.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=1558243456.1792549030&gtm=45be6aj1v9175081599za20ozb922467…”.

Chrome logged issues while loading the page (“Content security policy”).

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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,616 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel, Reddit Pixel and TikTok Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 14 cookies (measured from a US location before any click).

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