professortwang.com
Professor Twang and the Honky Tonk Review
1 failed · 6 warnings · 22 passed
Audited Sun, 26 Jul 2026 23:30:07 GMT · https://www.professortwang.com/
Meta & Head
19.4/25
Title, description, canonical, social tags — what search engines read first.
Meta descriptionhigh impactlow effort
No meta description found
The meta description is your ad copy in search results; without one, engines pull an arbitrary snippet from the page, which usually reads poorly and costs you clicks. Add <meta name="description" content="..."> with 70–160 characters that summarize the page and give a concrete reason to click — what the visitor gets plus a differentiator (free, instant, no signup). Write a unique description per page: one duplicated across the site is treated much like a missing one.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:description
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:description 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 "Professor Twang and the Honky Tonk Review" (41 characters)
- Canonical URLCanonical href is "https://www.professortwang.com"
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary"
- Page allows indexingNo restrictive robots meta tag
Content & Structure
23.4/25
Headings, copy depth, images, structured data, internal linking.
Image alt textmedium impactlow effort
2 of 3 images have alt text
Alt text is how search engines understand what an image shows — it feeds image-search rankings and is what screen readers announce to blind visitors. Add a short, specific alt attribute to every meaningful image, describing the content rather than listing keywords: alt="Golden retriever puppy playing in snow" beats alt="dog puppy pet animal". Give purely decorative images an empty alt="" instead of omitting the attribute, so assistive technology knows to skip them rather than reading out the filename.
7 passing checks
- Single H1 heading1 h1 found: "Professor Twang"
- Heading hierarchy7 headings in order without skipped levels
- Word count2401 words of visible text
- Structured data (JSON-LD)JSON-LD types found: WebSite, LocalBusiness
- HTML lang attribute<html lang="en-US">
- JavaScript-dependent contentvisible text ~7261 chars in the initial HTML
- Internal linking15 internal, 7 external links
Technical
20.5/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Fast time to first bytehigh impactmedium effort
833 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.
No mixed contentmedium impactlow effort
1 http:// subresource reference
Some images, scripts, or styles load over insecure http:// on this HTTPS page; browsers block insecure scripts outright and flag the page, which breaks functionality and undermines the padlock users look for. Update each reference to https:// — most hosts serve the same asset on both schemes — or re-host assets whose origins don't support TLS. Adding <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests"> is a quick safety net, but fix the underlying URLs too: hard-coded http:// links in databases and old content are the usual source.
Short redirect chainmedium impactlow effort
https://professortwang.com/ (301) → https://www.professortwang.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.
8 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Reasonable HTML size291.8 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.