Website review, no card needed

mbaer.com logo

mbaer.com website review

Visit site (opens in a new tab)Reviewed 5 November 202628 issues · 67 checks

This review found 28 issues worth fixing on mbaer.com, 7 of them high impact, across 67 checks. The most urgent: [role="img"] and [role="image"] elements must have alternative text (18 elements). 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 mbaer.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix76
  • Mobile performance score: 76

    76/100

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

  • Use efficient cache lifetimes

    100 ms · 495 KiB

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

  • Render-blocking requests

    500 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (builderservices.io, WebsiteBuilder.com and WordPress Site Stats and others), adding 1.1 MB and 272 ms of main-thread time.

  • Improve image delivery

    300 ms · 67 KiB

    1 image could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • builderservices.io adds 269 ms

    269 ms

    builderservices.io costs a phone 269 ms of main-thread work and 951 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.

  • Reduce unused JavaScript

    287 KiB

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

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    62 KiB

    About 62 KiB of CSS is downloaded but never applied on this page.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 113 ms

    113 ms

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

Core Web Vitals

5 to fix73
  • Largest Contentful Paint: 5.6 s

    5.6 s

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

  • Time to Interactive: 7.3 s

    7.3 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • 2 images without width and height

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

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 49 ms

    49 ms

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

Images and page weight

100
  • 1 image in older formats

    1 image (121 KiB) is 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.

  • 1 image below the first screen load straight away

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

  • About 0.3 g of CO₂ per visit

    0.35 g

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

2 checks passed
  • Page weight: 1.2 MB in 28 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 28 requests on a phone: scripts 511 KiB (7), images 499 KiB (5) and fonts 114 KiB (3). That is a lean page.

  • 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 9190
  • [role="img"] and [role="image"] elements must have alternative text (18 elements)

    [role="img"] and [role="image"] elements must have alternative text: 18 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (6 elements)

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

  • 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 (44 elements)

    All page content should be contained by landmarks: 44 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.

  • 6 links without text

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

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

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

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

4 to fixGoogle 8576
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No social preview image

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

  • No favicon declared

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

  • 27 internal links, 4 external

    The homepage links to 27 pages on mbaer.com and 4 external pages.

5 checks passed
  • Title: 32 characters

    Your title is a healthy 32 characters: “Home - Marjorie Baer Accessories”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://cdn.attracta.com/sitemap/1012631.xml.gz.

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.

  • No llms.txt

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

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

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 362 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

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.

  • 9 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Newfold Digital

Company

Headquarters
South San Francisco

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 mbaer.com, including 12 speed issues, 4 SEO issues and 5 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