Website review, no card needed
nuessing.de website review
Visit site (opens in a new tab)Reviewed 25 October 202635 issues · 75 checks
This review found 35 issues worth fixing on nuessing.de, 17 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
2.8 s · 2.4 MB92 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
Render-blocking requests
2.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Font display
1.7 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.7 s).
5,175 HTML elements
The page has 5,175 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
950 ms · 232 KiB7 images could be 232 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 76). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 141 KiBAbout 141 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Reduce unused JavaScript
600 ms · 203 KiBAbout 203 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 116 ms. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (findologic.com), adding 141 KiB and 28 ms of main-thread time.
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, 390 ms of it running JavaScript. That is comfortably low.
Server response: 225 ms
225 msYour server sent the HTML in 225 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.9 s
7.9 sYour largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (3.3 s).
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
44 images without width and height
44 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.
2 checks passed
Cumulative Layout Shift: 0.07
0.07The layout barely moves while loading (CLS 0.07, good is under 0.1).
Total Blocking Time: 68 ms
68 msScripts block the page for only 68 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
amica-teaser-bild-2.png weighs 15.7 MB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
15.4 MB3 images are downloaded at several times the size a phone draws them, for example amica-teaser-bild-2.png at 4,314 px wide, shown at 330 px. Resized copies would save about 15.4 MB.
7 images in older formats
7 images (16.5 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.
Page weight: 2.5 MB in 96 requests
2.5 MBYour homepage downloads 2.5 MB in 96 requests on a phone: images 1.6 MB (69), scripts 395 KiB (18) and fonts 320 KiB (3). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (171 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 85.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 68 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (11 characters)
Your title is only 11 characters: “Nüßing Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (24 characters)
Your meta description is only 24 characters: “Der Türgriff Online-Shop”. 70 to 160 characters is enough to sell the click.
No XML sitemap
No XML sitemap at https://www.nuessing.de/sitemapfeed, so Google discovers your pages only by following links.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
218 internal links, 10 external
The homepage links to 218 pages on nuessing.de and 10 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.nuessing.de/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No Organization structured data
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.
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 (4,053 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://nuessing.de/llms.txt (7 KiB, 10 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://nuessing.de/address, which answers with an error. Visitors hit a dead end and search engines drop it.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 103 found) and read each the way a search engine does.
6 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 7 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 7 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Loading the stylesheet 'https://cdn.findologic.com/login.symfony/web/autocomplete/08B967FA83D6277196B586339023FF13/fl_s…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 440 words of copy
The homepage carries about 440 words of visible text.
1 checks passed
6 short forms
6 short forms (3 fields at most) are right on the homepage.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 nuessing.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on nuessing.de, including 13 speed issues, 6 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.