Programmable

Website review, no card needed

noris.de logo

noris.de website review

Visit site (opens in a new tab)Reviewed 27 October 202619 issues · 71 checks

This review found 19 issues worth fixing on noris.de, 7 of them high impact, across 71 checks. The most urgent: render-blocking requests. 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

79C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
5.5 s3.2 sMay 9Oct 244.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.6 s
May 16, 20264.5 s
May 23, 20264.8 s
May 30, 20264.8 s
Jun 6, 20265.2 s
Jun 13, 20265.0 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.7 s
Jul 18, 20264.4 s
Jul 25, 20264.5 s
Aug 1, 20264.6 s
Aug 8, 20264.5 s
Aug 15, 20264.7 s
Aug 22, 20265.2 s
Aug 29, 20265.1 s
Sep 5, 20265.1 s
Sep 12, 20265.1 s
Sep 19, 20264.3 s
Sep 26, 20264.2 s
Oct 3, 20263.8 s
Oct 10, 20264.0 s
Oct 17, 20264.3 s
Oct 24, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
132 ms97 msMay 9Oct 24103 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026114 ms
May 16, 2026119 ms
May 23, 2026116 ms
May 30, 2026120 ms
Jun 6, 2026126 ms
Jun 13, 2026121 ms
Jun 20, 2026127 ms
Jun 27, 2026114 ms
Jul 4, 2026113 ms
Jul 11, 2026117 ms
Jul 18, 2026121 ms
Jul 25, 2026127 ms
Aug 1, 2026128 ms
Aug 8, 2026126 ms
Aug 15, 2026112 ms
Aug 22, 2026107 ms
Aug 29, 2026103 ms
Sep 5, 2026109 ms
Sep 12, 2026112 ms
Sep 19, 2026109 ms
Sep 26, 2026113 ms
Oct 3, 2026104 ms
Oct 10, 2026101 ms
Oct 17, 2026110 ms
Oct 24, 2026103 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

www.noris.de (opens in a new tab)
Full-page screenshot of noris.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. noris.de at 1.8 s1.8 s
  2. noris.de at 3.5 s3.5 s
  3. noris.de at 5.3 s5.3 s
  4. noris.de at 7.0 s7.0 s
  5. noris.de at 8.8 s8.8 s
  6. noris.de at 10.5 s10.5 s
  7. noris.de at 12.3 s12.3 s
  8. noris.de at 14.0 s14.0 s

Speed

3 to fix64

  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 77 KiB

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

  • Reduce unused JavaScript

    150 ms · 111 KiB

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

  • 2 long tasks on the main thread

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

  • Improve image delivery

    22 KiB

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

  • Legacy JavaScript

    8 KiB

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

  • Use efficient cache lifetimes

    6 KiB

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

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

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

  • Server response: 122 ms

    122 ms

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

Core Web Vitals

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

  • Speed Index: 17.0 s

    17.0 s

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

  • Largest Contentful Paint: 6.7 s

    6.7 s

    Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SOUVERÄNE IT-INFRASTRUKTUR AUS DEUTSCHLAND Vom IT-Whitespac…”. Most of its time is resource load delay (10.7 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.1 s

    2.1 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Time to Interactive: 6.9 s

    6.9 s

    The page becomes fully interactive after 6.9 s. Good is under 3.8 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.

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

4 checks passed

  • Real-user INP: 110 ms

    110 ms

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

  • Cumulative Layout Shift: 0.009

    0.009

    The layout barely moves while loading (CLS 0.009, good is under 0.1).

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

1 to fix93

  • 6 images below the first screen load straight away

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

  • About 0.3 g of CO₂ per visit

    0.34 g

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

3 checks passed

  • Page weight: 1.2 MB in 131 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 131 requests on a phone: images 442 KiB (17), scripts 332 KiB (52) and fonts 234 KiB (3). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (32 elements)

    All page content should be contained by landmarks: 32 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.

2 checks passed

  • Every image has alt text

    All 40 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290

  • Title is short (28 characters)

    Your title is only 28 characters: “Ihr Premium IT-Dienstleister”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • 217 internal links, 7 external

    The homepage links to 217 pages on noris.de and 7 external pages.

7 checks passed

  • Meta description: 131 characters

    Your meta description is 131 characters: “Ihr Premium IT-Dienstleister in Deutschland für Managed Services, Cloud, Network & Security, Colocation und hochsichere…”.

  • One H1 headline

    Your main headline reads: “Souveräne IT-Infrastruktur aus Deutschland”.

  • Canonical URL set

    The canonical URL is https://www.noris.de/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://noris.de/sitemap_index.xml.

AI search readiness

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

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix75

  • 3 linked pages are broken

    Your homepage links to https://www.noris.de/it-services/managed-services-application/e-commerce-outsourcing, https://www.noris.de/it-services/managed-services-application/devops-service and https://www.noris.de/it-services/managed-services-application/managed-azure-services, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 102 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 12 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 12 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    18 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80

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

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

    The homepage carries about 753 words of visible text.

4 checks passed

  • 1 call to action

    The homepage has 1 call to action, for example “Download-Bereich”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

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

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 noris.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
Analytics
Google Analytics | Google Tag Manager
Hosting
IT Service Provider located in Nuernberg, Germany

Company

Founded
1993
Headquarters
Nuremberg

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on noris.de, including 11 speed issues, 2 SEO issues and 1 conversion gap. 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