firstday.com website review

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

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

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

8 third-party services load with your homepage (Shopify, alia-prod.com and weglot.com and others), adding 6.1 MB and 2.6 s of main-thread time.

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

alia-prod.com costs a phone 657 ms of main-thread work and 731 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.

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

About 555 KiB of JavaScript is downloaded but never used on this page.

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

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

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

weglot.com costs a phone 430 ms of main-thread work and 113 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.

Clarity costs a phone 257 ms of main-thread work and 28 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 10 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

2 KiB JavaScript is shipped twice across bundles.

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.

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

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

Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Around 50% of children worldwide experience nutrient gaps. …”.

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

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

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

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

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

1 image 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' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.5 MB in 416 requests on a phone: media 4.1 MB (1), scripts 1.8 MB (151) and images 1.7 MB (82). Under 2 MB keeps phones on slow connections fast.

2 images (104 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.

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

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

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

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Table header text 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. (8 elements).

Your meta description is 190 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 172 pages on firstday.com and 4 external pages.

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

/customer_authentication/redirect, /pages/bundle-quiz and /pages/shop-by-age are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/pages/sale, /blogs/news, /customer_authentication/redirect, /pages/bundle-quiz, /pages/our-ingredients and /pages/heavy-metals-and-pesticides have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/sale, /blogs/news, /customer_authentication/redirect, /pages/bundle-quiz, /pages/shop-by-age and /pages/about-us and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/sale, /blogs/news, /pages/about-us, /pages/our-ingredients, /pages/our-science and /pages/heavy-metals-and-pesticides and 6 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 40 found) and read each the way a search engine does.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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://firstday.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.

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

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

DMARC is set to p=none, so mail pretending to be firstday.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 6 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.

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