Website review, no card needed

rlbycl.com logo

rlbycl.com website review

Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 73 checks

This review found 36 issues worth fixing on rlbycl.com, 12 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of rlbycl.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rlbycl.com at 0.9 s0.9 s
  2. rlbycl.com at 1.8 s1.8 s
  3. rlbycl.com at 2.7 s2.7 s
  4. rlbycl.com at 3.6 s3.6 s
  5. rlbycl.com at 4.5 s4.5 s
  6. rlbycl.com at 5.4 s5.4 s
  7. rlbycl.com at 6.3 s6.3 s
  8. rlbycl.com at 7.2 s7.2 s

Speed

8 to fix57
  • Reduce unused JavaScript

    1.2 s · 521 KiB

    About 521 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 632 KiB

    37 files are served with short cache lifetimes, so returning visitors download them again (632 KiB).

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Yotpo, Shopify and getclipara.com and others), adding 1.3 MB and 979 ms of main-thread time.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    650 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Shopify adds 222 ms

    222 ms

    Shopify costs a phone 222 ms of main-thread work and 440 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.

  • 1,688 HTML elements

    The page has 1,688 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    243 KiB

    5 images could be 243 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    83 KiB

    About 83 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    7 KiB

    7 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.

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix68
  • First Contentful Paint: 6.1 s

    6.1 s

    The first text or image appears after 6.1 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 16.5 s

    16.5 s

    The page becomes fully interactive after 16.5 s. Good is under 3.8 s.

  • Speed Index: 9.5 s

    9.5 s

    Visually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 6.1 s

    6.1 s

    Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to ensure you get the best experi…”. Most of its time is element render delay (3.0 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
  • Total Blocking Time: 188 ms

    188 ms

    Scripts block the page for only 188 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.015

    0.015

    The layout barely moves while loading (CLS 0.015, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.9 MB in 303 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 303 requests on a phone: scripts 1.5 MB (145), images 1.1 MB (27) and other files 867 KiB (102). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.12 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9394
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • 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 (“<img class="" src="//www.rlbycl.com/cdn/shop/file…” and “<img class="" src="//www.rlbycl.com/cdn/shop/file…”). One clear main headline is easier for people and search engines.

  • 83 internal links, 6 external

    The homepage links to 83 pages on rlbycl.com and 6 external pages.

6 checks passed
  • Meta description: 108 characters

    Your meta description is 108 characters: “Rachel Lynn x Corri Lynn jewelry is handcrafted in The USA using crystal, high-quality metals and materials.”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Shop Rachel Lynn x Corri Lynn Jewelry”.

  • Canonical URL set

    The canonical URL is https://www.rlbycl.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.rlbycl.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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 (329 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.rlbycl.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

7 to fix25
  • 1 linked page is broken

    Your homepage links to https://www.rlbycl.com/a/gc/gift-card, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://www.rlbycl.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://www.rlbycl.com/products/rlxcl-founders-dinner-ticket declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 1 linked page hidden from search

    https://www.rlbycl.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://www.rlbycl.com/products/rlxcl-founders-dinner-ticket all use the title “Shop Rachel Lynn x Corri Lynn Jewelry”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.rlbycl.com/collections/siriano-september-2025-nyfw-copy, https://www.rlbycl.com/pages/2026-christiano-nyfw-lookbook, https://www.rlbycl.com/collections/happy-birthday-micro, https://www.rlbycl.com/collections/happy-birthday, https://www.rlbycl.com/collections/bracelets and https://www.rlbycl.com/collections/necklaces and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.rlbycl.com/pages/rewards and https://www.rlbycl.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.

Best practices

2 to fixGoogle 7391
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://widget.getclipara.com/static/css/main.9300d31c.css' from origin 'https://www.rlbyc…”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    9 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • 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 200 words

    The homepage has only about 200 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SUBSCRIBE”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop By Collection”, “SHOP NOW” and “Contact Us”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before 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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 2 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.

  • 32 other companies contacted

    Loading the homepage contacts 32 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 rlbycl.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

Consentmo Gdpr · Clipara Shoppable Videos · Yotpo Loyalty Rewards · Inbox · Gdpr Backpack · Omnisend · cirkleinc.com · amazonaws.com · chimpstatic.com · esc-apps-cdn.com · useamp.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 36 issues on rlbycl.com, including 13 speed issues, 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25