Website review, no card needed

din-notlicht.com logo

din-notlicht.com website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 81 checks

This review found 32 issues worth fixing on din-notlicht.com, 13 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
2.5 s1.8 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.4 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Oct 31, 20262.1 s
Nov 7, 20261.9 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
115 ms82 msMay 30Nov 1495 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026105 ms
Jun 6, 2026111 ms
Jun 13, 2026106 ms
Jun 20, 2026104 ms
Jun 27, 202697 ms
Jul 4, 202692 ms
Jul 11, 202693 ms
Jul 18, 202693 ms
Jul 25, 202693 ms
Aug 1, 202693 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202696 ms
Aug 29, 202694 ms
Sep 5, 202694 ms
Sep 12, 202688 ms
Sep 19, 202686 ms
Sep 26, 202689 ms
Oct 3, 202688 ms
Oct 10, 202688 ms
Oct 17, 202688 ms
Oct 24, 202688 ms
Oct 31, 202687 ms
Nov 7, 202688 ms
Nov 14, 202695 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 din-notlicht.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. din-notlicht.com at 0.5 s0.5 s
  2. din-notlicht.com at 0.9 s0.9 s
  3. din-notlicht.com at 1.4 s1.4 s
  4. din-notlicht.com at 1.8 s1.8 s
  5. din-notlicht.com at 2.3 s2.3 s
  6. din-notlicht.com at 2.7 s2.7 s
  7. din-notlicht.com at 3.2 s3.2 s
  8. din-notlicht.com at 3.6 s3.6 s

Speed

7 to fix59
  • Improve image delivery

    9.6 s · 2.9 MB

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

  • Render-blocking requests

    2.1 s

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

  • Reduce unused JavaScript

    1.1 s · 208 KiB

    About 208 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 59

    59/100

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

  • Use efficient cache lifetimes

    800 ms · 124 KiB

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

  • Reduce unused CSS

    750 ms · 167 KiB

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

  • Font display

    700 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Other Google APIs/SDKs), adding 171 KiB and 105 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

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

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 28.0 s

    28.0 s

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

  • Time to Interactive: 28.3 s

    28.3 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.151

    0.151

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

4 checks passed
  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 105 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 31 ms

    31 ms

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

Images and page weight

1 to fix70
  • Page weight: 7.4 MB in 68 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 68 requests on a phone: images 6.0 MB (36), fonts 741 KiB (6) and scripts 493 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (409 KiB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (225 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.09 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9592
  • 8 text elements with low contrast

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

  • 4 images without alt text

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • 28 automated accessibility rules passed

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

SEO

3 to fixGoogle 8292
  • No structured data

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

  • 1 link crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 94 internal links, 3 external

    The homepage links to 94 pages on din-notlicht.com and 3 external pages.

7 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “➠ 40 Jahre Erfahrung in Notbeleuchtung ➠ 100% Kundennähe, durch Partner Vorort ➠ Innovative Lösungen ➠ Entwicklung und …”.

  • One H1 headline

    Your main headline reads: “40 Jahre Erfahrung”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “din-Sicherheitstechnik | Wir sind Experten für Notlicht”.

  • Canonical URL set

    The canonical URL is https://din-notlicht.com/de-at/.

  • 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://din-notlicht.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://din-notlicht.com/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.

2 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 (694 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 6 pages share a meta description

    https://din-notlicht.com/de-at/produkte-service/leuchten, https://din-notlicht.com/de-at/produkte-service/systeme, https://din-notlicht.com/de-at/produkte-service/service-software, https://din-notlicht.com/de-at/produkte-service/anwendungen, https://din-notlicht.com/de-at/referenzen and https://din-notlicht.com/de-at/walk-of-din-innsbruck use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.

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

  • Every page has a meta description

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

Best practices

2 to fixGoogle 9291
  • 13 small tap targets

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

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 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 form on the homepage

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

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

    The homepage carries about 700 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics and Matomo.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 din-notlicht.com, 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
Analytics
Google Analytics
Hosting
Neue Medien Muennich GmbH

Hiring

Hiring
3 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on din-notlicht.com, including 16 speed issues, 3 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

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