Website review, no card needed
regalrose.co.uk website review
Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 90 checks
This review found 34 issues worth fixing on regalrose.co.uk, 10 of them high impact, across 90 checks. The most urgent: improve image delivery. 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
Site score
83B- #28,197 of 124,112 reviewed websitesbeats 72%
- #18,446 of 69,786 online storesbeats 67%
- #17,861 of 63,472 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 139 ms |
| May 23, 2026 | 139 ms |
| May 30, 2026 | 143 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 152 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 153 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 158 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 160 ms |
| Oct 3, 2026 | 159 ms |
| Oct 10, 2026 | 157 ms |
| Oct 17, 2026 | 158 ms |
| Oct 24, 2026 | 160 ms |
| Oct 31, 2026 | 160 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
How it loaded on a phone
1.2 s
2.3 s
3.5 s
4.7 s
5.8 s
7.0 s
8.2 s
9.3 s
Speed
Improve image delivery
1.1 s · 857 KiB23 images could be 857 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 10.1 s
A phone's processor spends 10.1 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,282 HTML elements
The page has 4,282 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, hiverhq.com and Klaviyo and others), adding 2.6 MB and 1.8 s of main-thread time.
Reduce unused JavaScript
1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 803 ms
803 msGoogle Tag Manager costs a phone 803 ms of main-thread work and 806 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.
Render-blocking requests
600 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
hiverhq.com adds 295 ms
295 mshiverhq.com costs a phone 295 ms of main-thread work and 877 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.
Use efficient cache lifetimes
341 KiB88 files are served with short cache lifetimes, so returning visitors download them again (341 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Reduce unused CSS
135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
19 KiB19 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 31.3 s
31.3 sThe page becomes fully interactive after 31.3 s. Good is under 3.8 s.
Largest Contentful Paint: 5.5 s
5.5 sYour 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 “The 2026 Advent Calendar, shop now. Black Regalrose advent …”.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 139 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 552 ms
552 msReal visitors wait 552 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 448 requests
6.0 MBYour homepage downloads 6.0 MB in 448 requests on a phone: scripts 2.8 MB (174), images 1.7 MB (56) and other files 1.2 MB (199). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (180 KiB) is 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 1.7 g of CO₂ per visit
1.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 203.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Positive tabindex
14 elements have a tabindex above 0, which scrambles the keyboard order.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 330 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (178 characters)
Your meta description is 178 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.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
241 internal links, 7 external
The homepage links to 241 pages on regalrose.co.uk and 7 external pages.
6 checks passed
One H1 headline
Your main headline reads: “REGALROSE”.
Title: 36 characters
Your title is a healthy 36 characters: “REGALROSE Jewellery & Accessories UK”.
Canonical URL set
The canonical URL is https://www.regalrose.co.uk/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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.regalrose.co.uk/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
3 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 (1,536 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.regalrose.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.regalrose.co.uk/pages/newsletter, https://www.regalrose.co.uk/collections/gemstone-rings and https://www.regalrose.co.uk/collections/band-rings have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 109 found) and read each the way a search engine does.
6 checks passed
Linked pages load
10 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=20046685&Ver=2&mid=cee7c9fe-8dcc-4c15-a5aa-ce72a8d188ce&bo=3&sid=e1253c50d97611f1b6fc79175377cbbd&vid=e1256180d97611f1b0966beae6ced382&vids=0&msclkid=N&pi=918639831&lg.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Unable to process event: init,[object Object],function(i){t&&t(i),n(i)}”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
66 of 75 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 332 words of copy
The homepage carries about 332 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “SHOP ALL >”.
14 calls to action
The homepage has 14 calls to action, for example “CONTACT US”, “STYLE BOOK” and “SHOP ALL >”.
16 short forms
16 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 6 mores (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (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.
53 other companies contacted
Loading the homepage contacts 53 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 regalrose.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
- E-commerce
- Global-e;Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Headquarters
- Saint Albans
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on regalrose.co.uk, including 15 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.