beneunder.com website review

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

A phone's processor spends 5.1 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 (loox.io, quickcep.com and Shopify and others), adding 2.0 MB and 1.1 s of main-thread time.

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

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

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

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

quickcep.com costs a phone 219 ms of main-thread work and 561 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 171 ms of main-thread work and 597 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 134 ms of main-thread work and 311 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.

cloudfront.net costs a phone 124 ms of main-thread work and 330 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 214 KiB of CSS is downloaded but never applied on this page.

10 images could be 155 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

12 KiB could be saved by minifying CSS.

11 KiB JavaScript is shipped twice across bundles.

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.

The page becomes fully interactive after 23.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.

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

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

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

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

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

Your homepage downloads 5.7 MB in 446 requests on a phone: scripts 2.1 MB (130), images 1.7 MB (41) and other files 1.4 MB (260). Under 2 MB keeps phones on slow connections fast.

P1-MB_12999376-b659-4370-894e-562e5f1934de.jpg 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.61 g of CO₂e: 192.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

14 visible links have no text or label, so screen readers cannot say where they go.

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

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 401 pages on beneunder.com and 6 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/collections/new-arrivals-26-autumn-winter, /collections/new-in-sun-protection-jackets, /collections/new-in-long-sleeve-shirts, /collections/new-in-coats, /collections/new-in-bottoms and /collections/winter-hats and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/new-arrivals-26-autumn-winter, /collections/new-in-sun-protection-jackets, /collections/new-in-long-sleeve-shirts, /collections/new-in-coats, /collections/new-in-bottoms and /collections/winter-hats and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/new-in-sun-protection-jackets, /collections/new-in-long-sleeve-shirts, /collections/new-in-bottoms, /collections/winter-hats, /collections/new-in-sun-hats and /collections/new-in-sunglasses and 2 others took over 3 s to send their HTML from our server.

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

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.

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

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

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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