Website review, no card needed
bfi-stmk.at website review
Visit site (opens in a new tab)Reviewed 30 October 202630 issues · 73 checks
This review found 30 issues worth fixing on bfi-stmk.at, 15 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. 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
76C- #76,126 of 125,639 reviewed websitesbeats 35%
- #48,501 of 70,221 online storesbeats 26%
- #1,267 of 2,950 WooCommerce storesbeats 51%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 152 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 125 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 91 ms |
| Jun 27, 2026 | 89 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 86 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 86 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 85 ms |
| Oct 10, 2026 | 85 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 85 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.8 s
1.7 s
2.5 s
3.4 s
4.2 s
5.0 s
5.9 s
6.7 s
Speed
Use efficient cache lifetimes
7.3 s · 17.7 MB116 files are served with short cache lifetimes, so returning visitors download them again (17.7 MB).
Render-blocking requests
3.4 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused CSS
1.7 s · 341 KiBAbout 341 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
600 ms · 2.7 MB12 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused JavaScript
860 ms · 217 KiBAbout 217 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 860 ms faster on a phone.
Minify JavaScript
260 ms · 47 KiB47 KiB could be saved by minifying JavaScript.
Minify CSS
260 ms · 39 KiB39 KiB could be saved by minifying CSS.
1 third-party service on the page
1 third-party service load with your homepage (marketingsuite.info), adding 107 KiB and 52 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 305 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 29.5 s
29.5 sYour largest element takes 29.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 31.6 s
31.6 sThe page becomes fully interactive after 31.6 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.255
0.255The layout shifts by 0.255 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
40 images without width and height
40 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user INP: 112 ms
112 msReal visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 44% faster for real visitors
-44%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 152 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 46% faster for real visitors
-46%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 17.7 MB in 125 requests
17.7 MBYour homepage downloads 17.7 MB in 125 requests on a phone: images 8.5 MB (55), media 7.9 MB (4) and scripts 737 KiB (47). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.0 MB2 images are downloaded at several times the size a phone draws them, for example bfi-steiermark_digitale-services-e1771314942307-1920x960.jpg at 1,920 px wide, shown at 351 px. Resized copies would save about 1.0 MB.
16 images in older formats
16 images (7.8 MB) 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.
20 images below the first screen load straight away
20 images further down the page (6.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.0 g of CO₂ per visit
5.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.03 g of CO₂e: 603.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 checks passed
Every image has alt text
All 149 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
122 internal links, 14 external
The homepage links to 122 pages on bfi-stmk.at and 14 external pages.
8 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Das bfi Steiermark bietet vielfältige Aus- und Weiterbildungen, anerkannte Abschlüsse und persönliche Beratung. Für Ihr…”.
One H1 headline
Your main headline reads: “Vielfalt, die Sie weiterbringt”.
Title: 43 characters
Your title is a healthy 43 characters: “bfi Steiermark | Bildung. Freude inklusive.”.
Canonical URL set
The canonical URL is https://www.bfi-stmk.at/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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.bfi-stmk.at/sitemap_index.xml.
AI search readiness
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.bfi-stmk.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.
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 (777 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.bfi-stmk.at/warenkorb is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.bfi-stmk.at/warenkorb has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages slow to respond
https://www.bfi-stmk.at/fachbereich/berufsreifepruefung, https://www.bfi-stmk.at/fachbereich/werkmeisterschule, https://www.bfi-stmk.at/fachbereich/gesundheit-sozialberufe, https://www.bfi-stmk.at/fachbereich/it-mediendesign, https://www.bfi-stmk.at/fachbereich/technik-sicherheit and https://www.bfi-stmk.at/fachbereich/transport-logistik and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
5 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
35 of 37 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 8 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 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 848 words of copy
The homepage carries about 848 words of visible text.
2 checks passed
3 short forms
3 short forms (7 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
7 cookies set on arrival
7Opening the homepage sets 7 cookies (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 bfi-stmk.at, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Hosting
- Citycom
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on bfi-stmk.at, including 16 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.