Website review, no card needed

brandmoustache.com logo

brandmoustache.com website review

Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 63 checks

This review found 36 issues worth fixing on brandmoustache.com, 9 of them high impact, across 63 checks. The most urgent: documents must have <title> element to aid in navigation (1 element). 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.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. brandmoustache.com at 1.0 s1.0 s
  2. brandmoustache.com at 2.0 s2.0 s
  3. brandmoustache.com at 2.9 s2.9 s
  4. brandmoustache.com at 3.9 s3.9 s
  5. brandmoustache.com at 4.9 s4.9 s
  6. brandmoustache.com at 5.9 s5.9 s
  7. brandmoustache.com at 6.8 s6.8 s
  8. brandmoustache.com at 7.8 s7.8 s

Speed

2 to fix
  • 2 third-party services on the page

    2 third-party services load with your homepage (mpm3.com and youcangetwomen.com), adding 1.6 MB and 79 ms of main-thread time.

  • mpm3.com adds 73 ms

    73 ms

    mpm3.com costs a phone 73 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 130 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

1 to fix100
  • 32 images without width and height

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

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

1 checks passed
  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

3 to fix68
  • Page weight: 2.9 MB in 88 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 88 requests on a phone: images 2.7 MB (65), scripts 188 KiB (12) and stylesheets 40 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 20 images in older formats

    20 images (1.2 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.

  • 21 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.83 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

9 to fixGoogle 6583
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 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.

  • 16 images without alt text

    16 images have no alt text, which hurts accessibility and image search.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 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

8 to fixGoogle 7362
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (13 characters)

    Your title is only 13 characters: “米兰在线官网-米兰(中国)”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://brandmoustache.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at brandmoustache.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 43 internal links, 0 external

    The homepage links to 43 pages on brandmoustache.com and 0 external pages.

1 checks passed
  • Meta description: 90 characters

    Your meta description is 90 characters: “米兰在线官网以高效、稳定、易用为核心,为用户打造顺畅一致的在线访问体验。依托米兰在线官网,用户可以轻松进入目标页面,享受良好的兼容性与清爽的视觉效果,满足多种场景下的日常使用需求。”.

AI search readiness

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

  • No llms.txt

    There is no https://brandmoustache.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

3 to fix86
  • 8 pages share 3 titles

    / and https://brandmoustache.com/message.html all use the title “米兰在线官网-米兰(中国)”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://brandmoustache.com/view2-1.html, https://brandmoustache.com/list1.html, https://brandmoustache.com/list3.html, https://brandmoustache.com/list5.html, https://brandmoustache.com/list6.html and https://brandmoustache.com/list7.html and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://brandmoustache.com/view2-1.html, https://brandmoustache.com/list1.html, https://brandmoustache.com/list3.html, https://brandmoustache.com/list5.html, https://brandmoustache.com/list6.html and https://brandmoustache.com/list7.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://brandmoustache.com/view2-1.html, https://brandmoustache.com/list1.html, https://brandmoustache.com/list3.html, https://brandmoustache.com/list5.html, https://brandmoustache.com/list6.html and https://brandmoustache.com/list7.html and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 7385
  • 13 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 18 words

    The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 brandmoustache.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Yancy Limited

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on brandmoustache.com, including 3 speed issues, 8 SEO issues and 6 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