Website review, no card needed

monsroyale.com logo

monsroyale.com website review

Visit site (opens in a new tab)Reviewed 5 November 202623 issues · 80 checks

This review found 23 issues worth fixing on monsroyale.com, 11 of them high impact, across 80 checks. The most urgent: page weight: 25.2 MB in 274 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
1.2 s756 msMay 16Oct 31810 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.2 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 2026978 ms
Oct 10, 2026930 ms
Oct 17, 2026893 ms
Oct 24, 2026851 ms
Oct 31, 2026810 ms
Real-visitor tap response (INP)75th percentile, phones
135 ms72 msMay 16Oct 3179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026127 ms
May 23, 2026128 ms
May 30, 2026126 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026119 ms
Jun 27, 2026113 ms
Jul 4, 2026112 ms
Jul 11, 2026100 ms
Jul 18, 202696 ms
Jul 25, 202690 ms
Aug 1, 202690 ms
Aug 8, 202689 ms
Aug 15, 202689 ms
Aug 22, 202694 ms
Aug 29, 202690 ms
Sep 5, 202697 ms
Sep 12, 202696 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 202688 ms
Oct 10, 202686 ms
Oct 17, 202681 ms
Oct 24, 202679 ms
Oct 31, 202679 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 monsroyale.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. monsroyale.com at 0.4 s0.4 s
  2. monsroyale.com at 0.9 s0.9 s
  3. monsroyale.com at 1.3 s1.3 s
  4. monsroyale.com at 1.7 s1.7 s
  5. monsroyale.com at 2.1 s2.1 s
  6. monsroyale.com at 2.6 s2.6 s
  7. monsroyale.com at 3.0 s3.0 s
  8. monsroyale.com at 3.4 s3.4 s

Speed

6 to fix40
  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Clarity and 9gtb.com and others), adding 562 KiB and 501 ms of main-thread time.

  • 14 long tasks on the main thread

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

  • Klaviyo adds 264 ms

    264 ms

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

  • 1,693 HTML elements

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

  • Reduce unused JavaScript

    150 ms · 113 KiB

    About 113 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.

  • Use efficient cache lifetimes

    150 ms · 71 KiB

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

  • Legacy JavaScript

    150 ms · 19 KiB

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

  • Reduce unused CSS

    150 ms · 11 KiB

    About 11 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.

  • Improve image delivery

    132 KiB

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

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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 69.6 s

    69.6 s

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

  • Time to Interactive: 71.5 s

    71.5 s

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

  • Speed Index: 10.6 s

    10.6 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

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.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: 94 ms

    94 ms

    Real visitors wait 94 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: 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: 534 ms

    534 ms

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

  • Tap response (INP) got 38% faster for real visitors

    -38%

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

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

    -21%

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

2 to fix55
  • Page weight: 25.2 MB in 274 requests

    25.2 MB

    Your homepage downloads 25.2 MB in 274 requests on a phone: images 23.5 MB (72), other files 749 KiB (94) and scripts 716 KiB (80). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 22.8 MB together. On a phone connection a single image that size takes seconds.

  • About 7.1 g of CO₂ per visit

    7.14 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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
  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

  • 9 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • Meta description is long (269 characters)

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

  • 11 links with vague text

    11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 290 internal links, 10 external

    The homepage links to 290 pages on monsroyale.com and 10 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Merino Wool Base Layer: The Art of the Base Layer”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Merino Wool Apparel | Mons Royale USA”.

  • Canonical URL set

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

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

  • 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 9684
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=ba8d5ce1-1077-4762-8532-a1398b4651ca&referrer=&landingpage=https%3A%2F%2Fmonsroyale.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 613 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 MEN” and “SHOP WOMEN”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “GET IN TOUCH”, “LEARN MORE” and “Shop Men”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

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, Klaviyo and Meta Pixel 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.

  • 18 cookies set on arrival

    18

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

  • 42 other companies contacted

    Loading the homepage contacts 42 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 monsroyale.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

Awin Affiliate Marketing · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Sortd Merchandiser · Hreflang Tags · Wingify · gorgias.chat · 9gtb.com · cloudfront.net · getredo.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
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Wanaka

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on monsroyale.com, including 11 speed issues, 2 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