Website review, no card needed
florianwueest.com website review
Visit site (opens in a new tab)Reviewed 8 November 202610 issues · 66 checks
This review found 10 issues worth fixing on florianwueest.com, 1 of them high impact, across 66 checks. The most urgent: 19 text elements with low contrast. 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.5 s
1.0 s
1.4 s
1.9 s
2.4 s
2.9 s
3.3 s
3.8 s
Speed
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Reduce unused CSS
110 ms · 16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 66 ms. During a long task the page ignores taps.
Improve image delivery
58 KiB5 images could be 58 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 (simpleanalyticscdn.com, apollo.io and aplo-evnt.com), adding 13 KiB and 13 ms of main-thread time.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
3 checks passed
Mobile performance score: 98
98/100Your mobile performance score is 98. That is in Google's “good” band (90 and up).
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 218 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
6 checks passed
Cumulative Layout Shift: 0.094
0.094The layout barely moves while loading (CLS 0.094, good is under 0.1).
Time to Interactive: 3.0 s
3.0 sThe page is fully interactive after 3.0 s.
Speed Index: 2.0 s
2.0 sVisually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Hi there, I'm Florian. 👋 I'm a Swiss B2B SaaS marketing co…”.
Total Blocking Time: 8 ms
8 msScripts block the page for only 8 ms while loading. Good is under 200 ms.
Images and page weight
About 0.1 g of CO₂ per visit
0.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.13 g of CO₂e: 15.3 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: 461 KiB in 45 requests
461 KiBYour homepage downloads 461 KiB in 45 requests on a phone: scripts 201 KiB (19), images 150 KiB (18) and fonts 48 KiB (1). 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
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 17 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
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.
8 internal links, 5 external
The homepage links to 8 pages on florianwueest.com and 5 external pages.
6 checks passed
Meta description: 97 characters
Your meta description is 97 characters: “Hi, I'm Florian. B2B SaaS companies come to me when they want to improve their digital marketing.”.
One H1 headline
Your main headline reads: “Get More High-Quality Leads In 30 Days — Guaranteed”.
Title: 45 characters
Your title is a healthy 45 characters: “B2B SaaS Marketing Consultant | Florian Wüest”.
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://shipfa.st/sitemap.xml.
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://florianwueest.com/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,568 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a meta description
https://florianwueest.com/tos and https://florianwueest.com/privacy-policy use the same meta description. A description written for each page earns more clicks.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://florianwueest.com/saas-valuation-calculator, whose canonical is https://florianwueest.com/b2b-. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page with very little text
https://florianwueest.com/blog has 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.
6 internal pages checked
We fetched 6 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 6 pages we checked loaded without an error.
Every page has a meta description
All 6 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 6 pages that loaded have a <title>.
Best practices
1 small tap target
1 of 5 tappable elements near the top of the page is 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: the server responded with a status of 400 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 1,573 words of copy
The homepage carries about 1,573 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join The Waitlist”.
5 calls to action
The homepage has 5 calls to action, for example “Join The Waitlist”, “Join waitlist” and “Contact me”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 1 of them by other companies (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.
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.
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 florianwueest.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 10 issues on florianwueest.com, including 2 SEO issues and 1 conversion gap. 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.