Programmable

Website review, no card needed

lspnet.de logo

lspnet.de website review

Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 77 checks

This review found 31 issues worth fixing on lspnet.de, 9 of them high impact, across 77 checks. The most urgent: form elements must have labels (1 element). 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

Site score

74C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
970 ms831 msMay 23Nov 7931 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026874 ms
May 30, 2026887 ms
Jun 6, 2026905 ms
Jun 13, 2026925 ms
Jun 20, 2026925 ms
Jun 27, 2026933 ms
Jul 4, 2026927 ms
Jul 11, 2026918 ms
Jul 18, 2026923 ms
Jul 25, 2026906 ms
Aug 1, 2026899 ms
Aug 8, 2026884 ms
Aug 15, 2026859 ms
Aug 22, 2026848 ms
Aug 29, 2026847 ms
Sep 5, 2026863 ms
Sep 12, 2026894 ms
Sep 19, 2026920 ms
Sep 26, 2026949 ms
Oct 3, 2026954 ms
Oct 10, 2026947 ms
Oct 17, 2026945 ms
Oct 24, 2026923 ms
Oct 31, 2026926 ms
Nov 7, 2026931 ms
Real-visitor tap response (INP)75th percentile, phones
99 ms92 msMay 23Nov 793 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202697 ms
May 30, 202697 ms
Jun 6, 202697 ms
Jun 13, 202697 ms
Jun 20, 202697 ms
Jun 27, 202698 ms
Jul 4, 202698 ms
Jul 11, 202697 ms
Jul 18, 202697 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202695 ms
Aug 22, 202695 ms
Aug 29, 202695 ms
Sep 5, 202695 ms
Sep 12, 202695 ms
Sep 19, 202695 ms
Sep 26, 202695 ms
Oct 3, 202695 ms
Oct 10, 202695 ms
Oct 17, 202694 ms
Oct 24, 202694 ms
Oct 31, 202693 ms
Nov 7, 202693 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

de.wikipedia.org (opens in a new tab)
Full-page screenshot of lspnet.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lspnet.de at 0.6 s0.6 s
  2. lspnet.de at 1.2 s1.2 s
  3. lspnet.de at 1.7 s1.7 s
  4. lspnet.de at 2.3 s2.3 s
  5. lspnet.de at 2.9 s2.9 s
  6. lspnet.de at 3.5 s3.5 s
  7. lspnet.de at 4.1 s4.1 s
  8. lspnet.de at 4.7 s4.7 s

Speed

3 to fix59

  • Mobile performance score: 59

    59/100

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

  • Reduce unused JavaScript

    450 ms · 90 KiB

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

  • Render-blocking requests

    450 ms

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

  • Use efficient cache lifetimes

    150 ms · 59 KiB

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

  • Reduce unused CSS

    150 ms · 40 KiB

    About 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

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

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (wikimedia.org), adding 16 KiB and 1 ms of main-thread time.

2 checks passed

  • Main-thread work: 0.6 s

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

  • Server response: 35 ms

    35 ms

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

Core Web Vitals

6 to fix100

  • Cumulative Layout Shift: 0.441

    0.441

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Möchtest du ein angenehmeres Leseerlebnis und Zugang zu exk…”. Most of its time is element render delay (2.3 s).

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • Time to Interactive: 4.5 s

    4.5 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

7 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 INP: 93 ms

    93 ms

    Real visitors wait 93 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.

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 513 ms

    513 ms

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

  • Total Blocking Time: 24 ms

    24 ms

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

Images and page weight

100

  • About 0.1 g of CO₂ per visit

    0.11 g

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

4 checks passed

  • Page weight: 388 KiB in 32 requests

    388 KiB

    Your homepage downloads 388 KiB in 32 requests on a phone: scripts 285 KiB (7), HTML 36 KiB (1) and images 34 KiB (18). That is a lean page.

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

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8994

  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • 6 text elements with low contrast

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

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

  • 47 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

2 checks passed

  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (29 characters)

    Your title is only 29 characters: “Internet Protocol – Wikipedia”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://de.wikipedia.org/w/rest.php/site/v1/sitemap/0, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 139 internal links, 128 external

    The homepage links to 139 pages on lspnet.de and 128 external pages.

4 checks passed

  • One H1 headline

    Your main headline reads: “Internet Protocol”.

  • Canonical URL set

    The canonical URL is https://de.wikipedia.org/wiki/Internet_Protocol.

  • Structured data in place

    Structured data found: Article.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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://de.wikipedia.org/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 (1,863 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix50

  • 1 linked page is broken

    Your homepage links to https://de.wikipedia.org/wiki/Spezial:%C3%84nderungen_an_verlinkten_Seiten/Internet_Protocol, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 linked pages hidden from search

    https://de.wikipedia.org/wiki/Spezial:Spezialseiten, https://de.wikipedia.org/wiki/Spezial:Letzte_%C3%84nderungen, https://de.wikipedia.org/wiki/Spezial:Suche, https://de.wikipedia.org/wiki/Diskussion:Internet_Protocol and https://de.wikipedia.org/wiki/Spezial:Linkliste/Internet_Protocol are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://de.wikipedia.org/wiki/Wikipedia:Hauptseite and https://de.wikipedia.org/w/index.php all use the title “Wikipedia – Die freie Enzyklopädie”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://de.wikipedia.org/wiki/Wikipedia:Hauptseite, https://de.wikipedia.org/wiki/Portal:Wikipedia_nach_Themen, https://de.wikipedia.org/wiki/Spezial:Zuf%C3%A4llige_Seite, https://de.wikipedia.org/wiki/Spezial:Spezialseiten, https://de.wikipedia.org/wiki/Wikipedia:Beteiligen and https://de.wikipedia.org/wiki/Hilfe:Neuen_Artikel_anlegen and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://de.wikipedia.org/wiki/Spezial:Zuf%C3%A4llige_Seite, whose canonical is https://de.wikipedia.org/wiki/Robert_Mauvoisin. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

2 checks passed

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093

  • 135 small tap targets

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

  • 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

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 206 words

    The homepage has only about 206 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.

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.

  • 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 lspnet.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
MediaWiki 1.48.0-wmf.1
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on lspnet.de, including 9 speed issues, 4 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