Website review, no card needed

reuzel.com logo

reuzel.com website review

Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 77 checks

This review found 33 issues worth fixing on reuzel.com, 13 of them high impact, across 77 checks. The most urgent: page weight: 23.5 MB in 533 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

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.2 sMay 23Nov 71.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.4 s
Oct 31, 20261.3 s
Nov 7, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
172 ms143 msMay 23Nov 7169 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026146 ms
May 30, 2026146 ms
Jun 6, 2026147 ms
Jun 13, 2026150 ms
Jun 20, 2026151 ms
Jun 27, 2026153 ms
Jul 4, 2026153 ms
Jul 11, 2026151 ms
Jul 18, 2026149 ms
Jul 25, 2026147 ms
Aug 1, 2026147 ms
Aug 8, 2026148 ms
Aug 15, 2026153 ms
Aug 22, 2026154 ms
Aug 29, 2026155 ms
Sep 5, 2026155 ms
Sep 12, 2026155 ms
Sep 19, 2026155 ms
Sep 26, 2026157 ms
Oct 3, 2026157 ms
Oct 10, 2026155 ms
Oct 17, 2026155 ms
Oct 24, 2026160 ms
Oct 31, 2026163 ms
Nov 7, 2026169 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 reuzel.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. reuzel.com at 0.6 s0.6 s
  2. reuzel.com at 1.1 s1.1 s
  3. reuzel.com at 1.7 s1.7 s
  4. reuzel.com at 2.3 s2.3 s
  5. reuzel.com at 2.8 s2.8 s
  6. reuzel.com at 3.4 s3.4 s
  7. reuzel.com at 4.0 s4.0 s
  8. reuzel.com at 4.6 s4.6 s

Speed

8 to fix
  • Main-thread work: 7.8 s

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

  • 4,047 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hotjar, pickystory.com and heyamplify.com and others), adding 3.4 MB and 1.4 s of main-thread time.

  • Hotjar adds 396 ms

    396 ms

    Hotjar costs a phone 396 ms of main-thread work and 65 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.

  • pickystory.com adds 192 ms

    192 ms

    pickystory.com costs a phone 192 ms of main-thread work and 1.6 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.

  • heyamplify.com adds 182 ms

    182 ms

    heyamplify.com costs a phone 182 ms of main-thread work and 386 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.

  • rebuyengine.com adds 167 ms

    167 ms

    rebuyengine.com costs a phone 167 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.

  • Klaviyo adds 134 ms

    134 ms

    Klaviyo costs a phone 134 ms of main-thread work and 314 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.

  • Font display

    50 ms

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

  • 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: 10 ms

    10 ms

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

Core Web Vitals

3 to fix100
  • Speed Index: 13.4 s

    13.4 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

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

    +14%

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

8 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.3 s

    1.3 s

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

  • Real-user INP: 200 ms

    200 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 493 ms

    493 ms

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

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

    -24%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

6 to fix19
  • Page weight: 23.5 MB in 533 requests

    23.5 MB

    Your homepage downloads 23.5 MB in 533 requests on a phone: media 13.9 MB (5), images 4.3 MB (69) and scripts 3.5 MB (196). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    insta-image-3.jpg weighs 655 KiB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    773 KiB

    3 images are downloaded at several times the size a phone draws them, for example insta-image-3.jpg at 1,638 px wide, shown at 250 px. Resized copies would save about 773 KiB.

  • 12 images in older formats

    12 images (2.6 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.

  • An image on the first screen is lazy-loaded

    reuzel_veteransday_collection_3.webp 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 below the first screen load straight away

    3 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.7 g of CO₂ per visit

    6.67 g

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

Accessibility

8 to fixGoogle 7989
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 tap targets too small

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 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.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 72 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

3 to fixGoogle 8586
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Hair Pomade | Hair Styling Products for Men | Beard Products | REUZEL”.

  • 13 links crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • 139 internal links, 26 external

    The homepage links to 139 pages on reuzel.com and 26 external pages.

6 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Perfect your look with REUZEL's styling products for men. Shop incredible hair pomades, tonics, shampoos, conditioners,…”.

  • Canonical URL set

    The canonical URL is https://www.reuzel.com/.

  • Structured data in place

    Structured data found: 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://www.reuzel.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.reuzel.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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: 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,581 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • 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 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 22 small tap targets

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

  • 5 JavaScript errors while loading

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

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

    The homepage carries about 781 words of visible text.

4 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “SHOP”, “SHOP POMADE” and “Shop Styling”.

  • 15 short forms

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

  • Social proof on the page

    Social proof on the homepage: 32 testimonial or review blocks and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 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.

  • 45 other companies contacted

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

Apps your storefront loads

Redirects By Shopkit · Amplify Subscriptions · Yotpo Product Reviews · Loyalty Rewards And Referrals · Helium Customer Fields · Amplify Bundles Upsell · Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Subscriptions Pickystory · rebuyengine.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
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

Company

Headquarters
Denver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on reuzel.com, including 11 speed issues, 3 SEO 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