Website review, no card needed

tema.de logo

tema.de website review

Visit site (opens in a new tab)Reviewed 25 October 202625 issues · 74 checks

This review found 25 issues worth fixing on tema.de, 6 of them high impact, across 74 checks. The most urgent: font display. 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

Full-page screenshot of tema.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tema.de at 0.5 s0.5 s
  2. tema.de at 1.0 s1.0 s
  3. tema.de at 1.5 s1.5 s
  4. tema.de at 2.0 s2.0 s
  5. tema.de at 2.5 s2.5 s
  6. tema.de at 3.1 s3.1 s
  7. tema.de at 3.6 s3.6 s
  8. tema.de at 4.1 s4.1 s

Speed

6 to fix93
  • Font display

    2.0 s

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

  • Use efficient cache lifetimes

    1.1 s · 838 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Improve image delivery

    2.3 MB

    5 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    450 ms · 95 KiB

    About 95 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

    300 ms · 52 KiB

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

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 76 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • 1 third-party service on the page

    1 third-party service load with your homepage (wbstlds.com), adding 1 KiB and 0 ms of main-thread time.

3 checks passed
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93 (desktop: 98). That is in Google's “good” band (90 and up).

  • Main-thread work: 1.2 s

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

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

3 to fix95
  • 45 images without width and height

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

  • Speed Index: 4.8 s

    4.8 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TECHNO­LOGIE”. Most of its time is element render delay (1.7 s).

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

4 checks passed
  • Time to Interactive: 2.9 s

    2.9 s

    The page is fully interactive after 2.9 s.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.015

    0.015

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

  • Total Blocking Time: 18 ms

    18 ms

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

Images and page weight

1 to fix70
  • Page weight: 10.7 MB in 60 requests

    10.7 MB

    Your homepage downloads 10.7 MB in 60 requests on a phone: images 9.9 MB (30), fonts 575 KiB (7) and scripts 162 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (33 KiB) is 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.

  • 1 image below the first screen load straight away

    1 image further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.0 g of CO₂ per visit

    3.03 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.03 g of CO₂e: 363.9 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 9296
  • 3 text elements with low contrast

    3 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 (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • Title is short (29 characters)

    Your title is only 29 characters: “TEMA Technologie Marketing AG”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 H1 headlines

    There are 4 <h1> headlines (“TECHNO­LOGIE MARKETING.”, “BY TEMA” and “LET’S TALK IDEAS”). One clear main headline is easier for people and search engines.

  • Meta description is long (185 characters)

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

  • 30 internal links, 27 external

    The homepage links to 30 pages on tema.de and 27 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness, Organization and ProfessionalService.

  • 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://www.tema.de/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix81
  • 4 pages share 2 titles

    https://www.tema.de/cores/content-marketing and https://www.tema.de/cores all use the title “Content Marketing”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.tema.de/en and https://www.tema.de/work have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.tema.de/cores/content-marketing and https://www.tema.de/cores use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.tema.de/areas/conference-partnership-model, whose canonical is https://www.tema.de/cores/conference-partnership-model. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://www.tema.de/areas took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 9687
  • 4 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 21 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 536 words of visible text.

5 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 1 short form

    A short form (6 fields at most) is right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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 other company contacted

    Loading the homepage contacts 1 host 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 tema.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on tema.de, including 9 speed issues, 3 SEO issues and 3 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