absorbmore.com website review

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

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

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

8 third-party services load with your homepage (alia-prod.com, Google Tag Manager and Clarity and others), adding 2.0 MB and 1.1 s of main-thread time.

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

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

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

alia-prod.com costs a phone 356 ms of main-thread work and 447 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 333 ms of main-thread work and 666 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.

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

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

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

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

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

2 KiB could be saved by minifying CSS.

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 26.9 s. Good is under 3.8 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 image.

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 5.0 MB in 356 requests on a phone: scripts 1.9 MB (122), other files 1.2 MB (153) and images 972 KiB (47). Under 2 MB keeps phones on slow connections fast.

logo.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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.

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

All page content should be contained by landmarks: 3 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: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 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 should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is only 22 characters: “The Absorption Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 27 pages on absorbmore.com and 1 external page.

/collections/halloween-sale, /collections/all, /pages/about, /collections/weight-management, /pages/science and /collections/foundational-supplements and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/halloween-sale, /collections/all, /pages/about, /collections/weight-management, /pages/science and /collections/foundational-supplements and 4 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 13 pages linked from your homepage and read each the way a search engine does.

10 images failed to load on a phone, for example https://www.absorbmore.com/.

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

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

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.

The homepage carries about 574 words of visible text.

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

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