Website review, no card needed
rclstcloud.com website review
Visit site (opens in a new tab)Reviewed 8 November 202624 issues · 60 checks
This review found 24 issues worth fixing on rclstcloud.com, 4 of them high impact, across 60 checks. The most urgent: render-blocking requests. 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
84B- #17,285 of 94,994 reviewed websitesbeats 77%
- #10,733 of 51,117 online storesbeats 73%
- #10,397 of 46,236 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, nice-team.net and cart-bot.net and others), adding 1.2 MB and 556 ms of main-thread time.
Reduce unused JavaScript
650 KiBAbout 650 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 388 ms
388 msShopify costs a phone 388 ms of main-thread work and 936 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 808 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Minify JavaScript
72 KiB72 KiB could be saved by minifying JavaScript.
Reduce unused CSS
51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
6 KiB5 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
2 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94. That is in Google's “good” band (90 and up).
Server response: 37 ms
37 msYour server sent the HTML in 37 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.2 s
13.2 sThe page becomes fully interactive after 13.2 s. Good is under 3.8 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 217 ms
217 msScripts block taps and scrolling for 217 ms in total while the page loads. Good is under 200 ms.
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
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Really Cool Living - St. Cloud”.
Speed Index: 2.0 s
2.0 sVisually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 2.3 MB in 226 requests
2.3 MBYour homepage downloads 2.3 MB in 226 requests on a phone: scripts 1.2 MB (58), other files 885 KiB (152) and stylesheets 111 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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 (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
2 H1 headlines
There are 2 <h1> headlines (“Really Cool Living - St. Cloud” and “Opening soon!”). One clear main headline is easier for people and search engines.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.rclstcloud.com/cdn/shop/files/Title_532e2792-8544…”.
No XML sitemap
No XML sitemap at https://www.rclstcloud.com/sitemap.xml, so Google discovers your pages only by following links.
Only 1 internal link
The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.
4 checks passed
Title: 30 characters
Your title is a healthy 30 characters: “Really Cool Living - St. Cloud”.
Canonical URL set
The canonical URL is https://www.rclstcloud.com/password.
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 llms.txt
There is no https://www.rclstcloud.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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Other pages
1 internal page checked
We fetched 1 page linked from your homepage and read each the way a search engine does.
1 checks passed
Linked pages load
All 1 page we checked loaded without an error.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
2 checks passed
Tap targets are thumb-sized
7 of 7 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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 17 words
The homepage has only about 17 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 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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Subscribe”.
1 call to action
The homepage has 1 call to action, for example “Subscribe”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager 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.
11 cookies set on arrival
11Opening the homepage sets 11 cookies, 1 of them by other companies (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.
20 other companies contacted
Loading the homepage contacts 20 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 rclstcloud.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Cartbot · Bundler Bundles App · Selecty · Aftersell · Thank You Page · Montage Protection Plans · Ecomsend · nice-team.net · tagembed.com · robinpro.gallery · hubapi.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
- 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 24 issues on rclstcloud.com, including 8 speed issues, 5 SEO issues and 6 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.