Website review, no card needed

moriconi.co.uk logo

moriconi.co.uk website review

Visit site (opens in a new tab)Reviewed 7 November 202626 issues · 76 checks

This review found 26 issues worth fixing on moriconi.co.uk, 7 of them high impact, across 76 checks. The most urgent: main-thread work: 5.0 s. 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
1.6 s1.2 sMay 16Sep 191.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
146 ms114 msMay 16Sep 19136 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026136 ms
Jul 18, 2026141 ms
Jul 25, 2026142 ms
Aug 1, 2026138 ms
Aug 8, 2026122 ms
Aug 15, 2026123 ms
Aug 22, 2026120 ms
Aug 29, 2026118 ms
Sep 5, 2026125 ms
Sep 12, 2026124 ms
Sep 19, 2026136 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 moriconi.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. moriconi.co.uk at 0.8 s0.8 s
  2. moriconi.co.uk at 1.6 s1.6 s
  3. moriconi.co.uk at 2.5 s2.5 s
  4. moriconi.co.uk at 3.3 s3.3 s
  5. moriconi.co.uk at 4.1 s4.1 s
  6. moriconi.co.uk at 4.9 s4.9 s
  7. moriconi.co.uk at 5.7 s5.7 s
  8. moriconi.co.uk at 6.6 s6.6 s

Speed

8 to fix73
  • Main-thread work: 5.0 s

    A phone's processor spends 5.0 s on main-thread work while loading, 905 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused JavaScript

    600 ms · 448 KiB

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

  • Mobile performance score: 73

    73/100

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

  • Improve image delivery

    400 ms · 493 KiB

    5 images could be 493 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Render-blocking requests

    700 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, loox.io and Bold Commerce and others), adding 1.4 MB and 427 ms of main-thread time.

  • Shopify adds 151 ms

    151 ms

    Shopify costs a phone 151 ms of main-thread work and 624 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,106 HTML elements

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

  • Use efficient cache lifetimes

    231 KiB

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

  • 1 long task on the main thread

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

  • Legacy JavaScript

    34 KiB

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

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 35 ms

    35 ms

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

Core Web Vitals

3 to fix67
  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 14.0 s

    14.0 s

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

  • Speed Index: 4.1 s

    4.1 s

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

  • Tap response (INP) held steady for real visitors

    -6%

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

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

4 checks passed
  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Total Blocking Time: 15 ms

    15 ms

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

Images and page weight

2 to fix60
  • Page weight: 4.9 MB in 364 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 364 requests on a phone: images 2.5 MB (115), scripts 1.3 MB (145) and other files 655 KiB (72). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    219 KiB

    1 image is downloaded at several times the size a phone draws it, for example Nuova_collezione_sul_porto_mediterraneo.png at 2,000 px wide, shown at 390 px. Resized copies would save about 219 KiB.

  • About 1.4 g of CO₂ per visit

    1.39 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.7 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 load when needed

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

Accessibility

4 to fixGoogle 9295
  • 14 text elements with low contrast

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

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (49 elements)

    All page content should be contained by landmarks: 49 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

  • 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 66 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10082
  • No H1 headline

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

  • Meta description is long (286 characters)

    Your meta description is 286 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.

  • 140 internal links, 1 external

    The homepage links to 140 pages on moriconi.co.uk and 1 external page.

5 checks passed
  • Title: 35 characters

    Your title is a healthy 35 characters: “MORICONI ITALY – Moriconi Jewellery”.

  • Canonical URL set

    The canonical URL is https://moriconi.co.uk/.

  • Structured data in place

    Structured data found: 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://moriconi.co.uk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://moriconi.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.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 3 pages without a meta description

    https://moriconi.co.uk/pages/about, https://moriconi.co.uk/collections/infinity and https://moriconi.co.uk/collections/gift-sets have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://moriconi.co.uk/pages/about, https://moriconi.co.uk/collections/tuscany and https://moriconi.co.uk/collections/gift-sets 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 49 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 30 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 11 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 594 words of visible text.

  • Urgency cues

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “START SHOPPING”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop Now”, “Shop Best seller Clover” and “Shop Florentine”.

  • 6 short forms

    6 short forms (2 fields at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies, 1 of them by other companies (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.

  • 27 other companies contacted

    Loading the homepage contacts 27 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 moriconi.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Klaviyo Email Marketing Sms · Product Upsell · Bundle Products By Thimatic · webcontrive.com · loox.io · boldapps.net · nfcube.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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 moriconi.co.uk, including 11 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

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