selenepets.com website review

Google Tag Manager costs a phone 1.2 s of main-thread work and 313 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 8.3 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, trackcollect.com and megaracoon.com and others), adding 1,016 KiB and 2.0 s of main-thread time.

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

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

trackcollect.com costs a phone 681 ms of main-thread work and 108 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.

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

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

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

whop.com costs a phone 0 ms of main-thread work and 406 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 155 KiB of JavaScript is downloaded but never used on this page.

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

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

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.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s 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.45 g of CO₂e: 54.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 6 characters: “Selene”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to selenepets.whop.site, not selenepets.com, so Google may credit that host instead.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No XML sitemap at https://selenepets.whop.site/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 46 pages on selenepets.com and 5 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://selenepets.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://selenepets.com/products/the-kitty-fountain, https://selenepets.com/apps/track123, https://selenepets.com/customer_authentication/redirect, https://selenepets.com/products/dental-health-bundle and https://selenepets.com/products/antisplash-mat-for-the-doggy-fountain are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://selenepets.com/apps/track123 and https://selenepets.com/customer_authentication/redirect all use the title “Track order status”. Search engines can't tell which page to show for a search, so each competes with the others.

https://selenepets.com/collections/fountains, https://selenepets.com/products/the-kitty-fountain, https://selenepets.com/collections/accesories, https://selenepets.com/collections/selene-bundles, https://selenepets.com/pages/contact and https://selenepets.com/pages/account-subscription and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://selenepets.com/collections/fountains, https://selenepets.com/products/the-kitty-fountain, https://selenepets.com/pages/contact, https://selenepets.com/pages/account-subscription, https://selenepets.com/apps/track123 and https://selenepets.com/customer_authentication/redirect and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://selenepets.com/collections/fountains, https://selenepets.com/products/the-kitty-fountain, https://selenepets.com/collections/accesories, https://selenepets.com/pages/contact, https://selenepets.com/pages/account-subscription and https://selenepets.com/customer_authentication/redirect and 6 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Failed to construct 'URL': Invalid base URL”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 904 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and 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 4 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.