engold.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 1.9 MB and 821 ms of main-thread time.

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

About 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 440 ms faster on a phone.

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

Google Tag Manager costs a phone 286 ms of main-thread work and 351 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 226 ms of main-thread work and 633 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 204 ms of main-thread work and 560 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.

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

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

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

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

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

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

13 KiB could be saved by minifying JavaScript.

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

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

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

Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Isla Round Dining Table in Spanish Beige Marble”.

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

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

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

4 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 5.8 MB in 476 requests on a phone: scripts 1.9 MB (142), other files 1.4 MB (273) and media 1.2 MB (1). Under 2 MB keeps phones on slow connections fast.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

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

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

There are 3 <h1> headlines (“”, “” and “protect”). One clear main headline is easier for people and search engines.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 239 pages on engold.com and 10 external pages.

/collections/new-arrivals and /collections/last-call-collection use the same meta description. A description written for each page earns more clicks.

/pages/contact-us, /collections/all, /collections/ready-to-ship, /collections/ready-to-ship-furniture, /collections/new-arrivals and /collections/last-call-collection and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/contact-us and /collections/media-consoles 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 15 pages linked from your homepage (of 80 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.

1 link go through two or more redirects, for example https://engold.com/account.

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.

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

engold.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: 10 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Opening the homepage sets 13 cookies, 9 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.