This website audit report analyzes https://highmarkconstruction.com/ across 12 critical dimensions with actionable recommendations.
https://highmarkconstruction.com/
70Goodout of 100
Website Audit Report
High Mark Construction | Exterior Home Remodeling Company
May 13, 2026 · 12:59 (America/New_York) 221ms response HTTPS Secure
Executive Summary
https://highmarkconstruction.com/ scores 70/100 (C-). Strong areas include SEO. Priority improvements needed in Performance, Security, GEO. The site has 705 words, 19 images, and 1 schema blocks. Focus on the top recommendations below to improve your score.
221ms
Response Time
705
Word Count
19
Images
49
Links
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[Performance] 19 render-blocking scripts slow down initial paint
2[Performance] No lazy loading on images
3[Performance] No WebP or AVIF image formats found
4[Performance] Only 0/19 images have width/height attributes
5[Performance] No font-display property found
6[Performance] 9 inline <style> blocks
7[Performance] 33 inline scripts
8[Security] Missing Strict-Transport-Security header
9[Security] Missing Content-Security-Policy header
10[Security] Missing X-Content-Type-Options header
Top Recommendations
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
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
6Add font-display: swap to web font declarations to show fallback text while fonts load
7Extract inline styles into external CSS files for better caching and maintainability
8Move inline scripts to external files with defer attributes
9Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
10Implement a Content Security Policy to prevent XSS and injection attacks
11Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
12Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
Detailed Category Analysis
Key Findings
1Title tag is 57 characters — within optimal 30–60 range
2Meta description is 140 characters — within optimal 120–160 range
3Single H1 tag present: "Experience the way exterior home remodeling and repairs shou…"
4Clean heading hierarchy with no skipped levels
5Canonical URL is set and matches the page URL
6Complete Open Graph tags (title, description, image, url, type)
7Complete Twitter Card tags present
8HTML lang attribute set to "en-US"
9Favicon present
1039 internal links help establish site architecture
114 external links provide reference signals
12Content length of 705 words is adequate
Key Findings
1Excellent server response time: 221ms
2HTML size is 183KB — acceptable
3Responsive images with srcset detected
4Preloaded resources: style
51 async and 10 deferred scripts
6Cache-Control header with max-age is set
Issues Found
119 render-blocking scripts slow down initial paint
2No lazy loading on images
3No WebP or AVIF image formats found
4Only 0/19 images have width/height attributes
5No font-display property found
69 inline <style> blocks
733 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
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
6Add font-display: swap to web font declarations to show fallback text while fonts load
7Extract inline styles into external CSS files for better caching and maintainability
8Move inline scripts to external files with defer attributes
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1.0
2HTML5 doctype declared
3Character encoding declared
4Apple touch icons present
5Responsive images via srcset serve appropriate sizes per device
Issues Found
1No theme-color meta tag
2No web app manifest found
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
3Consider implementing a service worker for offline support and faster repeat visits
Key Findings
1HTTPS enabled — encrypted connection
Issues Found
1Missing Strict-Transport-Security header
2Missing Content-Security-Policy header
3Missing X-Content-Type-Options header
4Missing X-Frame-Options header
5Missing Referrer-Policy header
6Missing Permissions-Policy header
7Server header exposes technology: cloudflare
Recommendations to Reach 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Implement a Content Security Policy to prevent XSS and injection attacks
3Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
4Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
5Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
6Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
7Add Cross-Origin-Opener-Policy: same-origin-allow-popups
8Add Cross-Origin-Resource-Policy: cross-origin
9Remove or obfuscate the Server header to avoid exposing your technology stack
Key Findings
1Language declared: en-US
2All 2 forms have proper labels
3All 2 buttons have accessible labels
4Focus styles detected for keyboard navigation
Issues Found
1No skip navigation link
2Missing landmarks: main, footer
31 of 19 images (5%) missing alt text
4No ARIA attributes detected
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add semantic landmark elements: <main>, <footer>
3Add descriptive alt text to all images — use empty alt="" only for decorative images
4Add ARIA attributes to interactive elements for better screen reader support
Key Findings
11 schema block(s): Place, Organization, WebSite, ImageObject, WebPage, Service, LocalBusiness, Organization
2Some semantic elements: header, nav, section
3Complete social metadata (OG + Twitter Card)
46 strong entity mentions (bold/emphasized text)
5Social presence signals: facebook, instagram, linkedin
610 call-to-action elements detected
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns found
3No sitemap reference found
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
3Increase use of semantic HTML5 elements (article, section, aside, figure) for better AI understanding
4Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
5Add an FAQ section with FAQPage schema to increase chances of AI engine citations
6Create and reference an XML sitemap for AI crawler discoverability
Key Findings
1Moderate content depth (705 words)
26 emphasized entities
3Structured content: 6 lists, 0 tables — easily parsed by AI
Issues Found
1No structured Q&A content
2Low semantic markup ratio — 169 divs vs 3 semantic elements
3Weak E-E-A-T schema signals
4Paragraphs are too long for optimal AI consumption
Recommendations to Reach 100%
1Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
2Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
3Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
4Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
5Add Speakable schema markup to help voice assistants identify the most important content
Key Findings
16 lists provide scannable, AI-friendly content
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
4paragraphs may be too long for featured snippets
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
Key Findings
16 lists provide scannable answers for People Also Ask
2Video content detected — supports multimedia answer results
Issues Found
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4Paragraphs too long for answer engine extraction
5No breadcrumb navigation
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
5Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
6Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
Key Findings
1NAP information detected: phone: 16019251441
2Phone number(s) visible: 16019251441, 410-995-4980
3LocalBusiness schema: LocalBusiness
Issues Found
1No Google Maps embed
2No address microdata
3No geo meta tags
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
2Add an embedded Google Map to your contact or about page for local search signals
3Add PostalAddress schema or itemprop="address" microdata to your address elements
4Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
Key Findings
11 JSON-LD block(s) with types: Place, Organization, WebSite, ImageObject, WebPage, Service, LocalBusiness, Organization
2Service schema describes your offerings
3Rich schema diversity: 7 distinct types with properties
Issues Found
1Only basic schema implementation
2Place missing common identifiers (name/headline/url)
3Service has very few properties (2)
4Service missing common identifiers (name/headline/url)
Recommendations to Reach 100%
1Expand structured data with more specific schema types relevant to your content
2Add BreadcrumbList schema for site hierarchy
3Add FAQPage schema to FAQ content
4Consider adding HowTo schema for instructional content
5Add more properties to schema types — aim for at least 5 meaningful properties per type
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Form error/validation feedback detected
3Relative units (rem/em/clamp) detected — supports text resizing
4Focus styles detected for keyboard navigation visibility
5Page language declared — aids assistive technology
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
32 autoplay media element(s) detected
4Low semantic-to-div ratio — 169 divs vs 3 semantic elements
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
3Remove autoplay from media elements or provide controls — autoplay can be disorienting and violates WCAG 1.4.2
4Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
Limited-Time Offer
Audit-informed Optimizations for 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.
Use the audit findings to prioritize improvements during development. Scores depend on measured conditions; rankings and fixed scores are not guaranteed.