Website review, no card needed

mulroom.com logo

mulroom.com website review

Visit site (opens in a new tab)Reviewed 8 November 202628 issues · 75 checks

This review found 28 issues worth fixing on mulroom.com, 5 of them high impact, across 75 checks. The most urgent: render-blocking 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

Full-page screenshot of mulroom.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix77
  • Render-blocking requests

    1.3 s

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

  • 5,177 HTML elements

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

  • Mobile performance score: 77

    77/100

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

  • Reduce unused JavaScript

    408 KiB

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

  • Reduce unused CSS

    300 ms · 62 KiB

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

  • Main-thread work: 2.1 s

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

  • Shopify adds 102 ms

    102 ms

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

  • Google CDN adds 107 ms

    107 ms

    Google CDN costs a phone 107 ms of main-thread work and 298 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 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Shopify and Cloudflare CDN and others), adding 975 KiB and 231 ms of main-thread time.

  • Improve image delivery

    100 ms · 43 KiB

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

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    36 KiB

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

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

    11 ms

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

Core Web Vitals

5 to fix76
  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ori chair in pale wood beside a dining table in a white bri…”.

  • Time to Interactive: 7.3 s

    7.3 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 20 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

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

    79 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 387 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 387 requests on a phone: scripts 1.0 MB (118), other files 1.0 MB (165) and images 732 KiB (73). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9093
  • 7 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 44 links without text

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

  • Hidden but focusable

    20 elements hidden from screen readers can still receive keyboard focus.

  • 8 form fields without a label

    8 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 209 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. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • Meta description is long (165 characters)

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

  • 256 internal links, 2 external

    The homepage links to 256 pages on mulroom.com and 2 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Shopthe Source.”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Modern Furniture Thailand | Mulroom”.

  • Canonical URL set

    The canonical URL is https://mulroom.com/en.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://mulroom.com/en/collections/4-seater-sofa is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mulroom.com/en/collections/%E0%B9%80%E0%B8%94%E0%B8%A2%E0%B9%8C%E0%B9%80%E0%B8%9A%E0%B8%94, whose canonical is https://mulroom.com/en/collections/%e0%b9%80%e0%b8%94%e0%b8%a2%e0%b9%8c%e0%b9%80%e0%b8%9a%e0%b8%94. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages slow to respond

    https://mulroom.com/en/collections/apartment-sofa and https://mulroom.com/en/collections/%E0%B9%80%E0%B8%94%E0%B8%A2%E0%B9%8C%E0%B9%80%E0%B8%9A%E0%B8%94 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 109 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.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 10 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 449 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop the latest ↗” and “Get my 20% off ↗”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop the latest ↗”, “Need help choosing? Talk to Mulroom” and “Custom order”.

  • 5 short forms

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 13 cookies set on arrival

    13

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

  • 21 other companies contacted

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

Apps your storefront loads

Fontify · Google Youtube · Inbox · Descriptions Studio · Judge Me Reviews · Tabs Studio · Glo Color Swatch · Wellmade Content Snippets · Forms

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on mulroom.com, including 13 speed issues, 1 SEO issue and 3 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