Website review, no card needed

metalalchemist.com logo

metalalchemist.com website review

Visit site (opens in a new tab)Reviewed 17 November 202643 issues · 84 checks

This review found 43 issues worth fixing on metalalchemist.com, 16 of them high impact, across 84 checks. The most urgent: improve image delivery. 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

Full-page screenshot of metalalchemist.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. metalalchemist.com at 1.7 s1.7 s
  2. metalalchemist.com at 3.4 s3.4 s
  3. metalalchemist.com at 5.0 s5.0 s
  4. metalalchemist.com at 6.7 s6.7 s
  5. metalalchemist.com at 8.4 s8.4 s
  6. metalalchemist.com at 10.1 s10.1 s
  7. metalalchemist.com at 11.7 s11.7 s
  8. metalalchemist.com at 13.4 s13.4 s

Speed

14 to fix46
  • Improve image delivery

    11.0 s · 1.8 MB

    26 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.0 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 484 KiB

    About 484 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.1 s

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

  • 3,305 HTML elements

    The page has 3,305 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 (Hotjar, Shopify and datadoghq-browser-agent.com and others), adding 16.0 MB and 1.3 s of main-thread time.

  • Shopify adds 338 ms

    338 ms

    Shopify costs a phone 338 ms of main-thread work and 15.4 MB 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

    300 ms · 253 KiB

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

  • Render-blocking requests

    500 ms

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

  • Hotjar adds 374 ms

    374 ms

    Hotjar costs a phone 374 ms of main-thread work and 65 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

    300 ms · 78 KiB

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

  • 13 long tasks on the main thread

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

  • datadoghq-browser-agent.com adds 256 ms

    256 ms

    datadoghq-browser-agent.com costs a phone 256 ms of main-thread work and 59 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.

  • Klaviyo adds 183 ms

    183 ms

    Klaviyo costs a phone 183 ms of main-thread work and 333 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.

  • Legacy JavaScript

    50 ms · 44 KiB

    Polyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Minify JavaScript

    8 KiB

    8 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: 12 ms

    12 ms

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

Core Web Vitals

6 to fix48
  • Largest Contentful Paint: 31.3 s

    31.3 s

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

  • Speed Index: 17.4 s

    17.4 s

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

  • Time to Interactive: 34.8 s

    34.8 s

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

  • Total Blocking Time: 669 ms

    669 ms

    Scripts block taps and scrolling for 669 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 5 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix69
  • Page weight: 22.0 MB in 474 requests

    22.0 MB

    Your homepage downloads 22.0 MB in 474 requests on a phone: media 14.8 MB (3), images 4.1 MB (56) and scripts 1.3 MB (87). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    2025-12-01-PDPAlchemyforArmeniaArtboard15.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).

  • 7 images below the first screen load straight away

    7 images further down the page (263 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.2 g of CO₂ per visit

    6.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.22 g of CO₂e: 746.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

11 to fixGoogle 8787
  • 13 text elements with low contrast

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

  • Scrollable region must have keyboard access (12 elements)

    Scrollable region must have keyboard access: 12 elements on the page fail this check, rated serious by axe-core.

  • Form elements should have a visible label (3 elements)

    Form elements should have a visible label: 3 elements on the page fail this check, rated serious by axe-core.

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • 25 images without alt text

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

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

  • 13 links without text

    13 visible links have no text or label, so screen readers cannot say where they go.

  • 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. (1 element).

1 checks passed
  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 10 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 8583
  • Title is short (15 characters)

    Your title is only 15 characters: “Metal Alchemist”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (316 characters)

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 141 internal links, 6 external

    The homepage links to 141 pages on metalalchemist.com and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Because if you’re going to wear something beautiful, it might as well be powerful, too.”.

  • Canonical URL set

    The canonical URL is https://metalalchemist.com/.

  • 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://metalalchemist.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://metalalchemist.com/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 (1,208 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://metalalchemist.com/collections/best-selling-collection and https://metalalchemist.com/collections/cuffs use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://metalalchemist.com/collections/best-selling-collection and https://metalalchemist.com/collections/cuffs 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 54 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 2 pages that loaded have a meta description.

  • 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 2 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    22 of 26 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 493 words of copy

    The homepage carries about 493 words of visible text.

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 NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “SHOP ALL”, “SHOP ALL Show menu” and “Learn more”.

  • 27 short forms

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

  • Analytics in place

    Analytics detected: Hotjar.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 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.

  • 42 other companies contacted

    Loading the homepage contacts 42 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 metalalchemist.com, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Timesact Pre Order · Freegifts · Upcart · Mobilemenu · b-cdn.net · rise-ai.com · hextom.com · bogos.io

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
Analytics
Hotjar
Hosting
Shopify

Company

Headquarters
Newport

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on metalalchemist.com, including 20 speed issues, 4 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