Website Audit Report

Source diagnostic wording is preserved.

1. [Impact 3/3 · v6:psi-performance] Review the Lighthouse diagnostics for this category and retest.

2. Use srcset and sizes attributes on images to serve appropriately sized images per device

3. Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression

4. Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously

5. Reduce DOM node count to under ~1,500 by simplifying markup and paginating long lists (Lighthouse best practice) [Impact: Medium | Effort: Medium]

6. Set a Cache-Control header with an appropriate max-age (and immutable for versioned assets) to enable browser caching [Impact: Medium | Effort: Low]

7. Add width and height attributes (or CSS aspect-ratio) to every image to reserve space and prevent layout shift [Impact: Medium | Effort: Low]

8. Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.

Evidence and checks

Excellent server response time: 207ms

HTML is 695KB — typical for SSR framework with rich content

2 framework-managed script(s) — optimized by build pipeline

44/44 images use lazy loading

Modern image formats (WebP/AVIF) detected

Most images have explicit width/height attributes (prevents layout shift)

Preconnect hints for: https://fonts.googleapis.com, https://fonts.gstatic.com

Preloaded resources: script, image

font-display property detected — reduces invisible text during font loading

30 async and 1 deferred scripts

Cache-Control header with max-age is set

31 inline scripts (framework hydration/data — standard for SSR apps)

Lean CSS payload (~154KB)

JavaScript payload (~1926KB) is acceptable for framework app

HTTP/1.1 detected — protocol upgrade managed at CDN/infrastructure level

CDN detected: Cloudflare — reduces latency for global users

Gzip compression enabled

1 third-party script(s) — manageable count

6 resource hints (preconnect/prefetch/preload) optimize loading

5 framework hydration script(s) — standard for SSR apps

Variable fonts detected — reduces total font file downloads

Good analytics setup: GA4 + event tracking

Lab-proxy estimates — Speed Index ~6577ms, TTI ~7217ms, TBT ~2000ms (estimated from resource composition, not third-party field data)

Runtime JavaScript was not executed by this HTML scan. Use the JavaScript error diagnostics on the auditor page to analyze browser evidence; absence of logs is not a pass.

v6:psi-performance · Lighthouse Performance: 60/100 — Mobile-strategy Lighthouse category

Source diagnostic wording is preserved.

1. Implement srcset to serve smaller images on mobile devices, saving bandwidth

2. Reduce page weight below 3MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS

Evidence and checks

Viewport meta tag present: width=device-width, initial-scale=1, viewport-fit=cover

HTML5 doctype declared

Character encoding declared

Theme color meta tag set for mobile browsers

Web app manifest detected — PWA-ready

Apple touch icons present

Service worker detected — offline capability possible

44 images with lazy loading benefit mobile data users

Mobile-responsive hamburger menu detected

PWA install-ready: manifest + service worker + HTTPS all present

Web app manifest includes 19 icon sizes — good coverage

CSS safe-area-inset handling detected — notch/dynamic-island compatible

Touch feedback CSS detected (active states or touch-action)

3 internationalization signals detected (hreflang, lang, dir, locale meta)

5 image(s) without explicit width/height — most impactful for layout stability (CLS) on mobile (see Performance for remediation)

v6:psi-mobile · Lighthouse mobile usability evidence: 100/100 — [{"id":"meta-viewport","score":100,"title":"`[user-scalable=\"no\"]` is not used in the `<meta name=\"viewport\">` element and the `[maximum-scale]` attribute is not less than 5."},{"id":"target-size","score":100,"title":"Touch targets have sufficient size and spacing."}]

Source diagnostic wording is preserved.

1. Audit internal links for broken paths. Common issues: service slug changes, glossary terms without deep-dive pages, missing locale prefixes [Impact: High | Effort: Medium]

2. Include your primary keyword naturally in the first paragraph to establish topical relevance early

3. Include your primary keyword in the URL slug for improved crawlability and click-through rates

4. Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary

Evidence and checks

Title tag is 54 characters — within optimal 50–60 range (Google 2025-2026)

Meta description is 151 characters — within optimal 140–160 range (2025-2026)

Single H1 tag present: "Digital Marketing Company for SEO, AIO & Growth"

Clean heading hierarchy with no skipped levels

Canonical URL is set and matches the page URL

Complete Open Graph tags (title, description, image, url, type)

Complete Twitter Card tags present

HTML lang attribute set to "en"

Favicon present

173 internal links help establish site architecture

19 external links provide reference signals

196 total links — within recommended range

URL length (31 chars) is within optimal range

All external links have proper rel attributes (nofollow/noopener)

No redirect chain — direct URL resolution

Healthy internal link ratio: 88% of links are internal

Good anchor text diversity: 88% unique anchor texts

Good keyword alignment between title and H1

Optimal dofollow outbound links: 4 (ideal 2–5 per page for link authority signals)

Primary keyword "digital marketing company" found in H1 — strong on-page signal

Primary keyword not in URL — acceptable for homepage/root URLs

Strong E-E-A-T signals detected (9 indicators)

og:locale set to "en_US"

OG image uses WebP format — optimal for quality/size balance

OG image dimensions ≥1200×630px — optimal for all platforms

article:published_time present — content freshness signal for social platforms

article:modified_time present — update recency signal

Twitter card uses summary_large_image — maximum visual impact

Internal link density (34.8/1k words) — above average but acceptable for navigation-heavy pages

Optimal keyword density: "digital marketing company" at 0.6% (10 occurrences)

Low passive voice ratio (2%) — clear, active writing style

Table of Contents detected — improves dwell time and jump-link navigation

Zero-click optimized: 1 TL;DR/summary block(s) + 2 definition-style lead paragraph(s)

Strong entity salience: Digital Marketing Co, See How It Works, Marketing Co (score: 84)

Strong dwell/engagement signals: 3 indicators (ToC, related content, internal links)

Social share buttons detected: ShareThis

OG sharing completeness: 100% — all tags present for optimal social previews

3 hreflang annotation(s) present for international targeting

Character encoding declared as UTF-8

v6:description-presence · Meta description presence: 100/100 — Digital Marketing Co. is a full-service digital marketing company. We deliver SEO, AIO, GEO, AEO, link building & web development that drives real ROI.

v6:description-length · Meta description length: 100/100 — 151 characters; diagnostic range 70–170, not a ranking rule

v6:description-quality · Meta description quality heuristic: 100/100 — Placeholder and lexical-diversity checks; not semantic quality certification

v6:psi-seo · Lighthouse SEO: 100/100 — Mobile-strategy Lighthouse category

Source diagnostic wording is preserved.

Evidence and checks

v6:technical-status · Document HTTP status: 100/100 — HTTP 200

v6:technical-canonical · Canonical syntax: 100/100 — https://digitalmarketingco.org

v6:technical-language · Document language: 100/100 — en

v6:technical-refresh · Meta refresh: 100/100 — Meta refresh count: 0

Source diagnostic wording is preserved.

1. Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks

2. Strengthen CSP: consider nonce-based policies when feasible

3. When feasible, migrate to nonce-based CSP for inline scripts/styles

4. Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions

5. If these emails are not meant to be public, obfuscate them or replace with a contact form; for intentional contact addresses this is informational only [Impact: Info | Effort: Low]

6. A05 Injection: a Markdown renderer appears to run without an accompanying sanitizer. Always post-sanitize rendered HTML (DOMPurify) to prevent stored/DOM XSS.

Evidence and checks

HTTPS enabled — encrypted connection

HSTS header present — enforces HTTPS

Content Security Policy header present

X-Content-Type-Options: nosniff is set

X-Frame-Options header prevents clickjacking

Referrer-Policy set to: strict-origin-when-cross-origin

Permissions-Policy header restricts browser features

Cross-Origin-Opener-Policy set

Cross-Origin-Resource-Policy set

Cross-Origin-Embedder-Policy set

Server via CDN proxy (cloudflare) — header added by infrastructure, not application

All external links have security-safe rel attributes

HSTS with preload and adequate max-age — eligible for browser preload list

No cookie security issues detected

Privacy policy link detected

Cookie consent mechanism detected

CSP strictness score 40/100 — adequate for modern framework apps that require inline styles/scripts

CSP uses 2 unsafe-inline directive(s) — standard requirement for modern SSR frameworks

Permissions-Policy restricts 9 browser features (camera, microphone, geolocation, interest-cohort)

Rate limiting recommended for form endpoints

No server software/technology fingerprints exposed in headers or markup

security.txt present and valid (/.well-known/security.txt) — provides a channel for vulnerability disclosure

No stack traces or sensitive error details exposed in responses

No obvious secret/API-key patterns exposed in page source

33 script resource(s) catalogued for software-composition review

No common sensitive paths (.git, .env, server-status, …) were publicly accessible

Cross-origin isolation enabled (COOP + COEP) — hardened against Spectre-style side-channel and cross-origin leaks

A09: a client-side error/monitoring integration (e.g. Sentry/Datadog) is present — supports security logging & alerting.

Source diagnostic wording is preserved.

1. Review HTML structure for any non-framework-related nesting issues

2. Add <track kind="captions"> or <track kind="subtitles"> to all video elements (WCAG 1.2.2)

Evidence and checks

Language declared: en

Skip navigation link present

All key landmarks present (main, nav, footer)

All 44 images have alt attributes

All 1 forms have proper labels

All iframes have title attributes

All 38 buttons have accessible labels

Rich ARIA implementation: 92 elements with ARIA attributes

Focus styles detected for keyboard navigation

5 minor HTML validity issue(s) — common in modern framework component patterns

1 table(s) have captions/labels

v6:psi-accessibility · Lighthouse Accessibility: 100/100 — Mobile-strategy Lighthouse category

Source diagnostic wording is preserved.

1. When feasible, consolidate all structured data into JSON-LD format

2. Priority schemas to add: Article, Product, HowTo, Person

3. Consider adding HowTo schema for instructional content

4. Schema.org (maximize): step-by-step content detected but no HowTo schema. Add HowTo with HowToStep items (name, text, image) for step-based rich results.

5. Schema.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.

6. Schema.org (maximize): commerce signals detected but no Product schema. Add Product with offers (price, priceCurrency, availability), aggregateRating and review for product rich results.

Evidence and checks

3 JSON-LD block(s) with types: Organization, ProfessionalService, LocalBusiness, WebSite, ProfessionalService, LocalBusiness, WebPage, WebSite, SiteNavigationElement, BreadcrumbList

Some microdata attributes detected alongside JSON-LD — common for address/local business markup in modern frameworks

Comprehensive schema implementation

Strong top-tier schema coverage: LocalBusiness, Organization, FAQPage, BreadcrumbList, WebSite

BreadcrumbList schema → breadcrumb rich results

FAQPage schema → expandable FAQ rich results

Service schema describes your offerings

Review/Rating schema → star ratings in search results

No schema validity issues detected

Rich schema diversity: 9 distinct types with properties

Entity linking via sameAs: 10 external profiles linked — strengthens Knowledge Graph

Average schema property completeness: 96% — well-implemented

Rich results eligible: FAQ, Breadcrumbs, Review

Schema nesting depth: 2 levels — rich entity relationships

SearchAction schema present. Google retired the sitelinks search box in November 2024; this markup does not establish eligibility for that feature.

Additional rich result types: SoftwareApplication

Schema.org: a connected @graph with 15 entity types is present — strong structured-data maturity.

v6:social-tags · Open Graph and Twitter metadata: 100/100 — Four core sharing tags checked; not a direct ranking factor

Source diagnostic wording is preserved.

Evidence and checks

Rich structured data: 3 schema blocks (Organization, ProfessionalService, LocalBusiness, WebSite, ProfessionalService)

Hreflang tags: en, es, x-default

Strong semantic markup: header, nav, main, section, aside, details, summary, article, time, figure, mark, figcaption, address, footer

Complete social metadata (OG + Twitter Card)

Breadcrumb navigation present — aids AI in understanding site hierarchy

FAQ/Q&A content patterns detected — highly valuable for AI citation

Sitemap reference detected

20 strong entity mentions (bold/emphasized text)

Social presence signals: facebook, youtube, instagram, tiktok, twitter, linkedin

14 call-to-action elements detected

No AI crawlers blocked via meta tags — content accessible to AI search engines

robots.txt file found

AI crawlers explicitly allowed in robots.txt: GPTBot, ChatGPT-User, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Bytespider, Applebot-Extended, Cohere-ai, Amazonbot

robots.txt references 5 sitemap(s) — aids AI crawler discoverability

llms.txt detected (score: 83/100, quality: comprehensive)

llms-full.txt companion file detected (8KB)

llms.txt has proper title and description block

llms.txt has 7 well-organized sections

llms.txt references 16 URLs for AI navigation

llms.txt includes service/product catalog

llms.txt uses proper Markdown formatting for machine readability

llms.txt links to detailed documentation (llms-full.txt)

llms.txt referenced in HTML for discoverability

llms.txt uses canonical domain in URLs

High RAG-friendliness (100/100): 24 headings with IDs, 9 section anchors

Additional AI crawlers allowed: PerplexityBot, Bytespider, Amazonbot, Applebot-Extended, Cohere-ai

Content provenance signals detected (citations with sources, attributed claims)

Content freshness signals present (dateModified/datePublished/time elements)

Good HTML-to-text ratio (47%) — AI crawlers can extract content efficiently

Comprehensive content (4971 words) — strong for AI model training

Rich Q&A content (13 FAQ/accordion elements)

Strong entity emphasis: 20 key terms highlighted

Good semantic-to-div ratio: 108 semantic elements

Structured content: 10 lists, 2 tables — easily parsed by AI

E-E-A-T schema signals present (2 types)

Good paragraph length for readability and AI parsing

Speakable schema detected — content optimized for voice assistants

15 external citations — strong reference density for AI model training

43 statistics/data points — excellent for AI knowledge extraction

2 blockquotes/quotes enhance authority signals

Author expertise signals detected (bio, credentials, Person schema)

Strong CRO: 5 clear call-to-action elements detected

Above-the-fold CTA detected — captures immediate visitor attention

Good form usability score: 100/100

Trust signals present: Reviews/Testimonials, Trust Badges, Guarantee

Social proof elements detected — builds credibility and conversion confidence

Clear value proposition detected in heading elements

Source diagnostic wording is preserved.

1. GEO: only 10/72 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.

Evidence and checks

Direct question-answer patterns found — good for Google SGE and AI citations

2 comparison/data table(s) — highly extractable by AI

10 lists provide scannable, AI-friendly content

4 ordered lists provide step-by-step structure

How-to instructional patterns detected — valued by AI answer engines

1 definition list(s) — excellent for AI glossary extraction

Comprehensive content depth (4971 words) supports AI citation

20 emphasized terms suggest unique, quotable insights

3 schema blocks help AI engines understand content context

comprehensive content length — good for authority signals

Hreflang includes self-referencing tag

x-default hreflang fallback present

43 data points/statistics — content has original research signals

21 original data elements (charts, figures, data tables)

3 unique insight patterns detected (original research/analysis signals)

2 quotation elements enhance credibility for GEO

Source diagnostic wording is preserved.

1. Add HowTo schema to your instructional content for rich result eligibility

Evidence and checks

FAQPage schema markup present — eligible for rich FAQ results

Question-answer heading patterns support featured snippet capture

Speakable schema supports voice search optimization

Short paragraphs are well-suited for answer extraction

Breadcrumb navigation with schema aids answer context

10 lists provide scannable answers for People Also Ask

Video content detected — supports multimedia answer results

91 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction

Source diagnostic wording is preserved.

1. Local SEO: local business signals present but no explicit city/region in the title, H1 or opening paragraph. Add "City, State" to your title/H1 and intro to reinforce local relevance.

Evidence and checks

NAP information detected: phone: 4799999999, email: [email protected]

Phone number(s) visible: 4799999999, 2399999999

Email address found: [email protected]

LocalBusiness schema: LocalBusiness, LocalBusiness

Google Maps embed present — provides visual location confirmation

Address microdata markup detected

Geo meta tags present for location targeting

Business hours/opening hours detected

Review/Rating schema detected

Multiple location signals detected — consider individual location pages

Service area defined in schema

Source diagnostic wording is preserved.

1. Remove autoplay from media elements or provide controls — autoplay can be disorienting and violates WCAG 1.4.2

2. WCAG 2.2 (1.4.13 Content on Hover/Focus): 65 interactive elements rely on native title tooltips, which are not dismissable, hoverable or persistent. Replace with accessible tooltip components.

Evidence and checks

prefers-reduced-motion support detected — respects user motion preferences

High contrast / forced-colors mode supported

Links are visually distinguishable (underline or decoration detected)

Form error/validation feedback detected

Relative units (rem/em/clamp) detected — supports text resizing

Good semantic element usage (108 semantic elements)

Focus styles detected for keyboard navigation visibility

Page language declared — aids assistive technology

All ARIA roles are valid

Moderate cognitive load — acceptable for interactive modern web apps with rich UI patterns

Form error identification mechanisms present (WCAG 3.3.1)

Focus not obscured by sticky/fixed elements (WCAG 2.4.11)

Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8

2 ARIA live regions for dynamic content announcements

Reduced motion enforced: animations disabled when prefers-reduced-motion is set

Source diagnostic wording is preserved.

1. [Impact 3/3 · v6:cwv-lcp] Prioritize above-fold resources and remove render-blocking dependencies.

2. [Impact 3/3 · v6:cwv-tbt] Reduce long tasks and expensive event handlers; verify with a trace.

3. [Impact 3/3 · v6:cwv-fcp] Prioritize above-fold resources and remove render-blocking dependencies.

Evidence and checks

v6:cwv-lcp · LCP: 29/100 — 5701.032704514077 ms; lab

v6:cwv-inp · INP: unavailable — Unavailable; not estimated

v6:cwv-cls · CLS: 100/100 — 0.005857055730842146 ratio; lab

v6:cwv-fcp · FCP: 87/100 — 2101.010901504692 ms; lab

v6:cwv-ttfb · TTFB: 100/100 — 15 ms; lab

v6:cwv-tbt · TBT: 47/100 — 632 ms; lab

Source diagnostic wording is preserved.

Evidence and checks

v6:robots-valid · Robots syntax and response: 100/100 — HTTP 200; 404 means no robots file

v6:robots-access · Googlebot path access: 100/100 — /

v6:meta-indexability · Meta robots indexability: 100/100 — index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1

v6:header-indexability · X-Robots-Tag indexability: 100/100 — No restrictive response header

v6:crawl-budget · Parameter crawl signals: 100/100 — 0 parameterized internal destinations

Source diagnostic wording is preserved.

Evidence and checks

v6:sitemap-detection · Sitemap response: 100/100 — HTTP 200

v6:sitemap-xml · Sitemap XML validity: 100/100 — sitemapindex

v6:sitemap-count · Sitemap entry count: 100/100 — 4 child-sitemap references (not page count) in fetched document

v6:sitemap-lastmod · Lastmod integrity / freshness: unavailable — 0 dated entries; 0 invalid/future; oldest age days: unknown

v6:sitemap-robots-reference · Sitemap discovery in robots: 100/100 — Referenced

Source diagnostic wording is preserved.

Evidence and checks

v6:internal-links · Internal destinations: 100/100 — 75 unique destinations

v6:link-depth · Linked URL path depth: 100/100 — URL path depth ≤4 proxy; click depth beyond sampled edges is unknown

v6:external-hygiene · External transport quality: 100/100 — 19 unique external destinations; 0 HTTP links. Authority/relevance not inferred.

v6:broken-links · Broken link sample: 100/100 — [{"url":"https://digitalmarketingco.org/","status":200,"depth":1,"outgoing":196},{"url":"https://digitalmarketingco.org/launch-super-limited-time-offer","status":200,"depth":1,"outgoing":87},{"url":"https://digitalmarketingco.org/services","status":200,"depth":1,"outgoing":174},{"url":"https://digitalmarketingco.org/service-areas","status":200,"depth":1,"outgoing":153},{"url":"https://www.facebook.com/digitalmarketingcompanyagency","status":200,"depth":1,"outgoing":null},{"url":"https://youtube.com/@digitalmarketingcompanyagency","status":200,"depth":1,"outgoing":null}]

v6:anchor-diversity · Descriptive anchor diversity: 100/100 — 169 distinct anchors; 0 empty/generic of 192