Website review, no card needed

hunkmenswear.com logo

hunkmenswear.com website review

Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 83 checks

This review found 25 issues worth fixing on hunkmenswear.com, 8 of them high impact, across 83 checks. The most urgent: main-thread work: 7.7 s. 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
1.7 s1.4 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
197 ms110 msMay 16Oct 31139 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026121 ms
May 23, 2026120 ms
May 30, 2026121 ms
Jun 6, 2026129 ms
Jun 13, 2026139 ms
Jun 20, 2026154 ms
Jun 27, 2026163 ms
Jul 4, 2026170 ms
Jul 11, 2026169 ms
Jul 18, 2026166 ms
Jul 25, 2026167 ms
Aug 1, 2026171 ms
Aug 8, 2026171 ms
Aug 15, 2026178 ms
Aug 22, 2026180 ms
Aug 29, 2026186 ms
Sep 5, 2026187 ms
Sep 12, 2026183 ms
Sep 19, 2026174 ms
Sep 26, 2026165 ms
Oct 3, 2026162 ms
Oct 10, 2026154 ms
Oct 17, 2026153 ms
Oct 24, 2026146 ms
Oct 31, 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 hunkmenswear.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hunkmenswear.com at 0.5 s0.5 s
  2. hunkmenswear.com at 1.0 s1.0 s
  3. hunkmenswear.com at 1.4 s1.4 s
  4. hunkmenswear.com at 1.9 s1.9 s
  5. hunkmenswear.com at 2.4 s2.4 s
  6. hunkmenswear.com at 2.9 s2.9 s
  7. hunkmenswear.com at 3.4 s3.4 s
  8. hunkmenswear.com at 3.9 s3.9 s

Speed

11 to fix80
  • Main-thread work: 7.7 s

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

  • 5,312 HTML elements

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

  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80. 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 (alia-prod.com, Shopify and Yotpo and others), adding 2.2 MB and 663 ms of main-thread time.

  • Use efficient cache lifetimes

    588 KiB

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

  • Render-blocking requests

    450 ms

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

  • Improve image delivery

    150 ms · 295 KiB

    14 images could be 295 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused JavaScript

    409 KiB

    About 409 KiB of JavaScript is downloaded but never used on this page.

  • Shopify adds 189 ms

    189 ms

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

  • Yotpo adds 173 ms

    173 ms

    Yotpo costs a phone 173 ms of main-thread work and 507 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.

  • Soundest adds 0 ms

    0 ms

    Soundest costs a phone 0 ms of main-thread work and 394 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

    150 ms · 107 KiB

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

  • Font display

    200 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    18 KiB

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

  • Minify JavaScript

    8 KiB

    8 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: 8 ms

    8 ms

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

Core Web Vitals

2 to fix100
  • Time to Interactive: 20.4 s

    20.4 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

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

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

    +18%

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

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-31, 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).

10 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.2 s

    1.2 s

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

  • Real-user INP: 121 ms

    121 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 584 ms

    584 ms

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

  • Total Blocking Time: 195 ms

    195 ms

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

  • Speed Index: 3.2 s

    3.2 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 4.3 MB in 401 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 401 requests on a phone: scripts 1.3 MB (141), other files 1.2 MB (178) and images 1.0 MB (41). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    HUNK.HYBRIDSHORT_banner_mobile_pedro.webp weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (1.5 MB) are 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 1.2 g of CO₂ per visit

    1.21 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.2 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 9495
  • 39 text elements with low contrast

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

  • 5 tap targets too small

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (10 elements)

    Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor 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. (2 elements).

2 checks passed
  • Every image has alt text

    All 382 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

Google 100100
  • 118 internal links, 10 external

    The homepage links to 118 pages on hunkmenswear.com and 10 external pages.

8 checks passed
  • Meta description: 117 characters

    Your meta description is 117 characters: “Underwear, swimwear, and gear for men who show up bold. Elevated fit, standout colors, and confidence in every piece.”.

  • One H1 headline

    Your main headline reads: “HUNK Menswear”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “HUNK: Fit That Shows. Color That Speaks. Menswear Reimagined”.

  • Canonical URL set

    The canonical URL is https://hunkmenswear.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://hunkmenswear.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 (1,318 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 6 pages without a meta description

    https://hunkmenswear.com/collections/boxer-briefs, https://hunkmenswear.com/collections/swim-sport-briefs, https://hunkmenswear.com/collections/swim-shorts, https://hunkmenswear.com/collections/hybrid-shorts, https://hunkmenswear.com/collections/tank-tops and https://hunkmenswear.com/collections/hats 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 51 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

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.soundestlink.com/customFonts/css/6a6b6692114be9e5b256bf19' from origin 'http…”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

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

    The homepage carries about 798 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “SHOP NOW”, “SHOP” and “Subscribe”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and a star rating.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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.

  • 23 cookies set on arrival

    23

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

  • 36 other companies contacted

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

Apps your storefront loads

Triplewhale · Yotpo Product Reviews · Omnisend · Loop Returns · Unlimited Bundles

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 25 issues on hunkmenswear.com, including 13 speed issues 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