Website review, no card needed

cardiomiracle.com logo

cardiomiracle.com website review

Visit site (opens in a new tab)Reviewed 16 November 202645 issues · 89 checks

This review found 45 issues worth fixing on cardiomiracle.com, 17 of them high impact, across 89 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
4.2 s2.6 sMay 30Nov 143.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20263.1 s
Sep 12, 20263.2 s
Sep 19, 20263.4 s
Sep 26, 20263.6 s
Oct 3, 20263.9 s
Oct 10, 20264.0 s
Oct 17, 20263.9 s
Oct 24, 20263.9 s
Oct 31, 20263.7 s
Nov 7, 20263.8 s
Nov 14, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
168 ms133 msMay 30Nov 14156 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026145 ms
Jun 6, 2026139 ms
Jun 13, 2026140 ms
Jun 20, 2026137 ms
Jun 27, 2026142 ms
Jul 4, 2026146 ms
Jul 11, 2026150 ms
Jul 18, 2026154 ms
Jul 25, 2026161 ms
Aug 1, 2026164 ms
Aug 8, 2026162 ms
Aug 15, 2026162 ms
Aug 22, 2026160 ms
Aug 29, 2026155 ms
Sep 5, 2026161 ms
Sep 12, 2026162 ms
Sep 19, 2026163 ms
Sep 26, 2026162 ms
Oct 3, 2026160 ms
Oct 10, 2026159 ms
Oct 17, 2026161 ms
Oct 24, 2026163 ms
Oct 31, 2026163 ms
Nov 7, 2026157 ms
Nov 14, 2026156 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 cardiomiracle.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cardiomiracle.com at 0.8 s0.8 s
  2. cardiomiracle.com at 1.5 s1.5 s
  3. cardiomiracle.com at 2.3 s2.3 s
  4. cardiomiracle.com at 3.1 s3.1 s
  5. cardiomiracle.com at 3.9 s3.9 s
  6. cardiomiracle.com at 4.6 s4.6 s
  7. cardiomiracle.com at 5.4 s5.4 s
  8. cardiomiracle.com at 6.2 s6.2 s

Speed

14 to fix25
  • Render-blocking requests

    15.6 s

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

  • Reduce unused JavaScript

    10.1 s · 2.3 MB

    About 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.1 s faster on a phone.

  • Use efficient cache lifetimes

    3.3 s · 809 KiB

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

  • Mobile performance score: 25

    25/100

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

  • Main-thread work: 5.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Azure Web Services and route.com and others), adding 5.0 MB and 1.3 s of main-thread time.

  • Reduce unused CSS

    590 ms · 469 KiB

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

  • Legacy JavaScript

    500 ms · 92 KiB

    Polyfills for old browsers add 92 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

  • Azure Web Services adds 307 ms

    307 ms

    Azure Web Services costs a phone 307 ms of main-thread work and 2.6 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.

  • Google Tag Manager adds 311 ms

    311 ms

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

  • 14 long tasks on the main thread

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

  • route.com adds 189 ms

    189 ms

    route.com costs a phone 189 ms of main-thread work and 542 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.

  • Shopify adds 125 ms

    125 ms

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

  • rechargecdn.com adds 131 ms

    131 ms

    rechargecdn.com costs a phone 131 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.

  • Minify CSS

    239 KiB

    239 KiB could be saved by minifying CSS.

  • Minify JavaScript

    200 ms · 13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    138 KiB

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

  • 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: 12 ms

    12 ms

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

Core Web Vitals

12 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 CLS: 0.55

    0.55

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

  • First Contentful Paint: 16.5 s

    16.5 s

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

  • Largest Contentful Paint: 37.5 s

    37.5 s

    Your largest element takes 37.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hero-image.webp__PID:2194bcb8-9845-4d4d-88c7-58c6a2a91d6d”.

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 42.3 s

    42.3 s

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

  • Cumulative Layout Shift: 0.418

    0.418

    The layout shifts by 0.418 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Largest content (LCP) got 29% slower for real visitors

    +29%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Total Blocking Time: 429 ms

    429 ms

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

  • 17 images without width and height

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

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

    +10%

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

2 checks passed
  • Real-user INP: 153 ms

    153 ms

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

  • Real-user TTFB: 612 ms

    612 ms

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

Images and page weight

3 to fix60
  • Page weight: 7.8 MB in 464 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 464 requests on a phone: scripts 4.9 MB (110), other files 1.4 MB (256) and images 796 KiB (35). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    hero-image.webp 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).

  • 2 images far larger than shown

    136 KiB

    2 images are downloaded at several times the size a phone draws them, for example ezgif.com-resize_2560x.webp at 296 px wide, shown at 50 px. Resized copies would save about 136 KiB.

  • 4 images in older formats

    4 images (406 KiB) 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.

  • 3 images below the first screen load straight away

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

  • About 2.2 g of CO₂ per visit

    2.21 g

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

Accessibility

5 to fixGoogle 8893
  • 19 text elements with low contrast

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

  • 11 images without alt text

    11 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (3 elements)

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Meta description is long (239 characters)

    Your meta description is 239 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 50 internal links, 20 external

    The homepage links to 50 pages on cardiomiracle.com and 20 external pages.

6 checks passed
  • Title: 56 characters

    Your title is a healthy 56 characters: “Cardio Miracle - Nitric Oxide Supplement – CardioMiracle”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, MedicalEntity, Organization, Place and Product.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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

AI search readiness

100
  • No llms.txt

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://cardiomiracle.com/pages/media-inquiries is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://cardiomiracle.com/pages/our-team and https://cardiomiracle.com/pages/media-inquiries have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://cardiomiracle.com/pages/our-team and https://cardiomiracle.com/pages/media-inquiries have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    2 pages of 11 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187128040&Ver=2&mid=1e51b08f-3787-4c38-b856-ca555d6217d7&bo=1&sid=b856d160e20611f187fd47030c60ba0e&vid=b8570860e20611f180da17bad5f7abb9&vids=1&msclkid=N&pi=918639831&l.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “analytics is not defined”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix80
  • 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: 1 customer or partner logo. 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.

  • About 1,190 words of copy

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

7 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop Now”, “Try Cardio Miracle” and “SUBSCRIBE & SAVE”.

  • 5 short forms

    5 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links 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.

  • 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

1 to fix
  • 7 trackers load before any consent

    7

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

  • 22 cookies set on arrival

    22

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

  • 61 other companies contacted

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

Apps your storefront loads

Minmaxify Order Limits · Redo · Triplewhale · Xo Insert Code · Instafeed · Judge Me Reviews · Pagefly Ai Page Builder · Klaviyo Email Marketing Sms · Cartbot · reputon.com · goaffpro.com · rechargecdn.com · route.com · amazonaws.com · govx.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on cardiomiracle.com, including 26 speed issues, 2 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