trykradle.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Accessibe Accessibility Overlay and others), adding 3.6 MB and 1.8 s of main-thread time.

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

Shopify costs a phone 366 ms of main-thread work and 2.5 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.

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

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

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

Accessibe Accessibility Overlay costs a phone 338 ms of main-thread work and 250 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.

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Calm Pet is a Happy Pet Vet-formulated, natural supplemen…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.9 MB in 197 requests on a phone: images 2.4 MB (32), scripts 1.4 MB (61) and other files 782 KiB (91). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example TryKRD_Homepage_Pet-Wellness.png at 2,993 px wide, shown at 350 px. Resized copies would save about 481 KiB.

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

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

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

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There are 7 <h1> headlines (“Try Kradle”, “Kradle Pet Supplements” and “The simplest way to help your pet feel their best.”). One clear main headline is easier for people and search engines.

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

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://kradlemypet.com)”.

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

The homepage links to 98 pages on trykradle.com and 20 external pages.

There is no https://trykradle.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://trykradle.com/collections/calming, https://trykradle.com/collections/mobility, https://trykradle.com/collections/skin-allergy and https://trykradle.com/collections/topical-sprays have no meta description, so Google writes the search snippet from whatever text it finds.

https://trykradle.com/collections/shop-all has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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

The homepage carries about 551 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo (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 5 cookies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.