subimods.com website review

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

Shopify costs a phone 2.0 s of main-thread work and 898 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.

Google Tag Manager costs a phone 1.1 s of main-thread work and 700 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.

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Facebook and others), adding 2.4 MB and 4.2 s of main-thread time.

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

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

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

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

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

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

Facebook costs a phone 349 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.

88 KiB could be saved by minifying JavaScript.

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

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 33.2 s. Good is under 3.8 s.

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

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

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

Real visitors wait 210 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 5.7 MB in 490 requests on a phone: scripts 3.1 MB (143), other files 1.5 MB (300) and images 628 KiB (25). Under 2 MB keeps phones on slow connections fast.

6 images (686 KiB) are 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.

5 images are downloaded at several times the size a phone draws them, for example Mod_Taxi_Completed_EFI_-5_2_1620x1080_crop_center.webp at 1,620 px wide, shown at 390 px. Resized copies would save about 419 KiB.

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your title is 74 characters, so Google will cut it off around 60: “Subimods | Subaru Performance Parts, Accessories & Upgrades — Subimods.com”.

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

3 links have no real href, so search engines can't follow them.

The homepage links to 927 pages on subimods.com and 8 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.

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

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

/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

/customer_authentication/redirect, /collections/2002-2003-wrx-brakes, /collections/2002-2003-wrx-cooling, /collections/2002-2003-wrx-drivetrain, /collections/2002-2003-wrx-engine and /collections/2002-2003-wrx-engine-management and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/customer_authentication/redirect and /collections/2002-2003-wrx-fuel-system took over 3 s to send their HTML from our server.

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

5 errors were logged to the browser console while the page loaded, for example “attachCartListener is not defined”.

Large scripts ship without source maps.

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: a star rating. 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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 729 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 39 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.