This website audit report analyzes https://www.power1047.com/ across 12 critical dimensions with actionable recommendations.
https://www.power1047.com/
69Needs Workout of 100
Website Audit Report
Power 104.7 | Baltimore Hip Hop and R&B | Free Internet Radio
May 11, 2026 · 14:03 (America/New_York) 992ms response HTTPS Secure
Executive Summary
https://www.power1047.com/ scores 69/100 (D+). Strong areas include Mobile, WCAG. Priority improvements needed in Performance, Security, AIO. The site has 122 words, 10 images, and 3 schema blocks. Focus on the top recommendations below to improve your score.
992ms
Response Time
122
Word Count
10
Images
29
Links
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too long (61 chars — may be truncated in SERPs)
2[SEO] Meta description may be truncated (205 chars)
3[SEO] Canonical URL does not match the current page URL
4[SEO] Thin content (122 words)
5[SEO] Deprecated HTML tags found: <font> (2)
6[Performance] Very large HTML: 732KB
7[Performance] 4 render-blocking scripts slow down initial paint
8[Performance] No WebP or AVIF image formats found
9[Performance] 23 inline <style> blocks
10[Performance] 49 inline scripts
Top Recommendations
1Shorten your title to under 60 characters to prevent truncation
2Trim your meta description to under 160 characters
3Verify your canonical tag points to the correct URL to prevent duplicate content issues
4Expand your content to at least 300+ words for better search rankings
5Replace deprecated HTML tags with modern semantic equivalents
6Optimize server response time to under 500ms with caching or a CDN
7Critical: HTML is over 500KB — implement code splitting, lazy loading, and remove unnecessary markup
8Convert all non-critical scripts to async/defer to eliminate render-blocking resources
9Convert images to WebP or AVIF format for 30–50% file size reduction
10Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
11Extract inline styles into external CSS files for better caching and maintainability
12Move inline scripts to external files with defer attributes
Detailed Category Analysis
Key Findings
1Single H1 tag present: "Videos"
2Clean heading hierarchy with no skipped levels
3Complete Open Graph tags (title, description, image, url, type)
4Complete Twitter Card tags present
5HTML lang attribute set to "en"
6Favicon present
723 internal links help establish site architecture
86 external links provide reference signals
Issues Found
1Title tag is too long (61 chars — may be truncated in SERPs)
2Meta description may be truncated (205 chars)
3Canonical URL does not match the current page URL
4Thin content (122 words)
5Deprecated HTML tags found: <font> (2)
Recommendations to Reach 100%
1Shorten your title to under 60 characters to prevent truncation
2Trim your meta description to under 160 characters
3Verify your canonical tag points to the correct URL to prevent duplicate content issues
4Expand your content to at least 300+ words for better search rankings
5Replace deprecated HTML tags with modern semantic equivalents
Key Findings
1Acceptable response time: 992ms
21/10 images use lazy loading
3Responsive images with srcset detected
4Most images have explicit width/height attributes (prevents layout shift)
5Preloaded resources: fetch, fetch, fetch, fetch
6font-display property detected — reduces invisible text during font loading
76 async and 2 deferred scripts
8Cache-Control header with max-age is set
Issues Found
1Very large HTML: 732KB
24 render-blocking scripts slow down initial paint
3No WebP or AVIF image formats found
423 inline <style> blocks
549 inline scripts
Recommendations to Reach 100%
1Optimize server response time to under 500ms with caching or a CDN
2Critical: HTML is over 500KB — implement code splitting, lazy loading, and remove unnecessary markup
3Convert all non-critical scripts to async/defer to eliminate render-blocking resources
4Convert images to WebP or AVIF format for 30–50% file size reduction
5Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
6Extract inline styles into external CSS files for better caching and maintainability
7Move inline scripts to external files with defer attributes
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Apple touch icons present
5Service worker detected — offline capability possible
6Responsive images via srcset serve appropriate sizes per device
71 images with lazy loading benefit mobile data users
Issues Found
1No theme-color meta tag
2No web app manifest found
Recommendations to Reach 100%
1Add <meta name="theme-color"> for browser chrome styling on mobile
2Create a manifest.json for PWA capabilities and add-to-homescreen support
Key Findings
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3X-Content-Type-Options: nosniff is set
Issues Found
1Missing Content-Security-Policy header
2Missing X-Frame-Options header
3Missing Referrer-Policy header
4Missing Permissions-Policy header
5Server header exposes technology: Pepyaka
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
3Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
4Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
5Add Cross-Origin-Opener-Policy: same-origin-allow-popups
6Add Cross-Origin-Resource-Policy: cross-origin
7Remove or obfuscate the Server header to avoid exposing your technology stack
Key Findings
1Language declared: en
2All key landmarks present (main, nav, footer)
3All 10 images have alt attributes
4All 4 buttons have accessible labels
5Rich ARIA implementation: 17 elements with ARIA attributes
6Focus styles detected for keyboard navigation
Issues Found
1No skip navigation link
21 iframe(s) missing title
3Deprecated HTML tags impact accessibility
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add descriptive title attributes to all iframes
Key Findings
1Rich structured data: 3 schema blocks (WebSite, LocalBusiness, WebSite)
2Strong semantic markup: header, nav, main, section, footer
3Complete social metadata (OG + Twitter Card)
4Sitemap reference detected
5Social presence signals: instagram, twitter, tiktok
63 call-to-action elements detected
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns found
Recommendations to Reach 100%
1Add hreflang tags if your site serves multiple languages or regions
2Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
3Add an FAQ section with FAQPage schema to increase chances of AI engine citations
4Use <strong> and <em> tags to highlight key entities, concepts, and terms
Key Findings
1Structured content: 7 lists, 0 tables — easily parsed by AI
2Good paragraph length for readability and AI parsing
Issues Found
1Very thin content (122 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 114 divs vs 5 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
17 lists provide scannable, AI-friendly content
2How-to instructional patterns detected — valued by AI answer engines
33 schema blocks help AI engines understand content context
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
4thin 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
Key Findings
1Short paragraphs are well-suited for answer extraction
27 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: 17782094021
2Phone number(s) visible: 17782094021, 9283304
3LocalBusiness schema: LocalBusiness
Issues Found
1No Google Maps embed
2No address microdata
3No geo meta tags
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
2Add an embedded Google Map to your contact or about page for local search signals
3Add PostalAddress schema or itemprop="address" microdata to your address elements
4Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
Key Findings
13 JSON-LD block(s) with types: WebSite, LocalBusiness, WebSite
2Moderate schema coverage
Issues Found
1WebSite has very few properties (2)
2WebSite has very few properties (2)
Recommendations to Reach 100%
1Add BreadcrumbList schema for site hierarchy
2Add FAQPage schema to FAQ content
3Consider adding HowTo schema for instructional content
4Add more properties to schema types — aim for at least 5 meaningful properties per type
5Add more properties to schema types — aim for at least 5 meaningful properties per type
Key Findings
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Links are visually distinguishable (underline or decoration detected)
4Relative units (rem/em/clamp) detected — supports text resizing
5Focus styles detected for keyboard navigation visibility
6Page language declared — aids assistive technology
Issues Found
1Low semantic-to-div ratio — 114 divs vs 5 semantic elements
218 elements with tabindex="-1" — may hide content from keyboard users
Recommendations to Reach 100%
1Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
2Review elements with tabindex="-1" — ensure important interactive elements remain keyboard-accessible
Limited-Time Offer
Audit-informed Optimizations for 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.
Use the audit findings to prioritize improvements during development. Scores depend on measured conditions; rankings and fixed scores are not guaranteed.