Website review, no card needed

micheldesignworks.com logo

micheldesignworks.com website review

Visit site (opens in a new tab)Reviewed 20 November 202646 issues · 88 checks

This review found 46 issues worth fixing on micheldesignworks.com, 15 of them high impact, across 88 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

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.1 sMay 30Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.6 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.3 s
Nov 7, 20262.3 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
158 ms132 msMay 30Nov 14155 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026135 ms
Jun 6, 2026137 ms
Jun 13, 2026137 ms
Jun 20, 2026141 ms
Jun 27, 2026145 ms
Jul 4, 2026144 ms
Jul 11, 2026140 ms
Jul 18, 2026138 ms
Jul 25, 2026138 ms
Aug 1, 2026141 ms
Aug 8, 2026146 ms
Aug 15, 2026152 ms
Aug 22, 2026153 ms
Aug 29, 2026154 ms
Sep 5, 2026154 ms
Sep 12, 2026153 ms
Sep 19, 2026154 ms
Sep 26, 2026154 ms
Oct 3, 2026154 ms
Oct 10, 2026154 ms
Oct 17, 2026154 ms
Oct 24, 2026153 ms
Oct 31, 2026153 ms
Nov 7, 2026154 ms
Nov 14, 2026155 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 micheldesignworks.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. micheldesignworks.com at 1.5 s1.5 s
  2. micheldesignworks.com at 2.9 s2.9 s
  3. micheldesignworks.com at 4.4 s4.4 s
  4. micheldesignworks.com at 5.9 s5.9 s
  5. micheldesignworks.com at 7.3 s7.3 s
  6. micheldesignworks.com at 8.8 s8.8 s
  7. micheldesignworks.com at 10.2 s10.2 s
  8. micheldesignworks.com at 11.7 s11.7 s

Speed

15 to fix32
  • Render-blocking requests

    2.6 s

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

  • Main-thread work: 10.5 s

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

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 5,493 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Noibu and Google CDN and others), adding 2.2 MB and 3.0 s of main-thread time.

  • Use efficient cache lifetimes

    850 ms · 2.2 MB

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

  • Reduce unused JavaScript

    150 ms · 2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 105 KiB

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

  • Improve image delivery

    549 KiB

    42 images could be 549 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 489 ms

    489 ms

    Google Tag Manager costs a phone 489 ms of main-thread work and 356 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.

  • Noibu adds 472 ms

    472 ms

    Noibu costs a phone 472 ms of main-thread work and 197 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 400 ms

    400 ms

    Google CDN costs a phone 400 ms of main-thread work and 742 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.

  • 20 long tasks on the main thread

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

  • Osano CMP adds 391 ms

    391 ms

    Osano CMP costs a phone 391 ms of main-thread work and 102 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.

  • reddit adds 374 ms

    374 ms

    reddit costs a phone 374 ms of main-thread work and 59 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.

  • Font display

    100 ms

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

  • Legacy JavaScript

    66 KiB

    Polyfills for old browsers add 66 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    43 KiB

    43 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: 8 ms

    8 ms

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

Core Web Vitals

10 to fix33
  • 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 TTFB: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 17.9 s

    17.9 s

    Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Michel Design Works”.

  • Speed Index: 23.0 s

    23.0 s

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

  • Time to Interactive: 47.7 s

    47.7 s

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

  • Total Blocking Time: 2.2 s

    2.2 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user CLS: 0.19

    0.19

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

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

3 checks passed
  • Real-user INP: 187 ms

    187 ms

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

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

    -21%

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

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

4 to fix38
  • Page weight: 9.5 MB in 343 requests

    9.5 MB

    Your homepage downloads 9.5 MB in 343 requests on a phone: scripts 4.4 MB (80), images 3.5 MB (100) and fonts 899 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    FathersDay_NavTile.jpg weighs 570 KiB. On a phone connection a single image that size takes seconds.

  • 9 images in older formats

    9 images (2.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.

  • 24 images below the first screen load straight away

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

  • About 2.7 g of CO₂ per visit

    2.68 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.68 g of CO₂e: 321.8 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

4 to fixGoogle 10094
  • 2 text elements with low contrast

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

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

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

  • 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 (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 10084
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Michel Design Works” and “Recently Viewed”). One clear main headline is easier for people and search engines.

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

  • No X (Twitter) card tag

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

  • 410 internal links, 10 external

    The homepage links to 410 pages on micheldesignworks.com and 10 external pages.

4 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Discover Michel Design Works. Find luxurious home and personal care products, from candles to bath essentials, perfect …”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Michel Design Works - Family of Brands - Stonewall Kitchen”.

  • 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://www.stonewallkitchen.com/sitemap_index.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.

  • No llms.txt

    There is no https://www.stonewallkitchen.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 (2,824 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.stonewallkitchen.com/stonewall-kitchen-family-of-brands/stonewallkitchenfamilyofbrands.html and https://www.stonewallkitchen.com/stonewall-kitchen-brand/stonewallkitchen-brandpage.html all use the title “Stonewall Kitchen - America's Premier Specialty Food and Gift Basket …”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://www.stonewallkitchen.com/stonewall-kitchen-family-of-brands/stonewallkitchenfamilyofbrands.html and https://www.stonewallkitchen.com/stonewall-kitchen-brand/stonewallkitchen-brandpage.html use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.stonewallkitchen.com/stonewall-kitchen-brand/stonewallkitchen-brandpage.html, whose canonical is https://www.stonewallkitchen.com/stonewall-kitchen-family-of-brands/stonewallkitchenfamilyofbrands.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://www.stonewallkitchen.com/our-products/collections-variety-packs took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

  • 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

2 to fixGoogle 9291
  • 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 ()”.

  • 11 distorted images

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,458 words of copy

    The homepage carries about 1,458 words of visible text.

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop By Collection”, “New Reserve Jam Gifts” and “SIGN UP”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Cloudflare Web Analytics.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • 28 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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 micheldesignworks.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
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Oracle Cloud

Hiring

Hiring
32 open roles
Teams
Retail (8), Cafe (2), Dover Distribution Center (1), Production (1)
Job board
paylocity

Company

Headquarters
Katonah

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on micheldesignworks.com, including 25 speed issues, 4 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