everdries.com website review

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

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

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

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

8 third-party services load with your homepage (replocdn.com, Google Tag Manager and Klaviyo and others), adding 1.4 MB and 1.4 s of main-thread time.

replocdn.com costs a phone 516 ms of main-thread work and 733 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.

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

Google Tag Manager costs a phone 297 ms of main-thread work and 318 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.

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

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

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

About 25 KiB of CSS is downloaded but never applied on this page.

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.

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 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW: Everdries Cotton Collection Naturally soft, breathable…”.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

32 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 136 ms to 159 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.8 MB in 172 requests on a phone: scripts 1.5 MB (75), other files 621 KiB (70) and images 358 KiB (16). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (22 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 0.79 g of CO₂e: 94.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail 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 visible links have no text or label, so screen readers cannot say where they go.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

Your <h1> is empty.

The homepage links to 32 pages on everdries.com and 2 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/pages/home-nov-2025, /pages/all, /clearance, /policies/privacy-policy, /policies/shipping-policy and /policies/terms-of-service and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /clearance, whose canonical is /pages/clearance-collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/home-nov-2025, /pages/all and /clearance have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/home-nov-2025, /pages/all, /clearance and /pages/cotton-collection 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 9 pages linked from your homepage and read each the way a search engine does.

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

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.

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

everdries.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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be everdries.com is still delivered. Add a report address, check the reports, then move to quarantine.

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.

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