Website review, no card needed
rcpatinaguy.com website review
Visit site (opens in a new tab)Reviewed 11 November 202630 issues · 75 checks
This review found 30 issues worth fixing on rcpatinaguy.com, 7 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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
86BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.7 s
4.2 s
Speed
Use efficient cache lifetimes
1.4 s · 7.8 MB28 files are served with short cache lifetimes, so returning visitors download them again (7.8 MB).
Improve image delivery
5.3 MB5 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
650 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Reduce unused JavaScript
450 ms · 89 KiBAbout 89 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
150 ms · 28 KiBAbout 28 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 38 KiB and 1 ms of main-thread time.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 233 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 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.
Time to Interactive: 4.8 s
4.8 sThe page becomes fully interactive after 4.8 s. Good is under 3.8 s.
Largest Contentful Paint: 2.5 s
2.5 sYour largest element takes 2.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “100”. Most of its time is element render delay (2.3 s).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 26 ms
26 msScripts block the page for only 26 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.8 MB in 32 requests
7.8 MBYour homepage downloads 7.8 MB in 32 requests on a phone: images 7.5 MB (11), scripts 179 KiB (4) and fonts 127 KiB (3). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 5.9 MB together. On a phone connection a single image that size takes seconds.
6 images in older formats
6 images (7.1 MB) 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.
1 image below the first screen load straight away
1 image further down the page (378 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
62 KiB1 image is downloaded at several times the size a phone draws it, for example bgg.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 62 KiB.
About 2.2 g of CO₂ per visit
2.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.22 g of CO₂e: 266.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 text elements with low contrast
5 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 (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail 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.
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.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
25 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 30 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (213 characters)
Your meta description is 213 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://rcpatinaguy.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at rcpatinaguy.com/robots.txt, the first file search crawlers ask for.
23 internal links, 5 external
The homepage links to 23 pages on rcpatinaguy.com and 5 external pages.
4 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “RC Patina Guy LLC — Custom Branded RC Marketing Assets”.
Canonical URL set
The canonical URL is https://rcpatinaguy.com/.
Structured data in place
Structured data found: ProfessionalService.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
No llms.txt
There is no https://rcpatinaguy.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Other pages
3 pages share a title
https://rcpatinaguy.com/about.html, https://rcpatinaguy.com/project-6.html and https://rcpatinaguy.com/project-8.html all use the title “THE RC PATINA GUY”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://rcpatinaguy.com/about.html, https://rcpatinaguy.com/project-6.html and https://rcpatinaguy.com/project-8.html have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://rcpatinaguy.com/project-6.html, https://rcpatinaguy.com/services.html and https://rcpatinaguy.com/project-8.html have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://rcpatinaguy.com/project-6.html and https://rcpatinaguy.com/project-8.html have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 4 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 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 404 ()”.
2 checks passed
Tap targets are thumb-sized
21 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 123 words
The homepage has only about 123 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop for dope merchandise”.
2 calls to action
The homepage has 2 calls to action, for example “Email me, to place an order.” and “Shop for dope merchandise”.
Direct contact links
Visitors can reach you directly: 1 phone link and 4 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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.
2 other companies contacted
Loading the homepage contacts 2 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 rcpatinaguy.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Framework
- jQuery
- Hosting
- IBM Cloud
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 rcpatinaguy.com, including 10 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.