Website review, no card needed

2undranz.com logo

2undranz.com website review

Visit site (opens in a new tab)Reviewed 28 October 202630 issues · 74 checks

This review found 30 issues worth fixing on 2undranz.com, 10 of them high impact, across 74 checks. The most urgent: improve image delivery. 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 2undranz.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 2undranz.com at 1.0 s1.0 s
  2. 2undranz.com at 2.1 s2.1 s
  3. 2undranz.com at 3.1 s3.1 s
  4. 2undranz.com at 4.2 s4.2 s
  5. 2undranz.com at 5.2 s5.2 s
  6. 2undranz.com at 6.3 s6.3 s
  7. 2undranz.com at 7.3 s7.3 s
  8. 2undranz.com at 8.3 s8.3 s

Speed

9 to fix61
  • Improve image delivery

    1.4 s · 694 KiB

    11 images could be 694 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Reduce unused JavaScript

    1.5 s · 474 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and Shopify and others), adding 4.6 MB and 647 ms of main-thread time.

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Shopify adds 116 ms

    116 ms

    Shopify costs a phone 116 ms of main-thread work and 3.9 MB 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

    390 ms · 51 KiB

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

  • Main-thread work: 3.8 s

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

  • Render-blocking requests

    350 ms

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

  • Google Tag Manager adds 212 ms

    212 ms

    Google Tag Manager costs a phone 212 ms of main-thread work and 315 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.

  • Legacy JavaScript

    150 ms · 28 KiB

    Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 long tasks on the main thread

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

  • Use efficient cache lifetimes

    36 KiB

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

  • Minify JavaScript

    16 KiB

    16 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Duplicated JavaScript

    7 KiB

    7 KiB JavaScript is shipped twice across bundles.

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

5 to fix65
  • Largest Contentful Paint: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Swing Shift 6" Boxer Brief - 3 Pack Boxset - Black/Grey/Nav…”.

  • Time to Interactive: 15.7 s

    15.7 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • 5 images without width and height

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

2 checks passed
  • Total Blocking Time: 132 ms

    132 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

3 to fix53
  • Page weight: 7.2 MB in 460 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 460 requests on a phone: media 3.0 MB (1), scripts 1.6 MB (170) and other files 1.3 MB (231). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    5.jpg 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).

  • 3 images far larger than shown

    440 KiB

    3 images are downloaded at several times the size a phone draws them, for example Swing_Shift.jpg at 2,646 px wide, shown at 350 px. Resized copies would save about 440 KiB.

  • About 2.0 g of CO₂ per visit

    2.03 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9295
  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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 (3 elements)

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

1 to fixGoogle 8598
  • 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.

  • 69 internal links, 7 external

    The homepage links to 69 pages on 2undranz.com and 7 external pages.

8 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “EXCLUSIVE RETAILER Premium men’s underwear featuring the Joey Pouch®. No chafe, no ride-up, all-day comfort. Shop 2UNDR…”.

  • One H1 headline

    Your main headline reads: “2UNDR”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “2UNDR Australia & New Zealand | Premium Men’s Underwear”.

  • Canonical URL set

    The canonical URL is https://2undranz.com/.

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    46%

    The HTML your server sends has 432 of the 933 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

  • Organization data: 6 of 6 facts

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

  • llms.txt published

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://2undranz.com/pages/reviews is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://2undranz.com/collections/new-arrivals/products/swing-shift-boxer-brief-3-pack-black-grey-navy, whose canonical is https://2undranz.com/products/swing-shift-boxer-brief-3-pack-black-grey-navy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://2undranz.com/pages/built-for-bigger-guys has 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 31 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 13 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

  • About 933 words of copy

    The homepage carries about 933 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Sign Up”, “LEARN MORE” and “Shop”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Risk reducer mentioned

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

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

  • 19 cookies set on arrival

    19

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

  • 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 2undranz.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on 2undranz.com, including 14 speed issues, 1 SEO issue and 2 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