Website review, no card needed

rox.co.uk logo

rox.co.uk website review

Visit site (opens in a new tab)Reviewed 22 October 202626 issues · 83 checks

This review found 26 issues worth fixing on rox.co.uk, 9 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.3 s3.9 sMay 2Oct 174.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.0 s
May 16, 20264.1 s
May 23, 20264.1 s
May 30, 20264.1 s
Jun 6, 20264.2 s
Jun 13, 20264.3 s
Jun 20, 20264.4 s
Jun 27, 20264.5 s
Jul 4, 20264.8 s
Jul 11, 20265.1 s
Jul 18, 20265.1 s
Jul 25, 20265.1 s
Aug 1, 20265.1 s
Aug 8, 20265.1 s
Aug 15, 20265.0 s
Aug 22, 20264.8 s
Aug 29, 20264.6 s
Sep 5, 20264.3 s
Sep 12, 20264.4 s
Sep 19, 20264.7 s
Sep 26, 20264.7 s
Oct 3, 20264.7 s
Oct 10, 20264.3 s
Oct 17, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
241 ms139 msMay 2Oct 17206 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026151 ms
May 9, 2026152 ms
May 16, 2026152 ms
May 23, 2026165 ms
May 30, 2026184 ms
Jun 6, 2026206 ms
Jun 13, 2026225 ms
Jun 20, 2026221 ms
Jun 27, 2026219 ms
Jul 4, 2026216 ms
Jul 11, 2026223 ms
Jul 18, 2026228 ms
Jul 25, 2026229 ms
Aug 1, 2026212 ms
Aug 8, 2026205 ms
Aug 15, 2026189 ms
Aug 22, 2026178 ms
Aug 29, 2026187 ms
Sep 5, 2026187 ms
Sep 12, 2026204 ms
Sep 19, 2026213 ms
Sep 26, 2026209 ms
Oct 3, 2026207 ms
Oct 10, 2026197 ms
Oct 17, 2026206 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of rox.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rox.co.uk at 0.4 s0.4 s
  2. rox.co.uk at 0.8 s0.8 s
  3. rox.co.uk at 1.1 s1.1 s
  4. rox.co.uk at 1.5 s1.5 s
  5. rox.co.uk at 1.9 s1.9 s
  6. rox.co.uk at 2.3 s2.3 s
  7. rox.co.uk at 2.6 s2.6 s
  8. rox.co.uk at 3.0 s3.0 s

Speed

100
  • Use efficient cache lifetimes

    14 KiB

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

  • Legacy JavaScript

    10 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 6 ms of main-thread time.

  • Chained critical requests

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100 (desktop: 100). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.1 s

    A phone's processor spends 0.1 s on main-thread work while loading, 21 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Tap response (INP) got 33% slower for real visitors

    +33%

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

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

9 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 170 ms

    170 ms

    Real visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Largest Contentful Paint: 1.5 s

    1.5 s

    Your largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “This website is using a security service to protect itself …”.

  • Speed Index: 1.5 s

    1.5 s

    Visually, the page fills in at 1.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.5 s

    1.5 s

    The page is fully interactive after 1.5 s.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    chopard-happy-diamonds-mob.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).

  • 2 images in older formats

    2 images (316 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.01 g of CO₂ per visit

    0.01 g

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

2 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

  • Page weight: 23 KiB in 6 requests

    23 KiB

    Your homepage downloads 23 KiB in 6 requests on a phone: scripts 10 KiB (1), stylesheets 5 KiB (1) and images 5 KiB (2). That is a lean page.

Accessibility

7 to fixGoogle 9691
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 57 text elements with low contrast

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

  • 30 tap targets too small

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

  • ARIA input fields must have an accessible name (1 element)

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

  • 2 form fields without a label

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

  • ARIA role should be appropriate for the element (2 elements)

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

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • No main landmark

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

2 checks passed
  • Every image has alt text

    All 53 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 4062
  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Error status code

    The page answers with an error status, so search engines may drop it.

  • 3 H1 headlines

    There are 3 <h1> headlines (“CHOPARD HAPPY DIAMONDS”, “Diamonds & Thrills” and “Need Help?”). One clear main headline is easier for people and search engines.

  • Meta description is long (166 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 338 internal links, 30 external

    The homepage links to 338 pages on rox.co.uk and 30 external pages.

5 checks passed
  • Title: 64 characters

    Your title is a healthy 64 characters: “ROX - Diamonds & Thrills | Award Winning British Luxury Jeweller”.

  • Canonical URL set

    The canonical URL is https://www.rox.co.uk/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.rox.co.uk/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,710 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.rox.co.uk/llms.txt (4 KiB, 33 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix74
  • 1 linked page hidden from search

    https://www.rox.co.uk/catalogsearch/advanced is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.rox.co.uk/contactus and https://www.rox.co.uk/contact all use the title “Get In Touch With Us | ROX”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.rox.co.uk/catalogsearch/advanced and https://www.rox.co.uk/mwishlist_guest/wishlist/index have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.rox.co.uk/contactus and https://www.rox.co.uk/contact use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.rox.co.uk/contact, whose canonical is https://www.rox.co.uk/contactus. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages slow to respond

    https://www.rox.co.uk/jewellery, https://www.rox.co.uk/jewellery/wristwear, https://www.rox.co.uk/jewellery/earrings, https://www.rox.co.uk/jewellery/necklaces, https://www.rox.co.uk/jewellery/necklaces/collars and https://www.rox.co.uk/jewellery/rings and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 10 broken images

    10 images failed to load on a phone, for example https://www.rox.co.uk/.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://static.cloudflareinsights.com/beacon.min.js/vce701823e78c4301a35b7e07294d87301792088814092'…”.

2 checks passed
  • Tap targets are thumb-sized

    11 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No social proof

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

  • Local business without LocalBusiness data

    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 opening hours

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

  • No map or directions link

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

  • About 502 words of copy

    The homepage carries about 502 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Shop Happy Diamonds”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Contact Us”, “Call us on 0808 164 6448” and “Book an Appointment”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel, Microsoft Clarity and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Tag Manager, LinkedIn Insight, Meta Pixel, Microsoft Clarity and TikTok Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies (measured from a US location before any click).

  • 35 other companies contacted

    Loading the homepage contacts 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at rox.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Magento
Analytics
Google Tag Manager | Microsoft Clarity

Company

Founded
2002
Headquarters
United Kingdom

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on rox.co.uk, including 4 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25
rox.co.uk website review: scores and fixes | Programmable