authentic.com website review

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

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

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

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

8 third-party services load with your homepage (Kameleoon, Shopify and Accessibe Accessibility Overlay and others), adding 2.6 MB and 2.9 s of main-thread time.

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

20 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

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

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

Kameleoon costs a phone 887 ms of main-thread work and 57 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.

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

Accessibe Accessibility Overlay costs a phone 439 ms of main-thread work and 249 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 Tag Manager costs a phone 304 ms of main-thread work and 148 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

8 KiB could be saved by minifying JavaScript.

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.

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.

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

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

Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Collage of woman in flower-patterned dress and gold flats s…”.

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

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

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

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

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

Your homepage downloads 5.8 MB in 458 requests on a phone: images 2.4 MB (65), scripts 2.1 MB (236) and other files 831 KiB (135). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example collectionlist-championworkout.png at 700 px wide, shown at 154 px. Resized copies would save about 408 KiB.

1 image further down the page (48 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

There are 4 <h1> headlines (“The Home for Authentic Brands”, “Save More with Authentic Membership” and “Reverse Weave”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 301 pages on authentic.com and 64 external pages.

/collections/shop-all, /collections/champion, /collections/dc-shoes, /collections/fredericks-of-hollywood, /collections/juicy-couture and /collections/reebok and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/search-results, /collections/shop-all, /collections/champion, /collections/dc-shoes, /collections/fredericks-of-hollywood and /collections/juicy-couture and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/shop-all, /collections/champion, /collections/fredericks-of-hollywood, /collections/vince-camuto, /collections/womens-sandals-slides and /collections/womens-clothing and 2 others 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.

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

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

1 link go through two or more redirects, for example https://authentic.com/account.

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.

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

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

Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 374 words of visible text.

DMARC is set to p=none, so mail pretending to be authentic.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 Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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 19 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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.