Website review, no card needed
racingusa.com website review
Visit site (opens in a new tab)Reviewed 10 November 202625 issues · 72 checks
This review found 25 issues worth fixing on racingusa.com, 3 of them high impact, across 72 checks. The most urgent: delayed refresh under 20 hours must not be used (1 element). Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
88B- #4,701 of 95,489 reviewed websitesbeats 93%
- #2,477 of 51,504 online storesbeats 93%
- #2,401 of 46,611 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 960 ms |
| Oct 31, 2026 | 946 ms |
| Nov 7, 2026 | 935 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 303 ms |
| May 30, 2026 | 229 ms |
| Jun 6, 2026 | 209 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 183 ms |
| Jun 27, 2026 | 181 ms |
| Jul 4, 2026 | 181 ms |
| Jul 11, 2026 | 213 ms |
| Jul 18, 2026 | 218 ms |
| Jul 25, 2026 | 220 ms |
| Aug 1, 2026 | 204 ms |
| Aug 8, 2026 | 174 ms |
| Aug 15, 2026 | 165 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 201 ms |
| Sep 19, 2026 | 203 ms |
| Sep 26, 2026 | 201 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 249 ms |
| Oct 17, 2026 | 275 ms |
| Oct 24, 2026 | 285 ms |
| Oct 31, 2026 | 270 ms |
| Nov 7, 2026 | 247 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
Speed
Mobile performance score: 89
89/100Your mobile performance score is 89. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
636 KiBAbout 636 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
327 KiB12 images could be 327 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
300 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Shopify adds 120 ms
120 msShopify costs a phone 120 ms of main-thread work and 308 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.
Heroku adds 16 ms
16 msHeroku costs a phone 16 ms of main-thread work and 413 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Bing Ads and seguno.com and others), adding 1,019 KiB and 207 ms of main-thread time.
Minify JavaScript
148 KiB148 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
139 KiB12 files are served with short cache lifetimes, so returning visitors download them again (139 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.
Reduce unused CSS
37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 601 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.2 s
6.2 sThe page becomes fully interactive after 6.2 s. Good is under 3.8 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 303 ms to 247 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 105 ms
105 msReal visitors wait 105 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 487 ms
487 msReal visitors wait 487 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.5 s
2.5 sYour largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Guaranteed Lowest Prices • 15% Off a Second Item • In-Stock…”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 15 ms
15 msScripts block the page for only 15 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.4 MB in 194 requests
2.4 MBYour homepage downloads 2.4 MB in 194 requests on a phone: scripts 1.1 MB (56), other files 823 KiB (112) and images 393 KiB (15). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 83.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Headings should not be empty (1 element)
Headings should not be empty: 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 30 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “RacingUSA NASCAR Diecast, NASCAR T-Shirts, NASCAR Hats, Merchandise”.
Meta description is long (296 characters)
Your meta description is 296 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
290 internal links, 0 external
The homepage links to 290 pages on racingusa.com and 0 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://racingusa.com/.
Structured data in place
Structured data found: WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://racingusa.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
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://racingusa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 133 found) and read each the way a search engine does.
7 checks passed
Linked pages load
3 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 3 pages that loaded have a meta description.
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 3 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Shop by Driver”, “Subscribe” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
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.
1 other company contacted
Loading the homepage contacts 1 host 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 racingusa.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Postscript Sms Marketing · Flair · Seguno Popups · Upseller Product Upsell · Reputon Google Reviews Widget · Test Sms · Essentials Estimated Delivery · googleapis.com · herokuapp.com
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
- Framework
- jQuery
- 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 25 issues on racingusa.com, including 10 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.