This website audit report analyzes https://www.darudc.com/ across 12 critical dimensions with actionable recommendations.
https://www.darudc.com/
39Poorout of 100
Website Audit Report
Daru
August 4, 2026 at 3:32 AM GMT+5:30 413ms response HTTPS Secure
Executive Summary
https://www.darudc.com/ scores 39/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 42 words, 5 images, and 1 schema blocks. Data confidence: 80%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
413ms
Response Time
42
Word Count
5
Images
18
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is very short (4 chars)
2[SEO] Meta description is short (56 chars)
3[SEO] No H1 heading found
4[SEO] Thin content (42 words)
5[SEO] 8 external links missing recommended rel attributes
6[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
7[SEO] 8 dofollow external links — slightly above optimal range
8[SEO] Weak E-E-A-T signals (1 indicators)
9[SEO] Missing og:locale tag — social platforms may guess language/region
10[SEO] No social sharing buttons/widgets detected
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] Expand your meta description to 140–160 characters for better SERP visibility
3[Impact: High | Effort: Low] Add exactly one H1 tag with your primary keyword to establish page topic
4[Impact: Medium | Effort: Medium] Expand your content to at least 300+ words for better search rankings
5[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
6[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
7[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
8[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
9[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
10[Impact: High | Effort: Medium] Link to a Contact page — essential trust signal for E-E-A-T and local SEO
11[Impact: Medium | Effort: Low] Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
12[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
Detailed Category Analysis
Key Findings
1Canonical URL is set and matches the page URL
2Complete Open Graph tags (title, description, image, url, type)
3Complete Twitter Card tags present
4HTML lang attribute set to "en-US"
5Favicon present
610 internal links help establish site architecture
78 external links provide reference signals
818 total links — within recommended range
9URL length (23 chars) is within optimal range
10No redirect chain — direct URL resolution
11Healthy internal link ratio: 56% of links are internal
12Good anchor text diversity: 60% unique anchor texts
13Primary keyword present in URL — good URL optimization
14OG image dimensions ≥1200×630px — optimal for all platforms
Issues Found
1Title tag is very short (4 chars)
2Meta description is short (56 chars)
3No H1 heading found
4Thin content (42 words)
58 external links missing recommended rel attributes
6Title and description are identical to Open Graph tags — missed optimization opportunity
78 dofollow external links — slightly above optimal range
8Weak E-E-A-T signals (1 indicators)
9Missing og:locale tag — social platforms may guess language/region
10No social sharing buttons/widgets detected
Recommendations to Reach 100%
1Expand your title to 50–60 characters for better click-through rates and SERP visibility
2Expand your meta description to 140–160 characters for better SERP visibility
3Add exactly one H1 tag with your primary keyword to establish page topic
4Expand your content to at least 300+ words for better search rankings
5Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
6Customize og:title and og:description separately from page title/meta description for better social sharing CTR
7Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
8Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
9Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
10Link to a Contact page — essential trust signal for E-E-A-T and local SEO
11Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
12Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
13Upgrade Twitter card to "summary_large_image" for larger, more engaging previews
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
16SEO: 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: 413ms
2HTML size is 115KB — acceptable
3No render-blocking scripts detected
41/5 images use lazy loading
5Responsive images with srcset detected
6Preconnect hints for: https://images.squarespace-cdn.com, https://file.squarespace-cdn.com
7font-display property detected — reduces invisible text during font loading
80 async and 24 deferred scripts
9Lean CSS payload (~140KB)
10Gzip compression enabled
11Estimated LCP: ~1133ms — within Google's "good" threshold (<2.5s)
12Estimated INP: ~198ms — within Google's "good" threshold (<200ms)
Issues Found
1No WebP or AVIF image formats found
2Only 1/5 images have width/height attributes
3No effective Cache-Control header
419 inline <style> blocks
511 inline scripts
6Heavy JavaScript payload (~1235KB across 24 files)
7HTTP/1.1 detected — no multiplexing
8No CDN detected
924 third-party scripts from 3 domains — significant performance impact
1022 font files loaded — excessive font weight
114 render-blocking CSS files — delays first paint
12Potential long-task scripts: Inline script (~33KB)
13Moderate estimated CLS: 0.17 — above 0.1 "good" threshold
14Web fonts loaded without preload — causes FOIT/FOUT flash
15No analytics tracking detected — flying blind on user behavior
Recommendations to Reach 100%
1Convert images to WebP or AVIF format for 30–50% file size reduction
2Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
3Preload critical resources (fonts, hero images) with <link rel="preload">
4Set Cache-Control headers with appropriate max-age to leverage browser caching
5Extract inline styles into external CSS files for better caching and maintainability
6Move inline scripts to external files with defer attributes
7Reduce JavaScript with code splitting, tree shaking, and lazy loading. Target <500KB total JS for optimal performance
8Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
9Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
10Audit third-party scripts — defer non-critical ones and remove unused trackers/widgets to reduce main thread blocking
11Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
12Preload your primary font with <link rel="preload" as="font" crossorigin> for faster first contentful paint
13Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
14Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
15Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
16Add <link rel="preload" as="font" crossorigin> for your primary font files to eliminate flash of invisible/unstyled text
17Install Google Analytics 4 (GA4) with Google Tag Manager immediately — analytics is essential for measuring SEO and marketing ROI
18Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
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
51 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
2HSTS header present — enforces HTTPS
3X-Content-Type-Options: nosniff is set
4No stack traces or sensitive error details exposed in responses
5No raw email addresses exposed in page source
6No obvious secret/API-key patterns exposed in page source
724 script resource(s) catalogued for software-composition review
8No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Content-Security-Policy header
2Missing X-Frame-Options header
3Missing Referrer-Policy header
4Missing Permissions-Policy header
5Server header exposes technology: Squarespace
68 external links missing rel="noopener noreferrer" — security risk
7HSTS header present but missing preload directive
8Cookie security issues: missing HttpOnly flag; missing SameSite attribute
9No privacy policy detected
10No cookie consent banner detected
11No Subresource Integrity (SRI) on external scripts
12Server technology disclosed via response headers/markup: Server: Squarespace
13security.txt file is missing — no standardized channel for reporting vulnerabilities
14robots.txt discloses sensitive-looking path(s): /config — Disallow entries can act as a map for attackers
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 all external links with target="_blank" to prevent tabnabbing attacks
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
11Add a privacy policy link — required by GDPR, CCPA, and builds user trust
12Implement a cookie consent banner for GDPR/ePrivacy compliance
13Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
14Remove or obfuscate technology-revealing headers (Server, X-Powered-By, X-AspNet-Version) and the generator meta tag to reduce your attack surface
15Add 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]
16Avoid listing admin/private paths in robots.txt; protect them with authentication instead of relying on obscurity [Impact: Low | Effort: Low]
17A03 Software Supply Chain: only 0% of 24 cross-origin scripts use Subresource Integrity. Pin every third-party script with integrity+crossorigin and adopt SLSA provenance / a published SBOM for build integrity.
18A07 Authentication Failures: no phishing-resistant factor detected (WebAuthn/passkeys/TOTP MFA). Offer passkeys or TOTP and enforce ASVS L2 credential and session controls.
19A07 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.
20A09 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
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 5 images have alt attributes
5All 2 buttons have accessible labels
64 ARIA-attributed elements found
Issues Found
1No focus styles detected
22 minor HTML validity issue(s)
34 images missing explicit dimensions — causes layout shifts for screen reader users
42 duplicate ID(s) — breaks ARIA references and label associations
Recommendations to Reach 100%
1Add :focus-visible styles to all interactive elements for keyboard navigation visibility
2Review and fix HTML structure issues for better accessibility and cross-browser compatibility
3Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
4Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
5Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
6Accessibility (WCAG 2.2 3.2.6): no consistent help mechanism (contact/help/support link) detected. Provide help access in a consistent location across pages.
Key Findings
11 schema block(s): WebSite
2Strong semantic markup: header, nav, main, article, section, footer
3Complete social metadata (OG + Twitter Card)
4Social presence signals: instagram
5No AI crawlers blocked via meta tags — content accessible to AI search engines
6robots.txt file found
7robots.txt references 1 sitemap(s) — aids AI crawler discoverability
8Moderate RAG-friendliness (47/100)
9Content provenance signals detected (citations with sources, attributed claims)
10Good HTML-to-text ratio (46%) — AI crawlers can extract content efficiently
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns found
3No sitemap reference found
4robots.txt blocks CSS/JS/image assets — search engines and AI cannot render your page
5No llms.txt file found — AI models cannot find structured guidance for your site
6No 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
5Create and reference an XML sitemap for AI crawler discoverability
6Use <strong> and <em> tags to highlight key entities, concepts, and terms
7Remove Disallow rules for /css/, /js/, /images/ in robots.txt — Google and AI crawlers need these to render and understand your pages
8Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
9Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
10Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
11Add id attributes to headings and section elements for better RAG (Retrieval Augmented Generation) chunk targeting by AI systems
12Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
13AI Readiness (multimodal): only 0% of images have descriptive alt text (≥15 chars). Rich, standalone alt text lets multimodal models understand and cite your imagery.
Key Findings
1Good semantic-to-div ratio: 8 semantic elements
2Good paragraph length for readability and AI parsing
34 external citation(s)
4Author attribution present but missing expertise signals
Issues Found
1Very thin content (42 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Weak E-E-A-T schema signals
5No clear call-to-action elements detected
6No CTA above the fold
7Insufficient trust signals for conversion optimization
8No social proof elements
9No clear value proposition in headings
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
4Add structured content (lists, comparison tables) that AI models can easily extract and reference
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 author bio, credentials, and links to establish expertise signals for AI E-E-A-T evaluation
10Add prominent CTAs with action-oriented text ("Get Started", "Book a Call", "Try Free") — every page should guide users toward conversion
11Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
12Add trust signals: testimonials, trust badges, guarantees, client logos, and privacy indicators to boost conversion confidence
13Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
14Your H1 or hero section should clearly state your unique value proposition — what you offer, for whom, and why it matters
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Few or no lists
4Content too thin for AI citation value
5Insufficient structured data for generative engine context
6thin content — may not provide enough depth for AI engines
7No 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
3Use numbered and bulleted lists for step-by-step content — generative engines prefer structured, scannable formats
4Include how-to or step-by-step instructional content for generative AI answer inclusion
5Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
6Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
7Include unique statistics, expert quotes, and original insights that generative AI would want to cite
8Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
9Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
10Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
11Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
12GEO: 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
1Short paragraphs are well-suited for answer extraction
Issues Found
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
5Few concise answer paragraphs for snippet extraction
6No 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
6Add more bullet/numbered lists — search engines frequently pull list content into People Also Ask results
7Consider adding video content with VideoObject schema for multimedia search results
8Write concise 40–60 word paragraphs that directly answer common questions — these are extracted as featured snippets and voice answers
9Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
10AEO: 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: 0067712
2Phone number(s) visible: 0067712, 17822683760
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
7Local 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.
8Local SEO (NAP): a phone number is shown but not declared in structured data. Add telephone (and address) to LocalBusiness schema so NAP is machine-verifiable.
Key Findings
11 JSON-LD block(s) with types: WebSite
2All structured data uses JSON-LD format — Google's recommended format
3Some top-tier schemas: WebSite
4No schema validity issues detected
Issues Found
1Only basic schema implementation
2No sameAs properties in schema — missing entity disambiguation
3Schema property completeness averaging 50%
4No rich results eligibility detected
Recommendations to Reach 100%
1Expand structured data with more specific schema types relevant to your content
2Add more top-tier schema types — consider: LocalBusiness, Organization, Product
3Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
4Add missing high-impact schemas: Organization, Product, Person
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
10Fill in missing recommended properties for each schema type
11Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
12Add nested schemas (e.g., author within Article, offers within Product) to define entity relationships
13Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
14Schema.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
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Good semantic element usage (8 semantic elements)
4Page language declared — aids assistive technology
5All ARIA roles are valid
6Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3No 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 :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.