nancykoth.de website review

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

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

4 third-party services load with your homepage (jimstatic.com, jimcdn.com and jimdo-server.com and others), adding 6.6 MB and 212 ms of main-thread time.

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

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

jimcdn.com costs a phone 3 ms of main-thread work and 6.3 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.

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

jimstatic.com costs a phone 208 ms of main-thread work and 330 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

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

17 images have no width and height attributes, so the layout jumps as each one loads.

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.

Your homepage downloads 6.7 MB in 58 requests on a phone: images 6.3 MB (39), scripts 235 KiB (6) and stylesheets 54 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

14 images (4.8 MB) are 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.

14 images further down the page (4.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

10 images are downloaded at several times the size a phone draws them, for example image.png at 1,000 px wide, shown at 320 px. Resized copies would save about 369 KiB.

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

8 buttons have no accessible name, so screen readers announce just “button”.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 28 characters: “Home - Fotografin Nancy Koth”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“FOTOGRAFIN IN GREVESMÜHLEN & UMGEBUNG” and “♡ Gut zu wissen ♡”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 36 pages on nancykoth.de and 2 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.nancykoth.de/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.

https://www.nancykoth.de/j/legal-guarantee and https://www.nancykoth.de/j/withdrawal are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.nancykoth.de/aktuelles/aktionen-minis, https://www.nancykoth.de/aktuelles/fotoausstellungen, https://www.nancykoth.de/kontakt/agb, https://www.nancykoth.de/2026/01/31/familien-mini-shootings-2026, https://www.nancykoth.de/j/privacy and https://www.nancykoth.de/j/legal-guarantee and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nancykoth.de/familienfotoshooting-schwerin-nancy-koth and https://www.nancykoth.de/portrait use the same meta description. A description written for each page earns more clicks.

https://www.nancykoth.de/aktuelles/fotoausstellungen has 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.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 380 words of visible text.

Opening the homepage sets 4 cookies, 3 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.