Programmable

Website review, no card needed

tracetronic.de logo

tracetronic.de website review

Visit site (opens in a new tab)Reviewed 2 November 202634 issues · 81 checks

This review found 34 issues worth fixing on tracetronic.de, 13 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
946 ms695 msMay 16Oct 31917 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026810 ms
May 23, 2026791 ms
May 30, 2026799 ms
Jun 6, 2026767 ms
Jun 13, 2026782 ms
Jun 20, 2026825 ms
Jun 27, 2026736 ms
Jul 4, 2026748 ms
Jul 11, 2026765 ms
Jul 18, 2026792 ms
Jul 25, 2026792 ms
Aug 1, 2026724 ms
Aug 8, 2026742 ms
Aug 15, 2026731 ms
Aug 22, 2026787 ms
Aug 29, 2026841 ms
Sep 5, 2026839 ms
Sep 12, 2026881 ms
Sep 19, 2026856 ms
Sep 26, 2026810 ms
Oct 3, 2026798 ms
Oct 10, 2026820 ms
Oct 17, 2026912 ms
Oct 24, 2026911 ms
Oct 31, 2026917 ms
Real-visitor tap response (INP)75th percentile, phones
112 ms77 msMay 16Oct 3195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202698 ms
May 23, 202694 ms
May 30, 202696 ms
Jun 6, 202687 ms
Jun 13, 202681 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202690 ms
Jul 18, 202690 ms
Aug 8, 202690 ms
Aug 15, 202695 ms
Aug 22, 2026101 ms
Aug 29, 2026108 ms
Sep 5, 2026105 ms
Sep 12, 2026100 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202686 ms
Oct 10, 202687 ms
Oct 17, 202692 ms
Oct 24, 202692 ms
Oct 31, 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

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

How it loaded on a phone

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

Speed

5 to fix49

  • Use efficient cache lifetimes

    3.8 s · 1.9 MB

    46 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

  • Render-blocking requests

    1.0 s

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

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused CSS

    900 ms · 197 KiB

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

  • Font display

    350 ms

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

  • Reduce unused JavaScript

    150 ms · 83 KiB

    About 83 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 206 ms. During a long task the page ignores taps.

  • Improve image delivery

    68 KiB

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

  • Document request latency

    34 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 2 third-party services on the page

    2 third-party services load with your homepage (trctrnc.de and kununu.com), adding 76 KiB and 23 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.9 s

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

  • Server response: 210 ms

    210 ms

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

Core Web Vitals

6 to fix100

  • Cumulative Layout Shift: 0.586

    0.586

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Software Testing. Simplified. The intelligence behind softw…”.

  • Speed Index: 5.7 s

    5.7 s

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

  • Time to Interactive: 5.9 s

    5.9 s

    The page becomes fully interactive after 5.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.

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 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: 95 ms

    95 ms

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

    0.7 s

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

  • Real-user TTFB: 321 ms

    321 ms

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100

  • 2 images in older formats

    2 images (223 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.

  • About 0.6 g of CO₂ per visit

    0.56 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 67.5 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: 2.0 MB in 51 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 51 requests on a phone: images 1,001 KiB (24), fonts 513 KiB (6) and stylesheets 217 KiB (2). That is a lean page.

  • 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

8 to fixGoogle 5383

  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • 14 text elements with low contrast

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

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • <object> elements must have alternative text (1 element)

    <object> elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

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

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

  • 8 links without text

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

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed

  • 30 automated accessibility rules passed

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

SEO

7 to fixGoogle 8265

  • No meta description

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

  • Title is short (11 characters)

    Your title is only 11 characters: “tracetronic”. 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.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

    No XML sitemap at https://www.tracetronic.de/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at tracetronic.de/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 169 internal links, 15 external

    The homepage links to 169 pages on tracetronic.de and 15 external pages.

2 checks passed

  • One H1 headline

    Your main headline reads: “Software Testing. Simplified.”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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://www.tracetronic.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.

2 checks passed

  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix83

  • 2 pages share a title

    / and https://www.tracetronic.de/plattform/editionen all use the title “tracetronic”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.tracetronic.de/plattform/one-cx, https://www.tracetronic.de/plattform/editionen, https://www.tracetronic.de/produkte/ecu-test, https://www.tracetronic.de/produkte/extras, https://www.tracetronic.de/produkte/trace-check and https://www.tracetronic.de/produkte/test-guide and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.tracetronic.de/plattform/one-cx, https://www.tracetronic.de/produkte/ecu-test, https://www.tracetronic.de/produkte/extras, https://www.tracetronic.de/produkte/trace-check, https://www.tracetronic.de/produkte/test-guide and https://www.tracetronic.de/produkte/scenario-architect and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 38 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

Google 100100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40

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

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 429 words of visible text.

1 checks passed

  • Analytics in place

    Analytics detected: Matomo.

Privacy and tracking

  • 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 tracetronic.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Matomo
Hosting
Akamai Cloud

Hiring

Hiring
9 open roles
Job board
careers page
Careers page
www.tracetronic.de/jobs/stellenangebote (opens in a new tab)

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on tracetronic.de, including 11 speed issues, 7 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