Website review, no card needed

supplymaid.com logo

supplymaid.com website review

Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 70 checks

This review found 29 issues worth fixing on supplymaid.com, 5 of them high impact, across 70 checks. The most urgent: 30 text elements with low contrast. 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 supplymaid.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix91
  • Render-blocking requests

    650 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google CDN and Klaviyo and others), adding 1.4 MB and 381 ms of main-thread time.

  • Reduce unused JavaScript

    317 KiB

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

  • 2,938 HTML elements

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

  • Shopify adds 199 ms

    199 ms

    Shopify costs a phone 199 ms of main-thread work and 867 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 96 ms

    96 ms

    Google CDN costs a phone 96 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.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    79 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • Reduce unused CSS

    12 KiB

    About 12 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 JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.9 s

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

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

3 to fix90
  • Time to Interactive: 14.7 s

    14.7 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

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

  • Speed Index: 3.5 s

    3.5 s

    Visually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 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.

3 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Total Blocking Time: 82 ms

    82 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.1 MB in 368 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 368 requests on a phone: scripts 1.4 MB (154), other files 965 KiB (140) and images 276 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    2_18d4d9c7-d206-445a-96df-14e2c15540f0.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 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.2 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

4 to fixGoogle 9393
  • 30 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 10080
  • Title is short (10 characters)

    Your title is only 10 characters: “SupplyMaid”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (56 characters)

    Your meta description is only 56 characters: “Rugged, Waterproof Organizers for Professional Cleaners.”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 74 internal links, 1 external

    The homepage links to 74 pages on supplymaid.com and 1 external page.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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 https://supplymaid.com/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

6 to fix60
  • 1 page without a title

    https://supplymaid.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://supplymaid.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://supplymaid.com/products/cleaning-apron and https://supplymaid.com/products/7-pocket-waterproof-cleaning-apron all use the title “Professional Waterproof Cleaning Apron – SupplyMaid”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://supplymaid.com/collections/all, https://supplymaid.com/customer_authentication/redirect, https://supplymaid.com/policies/shipping-policy, https://supplymaid.com/collections/cleaning-products, https://supplymaid.com/collections/servers-apron and https://supplymaid.com/pages/contact-us and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://supplymaid.com/products/cleaning-apron and https://supplymaid.com/products/7-pocket-waterproof-cleaning-apron use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://supplymaid.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

2 checks passed
  • 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

2 to fix83
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 486 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ORDER BY PHONE: (541) 237-7330”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “ORDER BY PHONE: (541) 237-7330”, “CONTACT US” and “Shop Aprons”.

  • 5 short forms

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.

  • 19 cookies set on arrival

    19

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

  • 34 other companies contacted

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

Apps your storefront loads

Tapita Seo Speed · Judge Me Reviews · Klaviyo Email Marketing Sms · Google Youtube · Glo Color Swatch · Selleasy · Cartbite · Dealeasy · Ecomsend · vwa.la · trafficmanager.net

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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Bend

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on supplymaid.com, including 9 speed issues, 4 SEO issues and 2 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