Website review, no card needed
baufest.com website review
Visit site (opens in a new tab)Reviewed 31 October 202617 issues · 66 checks
This review found 17 issues worth fixing on baufest.com, 2 of them high impact, across 66 checks. The most urgent: fails Core Web Vitals for real visitors. 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
93AClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.5 s
2.2 s
2.9 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
Render-blocking requests
350 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Improve image delivery
269 KiB4 images could be 269 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
sanity.io adds 0 ms
0 mssanity.io costs a phone 0 ms of main-thread work and 348 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.
Reduce unused JavaScript
150 ms · 122 KiBAbout 122 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.
Legacy JavaScript
200 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, sanity.io and Google Analytics and others), adding 530 KiB and 153 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.
3 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96. That is in Google's “good” band (90 and up).
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 450 ms of it running JavaScript. That is comfortably low.
Server response: 21 ms
21 msYour server sent the HTML in 21 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.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 992 ms
992 msReal visitors wait 992 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 5.6 s
5.6 sThe page becomes fully interactive after 5.6 s. Good is under 3.8 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Largest Contentful Paint: 1.4 s
1.4 sYour largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “BUILDING THE NEXT GENERATION OF BUSINESSES”.
Total Blocking Time: 63 ms
63 msScripts block the page for only 63 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
35 KiB1 image is downloaded at several times the size a phone draws it, for example ccf2e20ebbf5be3e3cea04b080451b1a19fe9a81-1200x798.jpg at 1,200 px wide, shown at 292 px. Resized copies would save about 35 KiB.
1 image in older formats
1 image (75 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.3 g of CO₂ per visit
0.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.27 g of CO₂e: 32.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 965 KiB in 60 requests
965 KiBYour homepage downloads 965 KiB in 60 requests on a phone: scripts 406 KiB (14), images 359 KiB (19) and fonts 122 KiB (6). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “Custom Software Development, AI & Digital Solutions | Baufest | Baufest”.
72 internal links, 6 external
The homepage links to 72 pages on baufest.com and 6 external pages.
7 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Baufest builds custom software, AI solutions, and intelligent digital experiences that help enterprises modernize, scal…”.
One H1 headline
Your main headline reads: “Building the next generation of businesses”.
Canonical URL set
The canonical URL is https://www.baufest.com/en.
Structured data in place
Structured data found: Organization and WebSite.
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.baufest.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (779 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.baufest.com/llms.txt (17 KiB, 56 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
7 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.
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.
Every page has an H1
Each page we checked has a main headline.
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
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”.
2 checks passed
Tap targets are thumb-sized
37 of 41 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. 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 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 732 words of copy
The homepage carries about 732 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 baufest.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 17 issues on baufest.com, including 9 speed issues, 1 SEO issue 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.