Website review, no card needed

k-trinkl.de logo

k-trinkl.de website review

Visit site (opens in a new tab)Reviewed 16 November 202624 issues · 73 checks

This review found 24 issues worth fixing on k-trinkl.de, 7 of them high impact, across 73 checks. The most urgent: 2 text elements with low contrast. 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 k-trinkl.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. k-trinkl.de at 0.7 s0.7 s
  2. k-trinkl.de at 1.4 s1.4 s
  3. k-trinkl.de at 2.1 s2.1 s
  4. k-trinkl.de at 2.8 s2.8 s
  5. k-trinkl.de at 3.5 s3.5 s
  6. k-trinkl.de at 4.2 s4.2 s
  7. k-trinkl.de at 4.9 s4.9 s
  8. k-trinkl.de at 5.6 s5.6 s

Speed

2 to fix69
  • Mobile performance score: 69

    69/100

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

  • Use efficient cache lifetimes

    450 ms · 520 KiB

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

  • Font display

    200 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Improve image delivery

    147 KiB

    2 images could be 147 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    73 KiB

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

  • Reduce unused CSS

    62 KiB

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

  • Legacy JavaScript

    8 KiB

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

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

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 103 ms

    103 ms

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

Core Web Vitals

3 to fix67
  • Cumulative Layout Shift: 1

    1

    The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 6.6 s

    6.6 s

    Visually, the page fills in at 6.6 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.

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Katharina Trinkl Fotografin”.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.2 s

    1.2 s

    The page is fully interactive after 1.2 s.

Images and page weight

2 to fix86
  • An image on the first screen is lazy-loaded

    Titelbild_Hochzeit_See-oz00ljdh6a9fssoe5juy9fvr41doykxv01yv3 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).

  • 1 image far larger than shown

    22 KiB

    1 image is downloaded at several times the size a phone draws it, for example Titelbild_Hochzeit_See-oz00ljdh6a9fssoe5juy9fvr41doykxv01yv3 at 1,200 px wide, shown at 370 px. Resized copies would save about 22 KiB.

  • 1 image in older formats

    1 image (154 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 0.2 g of CO₂ per visit

    0.20 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.20 g of CO₂e: 24.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Page weight: 736 KiB in 21 requests

    736 KiB

    Your homepage downloads 736 KiB in 21 requests on a phone: images 268 KiB (3), scripts 197 KiB (11) and fonts 183 KiB (2). That is a lean page.

Accessibility

5 to fixGoogle 8993
  • 2 text elements with low contrast

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

  • Links look like plain text

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

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

  • 4 links without text

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • Structured data has 3 problems

    Structured data found (LocalBusiness, Organization, SiteNavigationElement and WebSite) but with 3 problems, for example “LocalBusiness: missing name”.

  • 50 internal links, 3 external

    The homepage links to 50 pages on k-trinkl.de and 3 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Echte Momente, natürliche Bilder und ganz viel Persönlichkeit: Fotografin in Augsburg für Businessportraits, Familien, …”.

  • One H1 headline

    Your main headline reads: “K. Trinkl Fotografin - Hochzeiten - Portraits - Businessfotos”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Katharina Trinkl Fotografin | Portrait, Hochzeit, Businessfotos”.

  • Canonical URL set

    The canonical URL is https://www.k-trinkl.de/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.k-trinkl.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.k-trinkl.de/llms.txt (1 KiB, 7 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.k-trinkl.de/businessfotografie and https://www.k-trinkl.de/business all use the title “Businessfotografie”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.k-trinkl.de/businessfotografie and https://www.k-trinkl.de/business use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.k-trinkl.de/businessfotografie, whose canonical is https://www.k-trinkl.de/business. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages with very little text

    https://www.k-trinkl.de/paare-portrait and https://www.k-trinkl.de/kontakt have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 7 pages slow to respond

    https://www.k-trinkl.de/businessfotografie, https://www.k-trinkl.de/hochzeit, https://www.k-trinkl.de/paare-portrait, https://www.k-trinkl.de/babybauch-newborn, https://www.k-trinkl.de/familie-kids and https://www.k-trinkl.de/wie-ich-arbeite and 1 other took over 3 s to send their HTML from our server.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

1 checks passed
  • 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 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 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.

  • Only about 184 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

3 checks passed
  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 k-trinkl.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KG

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on k-trinkl.de, including 5 speed issues, 1 SEO issue 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