playquizchamp.com
Quiz Champ | Create Your Own Jeopardy Game
0 failed · 3 warnings · 25 passed
Audited Tue, 28 Jul 2026 19:00:21 GMT · https://www.playquizchamp.com/
Meta & Head
23.6/25
Title, description, canonical, social tags — what search engines read first.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:image
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:image 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.
8 passing checks
- Title tag<title> is "Quiz Champ | Create Your Own Jeopardy Game" (42 characters)
- Meta descriptionMeta description is "Quiz Champ helps you create your own Jeopardy-style game online for classrooms, team building, parties, family game night, church groups, and events." (149 characters)
- Canonical URLCanonical href is "https://www.playquizchamp.com/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- 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
23.3/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Short redirect chainmedium impactlow effort
https://playquizchamp.com/ (308) → https://www.playquizchamp.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.
10 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
- Fast time to first byte270 ms
- Reasonable HTML size12.5 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.