Programmable

Website review, no card needed

branwyn.com logo

branwyn.com website review

Visit site (opens in a new tab)Reviewed 6 November 202614 issues · 96 checks

This review found 14 issues worth fixing on branwyn.com, 2 of them high impact, across 96 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

Site score

96A

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
928 ms631 msMay 16Oct 31665 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026795 ms
May 23, 2026800 ms
May 30, 2026805 ms
Jun 6, 2026817 ms
Jun 13, 2026808 ms
Jun 20, 2026802 ms
Jun 27, 2026798 ms
Jul 4, 2026787 ms
Jul 11, 2026784 ms
Jul 18, 2026789 ms
Jul 25, 2026796 ms
Aug 1, 2026806 ms
Aug 8, 2026817 ms
Aug 15, 2026828 ms
Aug 22, 2026852 ms
Aug 29, 2026870 ms
Sep 5, 2026877 ms
Sep 12, 2026894 ms
Sep 19, 2026886 ms
Sep 26, 2026889 ms
Oct 3, 2026849 ms
Oct 10, 2026785 ms
Oct 17, 2026747 ms
Oct 24, 2026683 ms
Oct 31, 2026665 ms
Real-visitor tap response (INP)75th percentile, phones
172 ms123 msMay 16Oct 31166 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026129 ms
May 30, 2026131 ms
Jun 6, 2026137 ms
Jun 13, 2026138 ms
Jun 20, 2026139 ms
Jun 27, 2026138 ms
Jul 4, 2026135 ms
Jul 11, 2026136 ms
Jul 18, 2026137 ms
Jul 25, 2026137 ms
Aug 1, 2026139 ms
Aug 8, 2026144 ms
Aug 15, 2026146 ms
Aug 22, 2026149 ms
Aug 29, 2026154 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026154 ms
Sep 26, 2026154 ms
Oct 3, 2026155 ms
Oct 10, 2026158 ms
Oct 17, 2026162 ms
Oct 24, 2026163 ms
Oct 31, 2026166 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

branwyn.com (opens in a new tab)
Full-page screenshot of branwyn.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

branwyn.com does not allow embedding, so this is Google's rendering of the page.

Speed

3 to fix100

  • Render-blocking requests

    1.2 s

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

  • 2,295 HTML elements

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

  • Shopify adds 2 ms

    2 ms

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

  • Use efficient cache lifetimes

    242 KiB

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

  • Improve image delivery

    69 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Amazon Web Services, Shopify and jQuery CDN and others), adding 422 KiB and 16 ms of main-thread time.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    42 KiB

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

  • Minify CSS

    13 KiB

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

3 checks passed

  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 62 ms of it running JavaScript. That is comfortably low.

  • Server response: 16 ms

    16 ms

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

Core Web Vitals

1 to fix100

  • Tap response (INP) got 28% slower for real visitors

    +28%

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

13 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: 0.9 s

    0.9 s

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

  • Real-user INP: 153 ms

    153 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 656 ms

    656 ms

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

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

    -15%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 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.002

    0.002

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Speed Index: 1.6 s

    1.6 s

    Visually, the page fills in at 1.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.2 s

    1.2 s

    The page is fully interactive after 1.2 s.

Images and page weight

1 to fix97

  • An image on the first screen is lazy-loaded

    BRANWYN_PERFORMANCE_INNERWEAR_XL_BUSTY_BRA_HIPSTER_WARM_NUDE 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.6 g of CO₂ per visit

    0.56 g

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

3 checks passed

  • Page weight: 2.0 MB in 89 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 89 requests on a phone: images 897 KiB (34), scripts 847 KiB (44) and fonts 110 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9696

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed

  • Every image has alt text

    All 126 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “BRANWYN | Performance Innerwear: Sustainable Merino Bras & Underwear”.

  • Meta description is long (312 characters)

    Your meta description is 312 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 142 internal links, 5 external

    The homepage links to 142 pages on branwyn.com and 5 external pages.

6 checks passed

  • One H1 headline

    Your main headline reads: “Natural, sustainable seamless Merino wool bras, underwear, & leggings”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://branwyn.com/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,829 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (10 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95

  • 9 pages without an H1

    /products/seamless-merino-wool-essential-bralette, /products/essential-busty-bra-womens-seamless-merino-wool, /products/essential-supreme-bra-seamless-merino-wool, /products/womens-seamless-merino-wool-essential-hipster, /products/womens-seamless-merino-wool-essential-bikini and /products/essential-womens-seamless-merino-wool-boyshort-underwear and 3 others 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 56 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 9693

  • 25 small tap targets

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

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.

Security and trust

100

  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (branwyn.com).

  • Valid certificate (49 days left)

    The certificate from Let's Encrypt · YE2 verifies for branwyn.com and is valid for another 49 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://branwyn.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 45 links work

    All 45 links checked from your homepage (40 internal, 5 external) answered without errors; 2 did not answer within 5 s.

Domain and trust

  • No CAA record

    branwyn.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    branwyn.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed

  • Domain is 13 years old

    13 years

    branwyn.com was registered in Apr 2013 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Apr 2028

    branwyn.com is registered until Apr 2028.

Content and conversion

100

  • About 1,280 words of copy

    The homepage carries about 1,280 words of visible text.

7 checks passed

  • Clear next step on the first screen

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

  • 17 calls to action

    The homepage has 17 calls to action, for example “Learn More”, “SHOP” and “Start shopping”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 136 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Email authentication

90

  • Email authentication score: 90/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed

  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:_spf.google.com include:mailer.giftcardpro.app -all”.

  • DKIM signing found

    A DKIM key is published (selector “google”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Apps on your store

Your storefront loads 20 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Blockify Fraud Filter · Sc Easy Redirects · Corso · Planet Discounts Upsells · Sami Product Labels · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Gift Card Pro · Judge Me Reviews · Triplewhale · Gorgias Live Chat Helpdesk · Region Restrictions · Planetdataset App · Loop Returns · verifypass.com · nfcube.com · cloudfront.net · thegoodapi.com · ecocart.tools · riskified.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

  • It loads jQuery 3.2.1, older than 3.5 (which fixed known security holes).

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Hiring

Hiring
2 open roles
Job board
careers page
Careers page
branwyn.com/pages/careers (opens in a new tab)

Company

Headquarters
Bend

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 14 issues on branwyn.com, including 4 speed issues and 3 SEO issues. 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