Website review, no card needed

montedesign.net logo

montedesign.net website review

Visit site (opens in a new tab)Reviewed 10 November 202643 issues · 88 checks

This review found 43 issues worth fixing on montedesign.net, 16 of them high impact, across 88 checks. The most urgent: page weight: 26.5 MB in 238 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
4.3 s1.9 sMay 23Nov 72.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.8 s
May 30, 20263.3 s
Jun 6, 20263.6 s
Jun 13, 20264.0 s
Jun 20, 20264.1 s
Jun 27, 20264.0 s
Jul 4, 20264.0 s
Jul 11, 20263.8 s
Jul 18, 20263.5 s
Jul 25, 20263.4 s
Aug 1, 20263.2 s
Aug 8, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.4 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.1 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.4 s
Oct 24, 20262.2 s
Oct 31, 20262.2 s
Nov 7, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
193 ms130 msMay 23Nov 7137 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026139 ms
May 30, 2026153 ms
Jun 6, 2026161 ms
Jun 13, 2026174 ms
Jun 20, 2026185 ms
Jun 27, 2026185 ms
Jul 4, 2026186 ms
Jul 11, 2026179 ms
Jul 18, 2026165 ms
Jul 25, 2026170 ms
Aug 1, 2026162 ms
Aug 8, 2026162 ms
Aug 15, 2026172 ms
Aug 22, 2026175 ms
Aug 29, 2026177 ms
Sep 5, 2026179 ms
Sep 12, 2026176 ms
Sep 19, 2026171 ms
Sep 26, 2026171 ms
Oct 3, 2026169 ms
Oct 10, 2026160 ms
Oct 17, 2026145 ms
Oct 24, 2026142 ms
Oct 31, 2026137 ms
Nov 7, 2026137 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 montedesign.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix55
  • Reduce unused JavaScript

    1.7 s · 445 KiB

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

  • Render-blocking requests

    1.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Lucky Orange, Klaviyo and TikTok and others), adding 24.7 MB and 876 ms of main-thread time.

  • Shopify adds 36 ms

    36 ms

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

  • Improve image delivery

    500 ms · 1.3 MB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    320 ms · 119 KiB

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

  • Use efficient cache lifetimes

    300 ms · 90 KiB

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

  • Main-thread work: 2.8 s

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

  • Klaviyo adds 139 ms

    139 ms

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

  • 6 long tasks on the main thread

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

  • Minify CSS

    190 ms · 17 KiB

    17 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    50 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 50 ms faster on a phone.

  • Font display

    50 ms

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

  • Minify JavaScript

    30 ms · 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: 6 ms

    6 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.38

    0.38

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

  • Largest Contentful Paint: 22.8 s

    22.8 s

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

  • Time to Interactive: 26.5 s

    26.5 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • 40 images without width and height

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

  • Total Blocking Time: 339 ms

    339 ms

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

  • Tap response (INP) held steady for real visitors

    -6%

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 136 ms

    136 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 555 ms

    555 ms

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

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

    -28%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.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

5 to fix28
  • Page weight: 26.5 MB in 238 requests

    26.5 MB

    Your homepage downloads 26.5 MB in 238 requests on a phone: media 20.6 MB (6), images 3.6 MB (57) and scripts 1.3 MB (88). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.

  • 4 images in older formats

    4 images (8.4 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.

  • 3 images below the first screen load straight away

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

  • 4 images far larger than shown

    251 KiB

    4 images are downloaded at several times the size a phone draws them, for example monte-sofa-sectionals-home-1.jpg at 1,200 px wide, shown at 354 px. Resized copies would save about 251 KiB.

  • About 7.5 g of CO₂ per visit

    7.50 g

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

Accessibility

9 to fixGoogle 7886
  • 1 button without a name

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

  • 11 text elements with low contrast

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

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 43 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: 43 passed and 9 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 8587
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Modern Luxurious Furniture for Your Nursery and Home by Monte Design”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

  • 299 internal links, 29 external

    The homepage links to 299 pages on montedesign.net and 29 external pages.

6 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “Shop beautiful, hand-crafted & timeless furniture for your modern family. Canadian made. GREENGUARD Gold Certified”.

  • One H1 headline

    Your main headline reads: “Handcrafted furniture made exclusively for you.”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://montedesign.com/collections/daybeds has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://montedesign.com/collections/in-stock, https://montedesign.com/collections/daybeds and https://montedesign.com/collections/beds-accessories 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 69 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 9285
  • 6 small tap targets

    6 of 18 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”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 351 words of copy

    The homepage carries about 351 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE PILLOWBACK” and “SHOP ALL BEDS →”.

  • 59 calls to action

    The homepage has 59 calls to action, for example “Shop all beds”, “Shop all daybeds” and “Shop all accessories”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity, LinkedIn Insight and TikTok Pixel.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 25 cookies set on arrival

    25

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

  • 37 other companies contacted

    Loading the homepage contacts 37 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 montedesign.net, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Instafeed · Microsoft Clarity · Klaviyo Email Marketing Sms · Selleasy · cloudfront.net · gorgias.chat · yotpo.com · 9gtb.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 | 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 43 issues on montedesign.net, including 18 speed issues, 3 SEO issues and 1 conversion gap. 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