Website review, no card needed

byvorda.com logo

byvorda.com website review

Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 79 checks

This review found 31 issues worth fixing on byvorda.com, 5 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.3 sMay 23Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
168 ms123 msMay 23Nov 7139 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026131 ms
May 30, 2026129 ms
Jun 6, 2026132 ms
Jun 13, 2026130 ms
Jun 20, 2026128 ms
Jun 27, 2026143 ms
Jul 4, 2026138 ms
Jul 11, 2026153 ms
Jul 18, 2026163 ms
Jul 25, 2026156 ms
Aug 1, 2026159 ms
Aug 8, 2026163 ms
Aug 15, 2026162 ms
Aug 22, 2026158 ms
Aug 29, 2026161 ms
Sep 5, 2026157 ms
Sep 12, 2026154 ms
Sep 19, 2026154 ms
Sep 26, 2026146 ms
Oct 3, 2026143 ms
Oct 10, 2026139 ms
Oct 17, 2026138 ms
Oct 24, 2026141 ms
Oct 31, 2026140 ms
Nov 7, 2026139 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

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

How it loaded on a phone

  1. byvorda.com at 0.4 s0.4 s
  2. byvorda.com at 0.8 s0.8 s
  3. byvorda.com at 1.1 s1.1 s
  4. byvorda.com at 1.5 s1.5 s
  5. byvorda.com at 1.9 s1.9 s
  6. byvorda.com at 2.3 s2.3 s
  7. byvorda.com at 2.6 s2.6 s
  8. byvorda.com at 3.0 s3.0 s

Speed

8 to fix71
  • Render-blocking requests

    1.1 s

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • 3,359 HTML elements

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

  • Mobile performance score: 71

    71/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 920 KiB and 831 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 325 KiB

    About 325 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Shopify adds 355 ms

    355 ms

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

  • Reduce unused CSS

    300 ms · 69 KiB

    About 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 3.4 s

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

  • 7 long tasks on the main thread

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

  • Use efficient cache lifetimes

    200 ms · 36 KiB

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 25 ms

    25 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 11.9 s

    11.9 s

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Total Blocking Time: 497 ms

    497 ms

    Scripts block taps and scrolling for 497 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 3.9 s

    3.9 s

    Visually, the page fills in at 3.9 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.

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 131 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 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.5 s

    1.5 s

    Real visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 145 ms

    145 ms

    Real visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 440 ms

    440 ms

    Real visitors wait 440 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 234 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 234 requests on a phone: scripts 1.1 MB (74), other files 763 KiB (110) and images 581 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (67 KiB) is 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.

  • About 0.8 g of CO₂ per visit

    0.78 g

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

2 checks passed
  • 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

4 to fixGoogle 9595
  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

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

  • 35 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h6, h1 → h3 and h2 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9279
  • Title is short (29 characters)

    Your title is only 29 characters: “Vorda - Your Botanical Ritual”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 35 links crawlers can't follow

    35 links have no real href, so search engines can't follow them.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 5 H1 headlines

    There are 5 <h1> headlines (“”, “Martian in African Rosewood” and “Martian in African Rosewood”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 209 internal links, 4 external

    The homepage links to 209 pages on byvorda.com and 4 external pages.

4 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Scent Your Space Naturally. Pure Essential Oils. Natural Wood Diffusers. Elegant Lamp Diffusers. Free Shipping on U.S. …”.

  • Canonical URL set

    The canonical URL is https://byvorda.com/.

  • 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://byvorda.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 (1,878 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 5 pages without a meta description

    https://byvorda.com/collections/fall-must-haves, https://byvorda.com/collections/gifts-75-100, https://byvorda.com/collections/gifts-50-75, https://byvorda.com/collections/gifts-30-50 and https://byvorda.com/collections/gifts-under-30 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 7791
  • 8 small tap targets

    8 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 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 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 31 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 11-field form

    Your longest form asks for 11 fields (6 required). Every extra field lowers completion.

  • 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 500 words of copy

    The homepage carries about 500 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE EDITION”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop All”, “Shop by Price” and “Shop by Benefit”.

  • Analytics in place

    Analytics detected: Google Analytics, HubSpot and PostHog.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 3 mores (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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 3 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.

  • 30 other companies contacted

    Loading the homepage contacts 30 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 byvorda.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Yotpo Loyalty Rewards · Yotpo Product Reviews · Klaviyo Email Marketing Sms · Aftersell · Giftnote App · Rep Connector · Biscuits Bundles · Upcart · rechargecdn.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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | PostHog
Hosting
Shopify

Company

Headquarters
Irvine

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on byvorda.com, including 13 speed issues, 5 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

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