Website review, no card needed
jewellersworkshop.com website review
Visit site (opens in a new tab)Reviewed 17 November 202628 issues · 56 checks
This review found 28 issues worth fixing on jewellersworkshop.com, 10 of them high impact, across 56 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.6 s
4.0 s
5.3 s
6.6 s
7.9 s
9.2 s
10.6 s
Speed
Reduce unused JavaScript
5.3 s · 635 KiBAbout 635 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Render-blocking requests
1.3 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Use efficient cache lifetimes
950 ms · 159 KiB6 files are served with short cache lifetimes, so returning visitors download them again (159 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
950 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 950 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Google Maps, Mixpanel and Other Google APIs/SDKs and others), adding 1.2 MB and 596 ms of main-thread time.
Google Maps adds 441 ms
441 msGoogle Maps costs a phone 441 ms of main-thread work and 951 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.
Reduce unused CSS
290 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 91 ms. During a long task the page ignores taps.
Improve image delivery
32 KiB3 images could be 32 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 872 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.8 s
10.8 sYour largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Jewellers Workshop fine jewellery workshop”. Most of its time is resource load delay (8.1 s).
Speed Index: 15.6 s
15.6 sVisually, the page fills in at 15.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 11.7 s
11.7 sThe page becomes fully interactive after 11.7 s. Good is under 3.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
2 checks passed
Total Blocking Time: 69 ms
69 msScripts block the page for only 69 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 48.1 MB in 92 requests
48.1 MBYour homepage downloads 48.1 MB in 92 requests on a phone: media 46.4 MB (8), scripts 1.2 MB (29) and images 355 KiB (34). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (115 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 13.6 g of CO₂ per visit
13.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 13.63 g of CO₂e: 1635.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (209 characters)
Your meta description is 209 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
3 checks passed
Title: 49 characters
Your title is a healthy 49 characters: “Florian Beck | Handmade Fine Jewellery, Byron Bay”.
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://jewellersworkshop.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 549 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
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.
llms.txt published
The site publishes https://jewellersworkshop.com/llms.txt (1 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Best practices
4 small tap targets
4 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 422 ()”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 549 words of copy
The homepage carries about 549 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP THE COLLECTION”.
Analytics in place
Analytics detected: Mixpanel.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Mixpanel (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
No consent tool detected
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.
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 jewellersworkshop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Hostinger Horizons
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Analytics
- Mixpanel
- Hosting
- Hostinger
Company
- Headquarters
- Byron Bay
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on jewellersworkshop.com, including 12 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.