www.teepublic.com — Website Report

Scored 55/100 · Scanned with Foglift

Site Technical Health

Mean of SEO, Performance, Security, and Accessibility.

teepublic.com scored 55. Addressing the 20 listed issues could raise its estimated score to 78.

SEO

AI ReadinessUnavailable

Performance

Security

Accessibility

Scan another domain Save this scan to your free account

5 critical10 warnings20 total issues

Quick wins

~158 min total fix time

1Missing language attribute~1m

2Zooming is disabled~2m

3Missing Permissions Policy header~2m

https://www.teepublic.com/ · 2026-04-09

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://www.teepublic.com/ Your site scores 55/100 overall, but AI engines may be missing you. Your AI Search Readiness is 90/100, and AI Citability is 53/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 5 critical issues and 10 warnings. Here's your prioritized action plan:

FIX FIRST (Critical): 1. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks.

2. 98 images missing alt text — Found 98 of 148 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search). 3. 66% of images lack alt text — 98 of 148 images have no alt attribute. Screen readers cannot describe these images to visually impaired users. 4. Zooming is disabled — Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content. 5. 11 render-blocking scripts

14 more critical fixes + quick wins in your full report

Create a free account to save this audit and unlock the complete action plan.

Save and unlock my full report

Free account. No credit card required.

Share This Technical Audit

Send this Technical Audit to a teammate or contact. The shareable link includes all scores and issues.

Email to Contact

AI Search Readiness

Technical and content signals that affect whether AI systems can access, understand, and reuse your page

No FAQ section foundwarning~15 min fix

AI assistants love Q&A content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your page, and you'll significantly increase your chances of being cited in AI-generated answers.

Quick Fix

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does your company do?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "We provide [your service]. Our solution helps..."
    }
  }]
}
</script>

Add an FAQ only when it reflects real customer questions. Never add one solely to contact, about, legal, or listing/index pages. FAQPage schema labels genuine questions and answers in a machine-readable format, making the page easier for search and AI systems to extract accurately.

How does AI see Teepublic?

When users ask AI about your industry, are you recommended?

Start with weekly Perplexity checks for Teepublic. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.

Set up weekly monitoring free

SEO & Technical Issues (19)

Missing Content Security Policy headercriticalSecurity~5 min fix

Add a Content-Security-Policy header to prevent XSS and injection attacks.

Quick Fix

# Nginx:
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';" always;

# Apache (.htaccess):
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"

# Next.js (next.config.js headers):
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'" }

Content-Security-Policy prevents XSS attacks by controlling which resources the browser can load.

98 images missing alt textcriticalSEO

Found 98 of 148 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).

66% of images lack alt textcriticalAccessibility

98 of 148 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.

Zooming is disabledcriticalAccessibility~2 min fix

Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content.

Quick Fix

<!-- Replace your viewport meta tag with this (allows zooming) -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Do NOT use: maximum-scale=1, user-scalable=no -->

Preventing zoom is an accessibility violation. Users with low vision need to zoom to read content.

11 render-blocking scriptscriticalPerformance

11 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.

Missing Permissions Policy headerwarningSecurity~2 min fix

Add a Permissions-Policy header to control browser feature access.

Quick Fix

# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }

Permissions-Policy restricts which browser features your site can use, reducing attack surface.

Title tag too longwarningSEO

Your title is 80 characters. Keep it under 60 for best display in search results.

Missing Open Graph tagswarningSEO~10 min fix

Missing og:title, og:description. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.

Quick Fix

<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Description for social sharing">
<meta property="og:image" content="https://yoursite.com/og-image.jpg">
<meta property="og:url" content="https://yoursite.com/page">
<meta property="og:type" content="website">

Open Graph tags control how your page looks when shared on Facebook, LinkedIn, and other social platforms.

Missing language attributewarningSEO~1 min fix

Add a lang attribute to your <html> tag (e.g., lang="en"). This helps search engines and screen readers understand your content's language.

Quick Fix

<html lang="en">
<!-- For other languages: lang="es", lang="fr", lang="de", lang="ja", etc. -->

The lang attribute helps search engines and screen readers understand your content's language.

No sitemap.xml foundwarningSEO~15 min fix

Your site is missing a sitemap.xml file. Sitemaps help search engines discover and index all your pages. Submit one to Google Search Console.

Quick Fix

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yoursite.com/</loc>
    <lastmod>2026-03-15</lastmod>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://yoursite.com/about</loc>
    <lastmod>2026-03-15</lastmod>
    <priority>0.8</priority>
  </url>
</urlset>

A sitemap.xml helps search engines discover and index all your pages. Place it at your site root.

Skipped heading levelwarningAccessibility

Heading hierarchy jumps from H3 to H5. Don't skip heading levels — this confuses screen readers and assistive technology.

Large HTML documentwarningPerformance

Your HTML is 375KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.

12 external scripts loadedwarningPerformance

Your page loads 12 external JavaScript files. Consider bundling some together and deferring non-critical scripts.

18 images without lazy loadingwarningPerformance

18 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.

Missing Twitter Card tagsinfoSEO~5 min fix

Add twitter:card meta tags for optimized appearance when your pages are shared on Twitter/X.

Quick Fix

<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="A compelling description">
<meta name="twitter:image" content="https://yoursite.com/twitter-image.jpg">

Twitter Card tags control how your page appears when shared on Twitter/X.

No navigation landmarkinfoAccessibility~5 min fix

Add a <nav> element to help screen reader users quickly find the navigation. This is a WCAG 2.4.1 requirement.

Quick Fix

<!-- Wrap your navigation in a <nav> element -->
<nav aria-label="Main navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
    <li><a href="/contact">Contact</a></li>
  </ul>
</nav>

The <nav> landmark lets screen reader users quickly jump to navigation (WCAG 2.4.1).

No main landmarkinfoAccessibility~3 min fix

Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.

Quick Fix

<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
  <h1>Page Title</h1>
  <p>Your primary content here...</p>
</main>

The <main> element identifies the primary content area, letting screen reader users skip to it directly.

No skip navigation linkinfoAccessibility~5 min fix

Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.

Quick Fix

<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
  Skip to main content
</a>

<!-- Add id to your main content area -->
<main id="main-content">
  ...
</main>

Skip links let keyboard users bypass repetitive navigation and jump straight to content.

HTML contains many commentsinfoPerformance

Found 6 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

Now

Estimated potential

+23 points estimated improvement from addressing 20 listed issues

Estimate based on the measured category scores and the issues listed in this audit.

Track your AI visibility over time

AI Visibility Monitoring

Free checks Perplexity weekly while you're active. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude with daily, twice-daily, or hourly monitoring.

Competitor Tracking

Compare your AI visibility against competitors. Know when they overtake you.

Weekly Digest

Get AI-generated insights emailed every Monday with action items.

Set up Free monitoring

Weekly Perplexity while active · No credit card required

Compare paid plans — from $49/mo