12benefits.com website review

Your mobile performance score is 67 (desktop: 100). Pages that score under 90 lose visitors before the first paint.

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

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

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

5 third-party services load with your homepage (Shopify, Klaviyo and Yotpo and others), adding 358 KiB and 137 ms of main-thread time.

1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Desktop scores 100 but mobile only 67. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two bottles of hair care products, one labeled as shampoo a…”.

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

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

The page becomes fully interactive after 7.1 s. Good is under 3.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.

image.png 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.48 g of CO₂e: 58.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “LocalBusiness: missing name”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 43 pages on 12benefits.com and 5 external pages.

/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/salon-professionals, /pages/about-us, /pages/contact-us, /pages/product-tutorials and /pages/data-sharing-opt-out have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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.

2 links go through two or more redirects, for example http://www.facebook.com/pages/12-Benefits/186271244742524.

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.

12benefits.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.

12benefits.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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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.

The homepage has only about 134 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

DMARC is set to p=none, so mail pretending to be 12benefits.com is still delivered. Reports are on, so moving to quarantine is the next step.

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.

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

Opening the homepage sets 16 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.