forchics.com website review

47 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

69 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and Klaviyo and others), adding 2.1 MB and 938 ms of main-thread time.

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

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

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

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

thefrontrowhealth.com costs a phone 83 ms of main-thread work and 925 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.

Klaviyo costs a phone 143 ms of main-thread work and 312 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 costs a phone 106 ms of main-thread work and 309 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 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

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

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

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.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

Your homepage downloads 9.4 MB in 509 requests on a phone: images 4.3 MB (97), scripts 1.7 MB (118) and fonts 1.7 MB (44). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“BLACK FRIDAY Sale” and “PheromonePerfumes”). One clear main headline is easier for people and search engines.

The homepage links to 124 pages on forchics.com and 1 external page.

/products/lash-growth-mascara and /products/lash-serum-and-mascara-set all use the title “Lash Growth Mascara - Better Than Falsies | ForChics”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/temporary-deal, /collections/pheromones, /products/body-oil, /collections/eyelash, /collections/eyebrow and /collections/hairs and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/products/pheromone-perfumes, /products/forchics-perfumes-seduction-sub, /products/forchics-perfumes-temptation-sub and /products/forchics-perfumes-devotion-sub use the same meta description. A description written for each page earns more clicks.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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://instagram.com/forchics.

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.

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

forchics.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 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 10 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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.

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.

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