Programmable

Website review, no card needed

springbud.us logo

springbud.us website review

Visit site (opens in a new tab)Reviewed 7 November 202621 issues · 72 checks

This review found 21 issues worth fixing on springbud.us, 5 of them high impact, across 72 checks. The most urgent: scrollable region must have keyboard access (2 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

Site score

84B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.8 s1.3 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.5 s
Aug 8, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.7 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
124 ms81 msMay 16Oct 31108 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202686 ms
May 23, 202688 ms
Sep 12, 2026119 ms
Sep 19, 2026107 ms
Oct 10, 2026110 ms
Oct 17, 2026112 ms
Oct 24, 2026108 ms
Oct 31, 2026108 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

springbud.us (opens in a new tab)
Full-page screenshot of springbud.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix68

  • Mobile performance score: 68

    68/100

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

  • Shopify adds 115 ms

    115 ms

    Shopify costs a phone 115 ms of main-thread work and 331 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Shopify, Judge.me and shop.app and others), adding 546 KiB and 217 ms of main-thread time.

  • Improve image delivery

    246 KiB

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

  • Use efficient cache lifetimes

    150 ms · 56 KiB

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

  • Reduce unused JavaScript

    140 ms · 61 KiB

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

  • Reduce unused CSS

    23 KiB

    About 23 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.

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

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100

  • Largest Contentful Paint: 6.0 s

    6.0 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

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

    +24%

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Time to Interactive: 6.1 s

    6.1 s

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

8 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.6 s

    1.6 s

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

  • Real-user INP: 106 ms

    106 ms

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

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

    1.2 s

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

  • Real-user TTFB: 688 ms

    688 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix81

  • Page weight: 2.0 MB in 286 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 286 requests on a phone: other files 872 KiB (119), images 527 KiB (29) and scripts 473 KiB (98). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    SpringBud_1.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.6 g of CO₂ per visit

    0.58 g

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

2 to fixGoogle 9796

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

2 checks passed

  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 10087

  • Meta description is short (40 characters)

    Your meta description is only 40 characters: “Fetal Dopplers &Baby Dopplers--SpringBud”. 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.

  • 66 internal links, 7 external

    The homepage links to 66 pages on springbud.us and 7 external pages.

5 checks passed

  • Title: 40 characters

    Your title is a healthy 40 characters: “Fetal Dopplers &Baby Dopplers--SpringBud”.

  • Canonical URL set

    The canonical URL is https://springbud.us/.

  • 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://springbud.us/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 (760 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix81

  • 2 pages share a title

    https://springbud.us/pages/pregnancy and https://springbud.us/blogs/pregnancy all use the title “pregnancy – SpringBud”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://springbud.us/collections/fetal-dopplers, https://springbud.us/collections/accessories, https://springbud.us/pages/video, https://springbud.us/pages/social, https://springbud.us/blogs/fetal-doppler and https://springbud.us/blogs/pregnancy and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://springbud.us/products/springbud-fd-500b-fetal-doppler-250-ml-aquasonic-100-gel and https://springbud.us/products/springbud-fd-500b-fetal-doppler-60g-aquasonic-100-gel use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://springbud.us/pages/pregnancy, https://springbud.us/pages/faqs, https://springbud.us/pages/about-us and https://springbud.us/pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://springbud.us/pages/video and https://springbud.us/pages/social 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 30 found) and read each the way a search engine does.

4 checks passed

  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71

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

  • About 397 words of copy

    The homepage carries about 397 words of visible text.

4 checks passed

  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop”, “Contact” and “Contact Us”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks and a star rating.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 springbud.us, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Avada Seo Suite · Judge Me Reviews · herokuapp.com · omnisnippet1.com

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on springbud.us, including 7 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