Programmable

Website review, no card needed

karriere.poco.de logo

karriere.poco.de website review

Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 79 checks

This review found 31 issues worth fixing on karriere.poco.de, 12 of them high impact, across 79 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

72C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.0 s898 msMay 9Oct 24933 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026951 ms
May 16, 2026942 ms
May 23, 2026952 ms
May 30, 2026947 ms
Jun 6, 2026950 ms
Jun 13, 2026950 ms
Jun 20, 2026914 ms
Jun 27, 2026915 ms
Jul 4, 2026922 ms
Jul 11, 2026920 ms
Jul 18, 2026938 ms
Jul 25, 2026960 ms
Aug 1, 2026954 ms
Aug 8, 2026983 ms
Aug 15, 2026997 ms
Aug 22, 2026968 ms
Aug 29, 20261.0 s
Sep 5, 2026963 ms
Sep 12, 2026951 ms
Sep 19, 2026957 ms
Sep 26, 2026977 ms
Oct 3, 20261.0 s
Oct 10, 2026994 ms
Oct 17, 2026987 ms
Oct 24, 2026933 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms79 msMay 9Oct 2486 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202684 ms
May 16, 202683 ms
May 23, 202684 ms
May 30, 202682 ms
Jun 6, 202680 ms
Jun 13, 202681 ms
Jun 20, 202682 ms
Jun 27, 202685 ms
Jul 4, 202685 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202688 ms
Aug 1, 202687 ms
Aug 8, 202685 ms
Aug 15, 202686 ms
Aug 22, 202683 ms
Aug 29, 202685 ms
Sep 5, 202686 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202686 ms
Oct 10, 202686 ms
Oct 17, 202686 ms
Oct 24, 202686 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

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

How it loaded on a phone

  1. karriere.poco.de at 0.9 s0.9 s
  2. karriere.poco.de at 1.7 s1.7 s
  3. karriere.poco.de at 2.6 s2.6 s
  4. karriere.poco.de at 3.4 s3.4 s
  5. karriere.poco.de at 4.3 s4.3 s
  6. karriere.poco.de at 5.1 s5.1 s
  7. karriere.poco.de at 6.0 s6.0 s
  8. karriere.poco.de at 6.8 s6.8 s

Speed

6 to fix57

  • Use efficient cache lifetimes

    5.3 s · 1.5 MB

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

  • Reduce unused JavaScript

    1.3 s · 222 KiB

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

  • Reduce unused CSS

    950 ms · 204 KiB

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

  • Mobile performance score: 57

    57/100

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

  • Minify JavaScript

    370 ms · 67 KiB

    67 KiB could be saved by minifying JavaScript.

  • concludis.de adds 134 ms

    134 ms

    concludis.de costs a phone 134 ms of main-thread work and 428 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cookiebot and concludis.de), adding 591 KiB and 280 ms of main-thread time.

  • Render-blocking requests

    250 ms

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

  • Improve image delivery

    134 KiB

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

  • Font display

    100 ms

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

  • 2 long tasks on the main thread

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

2 checks passed

  • Main-thread work: 1.1 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

4 to fix100

  • Largest Contentful Paint: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Möbeln Sie Ihre Karriere auf! Wer bereit ist, sich zu engag…”. Most of its time is resource load delay (6.2 s).

  • First Contentful Paint: 6.3 s

    6.3 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Time to Interactive: 10.4 s

    10.4 s

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

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 84 ms to 86 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 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 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: 87 ms

    87 ms

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

    0.6 s

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

  • Real-user TTFB: 293 ms

    293 ms

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

  • Cumulative Layout Shift: 0.009

    0.009

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

  • Total Blocking Time: 43 ms

    43 ms

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

Images and page weight

100

  • About 0.5 g of CO₂ per visit

    0.47 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.47 g of CO₂e: 56.7 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: 1.7 MB in 62 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 62 requests on a phone: scripts 660 KiB (31), images 528 KiB (5) and fonts 278 KiB (6). 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 8892

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 7 links without text

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

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

7 to fixGoogle 10067

  • Title is short (17 characters)

    Your title is only 17 characters: “Karriere bei POCO”. 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.

  • Meta description is short (17 characters)

    Your meta description is only 17 characters: “Karriere bei Poco”. 70 to 160 characters is enough to sell the click.

  • 5 H1 headlines

    There are 5 <h1> headlines (“Möbeln Sie Ihre Karriere auf!”, “Nichts Passendes für Sie dabei?” and “Job-Newsletter abonnieren, nichts mehr verpassen!”). One clear main headline is easier for people and search engines.

  • 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://karriere.poco.de/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • No X (Twitter) card tag

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

  • 52 internal links, 20 external

    The homepage links to 52 pages on karriere.poco.de and 20 external pages.

1 checks passed

  • Open Graph tags complete

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

AI search readiness

1 to fix81

  • 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://karriere.poco.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.

1 checks passed

  • Text is in the HTML

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

Other pages

3 to fix86

  • 2 pages share a title

    / and https://karriere.poco.de/component/concludis/jobad.html all use the title “Karriere bei POCO”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages share a meta description

    https://karriere.poco.de/arbeiten-bei-poco.html, https://karriere.poco.de/arbeiten-bei-poco/zentralen.html, https://karriere.poco.de/arbeiten-bei-poco/einrichtungsmaerkte.html, https://karriere.poco.de/arbeiten-bei-poco/logistikzentren.html, https://karriere.poco.de/einstieg-bei-poco.html and https://karriere.poco.de/bewerbungstipps.html and 2 others use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://karriere.poco.de/component/concludis/jobad.html and https://karriere.poco.de/component/concludis/jobmap have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://karriere.poco.de/component/concludis/jobad.html and https://karriere.poco.de/component/concludis/jobmap have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

5 checks passed

  • Linked pages load

    All 8 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 8 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33

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

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

    The homepage carries about 375 words of visible text.

1 checks passed

  • 1 short form

    A short form (5 fields at most) is right on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 3 other companies contacted

    Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed

  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • 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 karriere.poco.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
Joomla
Framework
jQuery
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 karriere.poco.de, including 10 speed issues, 7 SEO issues and 5 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