Website review, no card needed
falter.at website review
Visit site (opens in a new tab)Reviewed 19 October 202627 issues · 82 checks
This review found 27 issues worth fixing on falter.at, 4 of them high impact, across 82 checks. The most urgent: robots.txt blocks 6 AI answer engine crawlers. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.4 s |
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 94 ms |
| May 2, 2026 | 94 ms |
| May 9, 2026 | 94 ms |
| May 16, 2026 | 94 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 100 ms |
| Jul 11, 2026 | 97 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 99 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 101 ms |
| Sep 26, 2026 | 102 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 102 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
Speed
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 87). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
250 ms · 639 KiB10 images could be 639 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused JavaScript
450 ms · 200 KiBAbout 200 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
401 KiB11 files are served with short cache lifetimes, so returning visitors download them again (401 KiB).
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 682 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,692 HTML elements
The page has 1,692 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
250 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
3 third-party services on the page
3 third-party services load with your homepage (Didomi, Adition and Fathom Analytics), adding 242 KiB and 176 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 152 ms. During a long task the page ignores taps.
Legacy JavaScript
43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need.
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 87 but mobile only 53. A gap that wide usually means heavy scripts and images that hit phones hardest.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 275 ms
275 msYour server sent the HTML in 275 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 0.656
0.656The layout shifts by 0.656 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.7 s
3.7 sYour largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “(Dieser ALT-Text wurde mithilfe von KI erstellt) Person häl…”.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 94 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.6 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: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 465 ms
465 msReal visitors wait 465 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 193 ms
193 msScripts block the page for only 193 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.1 MB in 58 requests
2.1 MBYour homepage downloads 2.1 MB in 58 requests on a phone: images 826 KiB (22), scripts 725 KiB (17) and fonts 371 KiB (6). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
46 KiB1 image is downloaded at several times the size a phone draws it, for example denkmal-collage.jpg at 390 px wide, shown at 90 px. Resized copies would save about 46 KiB.
1 image in older formats
1 image (127 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.
About 0.6 g of CO₂ per visit
0.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 71.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
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.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 91 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
79 H1 headlines
There are 79 <h1> headlines (“Wie das Kopftuchverbot an Schulen umgesetzt wird”, “Heute aktuell” and “Ein Tag im Leben eines überprivilegierten Innenst…”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
145 internal links, 50 external
The homepage links to 145 pages on falter.at and 50 external pages.
6 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “News zu Politik, Medien, Kultur, Stadtleben, Natur sowie Österreichs größtes Veranstaltungsprogramm, Podcasts & Newslet…”.
Title: 58 characters
Your title is a healthy 58 characters: “FALTER | Unabhängiger Journalismus aus Österreich - FALTER”.
Canonical URL set
The canonical URL is https://www.falter.at/.
Structured data in place
Structured data found: Organization.
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://cdn.falter.at/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.falter.at/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (2,758 words), so crawlers that don't run JavaScript still read it.
Other pages
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.falter.at/aktuelle-ausgabe, whose canonical is https://www.falter.at/zeitung/ausgabe/202642. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.falter.at/suche has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.falter.at/aktuelle-ausgabe, https://www.falter.at/suche, https://www.falter.at/aktuell and https://www.falter.at/heute-in-wien took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 114 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
41 small tap targets
41 of 115 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 2,144 words of copy
The homepage carries about 2,144 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP”.
3 calls to action
The homepage has 3 calls to action, for example “Shop”.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Fathom.
Privacy and tracking
7 cookies set on arrival
7Opening the homepage sets 7 cookies (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: Didomi
A consent management tool (Didomi) 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 falter.at, 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 | Fathom
Company
- Founded
- 1977
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 falter.at, including 11 speed issues, 2 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.