gemmadiamonds.com website review

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

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

Shopify costs a phone 190 ms of main-thread work and 368 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 third-party services load with your homepage (Shopify and shop.app), adding 371 KiB and 190 ms of main-thread time.

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

9 KiB could be saved by minifying JavaScript.

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

1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

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

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

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

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

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.

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 13 characters: “GemmaDiamonds”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 17 pages on gemmadiamonds.com and 2 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/pages/contact has no meta description, so Google writes the search snippet from whatever text it finds.

/collections/live-stock and /collections/order-collection have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/live-stock, /collections/order-collection and /pages/contact 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 4 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Refused to apply style from 'https://gemmadiamonds.com/cdn/shop/t/30/assets/tiny.content.min.css?v=2659' because its MI…”.

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://gemmadiamonds.com/customer_authentication/redirect?locale=en&region_country=GB.

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.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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

The homepage shows no opening hours. If customers visit or call, show when.

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

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