foreverwick.com website review

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

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

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

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

8 third-party services load with your homepage (Shopify, rebuyengine.com and Privy and others), adding 2.4 MB and 878 ms of main-thread time.

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

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

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

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

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

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

rebuyengine.com costs a phone 200 ms of main-thread work and 360 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 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 130 ms faster on a phone.

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

14 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “With a chance to win a Diamond valued up to $12,000”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 103.3 MB in 472 requests on a phone: media 98.8 MB (10), images 2.2 MB (287) and scripts 1.3 MB (67). Under 2 MB keeps phones on slow connections fast.

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

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your meta description is only 60 characters: “Diamond In Every Candle + A Chance To Win A $12,000 Diamond!”. 70 to 160 characters is enough to sell the click.

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

Your <h1> is empty.

The homepage links to 57 pages on foreverwick.com and 5 external pages.

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

https://foreverwick.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://foreverwick.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://foreverwick.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://foreverwick.com/collections/diamond-candles, https://foreverwick.com/collections/signature-scents, https://foreverwick.com/collections/limited-edition, https://foreverwick.com/collections/precious-gemstone-collection, https://foreverwick.com/pages/diamond-exchange-1 and https://foreverwick.com/collections/all-jewelry use the same meta description. A description written for each page earns more clicks.

https://foreverwick.com/pages/diamond-exchange-1 and https://foreverwick.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 54 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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