This website audit report analyzes http://2amproject.com/ across 12 critical dimensions with actionable recommendations.
http://2amproject.com/
44Poorout of 100
Website Audit Report
2AM PROJECT | HOME
July 21, 2026 506ms response HTTPS Secure301 Redirect
Executive Summary
http://2amproject.com/ scores 44/100 (F). Strong areas include WCAG. Priority improvements needed in SEO, Performance, Security. The site has 189 words, 52 images, and 2 schema blocks. Data confidence: 80%. Sustainability score: 60/100. Focus on the top recommendations below to improve your score.
506ms
Response Time
189
Word Count
52
Images
13
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score History
Current scan2 scans recorded↑ 0 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is very short (18 chars)
2[SEO] Meta description may be truncated (185 chars)
3[SEO] Thin content (189 words)
4[SEO] Title and H1 share no keywords — misaligned topic signals
5[SEO] Primary keyword "2am project" not found in H1
6[SEO] Primary keyword missing from first paragraph
7[SEO] Weak E-E-A-T signals (2 indicators)
8[SEO] Low readability score (32 Flesch) — content is hard to read
9[SEO] Missing og:locale tag — social platforms may guess language/region
10[SEO] OG image dimensions too small for social platforms
Top Recommendations
1[Impact: High | Effort: Low] Expand your title to 50–60 characters for better click-through rates and SERP visibility
2[Impact: High | Effort: Low] Trim your meta description to under 160 characters to prevent truncation
3[Impact: Medium | Effort: Medium] Expand your content to at least 300+ words for better search rankings
4[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
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: Medium] Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
8[Impact: High | Effort: Medium] Link to a Contact page — essential trust signal for E-E-A-T and local SEO
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: Medium] Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
Detailed Category Analysis
Key Findings
1Single H1 tag present: "midnight munchies? ✅
open past midnight? ✅
late night d…"
2Clean heading hierarchy with no skipped levels
3Canonical URL is set and matches the page URL
4Complete Open Graph tags (title, description, image, url, type)
5Complete Twitter Card tags present
6HTML lang attribute set to "en"
7Favicon present
811 internal links help establish site architecture
92 external links provide reference signals
1013 total links — within recommended range
11URL length (27 chars) is within optimal range
12No redirect chain — direct URL resolution
13Healthy internal link ratio: 85% of links are internal
14Good anchor text diversity: 100% unique anchor texts
15Optimal dofollow outbound links: 2 (ideal 2–5 per page for link authority signals)
16Primary keyword present in URL — good URL optimization
17Twitter card uses summary_large_image — maximum visual impact
Issues Found
1Title tag is very short (18 chars)
2Meta description may be truncated (185 chars)
3Thin content (189 words)
4Title and H1 share no keywords — misaligned topic signals
5Primary keyword "2am project" not found in H1
6Primary keyword missing from first paragraph
7Weak E-E-A-T signals (2 indicators)
8Low readability score (32 Flesch) — content is hard to read
9Missing og:locale tag — social platforms may guess language/region
10OG image dimensions too small for social platforms
11Keyword stuffing detected: "2am project" appears 3 times (3.2% density — exceeds 3%)
12No social sharing buttons/widgets detected
Recommendations to Reach 100%
1Expand your title to 50–60 characters for better click-through rates and SERP visibility
2Trim your meta description to under 160 characters to prevent truncation
3Expand your content to at least 300+ words for better search rankings
4Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
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
7Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
8Link to a Contact page — essential trust signal for E-E-A-T and local SEO
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)
12Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
13Reduce keyword density from 3.2% to 0.5–2.5% — Google penalizes keyword stuffing. Use synonyms and natural language variations
14Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
15OG sharing completeness at 83% — add missing tags for better social previews
Key Findings
1Acceptable response time: 506ms
221/52 images use lazy loading
3Modern image formats (WebP/AVIF) detected
4Responsive images with srcset detected
5font-display property detected — reduces invisible text during font loading
66 async and 2 deferred scripts
7Cache-Control header with max-age is set
8HTTP/3 (QUIC) detected — fastest connection protocol
9CDN detected: CDN (unidentified) — reduces latency for global users
10Brotli compression enabled — best-in-class compression
11Estimated LCP: ~1366ms — within Google's "good" threshold (<2.5s)
12Variable fonts detected — reduces total font file downloads
13Server-Timing header present — enables performance debugging
Issues Found
1Very large HTML: 1217KB
23 render-blocking scripts slow down initial paint
3Only 5/52 images have width/height attributes
448 inline <style> blocks
555 inline scripts
6Large CSS payload (~763KB across 2 files) — slows rendering
7Moderate JavaScript payload (~900KB)
811 third-party scripts from 2 domains — significant performance impact
954 font files loaded — excessive font weight
102 render-blocking CSS file(s)
11Estimated CSS bundle ~783KB — above optimal
12Potential long-task scripts: Inline script (~11KB), Inline script (~16KB), Inline script (~54KB)
13High estimated CLS: 0.35 — exceeds Google's 0.25 threshold
14Estimated INP: ~211ms — needs improvement (goal: <200ms)
15Web fonts loaded without preload — causes FOIT/FOUT flash
16No analytics tracking detected — flying blind on user behavior
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
4Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
5Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
6Preload critical resources (fonts, hero images) with <link rel="preload">
7Extract inline styles into external CSS files for better caching and maintainability
8Move inline scripts to external files with defer attributes
9Reduce CSS payload with PurgeCSS, tree-shaking unused styles, and critical CSS inlining. Aim for <200KB total CSS
10Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
11Audit third-party scripts — defer non-critical ones and remove unused trackers/widgets to reduce main thread blocking
12Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
13Preload your primary font with <link rel="preload" as="font" crossorigin> for faster first contentful paint
14Consider inlining critical CSS and deferring non-essential stylesheets
15Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
16Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
17Fix CLS: add explicit width/height to all images and iframes, preload fonts, avoid injecting content above existing content
18Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
19Add <link rel="preload" as="font" crossorigin> for your primary font files to eliminate flash of invisible/unstyled text
20Install Google Analytics 4 (GA4) with Google Tag Manager immediately — analytics is essential for measuring SEO and marketing ROI
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
721 images with lazy loading benefit mobile data users
8Mobile-responsive hamburger menu detected
9Touch feedback CSS detected (active states or touch-action)
103 internationalization signals detected (hreflang, lang, dir, locale meta)
Issues Found
1No theme-color meta tag
2No web app manifest found
3Fixed-width elements detected (>800px) — may cause horizontal scrolling on mobile
4Only 2 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
5Estimated page weight ~5610KB — heavy for mobile data plans
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
3Replace fixed pixel widths with relative units (%, vw, max-width) to prevent horizontal overflow on small screens
4Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
5Add env(safe-area-inset-*) CSS for proper display on notched/island devices
6Reduce page weight below 3MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
Key Findings
1HTTPS enabled — encrypted connection
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4X-Content-Type-Options: nosniff is set
5Privacy policy link detected
6No stack traces or sensitive error details exposed in responses
7No raw email addresses exposed in page source
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
61 external link(s) without noopener/noreferrer
7HSTS header present but missing preload directive
8Cookie security issues: missing Secure flag; missing HttpOnly flag; missing SameSite attribute
9No cookie consent banner detected
10No Subresource Integrity (SRI) on external scripts
11Server technology disclosed via response headers/markup: Server: Pepyaka; Generator meta tag: Wix.com Website Builder
12security.txt file is missing — no standardized channel for reporting vulnerabilities
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
8Add rel="noopener noreferrer" to external links for security
9Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
10Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all cookies to prevent session hijacking and CSRF
11Implement a cookie consent banner for GDPR/ePrivacy compliance
12Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
13Remove or obfuscate technology-revealing headers (Server, X-Powered-By, X-AspNet-Version) and the generator meta tag to reduce your attack surface
14Add 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]
Key Findings
1Language declared: en
2All key landmarks present (main, nav, footer)
3All 52 images have alt attributes
4All iframes have title attributes
5Rich ARIA implementation: 59 elements with ARIA attributes
6Focus styles detected for keyboard navigation
Issues Found
1No skip navigation link
226 button(s) missing accessible labels
33 minor HTML validity issue(s)
447 images missing explicit dimensions — causes layout shifts for screen reader users
52 video(s) missing captions/subtitles
610 focusable element(s) inside aria-hidden containers
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add text content or aria-label to all buttons
3Review and fix HTML structure issues for better accessibility and cross-browser compatibility
4Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
5Add <track kind="captions"> or <track kind="subtitles"> to all video elements (WCAG 1.2.2)
6Remove focusable elements (links, buttons, inputs) from aria-hidden regions — they trap keyboard users in invisible content
Key Findings
12 schema block(s): LocalBusiness, WebSite
2Strong semantic markup: header, section, nav, main, footer
3Complete social metadata (OG + Twitter Card)
4Sitemap reference detected
5Social presence signals: instagram
6No AI crawlers blocked via meta tags — content accessible to AI search engines
7robots.txt file found
8robots.txt references 1 sitemap(s) — aids AI crawler discoverability
9llms.txt detected (score: 75/100, quality: comprehensive)
10llms.txt has proper title and description block
11llms.txt has 13 well-organized sections
12llms.txt references 4 URLs for AI navigation
13llms.txt includes service/product catalog
14llms.txt uses proper Markdown formatting for machine readability
15llms.txt uses canonical domain in URLs
16llms.txt includes citation/attribution guidance
17llms.txt includes version/date for freshness tracking
18High RAG-friendliness (100/100): 0 headings with IDs, 254 section anchors
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns found
3No llms-full.txt companion file found
4llms.txt is not referenced in HTML
5No content freshness signals (dateModified, datePublished, <time> elements)
Recommendations to Reach 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
2Add hreflang tags if your site serves multiple languages or regions
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Add an FAQ section with FAQPage schema to increase chances of AI engine citations
5Use <strong> and <em> tags to highlight key entities, concepts, and terms
6Create /llms-full.txt with detailed documentation — services, pricing, case studies, technical specs — for AI models that want depth
7Add more key page URLs to llms.txt — aim for 8-15 covering all major sections of your site
8Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your <head> for discoverability
9Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Structured content: 3 lists, 0 tables — easily parsed by AI
2Good paragraph length for readability and AI parsing
31 external citation(s)
41 call-to-action element(s) detected
5Above-the-fold CTA detected — captures immediate visitor attention
6Trust signals present: HTTPS Security, Privacy Policy
7Clear value proposition detected in heading elements
Issues Found
1Very thin content (189 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 498 divs vs 20 semantic elements
5Weak E-E-A-T schema signals
6No author or expertise signals
7No social proof elements
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
7Include specific statistics, percentages, and data points that AI models can extract and cite in responses
8Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
9Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
10Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
11Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
13 lists detected
22 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
5No hreflang tags — generative engines cannot determine language/region targeting
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
5Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
6Include unique statistics, expert quotes, and original insights that generative AI would want to cite
7Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
8Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
1Short paragraphs are well-suited for answer extraction
23 lists provide scannable answers for People Also Ask
3Video content detected — supports multimedia answer results
45 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
6Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
Key Findings
1NAP information detected: phone: 17842199684, email: [email protected]
2Phone number(s) visible: 17842199684, 2444635
3Email address found: [email protected]
4LocalBusiness schema: LocalBusiness
Issues Found
1No Google Maps embed
2No address microdata
3No geo meta tags
4LocalBusiness schema present but no opening hours
5No review/rating schema
Recommendations to Reach 100%
1Add an embedded Google Map to your contact or about page for local search signals
2Add PostalAddress schema or itemprop="address" microdata to your address elements
3Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
4Add openingHoursSpecification to your LocalBusiness schema — hours are a top local ranking factor
5Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
6Add areaServed property to your LocalBusiness schema to define your service radius
Key Findings
12 JSON-LD block(s) with types: LocalBusiness, WebSite
2All structured data uses JSON-LD format — Google's recommended format
3Moderate schema coverage
4Some top-tier schemas: LocalBusiness, WebSite
Issues Found
1WebSite has very few properties (2)
2No sameAs properties in schema — missing entity disambiguation
3Schema property completeness averaging 57%
4No rich results eligibility detected
Recommendations to Reach 100%
1Add more top-tier schema types — consider: Organization, Product, Article
2Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
3Add BreadcrumbList schema — enables breadcrumb rich results in Google
4Add FAQPage schema to FAQ content — enables expandable rich results
5Consider adding HowTo schema for instructional content
6Add more properties to schema types — aim for at least 5 meaningful properties per type
7Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles
8Fill in missing recommended properties for each schema type
9Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
10Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
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)
42 media element(s) without autoplay
5Relative units (rem/em/clamp) detected — supports text resizing
6Focus styles detected for keyboard navigation visibility
7Page language declared — aids assistive technology
8All ARIA roles are valid
9prefers-reduced-motion detected but enforcement unclear
Issues Found
1Low semantic-to-div ratio — 498 divs vs 20 semantic elements
273 elements with tabindex="-1" — may hide content from keyboard users
3Multiple fixed/sticky elements may obscure focused content (WCAG 2.4.11)
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
3Ensure sticky headers/footers do not fully obscure the keyboard focus indicator. Use scroll-padding-top or ensure focus remains visible under overlapping elements (WCAG 2.4.11 AA)
4Ensure prefers-reduced-motion actually disables animations (set animation: none and transition: none in the media query)
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.