heartsinprogress.com website review

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

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

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

5 images could be 77 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

3 third-party services load with your homepage (Shopify, shop.app and myshopify.com), adding 191 KiB and 60 ms of main-thread time.

About 11 KiB of CSS is downloaded but never applied on this page.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “slider image 1621243260e1af0c20-0”.

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

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

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

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.

banner12_c4d32114-a259-4982-b501-79bd9b4b7705.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).

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

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

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

1 image has no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your <h1> is empty.

The homepage links to 36 pages on heartsinprogress.com and 4 external pages.

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

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

/collections/all, /pages/about-us, /pages/contact, /customer_authentication/redirect, /policies/privacy-policy and /policies/refund-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/about-us, /pages/contact and /customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/contact has 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.

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

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 ()”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

3 links go through two or more redirects, for example https://heartsinprogress.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

heartsinprogress.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

heartsinprogress.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 386 words of visible text.

heartsinprogress.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

heartsinprogress.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

heartsinprogress.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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.

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