SEOWebsiteTool
90Grade B

vellum.club

Vellum — A premium private club for people with full lives.

1 failed · 4 warnings · 23 passed

Audited Thu, 23 Jul 2026 14:30:57 GMT · https://vellum.club/

Meta & Head

22.2/25

Title, description, canonical, social tags — what search engines read first.

  • Canonical URLmedium impactlow effort

    No <link rel="canonical"> found

    When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.

  • Open Graph tagsmedium impactlow effort

    Missing Open Graph tags: og:url

    Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:url tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.

7 passing checks
  • Title tag<title> is "Vellum — A premium private club for people with full lives." (59 characters)
  • Meta descriptionMeta description is "Vellum is a premium private club for people with full lives. Less noise. Better circles. A quieter way to meet the right people." (128 characters)
  • Viewport meta tagViewport is "width=device-width, initial-scale=1, interactive-widget=resizes-content"
  • Character encoding declaredCharacter encoding is declared
  • FaviconA <link rel="icon"> is present
  • Twitter card tagtwitter:card is "summary_large_image"
  • Page allows indexingrobots: index, follow

Content & Structure

25/25

Headings, copy depth, images, structured data, internal linking.

Everything we check in this category passed.

Technical

19.9/25

HTTPS, redirects, robots, sitemap, speed, crawlability.

  • Fast time to first bytehigh impactmedium effort

    4039 ms

    Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.

  • Short redirect chainmedium impactlow effort

    https://vellum-club.com/ (301) → https://vellum.club/

    Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.

  • Response compression enabledlow impactlow effort

    no content-encoding header

    This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.

9 passing checks
  • Served over HTTPSfinal URL uses https://
  • HTTP redirects to HTTPShttp:// redirects to https://
  • No mixed content0 http:// subresource references
  • robots.txt present and permissiverobots.txt exists and allows crawling
  • XML sitemap availablesitemap.xml exists and is valid XML
  • Reasonable HTML size29.7 KB
  • Missing pages return 404missing paths return HTTP 404/410
  • www and non-www resolve consistentlywww and non-www converge on the same host
  • HTML5 doctype<!DOCTYPE html> present

Performance

Core Web Vitals scoring via Google PageSpeed is coming soon.

Share your score

Embed this live badge on your site — it updates whenever the audit is re-run.

SEO score badge for vellum.club

More “v” sitesRecent audits