Website review, no card needed
funkeworks.de website review
Visit site (opens in a new tab)Reviewed 20 October 202627 issues · 73 checks
This review found 27 issues worth fixing on funkeworks.de, 8 of them high impact, across 73 checks. The most urgent: page weight: 4.7 MB in 70 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 147 ms |
| May 16, 2026 | 131 ms |
| May 23, 2026 | 127 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 118 ms |
| Jun 27, 2026 | 132 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 141 ms |
| Sep 5, 2026 | 125 ms |
| Sep 12, 2026 | 120 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.2 s
Speed
Mobile performance score: 79
79/100Your mobile performance score is 79 (desktop: 89). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 259 KiBAbout 259 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Improve image delivery
297 KiB10 images could be 297 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 third-party services on the page
3 third-party services load with your homepage (consentmanager.net, Google Tag Manager and Plausible), adding 419 KiB and 249 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 107 KiB4 files are served with short cache lifetimes, so returning visitors download them again (107 KiB).
Render-blocking requests
250 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Legacy JavaScript
100 ms · 8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 82 ms. During a long task the page ignores taps.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 342 ms of it running JavaScript. That is comfortably low.
Server response: 110 ms
110 msYour server sent the HTML in 110 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Auf Funkeworks.de und anderen Webseiten der FUNKE Works Gmb…”. Most of its time is element render delay (3.1 s).
Time to Interactive: 6.1 s
6.1 sThe page becomes fully interactive after 6.1 s. Good is under 3.8 s.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
3 checks passed
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 147 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 45 ms
45 msScripts block the page for only 45 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.7 MB in 70 requests
4.7 MBYour homepage downloads 4.7 MB in 70 requests on a phone: media 2.9 MB (4), images 1.1 MB (25) and scripts 562 KiB (34). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
41 KiB3 images are downloaded at several times the size a phone draws them, for example koeln-7f872871d7d81edf48131cb76ebed00fe104954f2ced47a0d73d65 at 900 px wide, shown at 269 px. Resized copies would save about 41 KiB.
About 1.3 g of CO₂ per visit
1.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.32 g of CO₂e: 158.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.funkeworks.de/sitemap.xml, 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 set, so this is minor.
22 internal links, 22 external
The homepage links to 22 pages on funkeworks.de and 22 external pages.
5 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Egal welche offenen Vakanzen Sie für Berufseinsteiger:innen haben – wir haben die geeigneten Produkte, mit denen Sie di…”.
One H1 headline
Your main headline reads: “Hi! Wir sind FUNKE Works.”.
Title: 47 characters
Your title is a healthy 47 characters: “FUNKE Works – Jobportale der FUNKE Mediengruppe”.
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.
AI search readiness
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.funkeworks.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
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,107 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without an H1
https://www.funkeworks.de/jobs, https://www.funkeworks.de/kontakt, https://www.funkeworks.de/jobs/472-sales-manager-m-w-d, https://www.funkeworks.de/jobs/16-sales-manager-m-w-d-b2b-schwerpunkt-agenturvertrieb, https://www.funkeworks.de/jobs/41-trainee-m-w-d-sales-vertrieb-fuer-azubiyo and https://www.funkeworks.de/jobs/307-sales-manager-m-w-d-b2b and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 10 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 10 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 912 words of copy
The homepage carries about 912 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Plausible.
Direct contact links
Visitors can reach you directly: 1 phone link and 6 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: consentmanager
A consent management tool (consentmanager) loads with the page.
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 funkeworks.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager | Plausible
- Hosting
- Heroku
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on funkeworks.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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.