daybird.co website review

24 images could be 833 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

About 448 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Accessibe Accessibility Overlay, Clarity and Shopify and others), adding 919 KiB and 642 ms of main-thread time.

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

About 69 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.

22 KiB could be saved by minifying JavaScript.

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

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

Polyfills for old browsers add 7 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.

5 KiB JavaScript is shipped twice across bundles.

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

2 KiB could be saved by minifying CSS.

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

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

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

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

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

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.

Your homepage downloads 4.3 MB in 361 requests on a phone: scripts 1.4 MB (105), images 1.4 MB (72) and other files 1.1 MB (157). Under 2 MB keeps phones on slow connections fast.

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

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

ARIA toggle fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

[role="img"] and [role="image"] elements must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 2 <h1> headlines (“Wear Less,Benefit More” and “4-in-1 Serum Skin Tint”). One clear main headline is easier for people and search engines.

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

The homepage links to 37 pages on daybird.co and 13 external pages.

The HTML your server sends has 631 of the 1,768 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://daybird.co/products/4-in-1-serum-skin-tint and https://daybird.co/products/tinted-skincare all use the title “4-in-1 Serum Skin Tint – Daybird”. Search engines can't tell which page to show for a search, so each competes with the others.

https://daybird.co/products/4-in-1-serum-skin-tint and https://daybird.co/products/tinted-skincare use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://daybird.co/products/tinted-skincare, whose canonical is https://daybird.co/products/4-in-1-serum-skin-tint. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://daybird.co/pages/find-my-shade, https://daybird.co/pages/our-story, https://daybird.co/pages/store-locator, https://daybird.co/pages/shipping-and-returns, https://daybird.co/pages/faq and https://daybird.co/pages/privacy-policy and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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 1,768 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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 31 cookies, 3 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 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.