tlyard.com website review

Shopify costs a phone 1.2 s of main-thread work and 1,000 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.

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

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

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

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

8 third-party services load with your homepage (Shopify, salesmartly.com and joy.so and others), adding 1.7 MB and 1.7 s of main-thread time.

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

About 725 KiB of JavaScript is downloaded but never used on this page.

salesmartly.com costs a phone 299 ms of main-thread work and 375 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 244 ms. During a long task the page ignores taps.

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

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

6 KiB JavaScript is shipped twice across bundles.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

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

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

The layout shifts by 0.11 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.3 MB in 273 requests on a phone: images 1.6 MB (50), scripts 1.5 MB (94) and other files 835 KiB (91). Under 2 MB keeps phones on slow connections fast.

Tlyard_Black_Friday-Member_perks-mb.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 1.22 g of CO₂e: 146.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 70 characters, so Google will cut it off around 60: “Tlyard - Premium Tesla Accessories | Model 3/Y/S/X & Cybertruck Upgrad”.

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

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

Your <h1> is empty.

The homepage links to 632 pages on tlyard.com and 5 external pages.

https://tlyard.com/collections/new-in and https://tlyard.com/collections/cybertruck have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://tlyard.com/collections/cybertruck-running-board/Cybertruck+Running-Board, whose canonical is https://tlyard.com/collections/cybertruck-running-board/cybertruck. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://tlyard.com/collections/tesla-bundle-deals, https://tlyard.com/collections/new-in, https://tlyard.com/collections/cybertruck, https://tlyard.com/collections/cybertruck-newest-cybertruck-accessories, https://tlyard.com/collections/cybertruck-interior and https://tlyard.com/collections/cybertruck-exterior and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://tlyard.com/products/frunk-molle-panels-2-pcs-for-tesla-cybertruck-2024-customizable-gear-storage-tlyard has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 images failed to load on a phone, for example https://tlyard.com/.

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

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

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