Website review, no card needed
rileysalonresources.com website review
Visit site (opens in a new tab)Reviewed 16 November 202627 issues · 64 checks
This review found 27 issues worth fixing on rileysalonresources.com, 8 of them high impact, across 64 checks. The most urgent: improve image delivery. 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
73C- #86,573 of 116,487 reviewed websitesbeats 22%
- #54,795 of 66,776 online storesbeats 15%
- #51,381 of 60,929 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
6.8 s · 2.3 MB9 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.8 s faster on a phone.
Use efficient cache lifetimes
5.2 s · 1.8 MB16 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
200 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.
1 third-party service on the page
1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 11 ms of main-thread time.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 37 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “KR_NP_S1”.
Time to Interactive: 9.0 s
9.0 sThe page becomes fully interactive after 9.0 s. Good is under 3.8 s.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images 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.
3 checks passed
Cumulative Layout Shift: 0.062
0.062The layout barely moves while loading (CLS 0.062, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
2 images over 500 KB
2 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
2.0 MB8 images are downloaded at several times the size a phone draws them, for example uP7RajiOMWFtjGSKtFoFiAABX2tj0VQDbknusgYX.png at 1,290 px wide, shown at 153 px. Resized copies would save about 2.0 MB.
Page weight: 2.7 MB in 26 requests
2.7 MBYour homepage downloads 2.7 MB in 26 requests on a phone: images 2.6 MB (12), fonts 109 KiB (3) and scripts 36 KiB (7). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (1.6 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.
An image on the first screen is lazy-loaded
web-slideshow-v1-49f098093a314416aaa04c7904d8f80b477a4bcdba9 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 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
Blocked from indexing
Google's crawler is blocked from indexing this page.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
7 H1 headlines
There are 7 <h1> headlines (“Loading your workspace”, “The Riley family is growing again. The Riley fami…” and “Built on relationships. Back to what matters. Bui…”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (212 characters)
Your meta description is 212 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://rsrhub.com/sitemap.xml, so Google discovers your pages only by following links.
19 internal links, 0 external
The homepage links to 19 pages on rileysalonresources.com and 0 external pages.
3 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “Riley Salon Resources | Professional Salon Brands & Support”.
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.
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.
No llms.txt
There is no https://rsrhub.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
1 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.
Other pages
8 linked pages hidden from search
https://rsrhub.com/brands, https://rsrhub.com/customer-service, https://rsrhub.com/brands/actiiv, https://rsrhub.com/brands/alphaparf-milano, https://rsrhub.com/brands/lanza and https://rsrhub.com/brands/reuzel and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
8 pages without a meta description
https://rsrhub.com/brands, https://rsrhub.com/customer-service, https://rsrhub.com/brands/actiiv, https://rsrhub.com/brands/alphaparf-milano, https://rsrhub.com/brands/lanza and https://rsrhub.com/brands/reuzel and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages slow to respond
https://rsrhub.com/brands, https://rsrhub.com/customer-service, https://rsrhub.com/brands/actiiv, https://rsrhub.com/brands/alphaparf-milano, https://rsrhub.com/brands/lanza and https://rsrhub.com/brands/reuzel and 2 others took over 3 s to send their HTML from our server.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 9 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.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 137 words
The homepage has only about 137 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Register”.
1 call to action
The homepage has 1 call to action, for example “Register”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
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 rileysalonresources.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on rileysalonresources.com, including 7 speed issues, 7 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.