Website review, no card needed

goldsmiths.co.uk logo

goldsmiths.co.uk website review

Visit site (opens in a new tab)Reviewed 26 October 202640 issues · 87 checks

This review found 40 issues worth fixing on goldsmiths.co.uk, 11 of them high impact, across 87 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.1 s1.7 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.6 s
May 16, 20264.7 s
May 23, 20264.7 s
May 30, 20264.7 s
Jun 6, 20264.5 s
Jun 13, 20264.4 s
Jun 20, 20264.2 s
Jun 27, 20263.9 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.5 s
Aug 1, 20263.3 s
Aug 8, 20262.8 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.3 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
487 ms237 msMay 9Oct 24413 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026337 ms
May 16, 2026325 ms
May 23, 2026312 ms
May 30, 2026304 ms
Jun 6, 2026290 ms
Jun 13, 2026278 ms
Jun 20, 2026270 ms
Jun 27, 2026266 ms
Jul 4, 2026269 ms
Jul 11, 2026278 ms
Jul 18, 2026292 ms
Jul 25, 2026307 ms
Aug 1, 2026334 ms
Aug 8, 2026376 ms
Aug 15, 2026414 ms
Aug 22, 2026441 ms
Aug 29, 2026457 ms
Sep 5, 2026458 ms
Sep 12, 2026451 ms
Sep 19, 2026438 ms
Sep 26, 2026431 ms
Oct 3, 2026425 ms
Oct 10, 2026427 ms
Oct 17, 2026427 ms
Oct 24, 2026413 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 goldsmiths.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix63
  • 4,064 HTML elements

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

  • Reduce unused JavaScript

    940 ms · 175 KiB

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

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

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

  • Reduce unused CSS

    760 ms · 171 KiB

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

  • rolex.com adds 166 ms

    166 ms

    rolex.com costs a phone 166 ms of main-thread work and 306 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (rolex.com, mPulse and Visual Studio and others), adding 451 KiB and 192 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Improve image delivery

    115 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 93 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Use efficient cache lifetimes

    5 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 25 ms

    25 ms

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

Core Web Vitals

8 to fix33
  • 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.

  • Real-user INP: 505 ms

    505 ms

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

  • Real-user CLS: 0.93

    0.93

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

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image of Rolex Lady Datejust Watch - Discover image”.

  • First Contentful Paint: 4.9 s

    4.9 s

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

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

    +27%

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

  • Time to Interactive: 7.0 s

    7.0 s

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

  • Speed Index: 5.2 s

    5.2 s

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

6 checks passed
  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 418 ms

    418 ms

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

  • Largest content (LCP) got 55% faster for real visitors

    -55%

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

  • Total Blocking Time: 84 ms

    84 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix65
  • 1 image over 500 KB

    gs-hp-dark-green-breitling.jpg weighs 620 KiB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (708 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.

  • 1 image far larger than shown

    3 KiB

    1 image is downloaded at several times the size a phone draws it, for example rolex-hp-banner-mobile-spa-uk-oct2026.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 3 KiB.

  • About 0.3 g of CO₂ per visit

    0.32 g

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

2 checks passed
  • Page weight: 1.1 MB in 65 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 65 requests on a phone: images 509 KiB (33), scripts 359 KiB (13) and stylesheets 185 KiB (5). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 10092
  • 2 text elements with low contrast

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

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

4 to fixGoogle 10076
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (78 characters)

    Your title is 78 characters, so Google will cut it off around 60: “Goldsmiths | Goldsmiths Jewellers | Watches, Diamonds & Jewellery Shop Near Me”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

  • 662 internal links, 15 external

    The homepage links to 662 pages on goldsmiths.co.uk and 15 external pages.

4 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Established in 1778, Goldsmiths is one of the leading quality jewellers in the UK - the perfect destination for luxury …”.

  • Canonical URL set

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

  • 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.goldsmiths.co.uk/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.goldsmiths.co.uk/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.

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

  • Text is in the HTML

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

Other pages

7 to fix55
  • 2 pages without a title

    https://www.goldsmiths.co.uk/wes and https://www.goldsmiths.co.uk/store-finder have no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.goldsmiths.co.uk/bespoke 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.goldsmiths.co.uk/rolex/book-an-appointment and https://www.goldsmiths.co.uk/by-personal-appointment all use the title “Book an Appointment | Goldsmiths”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.goldsmiths.co.uk/wes, https://www.goldsmiths.co.uk/store-finder, https://www.goldsmiths.co.uk/sell-my-watch and https://www.goldsmiths.co.uk/by-personal-appointment have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.goldsmiths.co.uk/c/SALE/All and https://www.goldsmiths.co.uk/c/SALE use the same meta description. A description written for each page earns more clicks.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.goldsmiths.co.uk/c/SALE/Jewellery, whose canonical is https://www.goldsmiths.co.uk/c/SALE/Jewellery?q=fh_view_size%3D48%26fh_view%3Dsearch%26wosg_site%3Dgoldsmiths_uk%26fh_refpath%3D69f18baf-e18d-4b56-84b8-099652ff5ca9%26fh_refview%3Dlister%26fh_reffacet%3Dpromotioncategory_goldsmiths_uk%26fh_location%3D%252f%252fcatalog01%252fen_GB%252fcategories%253c%257bcatalog01_sale%257d%252fcategories%253c%257bcatalog01_sale_salejewellery%257d%252fpromotioncategory_goldsmiths_uk%253e%257bextra10%257d&currentPage=0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.goldsmiths.co.uk/wes, https://www.goldsmiths.co.uk/rolex/book-an-appointment, https://www.goldsmiths.co.uk/store-finder and https://www.goldsmiths.co.uk/by-personal-appointment have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 7385
  • 16 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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 analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 986 words of copy

    The homepage carries about 986 words of visible text.

  • Urgency cues

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All Sale” and “Shop All Engagement Rings”.

  • 51 calls to action

    The homepage has 51 calls to action, for example “Book a Rolex Appointment”, “Book an Appointment” and “Shop All Sale”.

  • Social proof on the page

    Social proof on the homepage: 6 customer or partner logos and 13 trust badges.

  • 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

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

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

  • 16 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 goldsmiths.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
Angular

Company

Founded
1778
Headquarters
Leicester

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on goldsmiths.co.uk, including 14 speed issues, 4 SEO issues and 3 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