Website review, no card needed

odfashion.de logo

odfashion.de website review

Visit site (opens in a new tab)Reviewed 11 November 202625 issues · 72 checks

This review found 25 issues worth fixing on odfashion.de, 6 of them high impact, across 72 checks. The most urgent: render-blocking 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

Real-visitor load time (LCP)75th percentile, phones
1.0 s767 msAug 29Nov 7933 ms
Show as table
DateReal-visitor load time (LCP)
Aug 29, 2026804 ms
Sep 5, 2026794 ms
Sep 12, 2026804 ms
Sep 19, 2026864 ms
Sep 26, 2026879 ms
Oct 17, 2026863 ms
Oct 24, 2026903 ms
Oct 31, 2026977 ms
Nov 7, 2026933 ms
Real-visitor tap response (INP)75th percentile, phones
129 ms88 msSep 5Oct 31106 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 202693 ms
Sep 12, 2026102 ms
Sep 19, 2026104 ms
Sep 26, 2026112 ms
Oct 24, 2026124 ms
Oct 31, 2026106 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 odfashion.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. odfashion.de at 0.4 s0.4 s
  2. odfashion.de at 0.8 s0.8 s
  3. odfashion.de at 1.1 s1.1 s
  4. odfashion.de at 1.5 s1.5 s
  5. odfashion.de at 1.9 s1.9 s
  6. odfashion.de at 2.3 s2.3 s
  7. odfashion.de at 2.6 s2.6 s
  8. odfashion.de at 3.0 s3.0 s

Speed

5 to fix79
  • Render-blocking requests

    1.6 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 79

    79/100

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

  • Improve image delivery

    500 ms · 144 KiB

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

  • Shopify adds 313 ms

    313 ms

    Shopify costs a phone 313 ms of main-thread work and 528 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 · 60 KiB

    About 60 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.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, Cloudflare CDN and shop.app), adding 560 KiB and 328 ms of main-thread time.

  • Reduce unused JavaScript

    244 KiB

    About 244 KiB of JavaScript is downloaded but never used on this page.

  • 1 long task on the main thread

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

  • Use efficient cache lifetimes

    5 KiB

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

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

  • Server response: 69 ms

    69 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Arbeitskleidung von OD Sport & Fashion”.

  • Largest content (LCP) got 20% slower for real visitors

    +20%

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

  • Time to Interactive: 5.9 s

    5.9 s

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 93 ms to 106 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: 0.9 s

    0.9 s

    Real visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 337 ms

    337 ms

    Real visitors wait 337 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 13 ms

    13 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.0 MB in 203 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 203 requests on a phone: scripts 739 KiB (95), other files 694 KiB (77) and images 265 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    56 KiB

    1 image is downloaded at several times the size a phone draws it, for example od-home-ChatGPT_Image_8._Juli_2026_14_47_37.jpg at 1,520 px wide, shown at 390 px. Resized copies would save about 56 KiB.

  • About 0.6 g of CO₂ per visit

    0.57 g

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

1 to fixGoogle 10099
  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

    Your title is only 23 characters: “Home | OD Sport&Fashion”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“OD Sport&Fashion” and “Kleidung, die verbindet.”). One clear main headline is easier for people and search engines.

  • Meta description is long (181 characters)

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

  • 158 internal links, 6 external

    The homepage links to 158 pages on odfashion.de and 6 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://odfashion.de/.

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), 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 (535 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://odfashion.de/pages/kollektionen, https://odfashion.de/collections/schornsteinfeger-t-shirts, https://odfashion.de/collections/schornsteinfeger-jacken-westen and https://odfashion.de/collections/schornsteinfeger-accessoires have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://odfashion.de/pages/kollektionen, https://odfashion.de/collections/schornsteinfeger-t-shirts, https://odfashion.de/collections/schornsteinfeger-jacken-westen and https://odfashion.de/collections/schornsteinfeger-accessoires 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 51 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

Best practices

1 to fixGoogle 10084
  • 2 broken images

    2 images failed to load on a phone, for example https://odfashion.de/.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 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 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.

  • Only about 236 words

    The homepage has only about 236 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 11 cookies set on arrival

    11

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 odfashion.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

Ymq B2b Wholesale Solution · Zepto Product Personalizer · Powerful Form Builder · Fulbix Variant Images · Ymq Product Options · Tek Labs Gifts Upsell

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 25 issues on odfashion.de, including 8 speed issues, 3 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