Website review, no card needed

maisonco.com logo

maisonco.com website review

Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 80 checks

This review found 26 issues worth fixing on maisonco.com, 10 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
2.7 s1.1 sJul 4Nov 71.3 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20262.5 s
Aug 22, 20262.1 s
Sep 19, 20261.9 s
Sep 26, 20261.7 s
Oct 3, 20261.5 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Nov 7, 20261.3 s

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 maisonco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maisonco.com at 0.5 s0.5 s
  2. maisonco.com at 0.9 s0.9 s
  3. maisonco.com at 1.4 s1.4 s
  4. maisonco.com at 1.9 s1.9 s
  5. maisonco.com at 2.4 s2.4 s
  6. maisonco.com at 2.8 s2.8 s
  7. maisonco.com at 3.3 s3.3 s
  8. maisonco.com at 3.8 s3.8 s

Speed

6 to fix74
  • Use efficient cache lifetimes

    50.0 s · 35.1 MB

    79 files are served with short cache lifetimes, so returning visitors download them again (35.1 MB).

  • Improve image delivery

    44.9 s · 11.3 MB

    74 images could be 11.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 44.9 s faster on a phone.

  • 1 third-party service on the page

    1 third-party service load with your homepage (laravel.cloud), adding 35.1 MB and 0 ms of main-thread time.

  • laravel.cloud adds 0 ms

    0 ms

    laravel.cloud costs a phone 0 ms of main-thread work and 35.1 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.

  • Mobile performance score: 74

    74/100

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

  • 2,601 HTML elements

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

  • Reduce unused JavaScript

    160 ms · 26 KiB

    About 26 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • Reduce unused CSS

    160 ms · 20 KiB

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 83 ms. During a long task the page ignores taps.

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 54.1 s

    54.1 s

    Your largest element takes 54.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to keep the site working and — with your per…”.

  • Time to Interactive: 54.4 s

    54.4 s

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

  • 103 images without width and height

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

10 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 CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 702 ms

    702 ms

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

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

    -38%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.5 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 33 ms

    33 ms

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

Images and page weight

6 to fix19
  • Page weight: 36.5 MB in 93 requests

    36.5 MB

    Your homepage downloads 36.5 MB in 93 requests on a phone: images 36.2 MB (85), fonts 244 KiB (5) and scripts 43 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 32.2 MB together. On a phone connection a single image that size takes seconds.

  • 25 images far larger than shown

    24.4 MB

    25 images are downloaded at several times the size a phone draws them, for example coral-gables-2Q5Om2FKJeQJdvbt.jpg at 4,000 px wide, shown at 342 px. Resized copies would save about 24.4 MB.

  • 40 images in older formats

    40 images (35.0 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.

  • 6 images below the first screen load straight away

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

  • An image on the first screen is lazy-loaded

    Ilk4IGAeedBAnZwN.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 10.4 g of CO₂ per visit

    10.36 g

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

Accessibility

3 to fixGoogle 9395
  • 5 text elements with low contrast

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

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 67 links without text

    67 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. (7 elements).

2 checks passed
  • Every image has alt text

    All 186 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is short (12 characters)

    Your title is only 12 characters: “Maison & Co.”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 692 internal links, 4 external

    The homepage links to 692 pages on maisonco.com and 4 external pages.

5 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Curated luxury appliances, plumbing, lighting, and hardware. Serving Florida's most discerning homeowners, designers, a…”.

  • One H1 headline

    Your main headline reads: “It’s where you live. It’s what we live for.”.

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

1 to fix98
  • 15 pages share a meta description

    https://maisonco.com/shop/appliances, https://maisonco.com/shop/plumbing, https://maisonco.com/shop/wellness, https://maisonco.com/shop/lighting, https://maisonco.com/shop/hardware and https://maisonco.com/shop/outdoor and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage 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 9697
  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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.

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

  • Thin social proof

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

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

    The homepage carries about 606 words of visible text.

6 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop the Look”, “Contact Us” and “Join the Collective”.

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: HubSpot.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 5 cookies set on arrival

    5

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

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 maisonco.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
Tailwind CSS
E-commerce
Shopify;Shopify Local Pickup;Shopify Plus
Hosting
Cloudflare

Hiring

Hiring
1 open role
Job board
careers page

Company

Headquarters
Miami

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on maisonco.com, including 9 speed issues, 3 SEO issues 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