loyaltees.com website review

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

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

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

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

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

1 long task block the main thread while loading, the longest for 57 ms. During a long task the page ignores taps.

7 third-party services load with your homepage (Shopify, Google Fonts and shop.app and others), adding 412 KiB and 2 ms of main-thread time.

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.

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

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.

By the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 66.7 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: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 172 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 83 characters, so Google will cut it off around 60: “Custom Pet Shirts, Portraits & Gifts | Unique Art for Pet Lovers – Loyal Tees Store”.

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

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

Your <h1> is empty.

The homepage links to 458 pages on loyaltees.com and 1 external page.

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.

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

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

https://loyaltees.com/collections/custom-pet-iphone-cases and https://loyaltees.com/collections/custom-pet-iphone-cases/iPhone all use the title “Custom Pet iPhone Cases - Your Pet, Always in Hand | Loyal Tees – Loy…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://loyaltees.com/collections/loyal-pet-hats, https://loyaltees.com/collections/pet-artworks, https://loyaltees.com/collections/themed-pet-portrait, https://loyaltees.com/collections/custom-pet-samsung-phone-cases, https://loyaltees.com/collections/loyal-pet-necklace and https://loyaltees.com/collections/shop-pet-pillows and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://loyaltees.com/collections/custom-pet-iphone-cases and https://loyaltees.com/collections/custom-pet-iphone-cases/iPhone use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://loyaltees.com/collections/custom-pet-iphone-cases/iPhone, whose canonical is https://loyaltees.com/collections/custom-pet-iphone-cases. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://loyaltees.com/collections and https://loyaltees.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

https://loyaltees.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

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

The page uses urgency cues (a countdown or limited-time wording).

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 6 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.