ycarpart.com website review

YouTube costs a phone 1.5 s of main-thread work and 2.9 MB 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 9.2 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (YouTube, Shopify and Google CDN and others), adding 4.9 MB and 2.4 s of main-thread time.

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

29 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

Shopify costs a phone 404 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.

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

Google CDN costs a phone 180 ms of main-thread work and 299 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.

45 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 21 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.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 147 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.7 MB in 524 requests on a phone: scripts 4.1 MB (125), images 2.8 MB (61) and other files 1.6 MB (284). Under 2 MB keeps phones on slow connections fast.

d386874de98442f2a864696af1cce026.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).

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 367 pages on ycarpart.com and 2 external pages.

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

https://ycarpart.com/products/black-front-bumper-grille-grill-fit-ford-f150-2024-with-led, https://ycarpart.com/products/black-front-bumper-grille-grill-fit-ford-f150-raptor-2024-only, https://ycarpart.com/products/front-bumper-grille-cl3z8200da-fit-ford-f150-2010-2014-raptor-w-o-camera-hole and https://ycarpart.com/products/1999-2004-excursion-f250-f350-f450-f550-ford-raptor-style-grill-replacement-super-duty-black-generic declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

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

/, https://ycarpart.com/products/black-front-bumper-grille-grill-fit-ford-f150-2024-with-led, https://ycarpart.com/products/black-front-bumper-grille-grill-fit-ford-f150-raptor-2024-only, https://ycarpart.com/products/front-bumper-grille-cl3z8200da-fit-ford-f150-2010-2014-raptor-w-o-camera-hole and https://ycarpart.com/products/1999-2004-excursion-f250-f350-f450-f550-ford-raptor-style-grill-replacement-super-duty-black-generic all use the title “YCarPart - Quality Parts For Powerful Rides | ycarpart”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ycarpart.com/customer_authentication/redirect, https://ycarpart.com/collections/f150, https://ycarpart.com/collections/f150-09-14, https://ycarpart.com/collections/f150-15-17, https://ycarpart.com/collections/f150-18-20 and https://ycarpart.com/collections/f250-f550 have no meta description, so Google writes the search snippet from whatever text it finds.

https://ycarpart.com/products/black-front-bumper-grille-grill-fit-ford-f150-2024-with-led, https://ycarpart.com/products/black-front-bumper-grille-grill-fit-ford-f150-raptor-2024-only, https://ycarpart.com/products/front-bumper-grille-cl3z8200da-fit-ford-f150-2010-2014-raptor-w-o-camera-hole and https://ycarpart.com/products/1999-2004-excursion-f250-f350-f450-f550-ford-raptor-style-grill-replacement-super-duty-black-generic use the same meta description. A description written for each page earns more clicks.

https://ycarpart.com/customer_authentication/redirect, https://ycarpart.com/collections/ford-grille, https://ycarpart.com/collections/f150, https://ycarpart.com/products/matte-black-front-honeycomb-bumper-grille-grill-fit-ford-f150-1992-1996-w-led, https://ycarpart.com/products/matte-black-front-honeycomb-bumper-grille-grill-fit-ford-f150-1999-2003-w-led and https://ycarpart.com/products/04-08-f150-ford-raptor-style-black-front-mesh-hood-grill-grille-replacement-with-led-generic and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://review-images.judgeme.com/ycarpart/1788888594__1788888582690-img_2004__original.jpeg?quality=80&width=480.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'themeName')”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 1,407 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 11 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.