beverlinhills.com website review

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

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

8 third-party services load with your homepage (route.com, Shopify and Klaviyo and others), adding 2.6 MB and 2.1 s of main-thread time.

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

About 709 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

route.com costs a phone 684 ms of main-thread work and 717 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 646 ms. During a long task the page ignores taps.

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

Klaviyo costs a phone 377 ms of main-thread work and 387 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.

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

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

5 KiB could be saved by minifying JavaScript.

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

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

104 KiB JavaScript is shipped twice across bundles.

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

13 KiB could be saved by minifying CSS.

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.

Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FALL EXCLUSIVE GOLDEN HARVEST AVAILABLE NOW SHOP Everyday E…”.

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

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

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

The first text or image appears after 2.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.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.3 MB in 532 requests on a phone: scripts 2.1 MB (242), images 1.1 MB (23) and other files 1,016 KiB (208). Under 2 MB keeps phones on slow connections fast.

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

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

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

The homepage links to 48 pages on beverlinhills.com and 6 external pages.

Your Organization JSON-LD is missing logo, 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.

/products/golden-harvest and /collections/coffee/products/golden-harvest all use the title “Golden Harvest – Beverlin Hills”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/coffee, /collections/home-goods, /blogs/news, /pages/contact and /policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

/products/golden-harvest and /collections/coffee/products/golden-harvest use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /collections/coffee/products/golden-harvest, whose canonical is /products/golden-harvest. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/coffee has no <h1> headline, so visitors and search engines get no clear main topic.

/pages/contact has 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 17 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

beverlinhills.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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

DMARC is set to p=none, so mail pretending to be beverlinhills.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 Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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 15 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.