Website review, no card needed

racelinewheels.com logo

racelinewheels.com website review

Visit site (opens in a new tab)Reviewed 8 November 202636 issues · 89 checks

This review found 36 issues worth fixing on racelinewheels.com, 12 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.7 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
96 ms90 msMay 16Oct 3194 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202691 ms
May 23, 202692 ms
May 30, 202695 ms
Jun 6, 202695 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202695 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 15, 202695 ms
Aug 22, 202695 ms
Aug 29, 202695 ms
Sep 5, 202694 ms
Sep 12, 202694 ms
Sep 19, 202694 ms
Sep 26, 202695 ms
Oct 3, 202693 ms
Oct 10, 202693 ms
Oct 17, 202693 ms
Oct 24, 202691 ms
Oct 31, 202694 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of racelinewheels.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. racelinewheels.com at 0.6 s0.6 s
  2. racelinewheels.com at 1.2 s1.2 s
  3. racelinewheels.com at 1.7 s1.7 s
  4. racelinewheels.com at 2.3 s2.3 s
  5. racelinewheels.com at 2.9 s2.9 s
  6. racelinewheels.com at 3.5 s3.5 s
  7. racelinewheels.com at 4.0 s4.0 s
  8. racelinewheels.com at 4.6 s4.6 s

Speed

10 to fix60
  • Reduce unused JavaScript

    2.9 s · 630 KiB

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

  • Use efficient cache lifetimes

    2.5 s · 516 KiB

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

  • Mobile performance score: 60

    60/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Affirm, POWr and Shopify and others), adding 991 KiB and 771 ms of main-thread time.

  • Improve image delivery

    773 KiB

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

  • Render-blocking requests

    650 ms

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

  • Reduce unused CSS

    430 ms · 65 KiB

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

  • Main-thread work: 3.5 s

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

  • 2,924 HTML elements

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

  • Shopify adds 148 ms

    148 ms

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

  • Legacy JavaScript

    200 ms · 38 KiB

    Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 5 long tasks on the main thread

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

  • Minify CSS

    150 ms · 12 KiB

    12 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

1 checks passed
  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 24.1 s

    24.1 s

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

  • Time to Interactive: 25.0 s

    25.0 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 110 ms

    110 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 431 ms

    431 ms

    Real visitors wait 431 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

  • Total Blocking Time: 163 ms

    163 ms

    Scripts block the page for only 163 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 6.4 MB in 233 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 233 requests on a phone: images 4.0 MB (47), scripts 1.3 MB (74) and other files 767 KiB (95). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

    6 images further down the page (150 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.82 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 9490
  • 20 tap targets too small

    20 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • Page should contain a level-one heading (1 element)

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

  • 10 links without text

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

  • 4 text elements with low contrast

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8583
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//racelinewheels.com/cdn/shop/files/Raceline_PitCrew_Lo…”.

  • 2 links crawlers can't follow

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

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 137 internal links, 20 external

    The homepage links to 137 pages on racelinewheels.com and 20 external pages.

5 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “Raceline Wheels offers performance wheels for off-road, street, and track use so you can Go Everywhere. Find your wheel…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Raceline Wheels: Performance Aftermarket Wheels”.

  • Canonical URL set

    The canonical URL is https://racelinewheels.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://racelinewheels.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,530 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://racelinewheels.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://racelinewheels.com/collections/utv-tires, https://racelinewheels.com/collections/golf-cart-wheels, https://racelinewheels.com/pages/wheel-builder and https://racelinewheels.com/collections/accessories have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://racelinewheels.com/collections/garage, https://racelinewheels.com/collections/truck-suv, https://racelinewheels.com/collections/offroad-beadlock-wheels, https://racelinewheels.com/collections/customs, https://racelinewheels.com/collections/passcar and https://racelinewheels.com/collections/utv-atv and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://racelinewheels.com/collections/truck-suv, https://racelinewheels.com/collections/offroad-beadlock-wheels, https://racelinewheels.com/collections/customs, https://racelinewheels.com/collections/passcar, https://racelinewheels.com/collections/utv-tires and https://racelinewheels.com/collections/golf-cart-wheels and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 8 broken images

    8 images failed to load on a phone, for example https://racelinewheels.com/.

  • 19 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    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.

  • No analytics detected

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

  • No opening hours

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

  • Phone number is not tap-to-call

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

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 586 words of copy

    The homepage carries about 586 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP” and “SHOP SALE”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “SHOP”, “SHOP 2 PIECE CUSTOMS” and “Where to Buy”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 25 other companies contacted

    Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at racelinewheels.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on racelinewheels.com, including 14 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25