This website audit report analyzes https://outlierjets.com across 12 critical dimensions with actionable recommendations.
https://outlierjets.com
67Needs Workout of 100
Website Audit Report
I am outlier | Outlier Jets - Outlier
May 19, 2026 at 10:37 AM EDT 299ms response HTTPS Secure
Executive Summary
https://outlierjets.com scores 67/100 (D+). Priority improvements needed in Performance, AI Readiness, AIO. The site has 504 words, 30 images, and 0 schema blocks. Focus on the top recommendations below to improve your score.
299ms
Response Time
504
Word Count
30
Images
50
Links
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Heading hierarchy gaps: h1 → h3 (skips h2), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h6 (skips h3), h3 → h6 (skips h4), h3 → h6 (skips h4)
2[SEO] Missing canonical URL
3[SEO] No Twitter Card tags found
4[SEO] 5 empty/unlabeled links found
5[Performance] 9 render-blocking scripts slow down initial paint
6[Performance] No lazy loading on images
7[Performance] No WebP or AVIF image formats found
8[Performance] No responsive image srcset found
9[Performance] Only 0/30 images have width/height attributes
10[Performance] No font-display property found
Top Recommendations
1Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
2Add a <link rel="canonical"> tag pointing to the preferred version of this page
3Add Twitter Card meta tags for better social media previews
4Add descriptive anchor text to all links for better SEO and accessibility
5Convert all non-critical scripts to async/defer to eliminate render-blocking resources
6Add loading="lazy" to below-the-fold images to improve initial page load
7Convert images to WebP or AVIF format for 30–50% file size reduction
8Use srcset and sizes attributes on images to serve appropriately sized images per device
9Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
10Preload critical resources (fonts, hero images) with <link rel="preload">
11Add font-display: swap to web font declarations to show fallback text while fonts load
12Move inline scripts to external files with defer attributes
Detailed Category Analysis
Key Findings
1Title tag is 37 characters — within optimal 30–60 range
2Meta description is 128 characters — within optimal 120–160 range
3Single H1 tag present: "Elevate Your Journey"
4Complete Open Graph tags (title, description, image, url, type)
5HTML lang attribute set to "en"
6Favicon present
731 internal links help establish site architecture
86 external links provide reference signals
9Content length of 504 words is adequate
Issues Found
1Heading hierarchy gaps: h1 → h3 (skips h2), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h6 (skips h3), h3 → h6 (skips h4), h3 → h6 (skips h4)
2Missing canonical URL
3No Twitter Card tags found
45 empty/unlabeled links found
Recommendations to Reach 100%
1Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
2Add a <link rel="canonical"> tag pointing to the preferred version of this page
3Add Twitter Card meta tags for better social media previews
4Add descriptive anchor text to all links for better SEO and accessibility
Key Findings
1Excellent server response time: 299ms
2Lean HTML document: 48KB
3Preconnect hints for: https://fonts.googleapis.com, https://fonts.gstatic.com
44 async and 2 deferred scripts
5Cache-Control header with max-age is set
Issues Found
19 render-blocking scripts slow down initial paint
2No lazy loading on images
3No WebP or AVIF image formats found
4No responsive image srcset found
5Only 0/30 images have width/height attributes
6No font-display property found
717 inline scripts
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 explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
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
8Move inline scripts to external files with defer attributes
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
Issues Found
1No web app manifest found
2Missing Apple touch icon
3No responsive image srcset — mobile users may download oversized images
Recommendations to Reach 100%
1Create a manifest.json for PWA capabilities and add-to-homescreen support
2Add <link rel="apple-touch-icon"> for iOS homescreen icons
3Consider implementing a service worker for offline support and faster repeat visits
4Implement srcset to serve smaller images on mobile devices, saving bandwidth
Key Findings
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3X-Content-Type-Options: nosniff is set
4X-Frame-Options header prevents clickjacking
Issues Found
1Missing Content-Security-Policy header
2Missing Referrer-Policy header
3Missing Permissions-Policy header
4Server header exposes technology: LiteSpeed
5X-Powered-By header exposes: PHP/8.0.30
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
3Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
4Add Cross-Origin-Opener-Policy: same-origin-allow-popups
5Add Cross-Origin-Resource-Policy: cross-origin
6Remove or obfuscate the Server header to avoid exposing your technology stack
7Remove X-Powered-By header
Key Findings
1Language declared: en
2All key landmarks present (main, nav, footer)
3All 30 images have alt attributes
4All 4 buttons have accessible labels
Issues Found
1No skip navigation link
23 form(s) missing proper labels
3No ARIA attributes detected
4Heading hierarchy has gaps — confusing for screen readers
5No focus styles detected
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add <label> elements associated with every form input via for/id attributes
3Add ARIA attributes to interactive elements for better screen reader support
4Add :focus-visible styles to all interactive elements for keyboard navigation visibility
Key Findings
1Strong semantic markup: nav, main, section, footer
2FAQ/Q&A content patterns detected — highly valuable for AI citation
3Social presence signals: linkedin, instagram, facebook, youtube, twitter
42 call-to-action elements detected
Issues Found
1No structured data (Schema.org) found
2Incomplete social metadata
3No breadcrumb navigation
4No 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
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Create and reference an XML sitemap for AI crawler discoverability
5Use <strong> and <em> tags to highlight key entities, concepts, and terms
Key Findings
1Structured content: 8 lists, 0 tables — easily parsed by AI
Issues Found
1Content may be too thin for AI optimization (504 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 127 divs vs 8 semantic elements
5Weak E-E-A-T schema signals
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
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
28 lists provide scannable, AI-friendly content
3How-to instructional patterns detected — valued by AI answer engines
Issues Found
1No data tables for AI comparison extraction
2Insufficient structured data for generative engine context
Recommendations to Reach 100%
1Add comparison tables with structured data — generative AI engines frequently cite tabular content
2Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
3Include unique statistics, expert quotes, and original insights that generative AI would want to cite
4Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
Key Findings
1Question-answer heading patterns support featured snippet capture
28 lists provide scannable answers for People Also Ask
Issues Found
1No FAQ content or schema
2How-to content exists but lacks HowTo schema
3No Speakable schema for voice search
4No 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
3Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
4Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
5Consider adding video content with VideoObject schema for multimedia search results
Key Findings
1NAP information detected: phone: 3955086
2Phone number(s) visible: 3955086
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
3Page language declared — aids assistive technology
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3No error suggestion mechanisms detected in forms
4Low semantic-to-div ratio — 127 divs vs 8 semantic elements
5No focus styles 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
3Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
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)
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.