Website review, no card needed
rudyprojectna.com website review
Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 83 checks
This review found 32 issues worth fixing on rudyprojectna.com, 11 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
83B- #27,005 of 117,615 reviewed websitesbeats 72%
- #17,851 of 66,923 online storesbeats 67%
- #17,312 of 61,018 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 103 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 152 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 154 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
How it loaded on a phone
1.1 s
2.1 s
3.2 s
4.3 s
5.3 s
6.4 s
7.5 s
8.5 s
Speed
Reduce unused JavaScript
4.6 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.6 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 368 KiB13 files are served with short cache lifetimes, so returning visitors download them again (368 KiB).
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.0 s
A phone's processor spends 8.0 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,164 HTML elements
The page has 4,164 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 (Google Tag Manager, Shopify and Facebook and others), adding 2.4 MB and 1.6 s of main-thread time.
Google Tag Manager adds 398 ms
398 msGoogle Tag Manager costs a phone 398 ms of main-thread work and 499 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.
Render-blocking requests
400 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
Shopify adds 334 ms
334 msShopify costs a phone 334 ms of main-thread work and 628 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
292 KiB18 images could be 292 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Facebook adds 262 ms
262 msFacebook costs a phone 262 ms of main-thread work and 284 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.
ZenDesk adds 224 ms
224 msZenDesk costs a phone 224 ms of main-thread work and 431 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.
Klaviyo adds 208 ms
208 msKlaviyo costs a phone 208 ms of main-thread work and 433 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
150 ms · 67 KiBPolyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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 JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 24.8 s
24.8 sYour largest element takes 24.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners, including Shopify, use cookies and oth…”.
Time to Interactive: 29.4 s
29.4 sThe page becomes fully interactive after 29.4 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 911 ms
911 msScripts block taps and scrolling for 911 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 48% slower for real visitors
+48%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 103 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s 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: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 133 ms
133 msReal visitors wait 133 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 519 ms
519 msReal visitors wait 519 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.9 MB in 450 requests
5.9 MBYour homepage downloads 5.9 MB in 450 requests on a phone: scripts 2.8 MB (139), images 1.8 MB (181) and other files 921 KiB (104). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (299 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.
4 images below the first screen load straight away
4 images further down the page (131 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.68 g of CO₂e: 201.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 2 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (99 characters)
Your title is 99 characters, so Google will cut it off around 60: “Rudy Project | Official North American Site | Elevate Your Performance – Rudy Project Nor…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Rudy Project North America” and “Shop By Sport”). One clear main headline is easier for people and search engines.
Meta description is long (249 characters)
Your meta description is 249 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
447 internal links, 11 external
The homepage links to 447 pages on rudyprojectna.com and 11 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.rudyprojectna.com/.
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://www.rudyprojectna.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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (3,276 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.rudyprojectna.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 96 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
71 of 77 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 2,377 words of copy
The homepage carries about 2,377 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP WINGDREAM” and “SHOP ASTRAL ARC”.
25 calls to action
The homepage has 25 calls to action, for example “Shop All”, “Shop Sale Items” and “SHOP WINGDREAM”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 111 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Meta Pixel.
Privacy and tracking
5 trackers load before any consent
5Before 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
42 other companies contacted
Loading the homepage contacts 42 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 rudyprojectna.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Triplewhale · Elevar Conversion Tracking · Loyalty Rewards And Referrals · Assortion · Blocky Fraud Blocker · Klaviyo Email Marketing Sms · Avada Cookie Bar · Rudy Ambassador Framework · Variable Products · Sunglass Builder · govx.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
Company
- Headquarters
- San Clemente
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on rudyprojectna.com, including 20 speed issues, 5 SEO issues and 1 conversion gap. 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.