SEO report for helloyes.dev
https://helloyes.dev/ · checked Wed, 11 Nov 2026 05:07 GMT
Fix these first
- Title tagcritical
“Welcome - hello, yes. I'm Thomas Michael Semmler: CSS Developer, Designer & Developer from Vienna, Austria”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- Canonical URLhigh
No canonical tag.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- Topic focushigh
3 of 11 title keywords appear in the main content (missing: welcome, hello, yes, thomas, michael, semmler, vienna, austria).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- Open Graph & social cardsmedium
Open Graph title or image missing.
Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.
- Word countmedium
40 words of main content (inside <main>).
Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to helloyes.dev…
Indexing & crawling 69%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- !
robots.txthigh
No robots.txt found (HTTP 404) – crawlers may read everything.
Googlebot is allowed to crawl this page.
Fix: Add a robots.txt that allows crawling and lists your sitemap.
- ✗
XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- ✗
Canonical URLhigh
No canonical tag.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.helloyes.dev redirects to helloyes.dev.
Search snippet & sharing 29%
How the page looks in Google results and when shared.
- ✗
Title tagcritical
“Welcome - hello, yes. I'm Thomas Michael Semmler: CSS Developer, Designer & Developer from Vienna, Austria”
About 1003px of Google's ~580px desktop width – it will probably be cut off.
Repeated words: developer.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- !
Meta descriptionhigh
56 characters, ~363px of ~990px.
Short – sell the click with a benefit and a call to action.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 46%
Is there enough clear, useful text that matches what the page targets?
- ✗
Word countmedium
40 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.
- i
Readabilitymedium
Not enough paragraph text to score readability.
- ✗
Topic focushigh
3 of 11 title keywords appear in the main content (missing: welcome, hello, yes, thomas, michael, semmler, vienna, austria).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- ✓
H1 headingcritical
“Design Engineering, Accessibility, Frontend Design & CSS”
- !
Heading structuremedium
1 headings for 40 words.
Levels are in order.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
4% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 38%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✗
Trust pages (E-E-A-T)medium
Links found to about; missing contact and privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 81%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
12 internal and 4 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- !
Broken links (sample)high
Checked 8 internal link(s).
Broken: /hire (404).
7 link(s) point to a redirect – link to the final address instead.
Fix: Fix or remove links that return errors, and update links that redirect.
Performance 97%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
501 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✓
HTML sizemedium
26 kB of HTML.
- ✓
Compressionmedium
Compressed with br.
- ✓
Render-blocking resourceshigh
0 blocking script(s) and 2 stylesheet(s) in <head>.
- ✓
Scripts & third partiesmedium
3 script tag(s); files loaded from 1 other domain(s): cdn.usefathom.com.
- ✓
Imagesmedium
1 image(s).
All images reserve their space.
1 use WebP/AVIF or responsive srcset.
- !
Cachinglow
Cache-Control: public,max-age=0,must-revalidate
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 92%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=31536000
- ✗
Security headerslow
Present: none.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 100%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1.0
- ✓
Image alt textmedium
All 1 images have alt text.
- ✓
Form labelsmedium
All 8 form fields are labelled.
- ✓
Link nameslow
Every link has a readable name.
- ✓
Tap-to-contactmedium
One-tap contact: email.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- ✓
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
An email link is shown.
- i
Map & directionslow
No map or directions link.