Website review, no card needed

racecompengineering.com logo

racecompengineering.com website review

Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 81 checks

This review found 30 issues worth fixing on racecompengineering.com, 8 of them high impact, across 81 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
1.1 s828 msMay 16Oct 31862 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.0 s
May 23, 2026990 ms
May 30, 2026943 ms
Jun 6, 2026943 ms
Jun 13, 2026932 ms
Jun 20, 2026926 ms
Jun 27, 2026944 ms
Jul 4, 2026941 ms
Jul 11, 2026910 ms
Jul 18, 2026921 ms
Jul 25, 2026946 ms
Aug 1, 2026961 ms
Aug 8, 2026997 ms
Aug 15, 2026976 ms
Aug 22, 2026951 ms
Aug 29, 2026983 ms
Sep 5, 2026986 ms
Sep 12, 2026978 ms
Sep 19, 2026980 ms
Sep 26, 2026916 ms
Oct 3, 2026873 ms
Oct 10, 2026864 ms
Oct 17, 2026856 ms
Oct 24, 2026877 ms
Oct 31, 2026862 ms
Real-visitor tap response (INP)75th percentile, phones
81 ms65 msMay 16Oct 3167 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202671 ms
May 23, 202671 ms
May 30, 202674 ms
Jun 6, 202676 ms
Jun 13, 202678 ms
Jun 20, 202678 ms
Jun 27, 202676 ms
Jul 4, 202674 ms
Jul 11, 202673 ms
Jul 18, 202671 ms
Jul 25, 202672 ms
Aug 1, 202673 ms
Aug 8, 202671 ms
Aug 15, 202675 ms
Aug 22, 202675 ms
Aug 29, 202675 ms
Sep 5, 202678 ms
Sep 12, 202679 ms
Sep 19, 202675 ms
Sep 26, 202678 ms
Oct 3, 202672 ms
Oct 10, 202671 ms
Oct 17, 202670 ms
Oct 24, 202669 ms
Oct 31, 202667 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 racecompengineering.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. racecompengineering.com at 1.1 s1.1 s
  2. racecompengineering.com at 2.1 s2.1 s
  3. racecompengineering.com at 3.2 s3.2 s
  4. racecompengineering.com at 4.3 s4.3 s
  5. racecompengineering.com at 5.3 s5.3 s
  6. racecompengineering.com at 6.4 s6.4 s
  7. racecompengineering.com at 7.5 s7.5 s
  8. racecompengineering.com at 8.5 s8.5 s

Speed

8 to fix59
  • Reduce unused JavaScript

    1.2 s · 732 KiB

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

  • 3,348 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Shopify and shop.app and others), adding 1.9 MB and 841 ms of main-thread time.

  • Mobile performance score: 59

    59/100

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

  • YouTube adds 516 ms

    516 ms

    YouTube costs a phone 516 ms of main-thread work and 1,015 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.

  • Improve image delivery

    300 ms · 191 KiB

    10 images could be 191 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 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.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Shopify adds 267 ms

    267 ms

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

  • Reduce unused CSS

    260 ms · 166 KiB

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

  • Render-blocking requests

    250 ms

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

  • Minify JavaScript

    150 ms · 32 KiB

    32 KiB could be saved by minifying JavaScript.

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    29 KiB

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

  • 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 8.4 s

    8.4 s

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

  • Time to Interactive: 16.3 s

    16.3 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Cumulative Layout Shift: 0.127

    0.127

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

  • Tap response (INP) held steady for real visitors

    -4%

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

8 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: 0.9 s

    0.9 s

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

  • Real-user INP: 68 ms

    68 ms

    Real visitors wait 68 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: 0.6 s

    0.6 s

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

  • Real-user TTFB: 377 ms

    377 ms

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

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

    -15%

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

  • Total Blocking Time: 128 ms

    128 ms

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

Images and page weight

2 to fix81
  • Page weight: 3.8 MB in 289 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 289 requests on a phone: scripts 1.6 MB (125), images 987 KiB (30) and other files 831 KiB (110). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    61E5F030-16C7-45FD-ABB4-5D51E0E2DE90_1_201_a.jpg 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).

  • About 1.1 g of CO₂ per visit

    1.08 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 130.0 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

5 to fixGoogle 9194
  • 2 tap targets too small

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

  • 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.

  • Zoom is disabled

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

  • 4 links without text

    4 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)

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

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

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • Meta description is short (53 characters)

    Your meta description is only 53 characters: “Custom-engineered suspension products for Subaru cars”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • 96 internal links, 4 external

    The homepage links to 96 pages on racecompengineering.com and 4 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Racecomp Engineering”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Racecomp Engineering | Subaru Suspension Solutions”.

  • Canonical URL set

    The canonical URL is https://www.racecompengineering.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://www.racecompengineering.com/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

2 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.

  • llms.txt published

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

Other pages

1 to fix95
  • 11 pages without a meta description

    https://www.racecompengineering.com/collections/sway-bar-end-links, https://www.racecompengineering.com/collections/2022-wrx, https://www.racecompengineering.com/collections/2022-brz-gr86, https://www.racecompengineering.com/collections/2013-brz-fr-s-86, https://www.racecompengineering.com/collections/2015-2020-sti and https://www.racecompengineering.com/collections/2015-2020-wrx and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 7391
  • 17 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

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

  • No social proof

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

  • No analytics detected

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

  • Only about 120 words

    The homepage has only about 120 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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 risk reducer

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

2 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Shop” and “Shop by Car”.

  • 4 short forms

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

Privacy and tracking

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 7 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 racecompengineering.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Rivyo Product Review · cloudfront.net · ablestar.app

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on racecompengineering.com, including 13 speed issues, 2 SEO issues and 4 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