tunerdepot.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and loox.io and others), adding 2.0 MB and 1.7 s of main-thread time.

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

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

Google Tag Manager costs a phone 511 ms of main-thread work and 330 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.

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

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

loox.io costs a phone 293 ms of main-thread work and 567 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.

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

Facebook costs a phone 303 ms of main-thread work and 227 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 305 ms. During a long task the page ignores taps.

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

Shopify costs a phone 99 ms of main-thread work and 647 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.

Polyfills for old browsers add 41 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 17.9 s. Good is under 3.8 s.

Your largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AMERICA'S #1 DIESEL PERFORMANCE STORE UNLOCK YOUR DIESEL TR…”.

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 4.4 MB in 417 requests on a phone: images 1.7 MB (51), scripts 1.4 MB (100) and other files 1.1 MB (224). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example pipe-egr.png at 820 px wide, shown at 72 px. Resized copies would save about 105 KiB.

1 image (36 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

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

The homepage links to 163 pages on tunerdepot.com and 7 external pages.

There is no https://tunerdepot.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://tunerdepot.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://tunerdepot.com/collections/all and https://tunerdepot.com/pages/bundle-builder have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343000169&Ver=2&mid=366669d8-90a2-4f8e-848e-aefa13ab2132&bo=1&sid=a3103f40dc7c11f195e4a9668b872a73&vid=a3104d30dc7c11f190085d50b3cfd58b&vids=1&msclkid=N&pi=918639831&l.

3 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

The homepage carries about 883 words of visible text.

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