This website audit report analyzes http://ViasatAds.com across 12 critical dimensions with actionable recommendations.
http://ViasatAds.com
50Needs Workout of 100
Website Audit Report
In-flight advertising with Viasat Ads | Viasat Ads
August 20, 2026 at 2:59 PM EDT 297ms response HTTPS Secure301 Redirect
Executive Summary
http://ViasatAds.com scores 50/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 538 words, 23 images, and 1 schema blocks. Data confidence: 90%. Sustainability score: 80/100. Focus on the top recommendations below to improve your score.
297ms
Response Time
538
Word Count
23
Images
51
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score History
Current scan4 scans recorded· Tap or hover a point for score & time↑ 0 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Meta description may be truncated (203 chars)
2[SEO] Missing Twitter tags: twitter:image
3[SEO] 5 empty/unlabeled links found
4[SEO] 9 external links missing recommended rel attributes
5[SEO] 9 dofollow external links — slightly above optimal range
6[SEO] Primary keyword "flight advertising with" not found in H1
7[SEO] Primary keyword missing from first paragraph
8[SEO] Low readability score (19 Flesch) — content is hard to read
9[SEO] Missing og:locale tag — social platforms may guess language/region
10[SEO] Very high internal link density (78.1/1k words) — may appear spammy
Top Recommendations
1[Impact: High | Effort: Low] Trim your meta description to under 160 characters to prevent truncation
2[Impact: Medium | Effort: Medium] Add descriptive anchor text to all links for better SEO and accessibility
3[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
4[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
5[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
6[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
7[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
8[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
9[Impact: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
10[Impact: Medium | Effort: Low] Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
11[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
12[Impact: Medium | Effort: Low] Add <meta property="article:published_time"> for content freshness signals in social shares
Detailed Category Analysis
Key Findings
1Title tag is 50 characters — within optimal 50–60 range (Google 2025-2026)
2Single H1 tag present: "Captivate the travel audience with in-flight advertising"
3Clean heading hierarchy with no skipped levels
4Canonical URL is set and matches the page URL
5Complete Open Graph tags (title, description, image, url, type)
6HTML lang attribute set to "en-US"
7Favicon present
842 internal links help establish site architecture
99 external links provide reference signals
10Content length of 538 words is adequate
1151 total links — within recommended range
12URL length (26 chars) is within optimal range
13No redirect chain — direct URL resolution
14Healthy internal link ratio: 82% of links are internal
15Good keyword alignment between title and H1
16Primary keyword not in URL — acceptable for homepage/root URLs
17Moderate E-E-A-T signals (3 indicators)
18Twitter card uses summary_large_image — maximum visual impact
19Moderate entity presence: Viasat Ads, Sponsored Wi, Resources Contact
20Social share buttons detected: ShareThis
Issues Found
1Meta description may be truncated (203 chars)
2Missing Twitter tags: twitter:image
35 empty/unlabeled links found
49 external links missing recommended rel attributes
59 dofollow external links — slightly above optimal range
6Primary keyword "flight advertising with" not found in H1
7Primary keyword missing from first paragraph
8Low readability score (19 Flesch) — content is hard to read
9Missing og:locale tag — social platforms may guess language/region
10Very high internal link density (78.1/1k words) — may appear spammy
11Primary keyword "flight advertising with" not found in body content
Recommendations to Reach 100%
1Trim your meta description to under 160 characters to prevent truncation
2Add descriptive anchor text to all links for better SEO and accessibility
3Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
4Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
5Include your primary keyword in the H1 heading for strongest on-page SEO signal
6Include your primary keyword naturally in the first paragraph to establish topical relevance early
7Include your primary keyword in the URL slug for improved crawlability and click-through rates
8Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
9Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
10Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
11Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
12Add <meta property="article:published_time"> for content freshness signals in social shares
13Add <meta property="article:modified_time"> to signal content freshness
14Reduce internal link density — excessive linking dilutes individual link value
15Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
16Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
17OG sharing completeness at 83% — add missing tags for better social previews
18SEO (E-E-A-T): no author linkage or sameAs identity markup detected. Add a verifiable author byline with rel="author" and sameAs links to strengthen Experience/Expertise signals.
19SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Excellent server response time: 297ms
2HTML size is 186KB — acceptable
323/23 images use lazy loading
4Responsive images with srcset detected
5Preconnect hints for: https://assets.adobedtm.com, https://s7d1.scene7.com
6Preloaded resources: font, font, font, font, font, font, font
70 async and 1 deferred scripts
8Cache-Control header with max-age is set
9JavaScript payload (~304KB) is acceptable
10CDN detected: CloudFront — reduces latency for global users
11Gzip compression enabled
122 third-party script(s) — manageable count
1330 resource hints (preconnect/prefetch/preload) optimize loading
147 font(s) preloaded for faster text rendering
15Estimated LCP: ~1837ms — within Google's "good" threshold (<2.5s)
16Estimated INP: ~111ms — within Google's "good" threshold (<200ms)
Issues Found
15 render-blocking scripts slow down initial paint
2No WebP or AVIF image formats found
3Only 0/23 images have width/height attributes
4No font-display property found
5Moderate CSS payload (~240KB)
6HTTP/1.1 detected — no multiplexing
77 font files loaded — excessive font weight
88 render-blocking CSS files — delays first paint
9Estimated CSS bundle ~320KB — above optimal
10Moderate estimated CLS: 0.25 — above 0.1 "good" threshold
11No analytics tracking detected — flying blind on user behavior
Recommendations to Reach 100%
1Convert all non-critical scripts to async/defer to eliminate render-blocking resources
2Convert images to WebP or AVIF format for 30–50% file size reduction
3Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
4Add font-display: swap to web font declarations to show fallback text while fonts load
5Consider purging unused CSS and using critical CSS extraction to reduce render-blocking stylesheets
6Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
7Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
8Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
9Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
10Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
11Install Google Analytics 4 (GA4) with Google Tag Manager immediately — analytics is essential for measuring SEO and marketing ROI
12Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
13Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
14Performance: only 0/23 images set decoding="async". Add decoding="async" to non-critical images to keep image decode off the main thread.
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Responsive images via srcset serve appropriate sizes per device
523 images with lazy loading benefit mobile data users
6Mobile-responsive hamburger menu detected
Issues Found
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
4Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
5Only 1 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
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
3Add <link rel="apple-touch-icon"> for iOS homescreen icons
4Consider implementing a service worker for offline support and faster repeat visits
5Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
6Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
7Add env(safe-area-inset-*) CSS for proper display on notched/island devices
8Add :active / touch-action CSS for tactile feedback on mobile interactions
9Mobile/PWA: incomplete Apple web-app meta tags (missing capable, status-bar-style, title). Add apple-mobile-web-app-capable, -status-bar-style and -title for a polished iOS home-screen install.
10Mobile/PWA: viewport meta lacks viewport-fit=cover. Add it (with safe-area-inset padding) so content renders edge-to-edge on notched/dynamic-island devices.
Key Findings
1HTTPS enabled — encrypted connection
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4Content Security Policy header present
5X-Content-Type-Options: nosniff is set
6Referrer-Policy set to: strict-origin-when-cross-origin
7HSTS with preload and adequate max-age — eligible for browser preload list
8Privacy policy link detected
9Rate limiting recommended for form endpoints
10No stack traces or sensitive error details exposed in responses
11No raw email addresses exposed in page source
12No obvious secret/API-key patterns exposed in page source
136 script resource(s) catalogued for software-composition review
14No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing X-Frame-Options header
2Missing Permissions-Policy header
3Server header exposes technology: Apache
49 external links missing rel="noopener noreferrer" — security risk
5Cookie security issues: missing HttpOnly flag
6No cookie consent banner detected
7No Subresource Integrity (SRI) on external scripts
8Server technology disclosed via response headers/markup: Server: Apache
9security.txt file is missing — no standardized channel for reporting vulnerabilities
10Legacy X-XSS-Protection header present — deprecated and can introduce vulnerabilities in older browsers
11CSP is missing key hardening directive(s): base-uri, form-action, object-src, frame-ancestors
12Dangerous client-side sink(s) detected in inline scripts: innerHTML assignment — potential DOM-based XSS vectors
Recommendations to Reach 100%
1Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
2Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
3Add Cross-Origin-Opener-Policy: same-origin-allow-popups
4Add Cross-Origin-Resource-Policy: cross-origin
5Remove or obfuscate the Server header to avoid exposing your technology stack
6Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
7Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all cookies to prevent session hijacking and CSRF
8Implement a cookie consent banner for GDPR/ePrivacy compliance
9Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
10Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
11Remove or obfuscate technology-revealing headers (Server, X-Powered-By, X-AspNet-Version) and the generator meta tag to reduce your attack surface
12Add an RFC 9116 security.txt at /.well-known/security.txt with Contact and Expires fields so researchers can responsibly report security issues [Impact: Low | Effort: Low]
13Remove the deprecated X-XSS-Protection header and rely on a strong Content-Security-Policy instead [Impact: Low | Effort: Low]
14Add the missing CSP directives (base-uri, form-action, object-src, frame-ancestors) — e.g. object-src 'none', base-uri 'self', frame-ancestors 'none' — to close common bypasses [Impact: Medium | Effort: Low]
15Avoid eval, document.write, innerHTML and Function() with untrusted input; prefer textContent, DOM APIs and a trusted-types policy [Impact: Medium | Effort: Medium]
16A03 Software Supply Chain: only 0% of 2 cross-origin scripts use Subresource Integrity. Pin every third-party script with integrity+crossorigin and adopt SLSA provenance / a published SBOM for build integrity.
17A07 Authentication Failures: cookies do not use the __Host-/__Secure- prefix. Prefix session cookies with __Host- (with Secure, Path=/, no Domain) and add the Partitioned (CHIPS) attribute for cross-site isolation.
18A09 Logging & Alerting Failures: no client-side error/security monitoring detected. Add centralized logging with tamper-evident storage and real-time alerting on auth failures and anomalies.
Key Findings
1Language declared: en-US
2All key landmarks present (main, nav, footer)
3All 23 images have alt attributes
4All 1 forms have proper labels
5All 2 buttons have accessible labels
6Rich ARIA implementation: 77 elements with ARIA attributes
7No major HTML nesting or validity issues detected
Issues Found
1No skip navigation link
2No focus styles detected
323 images missing explicit dimensions — causes layout shifts for screen reader users
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add :focus-visible styles to all interactive elements for keyboard navigation visibility
3Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
4Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
11 schema block(s): Organization, WebSite
2Hreflang tags: en-us, pt-br, es-mx, es-es
3Strong semantic markup: header, nav, main, footer
4Complete social metadata (OG + Twitter Card)
5Social presence signals: twitter, facebook, instagram, linkedin, youtube
64 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8robots.txt file found
9robots.txt references 4 sitemap(s) — aids AI crawler discoverability
10High RAG-friendliness (100/100): 0 headings with IDs, 107 section anchors
11Content provenance signals detected (citations with sources, attributed claims)
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns found
3No sitemap reference found
4No llms.txt file found — AI models cannot find structured guidance for your site
5No content freshness signals (dateModified, datePublished, <time> elements)
6Very low HTML-to-text ratio (4%) — mostly markup, little visible content
Recommendations to Reach 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
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
4Create and reference an XML sitemap for AI crawler discoverability
5Use <strong> and <em> tags to highlight key entities, concepts, and terms
6Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
7Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
8Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
9Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
10Increase text-to-HTML ratio by adding more substantive content and reducing excessive markup/scripts
Key Findings
1Structured content: 14 lists, 0 tables — easily parsed by AI
25 external citations — strong reference density for AI model training
3Strong CRO: 4 clear call-to-action elements detected
4Above-the-fold CTA detected — captures immediate visitor attention
5Trust signals present: HTTPS Security, Privacy Policy
6Clear value proposition detected in heading elements
Issues Found
1Content may be too thin for AI optimization (538 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 794 divs vs 10 semantic elements
5Weak E-E-A-T schema signals
6No author or expertise signals
7Low form usability score (50/100) — may reduce form completions
8No social proof elements
Recommendations to Reach 100%
1Expand content to 1000+ words with comprehensive topic coverage for better AI model training value
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
7Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
8Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
9Improve form usability: add labels, placeholders, required field indicators, and clear submit buttons
10Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
114 lists provide scannable, AI-friendly content
257 original data elements (charts, figures, data tables)
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Insufficient structured data for generative engine context
4Hreflang set is missing a self-referencing tag — reduces geo-targeting accuracy
5Hreflang set is missing x-default fallback
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
3Include how-to or step-by-step instructional content for generative AI answer inclusion
4Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
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
7Include a self-referencing hreflang tag on every page (e.g., <link rel="alternate" hreflang="en" href="current-page-url">)
8Add <link rel="alternate" hreflang="x-default" href="primary-url"> as a fallback for unmatched languages/regions
9Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
10GEO: only 0/18 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
11GEO: no comparison tables or step-by-step structured blocks found. Add comparison tables and ordered how-to steps — formats generative engines favor for structured, citable answers.
Key Findings
114 lists provide scannable answers for People Also Ask
210 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
5No direct answer patterns ("X is defined as...", "X refers to...")
Recommendations to Reach 100%
1Create an FAQ section with FAQPage structured data — essential for People Also Ask and featured snippet inclusion
2Consider adding how-to content with HowTo schema for step-by-step rich results
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
7Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
8AEO: no 40–60 word concise answer directly follows a question heading. Lead each question section with a self-contained ~40–60 word answer to win featured snippets and voice answers.
Key Findings
1NAP information detected: phone: 17601127362
2Phone number(s) visible: 17601127362, 915-5629
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
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
6Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Key Findings
11 JSON-LD block(s) with types: Organization, WebSite
2Some top-tier schemas: Organization, WebSite
3No schema validity issues detected
Issues Found
1Microdata or RDFa detected alongside JSON-LD
2Only basic schema implementation
3No sameAs properties in schema — missing entity disambiguation
4No rich results eligibility detected
Recommendations to Reach 100%
1Migrate all structured data to JSON-LD format — it's easier to maintain, debug, and is Google's preferred format
2Expand structured data with more specific schema types relevant to your content
3Add more top-tier schema types — consider: LocalBusiness, Product, Article
4Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
5Add BreadcrumbList schema — enables breadcrumb rich results in Google
6Add FAQPage schema to FAQ content — enables expandable rich results
7Consider adding HowTo schema for instructional content
8Add more schema types — diverse structured data improves AI and search engine understanding
9Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles
10Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
11Add nested schemas (e.g., author within Article, offers within Product) to define entity relationships
12Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
13Schema.org (maximize): long-form article content detected but no Article/BlogPosting schema. Add Article with headline, author, datePublished, dateModified, image and publisher for maximal eligibility.
Key Findings
1Form error/validation feedback detected
2Relative units (rem/em/clamp) detected — supports text resizing
3Page language declared — aids assistive technology
4All ARIA roles are valid
5Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
6Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3Links may not be distinguishable from surrounding text
4Low semantic-to-div ratio — 794 divs vs 10 semantic elements
5No focus styles detected
6No form error identification detected
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
3Ensure links have visible underlines or other non-color visual indicators (WCAG 1.4.1)
4Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
5Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
6Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
7Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
8WCAG 2.2 (1.4.13 Content on Hover/Focus): 17 interactive elements rely on native title tooltips, which are not dismissable, hoverable or persistent. Replace with accessible tooltip components.
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.