pardyalone.com website review

About 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 15.4 s faster on a phone.

10 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

485 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 3.0 s faster on a phone.

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

8 third-party services load with your homepage (YouTube, route.com and Klaviyo and others), adding 4.5 MB and 1.3 s of main-thread time.

YouTube costs a phone 798 ms of main-thread work and 2.9 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.

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

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

route.com costs a phone 350 ms of main-thread work and 1.1 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.

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

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

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

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

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

6 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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 6.5 MB in 325 requests on a phone: scripts 4.1 MB (145), images 844 KiB (22) and other files 838 KiB (133). Under 2 MB keeps phones on slow connections fast.

Pardy_Hero.png 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).

7 images further down the page (358 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.84 g of CO₂e: 220.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

3 frames have no title, so screen-reader users cannot tell what they contain.

2 tap targets are too small or too close together to hit reliably with a finger.

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: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

The homepage links to 84 pages on pardyalone.com and 9 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

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

https://pardyalone.com/pages/shows, https://pardyalone.com/collections/shop-all, https://pardyalone.com/collections/its-okay-to-not-be-okay, https://pardyalone.com/collections/apparel, https://pardyalone.com/collections/accessories and https://pardyalone.com/pages/music and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pardyalone.com/products/halo-tee and https://pardyalone.com/products/angel-444-tee use the same meta description. A description written for each page earns more clicks.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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

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

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 has only about 217 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Amplitude, Google Ads 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 10 cookies, 1 of them by other companies (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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.