This website audit report analyzes https://www.WBJC.com/ across 12 critical dimensions with actionable recommendations.
https://www.WBJC.com/
50Needs Workout of 100
Website Audit Report
WBJC
May 11, 2026 185ms response HTTPS Secure
Executive Summary
https://www.WBJC.com/ scores 50/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 261 words, 11 images, and 0 schema blocks. Focus on the top recommendations below to improve your score.
185ms
Response Time
261
Word Count
11
Images
71
Links
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too short (4 chars)
2[SEO] Missing meta description
3[SEO] Multiple H1 tags found (4)
4[SEO] Heading hierarchy gaps: h2 → h4 (skips h3), h1 → h3 (skips h2)
5[SEO] No Open Graph tags found
6[SEO] No Twitter Card tags found
7[SEO] Missing lang attribute on <html>
8[SEO] Thin content (261 words)
9[SEO] Deprecated HTML tags found: <font> (1)
10[Performance] 8 render-blocking scripts slow down initial paint
Top Recommendations
1Expand your title to 30–60 characters for better click-through rates
2Add a compelling meta description of 120–160 characters with target keywords
3Consolidate to a single H1 tag — use H2–H6 for subtopics
4Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
5Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
6Add Twitter Card meta tags for better social media previews
7Add lang="en" (or appropriate language) to your <html> tag
8Expand your content to at least 300+ words for better search rankings
9Replace deprecated HTML tags with modern semantic equivalents
10Convert all non-critical scripts to async/defer to eliminate render-blocking resources
11Add loading="lazy" to below-the-fold images to improve initial page load
12Convert images to WebP or AVIF format for 30–50% file size reduction
Detailed Category Analysis
Key Findings
1Canonical URL is set and matches the page URL
2Favicon present
361 internal links help establish site architecture
410 external links provide reference signals
Issues Found
1Title tag is too short (4 chars)
2Missing meta description
3Multiple H1 tags found (4)
4Heading hierarchy gaps: h2 → h4 (skips h3), h1 → h3 (skips h2)
5No Open Graph tags found
6No Twitter Card tags found
7Missing lang attribute on <html>
8Thin content (261 words)
9Deprecated HTML tags found: <font> (1)
Recommendations to Reach 100%
1Expand your title to 30–60 characters for better click-through rates
2Add a compelling meta description of 120–160 characters with target keywords
3Consolidate to a single H1 tag — use H2–H6 for subtopics
4Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
5Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
6Add Twitter Card meta tags for better social media previews
7Add lang="en" (or appropriate language) to your <html> tag
8Expand your content to at least 300+ words for better search rankings
9Replace deprecated HTML tags with modern semantic equivalents
Key Findings
1Excellent server response time: 185ms
2Lean HTML document: 41KB
31 async and 0 deferred scripts
4Cache-Control header with max-age is set
Issues Found
18 render-blocking scripts slow down initial paint
2No lazy loading on images
3No WebP or AVIF image formats found
4No responsive image srcset found
5No font-display property found
68 inline <style> blocks
Recommendations to Reach 100%
1Convert all non-critical scripts to async/defer to eliminate render-blocking resources
2Add loading="lazy" to below-the-fold images to improve initial page load
3Convert images to WebP or AVIF format for 30–50% file size reduction
4Use srcset and sizes attributes on images to serve appropriately sized images per device
5Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
6Preload critical resources (fonts, hero images) with <link rel="preload">
7Add font-display: swap to web font declarations to show fallback text while fonts load
8Extract inline styles into external CSS files for better caching and maintainability
Key Findings
1HTML5 doctype declared
2Character encoding declared
Issues Found
1Missing viewport meta tag — page will not render correctly on mobile
2No theme-color meta tag
3No web app manifest found
4Missing Apple touch icon
5No responsive image srcset — mobile users may download oversized images
Recommendations to Reach 100%
1Add <meta name="viewport" content="width=device-width, initial-scale=1"> immediately
2Add <meta name="theme-color"> for browser chrome styling on mobile
3Create a manifest.json for PWA capabilities and add-to-homescreen support
4Add <link rel="apple-touch-icon"> for iOS homescreen icons
5Consider implementing a service worker for offline support and faster repeat visits
6Implement srcset to serve smaller images on mobile devices, saving bandwidth
Key Findings
1HTTPS enabled — encrypted connection
Issues Found
1Missing Strict-Transport-Security header
2Missing Content-Security-Policy header
3Missing X-Content-Type-Options header
4Missing X-Frame-Options header
5Missing Referrer-Policy header
6Missing Permissions-Policy header
7Server header exposes technology: nginx
8X-Powered-By header exposes: WP Engine
Recommendations to Reach 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Implement a Content Security Policy to prevent XSS and injection attacks
3Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
4Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
5Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
6Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
7Add Cross-Origin-Opener-Policy: same-origin-allow-popups
8Add Cross-Origin-Resource-Policy: cross-origin
9Remove or obfuscate the Server header to avoid exposing your technology stack
10Remove X-Powered-By header
Key Findings
1Focus styles detected for keyboard navigation
Issues Found
1Missing lang attribute on <html>
2No skip navigation link
3Missing landmarks: main, nav, footer
41 of 11 images (9%) missing alt text
5No ARIA attributes detected
6Heading hierarchy has gaps — confusing for screen readers
7Deprecated HTML tags impact accessibility
Recommendations to Reach 100%
1Add a lang attribute to help screen readers identify the page language
2Add a "Skip to main content" link as the first focusable element for keyboard users
3Add semantic landmark elements: <main>, <nav>, <footer>
4Add descriptive alt text to all images — use empty alt="" only for decorative images
5Add ARIA attributes to interactive elements for better screen reader support
Key Findings
1Social presence signals: facebook, twitter
24 call-to-action elements detected
Issues Found
1No structured data (Schema.org) found
2No semantic HTML elements detected
3Incomplete social metadata
4No breadcrumb navigation
5No FAQ or Q&A content patterns found
6No sitemap reference found
Recommendations to Reach 100%
1Implement JSON-LD structured data — start with Organization, BreadcrumbList, and page-specific types
2Add hreflang tags if your site serves multiple languages or regions
3Replace generic divs with semantic HTML5 elements to help AI models understand your content structure
4Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
5Add an FAQ section with FAQPage schema to increase chances of AI engine citations
6Create and reference an XML sitemap for AI crawler discoverability
7Use <strong> and <em> tags to highlight key entities, concepts, and terms
Key Findings
1Structured content: 9 lists, 0 tables — easily parsed by AI
Issues Found
1Very thin content (261 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 34 divs vs 0 semantic elements
5Weak E-E-A-T schema signals
Recommendations to Reach 100%
1AI models value comprehensive, authoritative content — aim for 1000–2000+ words covering the topic thoroughly
2Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
3Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
4Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
5Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
6Add Speakable schema markup to help voice assistants identify the most important content
Key Findings
19 lists provide scannable, AI-friendly content
2How-to instructional patterns detected — valued by AI answer engines
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Content too thin for AI citation value
4Insufficient structured data for generative engine context
5thin content — may not provide enough depth for AI engines
Recommendations to Reach 100%
1Structure content with clear questions as headings (H2/H3) followed by concise, definitive answers in the first paragraph
2Add comparison tables with structured data — generative AI engines frequently cite tabular content
3Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
4Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
5Include unique statistics, expert quotes, and original insights that generative AI would want to cite
6Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
Key Findings
19 lists provide scannable answers for People Also Ask
Issues Found
1No FAQ content or schema
2How-to content exists but lacks HowTo schema
3Content not optimized for featured snippets
4No Speakable schema for voice search
5No breadcrumb navigation
Recommendations to Reach 100%
1Create an FAQ section with FAQPage structured data — essential for People Also Ask and featured snippet inclusion
2Add HowTo schema to your instructional content for rich result eligibility
3Use question-based H2/H3 headings followed by a direct 40–60 word answer paragraph for featured snippet targeting
4Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
5Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
6Consider adding video content with VideoObject schema for multimedia search results
Key Findings
1NAP information detected: phone: 16436249078
2Phone number(s) visible: 16436249078, 15099413069
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
2Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
3Add an embedded Google Map to your contact or about page for local search signals
4Add PostalAddress schema or itemprop="address" microdata to your address elements
5Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
Issues Found
1No Schema.org structured data found
Recommendations to Reach 100%
1Implement JSON-LD structured data immediately — start with Organization, WebSite, and BreadcrumbList
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Focus styles detected for keyboard navigation visibility
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3No semantic HTML5 elements detected
4Missing lang attribute
Recommendations to Reach 100%
1Add @media (prefers-reduced-motion: reduce) to disable animations for users who are sensitive to motion
2Add @media (prefers-contrast: high) or (forced-colors: active) styles for users with low vision
3Use semantic elements (main, nav, article, section, aside, header, footer) for WCAG-compliant page structure
4Add lang attribute to <html> element (WCAG 3.1.1)
Limited-Time Offer
All 12 Optimizations — Bundled Into Your Custom Website
We're currently bundling every optimization from this audit — SEO, AIO, GEO, AEO, Schema.org, WCAG accessibility, performance, security, and more — directly into our Custom Web Application Development service.
Instead of fixing issues after launch, we eliminate them from the start. Every website we build ships production-ready with a 90+ score across all 12 audit dimensions.