Website review, no card needed

colognewatchdiamond.de logo

colognewatchdiamond.de website review

Visit site (opens in a new tab)Reviewed 16 November 202630 issues · 74 checks

This review found 30 issues worth fixing on colognewatchdiamond.de, 7 of them high impact, across 74 checks. The most urgent: page weight: 6.2 MB in 141 requests. 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 colognewatchdiamond.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. colognewatchdiamond.de at 0.6 s0.6 s
  2. colognewatchdiamond.de at 1.2 s1.2 s
  3. colognewatchdiamond.de at 1.9 s1.9 s
  4. colognewatchdiamond.de at 2.5 s2.5 s
  5. colognewatchdiamond.de at 3.1 s3.1 s
  6. colognewatchdiamond.de at 3.7 s3.7 s
  7. colognewatchdiamond.de at 4.3 s4.3 s
  8. colognewatchdiamond.de at 5.0 s5.0 s

Speed

5 to fix88
  • Improve image delivery

    1.3 MB

    21 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 88

    88/100

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

  • Reduce unused JavaScript

    450 ms · 107 KiB

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

  • Render-blocking requests

    500 ms

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

  • 1,700 HTML elements

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Klaviyo, Shopify and nfcube.com), adding 198 KiB and 114 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    85 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • Use efficient cache lifetimes

    10 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (10 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

4 to fix95
  • Speed Index: 5.8 s

    5.8 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Time to Interactive: 5.4 s

    5.4 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Entdecken Sie unsere große Auswahl an Marken-,Diamant- und …”. Most of its time is element render delay (2.6 s).

  • 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
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 47 ms

    47 ms

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

Images and page weight

2 to fix64
  • Page weight: 6.2 MB in 141 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 141 requests on a phone: media 3.4 MB (1), images 1.6 MB (25) and other files 631 KiB (59). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    cd-hermes-banner-mobile-1-kompressed.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).

  • About 1.8 g of CO₂ per visit

    1.77 g

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

4 to fixGoogle 9193
  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 2 images without alt text

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

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

    All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate 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. (4 elements).

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 6152
  • Page is set to noindex

    The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (21 characters)

    Your title is only 21 characters: “Cologne Watch Diamond”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Exklusiver Schmuck” and “Hermès Handtaschen”). One clear main headline is easier for people and search engines.

  • Meta description is long (213 characters)

    Your meta description is 213 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 134 internal links, 8 external

    The homepage links to 134 pages on colognewatchdiamond.de and 8 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.colognewatchdiamond.de/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.colognewatchdiamond.de/sitemap.xml.

AI search readiness

100
4 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,030 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.colognewatchdiamond.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 15 linked pages hidden from search

    https://www.colognewatchdiamond.de/collections/schmuck, https://www.colognewatchdiamond.de/collections/goldschmuck, https://www.colognewatchdiamond.de/collections/diamant-schmuck, https://www.colognewatchdiamond.de/collections/bucherer, https://www.colognewatchdiamond.de/collections/bvlgari and https://www.colognewatchdiamond.de/collections/cartier and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 12 pages without a meta description

    https://www.colognewatchdiamond.de/collections/bucherer, https://www.colognewatchdiamond.de/collections/bvlgari, https://www.colognewatchdiamond.de/collections/cartier, https://www.colognewatchdiamond.de/collections/chopard, https://www.colognewatchdiamond.de/collections/piaget and https://www.colognewatchdiamond.de/collections/pomellato and 6 others 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 60 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 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 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    51 of 54 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 692 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Ebay Shop”.

  • 4 short forms

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 9 cookies set on arrival

    9

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 colognewatchdiamond.de, 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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Hulk Contact Form Builder · Instafeed · Noindexly · Page Speed Optimizer · Easy Tabs Product Tabs

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

Framework
Bootstrap
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 30 issues on colognewatchdiamond.de, including 9 speed issues, 5 SEO issues and 6 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