kinship.co website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Facebook and others), adding 2.1 MB and 1.5 s of main-thread time.

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

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

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

Google/Doubleclick Ads costs a phone 298 ms of main-thread work and 533 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.

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

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

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

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.

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

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

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

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

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

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

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

Your homepage downloads 3.7 MB in 154 requests on a phone: scripts 2.4 MB (59), images 796 KiB (32) and fonts 213 KiB (5). Under 2 MB keeps phones on slow connections fast.

1324947662 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example image at 2,400 px wide, shown at 285 px. Resized copies would save about 100 KiB.

1 image further down the page (43 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Some list items are not inside a list.

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

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

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 1,089 pages on kinship.co and 34 external pages.

There is no https://www.adoptapet.com/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.adoptapet.com/animal-shelters-near-me has no <title>, so Google invents the link text in results.

https://www.adoptapet.com/blog and https://www.adoptapet.com/shelter-guide all use the title “Adopt a Pet – Pet Advice for Adopters and Pet Parents”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.adoptapet.com/animal-shelters-near-me and https://www.adoptapet.com/dog-breeds have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.adoptapet.com/blog and https://www.adoptapet.com/shelter-guide use the same meta description. A description written for each page earns more clicks.

https://www.adoptapet.com/animal-shelters-near-me, https://www.adoptapet.com/blog and https://www.adoptapet.com/shelter-guide have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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 15 cookies (measured from a US location before any click).

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