fanzyblade.com

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

Everything we check in this category passed.

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

• Single H1 headinghigh impactlow effort

  0 h1 headings found

  The h1 is the visible headline of the page and one of the clearest signals to search engines of what it's about; with none present, engines lean on surrounding text and may misread the topic. Add exactly one h1 near the top that states the main topic in plain language and includes the primary keyword, e.g. <h1>Merge PDF Files Online</h1>. Don't fake it with a styled <div> — the semantic tag itself is what crawlers and screen readers actually read.

• Hreflang annotationslow impactlow effort

  2 hreflang link(s) present but no x-default entry

  Your hreflang set has no x-default entry, so search engines must guess which version to show visitors whose language you don't list — and they often pick a poorly matched one. Add <link rel="alternate" hreflang="x-default" href="https://www.example.com/"> pointing at your fallback page, typically the English version or a language-selector page. Remember that hreflang must be reciprocal: every version, including the x-default target, should carry the full set of alternate links back to all the others.

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

• Fast time to first bytehigh impactmedium effort

  3388 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://fanzyblade.com/ (301) → https://www.fanzyblade.com/

  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.

• Missing pages return 404low impactlow effort

  missing paths return a non-404 status (soft 404)

  URLs that don't exist on your site return a success status instead of 404 — search engines call these soft 404s, keep recrawling them, and may index the useless placeholder pages, wasting crawl budget that should go to real content. Configure your server or framework to return an actual 404 status (or 410 for permanently removed content) along with your error page. The classic mistake is serving a friendly "page not found" template with a 200 status — crawlers ignore the visible message; only the status code counts.