runnin4tacos.com website review

About 759 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, anglerfox.com and route.com and others), adding 2.0 MB and 1.5 s of main-thread time.

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

Shopify costs a phone 701 ms of main-thread work and 895 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 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.

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

anglerfox.com costs a phone 444 ms of main-thread work and 159 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

4 KiB could be saved by minifying JavaScript.

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

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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tune Outdoor M1L vs Super Pacific X1: Which Truck Camper Is…”.

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

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

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

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

Your homepage downloads 4.9 MB in 274 requests on a phone: scripts 1.8 MB (112), other files 1.6 MB (117) and images 1.1 MB (27). Under 2 MB keeps phones on slow connections fast.

Tune-Outdoor-M1L-vs-Superpacific-X1_9dc66384-b6d0-4ebf-9418- 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).

1 image (168 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

4 elements hidden from screen readers can still receive keyboard focus.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Your title is 67 characters, so Google will cut it off around 60: “Denver's Best Toyota Off-Road Parts Store & Installation Shop | R4T”.

Your meta description is 319 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.

The homepage links to 864 pages on runnin4tacos.com and 10 external pages.

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://runnin4tacos.com/collections/3g-sequoia and https://runnin4tacos.com/collections/3g-sequoia/Roof-Rack-Accessories all use the title “3G Sequoia (2023+)”. Search engines can't tell which page to show for a search, so each competes with the others.

https://runnin4tacos.com/collections/all-tacoma-products, https://runnin4tacos.com/collections/all-4runner-products, https://runnin4tacos.com/collections/all-tundra-products, https://runnin4tacos.com/collections/3g-sequoia, https://runnin4tacos.com/collections/3g-sequoia-bumpers and https://runnin4tacos.com/collections/3g-sequoia-bumper-accessories and 7 others 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://runnin4tacos.com/collections/3g-sequoia/Roof-Rack-Accessories, whose canonical is https://runnin4tacos.com/collections/3g-sequoia/roof-rack-accessories. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://runnin4tacos.com/collections/all-tacoma-products, https://runnin4tacos.com/collections/all-4runner-products and https://runnin4tacos.com/collections/all-tundra-products have no <h1> headline, so visitors and search engines get no clear main topic.

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

19 of 67 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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.

Social proof on the homepage: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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