Audit complete · 19d ago

ui.philippekam.dev

↗ ui.philippekam.dev
Verdict
Caution

4 ship-blockers, 14 should-fix

  • Site typeunclear
  • Confidence0%
  • Discovered16 URLs
ERROR · ui.philippekam.dev/perf-stressWARNING · ui.philippekam.dev/components/black-holeWARNING · ui.philippekam.dev/components/atmospheric-skyWARNING · ui.philippekam.dev/components/chromatic-fieldWARNING · ui.philippekam.dev/components/crown-glowWARNING · ui.philippekam.dev/components/solar-flareWARNING · ui.philippekam.dev/components/milky-wayWARNING · ui.philippekam.dev/getting-startedWARNING · ui.philippekam.dev/components/radiant-veilWARNING · ui.philippekam.dev/components/mesh-gradientWARNING · ui.philippekam.dev/components/shimmer-ringWARNING · ui.philippekam.dev/INFO · ui.philippekam.dev/components/chromatic-leaksINFO · ui.philippekam.dev/components/halo-ringINFO · ui.philippekam.dev/design-system
Pages1with blockers11with should-fix3with info0clean15 scanned
Pages
15
scanned
Blockers
4
findings
Should fix
14
findings
Info
59
findings
Clean
0
pages

Heuristic score over 15 sampled pages, not Google's classifier. How to read this ↓

Category grades

Integrity
C
33 issues
Discoverability
A
4 issues
Citation
A
40 issues
Data
A
0 issues
Severity adjustments8 rules softened by the unclear profile

These rules still ran and emitted findings: the site-type profile lowered their severity so the score reflects how the signal applies to this kind of site, not a one-size-fits-all penalty.

aeo/answer-firstaeo/citable-factsaeo/freshness-signalscontent/eeat-signalscontent/heading-structurecontent/missing-authorspam/thin-contenttech/og-completeness

Save this audit to your history, sign in.

Monitor this domain with Pro →
Audit another site
Origin readinessNot ready
25 live fetches
Median TTFB
1118ms
p95 TTFB
5869ms
5xx rate
0%
Cache assisted
16%
Crawl coverageDiscovered 16 · audited 15 · skipped 0

Origin looks unprepared for crawl load. A cache-cold dynamic origin at this rate will struggle under bot traffic and may leak to your database bill.

Fix: add an edge CDN with a sensible s-maxage, or an app-layer query cache (Redis / Next.js unstable_cache) between the route handler and the database.

Findings · 77

sampled 15 pages
Top fixes by impactseverity × pages affected
  1. 1
    content/citation-coveragewarningmoderate10 pages

    https://ui.philippekam.dev/components/black-hole makes 21 quantified claims but cites 0 authoritative sources.

  2. 2
    tech/canonical-consistencyerrorquick1 page

    https://ui.philippekam.dev/perf-stress is missing a canonical URL.

  3. 3
    content/unique-valueerrorstructural1 page

    https://ui.philippekam.dev/perf-stress has low unique-content density 0.115 (11.5% of its 1 distinct words are page-distinctive; floor 0.20). Most of its vocabulary also appears on other pages.

  4. 4
    content/meta-uniquenesserrormoderate11 pages

    11 pages share the same meta description template after entity masking.

  5. 5
    links/orphan-pageserrormoderate1 page

    https://ui.philippekam.dev/perf-stress has no inbound links from other pages in this crawl.

Blockers· 4

Severity error/critical · must fix before shipping
Errorcontent/unique-value1 finding

https://ui.philippekam.dev/perf-stress has low unique-content density 0.115 (11.5% of its 1 distinct words are page-distinctive; floor 0.20). Most of its vocabulary also appears on other pages.

↗ ui.philippekam.dev/perf-stress
Fix

Raise originality density: add page-specific text, a distinct lead, this record's own facts, page-specific examples. Content repeated across pages on the same axis (boilerplate, shared legal/spec blocks, per-axis data like a role's regulations across that role's documents) is common vocabulary and does NOT raise density, even when it is useful.

structural↗ Read more↗ Google docs1 page affected
Affected pages1
Errorcontent/meta-uniqueness1 finding

11 pages share the same meta description template after entity masking.

Fix

Write a unique meta description for each page that highlights what makes it specifically different.

moderate↗ Read more↗ Google docs11 pages affected
Affected pages11

Should fix· 14

Severity warning · should fix before scaling
Warninglow confidencecontent/citation-coverage10 findings

https://ui.philippekam.dev/components/black-hole makes 21 quantified claims but cites 0 authoritative sources.

↗ ui.philippekam.dev/components/black-hole
Fix

Cite the primary sources behind your numbers: link the statute, standard, dataset, .gov/.edu page, or research that backs each statistic. AI Overviews and Google's helpful-content systems weight pages that ground claims in authoritative references. Note: this rule detects statistic+citation co-occurrence, not semantic correctness.

moderate↗ Read more↗ Google docs10 pages affected
Affected pages10
Warninglow confidenceaeo/llms-txt1 finding

No llms.txt found at https://ui.philippekam.dev/llms.txt. llms.txt is a draft standard with low adoption: absence isn't a defect, only a missed opportunity.

Fix

Create https://ui.philippekam.dev/llms.txt to guide AI engines toward your most authoritative, citable content. Start with an # H1 title, a blockquote summary, then ## sections listing your key pages as markdown links. See https://llmstxt.org for the emerging convention.

moderate↗ Read more↗ Google docs
Warningcontent/image-attributes1 finding

https://ui.philippekam.dev/: 11 of 11 <img> tags declare neither width/height attributes nor inline sizing (e.g. /previews/radiant-veil.jpg, /previews/chromatic-leaks.jpg, /previews/halo-ring.jpg). Without an aspect ratio the browser cannot reserve space, so content shifts as each image loads, which is what Cumulative Layout Shift measures.

↗ ui.philippekam.dev/
Fix

Set the intrinsic width and height attributes on each <img> and let CSS scale it (width: 100%; height: auto). The browser derives aspect-ratio from the attribute pair and reserves the box before the bytes arrive. In a template, bind both from the same data source as the src.

moderate↗ Read more↗ Google docs1 page affected
Affected pages1
Warningcontent/meta-description-presence1 finding

https://ui.philippekam.dev/perf-stress has no meta description, so Google will compose the snippet itself from page text, so you lose control over the SERP pitch and likely CTR.

↗ ui.philippekam.dev/perf-stress
Fix

Add <meta name="description" content="..."> to <head> with a summary written for THIS page (not a site-wide boilerplate line).

moderate↗ Read more↗ Google docs1 page affected
Affected pages1

Informational· 59

Severity info · tracked for trend analysis
Infolow confidenceaeo/freshness-signals15 findings

https://ui.philippekam.dev/ has no dateModified signal (no JSON-LD dateModified, no modification meta tag, no visible "Last updated"). Evergreen pages may legitimately omit this: verify whether freshness signals matter for this page type.

↗ ui.philippekam.dev/
Fix

Add a freshness signal so AI engines know the page is current. Three recommended places: (1) dateModified in your JSON-LD schema, (2) a visible "Last updated: YYYY-MM-DD" line in the page content, (3) accurate <lastmod> in your sitemap. For pSEO templates, automate dateModified to update when your underlying data source changes.

moderate↗ Read more↗ Google docs15 pages affected
Affected pages15
Infolow confidenceaeo/citable-facts13 findings

https://ui.philippekam.dev/ has 0 unique citable facts. AI Overviews cite specific numbers and named references.

↗ ui.philippekam.dev/
Fix

Replace vague language ("varies", "several weeks", "affordable", "many options") with specific values a reader or AI engine would cite: exact prices, percentages, dates, timeframes, version numbers, named products, standards, or regulations that apply to this page. For pSEO templates, bind these values from your data source so each page gets entity-specific numbers instead of repeating the same template wording. Target: 8+ unique facts per page.

moderate↗ Read more↗ Google docs13 pages affected
Affected pages13
Infolow confidencecontent/heading-structure12 findings

https://ui.philippekam.dev/components/chromatic-leaks has no <h1> element.

↗ ui.philippekam.dev/components/chromatic-leaks
Fix

Add a single <h1> that names the page's primary topic. Google uses H1 to disambiguate when the title tag is unclear.

moderate↗ Read more↗ Google docs12 pages affected
Affected pages12
Infolow confidenceaeo/answer-first11 findings

https://ui.philippekam.dev/components/chromatic-leaks does not open with a direct, extractable answer: opener is identical to other pages after entity masking; no specific numbers, dates, or dollar amounts

↗ ui.philippekam.dev/components/chromatic-leaks
Fix

Restructure the template to open with entity-specific facts. Instead of boilerplate or a topic preamble, lead with a complete-answer sentence containing the key number, date, agency, or form name a reader (or AI Overview) would cite. Target: <100 words, at least one concrete number, at least one named entity.

moderate↗ Read more↗ Google docs11 pages affected
Affected pages11
Infolow confidencespam/thin-content4 findings

https://ui.philippekam.dev/ has thin content (98 words).

Fix

Add at least 202 more words of substantive content relevant to this page's specific topic.

moderate↗ Read more↗ Google docs
Infolow confidencecontent/missing-author1 finding

All 15 pages have no author signals (meta author, schema author, byline, or rel="author" link). This is a site-wide E-E-A-T risk. Author bylines matter most on blog/news content; technical docs and product pages legitimately omit them.

Fix

Add author attribution site-wide: <meta name="author" content="Name">, a visible byline, or author data in your JSON-LD schema.

quick↗ Read more↗ Google docs15 pages affected
Affected pages15
Infolow confidencecontent/eeat-signals1 finding

All 15 pages have fewer than 2 out of 4 E-E-A-T signal categories. Site-wide trust signals are missing.

Fix

Add trust signals site-wide: author info, publication dates, about page links, sources, or "last updated" markers.

moderate↗ Read more↗ Google docs15 pages affected
Affected pages15
Infocontent/image-attributes1 finding

https://ui.philippekam.dev/ serves 11 images and not one uses srcset or <picture>, so phones download the desktop-sized file. Google recommends responsive images; this is guidance rather than a requirement, and no image dimension or byte limit is documented.

↗ ui.philippekam.dev/
Fix

Emit a srcset with a handful of widths plus a sizes attribute, or wrap the img in <picture> to offer a modern format with a fallback. Most image CDNs and framework Image components generate both from one source URL.

moderate↗ Read more↗ Google docs1 page affected
Affected pages1
Infolow confidencetech/og-completeness1 finding

https://ui.philippekam.dev/perf-stress is missing Open Graph tags: og:title, og:description, og:image, og:type, og:url.

↗ ui.philippekam.dev/perf-stress
Fix

Add the missing meta tags inside <head>: <meta property="og:title" content="..."> <meta property="og:description" content="..."> <meta property="og:image" content="..."> <meta property="og:type" content="..."> <meta property="og:url" content="...">.

moderate↗ Read more↗ Google docs1 page affected
Affected pages1

Is this your site?

Claim it to manage the listing, get a verified badge, and a followed backlink.

pseolint grade for ui.philippekam.dev

Show the grade

ui.philippekam.dev passed the audit. Embed the badge on your site or README; it always shows your current grade.

Markdown[![pseolint grade](https://pseolint.dev/api/badge/ui.philippekam.dev)](https://pseolint.dev/r/8qVZ5NjwH3)
HTML<a href="https://pseolint.dev/r/8qVZ5NjwH3"><img src="https://pseolint.dev/api/badge/ui.philippekam.dev" alt="pseolint grade for ui.philippekam.dev" /></a>

How to read this report

  • Sample, not censusScored on 15 sampled pages from sitemap.xml. Template clusters across un-sampled pages may be missed.
  • Heuristic, not verdictRules inferred from public SpamBrain guidance, a structured conversation, not Google's classifier.
  • Server-rendered by defaultWe read the HTML the server returns. Client-rendered content looks empty to us; Pro audits can render JS-heavy / SPA pages in a browser first.
  • Page budgetpseolint samples up to 200 pages on free audits (50 without an account) and treats sitemap.xml as the source of truth. Pro lifts the budget to 500 pages on manual re-audits and crawls beyond the sitemap.
  • RetentionThis report is kept permanently because the site is on the public leaderboard.
  • Fair useRetention, rate limits and crawl behaviour are documented in full at pseolint.dev/limits.