Enter password to view Website Audit
Analysis
Website
vialytics
Analysis
Website
vialytics
Analysis
Website
vialytics
Summary
About
Company
vialytics
Overall Score of Website
22
Analysed on 2026-03-24
Description
AI-powered road management platform for municipalities. Founded 2017/2018 by Patrick Glaser, Achim Hoth, and Danilo Jovicic-Albrecht in Stuttgart, Germany. Product: smartphone-mounted in municipal vehicles photographs road every 10 feet (every ~3 metres); AI detects and classifies pavement defects (cracking, patches, potholes, surface wear) and inventory assets (signs, manholes, drains, markings); results displayed in a map-based web dashboard within hours of data collection. Three tiers: Essentials (documentation + inspection), Pro (+ AI analysis + work orders), Enterprise (+ integrations + advanced planning). 500-600+ local authorities across 7 countries (US, Germany, France, Czech Republic, Switzerland, Austria, Netherlands). Confirmed US customers: Edison NJ, Bethel CT, Sugar Hill GA, Huntington County IN, Brighton NY, City of Hartford CT (June 2025). Referenced competitive displacement of Better Roads. 250 million road images processed, 15-20 million added per month. Tech stack: HubSpot CMS (hubfs image URLs, no-cache.hubspot.com CTAs, hsLang URL parameters). Multilingual: .com (EN), .de (DE), .fr (FR). Funding: $19.22M total ($10M Series A Jan 2023 led by Scania Growth Capital; €8M Series A-II Dec 2024 led by Acton Capital; investors: Scania Growth Capital, EnBW New Ventures, Statkraft Ventures, Acton Capital, East Hill Equity, Cyber Valley). ~60-120 employees.
Market
Smart Infrastructure / Pavement Management Software / GovTech / Urban Mobility / AI Road Inspection
Audience
Public works directors and city engineers at US municipalities (population 5,000-500,000) managing road maintenance budgets; infrastructure budget officers seeking to replace manual inspection with continuous AI monitoring; county road superintendents evaluating pavement management software
HQ
Stuttgart, Germany (Americas HQ: Short Hills, NJ, USA)
Visualisation
Spider Chart
Performance
5
Performance
8
Performance
12
SEO
16
SEO
20
SEO
24
Geo
28
Accessibility
32
Accessibility
36
Content
40
Performance
Hero Background Video — Autoplay MP4 — Major LCP and Bandwidth Penalty on Mobile
Score
5
Severity
Critical
Finding
The homepage HTML confirms a full-bleed autoplay hero video: 'https://www.vialytics.com/hubfs/Slowed%20Down%20Hero%20Video.mp4'. Unoptimised autoplay video is the single most common cause of poor Core Web Vitals on marketing homepages. On a typical 4G mobile connection, a multi-MB MP4 blocks the Largest Contentful Paint element from rendering, pushing LCP well beyond Google's 2.5s good threshold. HubSpot CMS cannot automatically optimise hosted MP4 files, and no poster image or lazy-load attribute is visible in the markup. Additionally, public works directors and municipal engineers — the primary buyers — often access websites from government networks or field devices with throttled connections.
Recommendation
Replace or supplement the hero video with: (1) a static WebP poster image as the default visible element, preloaded in the <head> via <link rel='preload' as='image'>; (2) the video loading only after user interaction or after a 3-second delay via IntersectionObserver; (3) a compressed WebM version alongside the MP4 for browsers that support it. Target LCP under 2.5s on simulated 4G mobile in Lighthouse. The visual impact of the video can be preserved while fully decoupling it from the LCP metric.
Performance
Hero Background Video — Autoplay MP4 — Major LCP and Bandwidth Penalty on Mobile
Score
5
Severity
Critical
Finding
The homepage HTML confirms a full-bleed autoplay hero video: 'https://www.vialytics.com/hubfs/Slowed%20Down%20Hero%20Video.mp4'. Unoptimised autoplay video is the single most common cause of poor Core Web Vitals on marketing homepages. On a typical 4G mobile connection, a multi-MB MP4 blocks the Largest Contentful Paint element from rendering, pushing LCP well beyond Google's 2.5s good threshold. HubSpot CMS cannot automatically optimise hosted MP4 files, and no poster image or lazy-load attribute is visible in the markup. Additionally, public works directors and municipal engineers — the primary buyers — often access websites from government networks or field devices with throttled connections.
Recommendation
Replace or supplement the hero video with: (1) a static WebP poster image as the default visible element, preloaded in the <head> via <link rel='preload' as='image'>; (2) the video loading only after user interaction or after a 3-second delay via IntersectionObserver; (3) a compressed WebM version alongside the MP4 for browsers that support it. Target LCP under 2.5s on simulated 4G mobile in Lighthouse. The visual impact of the video can be preserved while fully decoupling it from the LCP metric.
Performance
Hero Background Video — Autoplay MP4 — Major LCP and Bandwidth Penalty on Mobile
Score
5
Severity
Critical
Finding
The homepage HTML confirms a full-bleed autoplay hero video: 'https://www.vialytics.com/hubfs/Slowed%20Down%20Hero%20Video.mp4'. Unoptimised autoplay video is the single most common cause of poor Core Web Vitals on marketing homepages. On a typical 4G mobile connection, a multi-MB MP4 blocks the Largest Contentful Paint element from rendering, pushing LCP well beyond Google's 2.5s good threshold. HubSpot CMS cannot automatically optimise hosted MP4 files, and no poster image or lazy-load attribute is visible in the markup. Additionally, public works directors and municipal engineers — the primary buyers — often access websites from government networks or field devices with throttled connections.
Recommendation
Replace or supplement the hero video with: (1) a static WebP poster image as the default visible element, preloaded in the <head> via <link rel='preload' as='image'>; (2) the video loading only after user interaction or after a 3-second delay via IntersectionObserver; (3) a compressed WebM version alongside the MP4 for browsers that support it. Target LCP under 2.5s on simulated 4G mobile in Lighthouse. The visual impact of the video can be preserved while fully decoupling it from the LCP metric.
Performance
HubSpot CTA Images Served from no-cache.hubspot.com — Third-Party Origin Latency on Every Page
Score
8
Severity
High
Finding
The page source confirms multiple CTAs loaded from 'no-cache.hubspot.com': contact button PNG, phone number PNG, 'Get started' PNG. These are bitmap PNG images (not SVG or HTML elements) served from a third-party subdomain with the 'no-cache' prefix explicitly in the hostname, meaning browser cache headers are stripped. Every page load incurs an extra DNS lookup + TCP handshake + TLS handshake to no-cache.hubspot.com for buttons that should be native HTML. This pattern typically costs 200–400ms of extra connection time on repeat visits and prevents any caching benefit.
Recommendation
Replace all HubSpot CTA image-based buttons with native HTML <a> elements styled with CSS. The phone number '+1 (973) 315 8469' and 'Contact' CTA do not need to be PNG images — they should be text links or HTML buttons. This eliminates the no-cache.hubspot.com dependency entirely for above-the-fold CTAs, reducing both connection overhead and paint delays. Use HubSpot's smart CTA functionality only where personalisation genuinely requires it.
Performance
HubSpot CTA Images Served from no-cache.hubspot.com — Third-Party Origin Latency on Every Page
Score
8
Severity
High
Finding
The page source confirms multiple CTAs loaded from 'no-cache.hubspot.com': contact button PNG, phone number PNG, 'Get started' PNG. These are bitmap PNG images (not SVG or HTML elements) served from a third-party subdomain with the 'no-cache' prefix explicitly in the hostname, meaning browser cache headers are stripped. Every page load incurs an extra DNS lookup + TCP handshake + TLS handshake to no-cache.hubspot.com for buttons that should be native HTML. This pattern typically costs 200–400ms of extra connection time on repeat visits and prevents any caching benefit.
Recommendation
Replace all HubSpot CTA image-based buttons with native HTML <a> elements styled with CSS. The phone number '+1 (973) 315 8469' and 'Contact' CTA do not need to be PNG images — they should be text links or HTML buttons. This eliminates the no-cache.hubspot.com dependency entirely for above-the-fold CTAs, reducing both connection overhead and paint delays. Use HubSpot's smart CTA functionality only where personalisation genuinely requires it.
Performance
HubSpot CTA Images Served from no-cache.hubspot.com — Third-Party Origin Latency on Every Page
Score
8
Severity
High
Finding
The page source confirms multiple CTAs loaded from 'no-cache.hubspot.com': contact button PNG, phone number PNG, 'Get started' PNG. These are bitmap PNG images (not SVG or HTML elements) served from a third-party subdomain with the 'no-cache' prefix explicitly in the hostname, meaning browser cache headers are stripped. Every page load incurs an extra DNS lookup + TCP handshake + TLS handshake to no-cache.hubspot.com for buttons that should be native HTML. This pattern typically costs 200–400ms of extra connection time on repeat visits and prevents any caching benefit.
Recommendation
Replace all HubSpot CTA image-based buttons with native HTML <a> elements styled with CSS. The phone number '+1 (973) 315 8469' and 'Contact' CTA do not need to be PNG images — they should be text links or HTML buttons. This eliminates the no-cache.hubspot.com dependency entirely for above-the-fold CTAs, reducing both connection overhead and paint delays. Use HubSpot's smart CTA functionality only where personalisation genuinely requires it.
Performance
Navigation Links Using javascript:; — Dropdown Menus Block Crawlability and Add JS Parse Overhead
Score
12
Severity
High
Finding
The page source shows all primary nav dropdown triggers as 'javascript:;' href values — e.g. '<a href="javascript:;">Solutions</a>'. This pattern requires JavaScript to execute before navigation works, creating an interaction delay (poor INP) and making the dropdown links uncrawlable by Googlebot in its initial pass. HubSpot CMS megamenu dropdowns commonly use this pattern, but it forces the browser to parse and execute JavaScript to enable primary navigation — a render-blocking interaction on slow devices.
Recommendation
Replace javascript:; nav links with either: (1) CSS-only dropdown menus using :hover/:focus-within (no JS required), or (2) proper anchor href targets pointing to the section or child page, with JavaScript enhancing rather than replacing the navigation. At minimum, add aria-haspopup and aria-expanded attributes to support keyboard and screen reader navigation. This improves both INP scores and Googlebot crawl depth.
Performance
Navigation Links Using javascript:; — Dropdown Menus Block Crawlability and Add JS Parse Overhead
Score
12
Severity
High
Finding
The page source shows all primary nav dropdown triggers as 'javascript:;' href values — e.g. '<a href="javascript:;">Solutions</a>'. This pattern requires JavaScript to execute before navigation works, creating an interaction delay (poor INP) and making the dropdown links uncrawlable by Googlebot in its initial pass. HubSpot CMS megamenu dropdowns commonly use this pattern, but it forces the browser to parse and execute JavaScript to enable primary navigation — a render-blocking interaction on slow devices.
Recommendation
Replace javascript:; nav links with either: (1) CSS-only dropdown menus using :hover/:focus-within (no JS required), or (2) proper anchor href targets pointing to the section or child page, with JavaScript enhancing rather than replacing the navigation. At minimum, add aria-haspopup and aria-expanded attributes to support keyboard and screen reader navigation. This improves both INP scores and Googlebot crawl depth.
Performance
Navigation Links Using javascript:; — Dropdown Menus Block Crawlability and Add JS Parse Overhead
Score
12
Severity
High
Finding
The page source shows all primary nav dropdown triggers as 'javascript:;' href values — e.g. '<a href="javascript:;">Solutions</a>'. This pattern requires JavaScript to execute before navigation works, creating an interaction delay (poor INP) and making the dropdown links uncrawlable by Googlebot in its initial pass. HubSpot CMS megamenu dropdowns commonly use this pattern, but it forces the browser to parse and execute JavaScript to enable primary navigation — a render-blocking interaction on slow devices.
Recommendation
Replace javascript:; nav links with either: (1) CSS-only dropdown menus using :hover/:focus-within (no JS required), or (2) proper anchor href targets pointing to the section or child page, with JavaScript enhancing rather than replacing the navigation. At minimum, add aria-haspopup and aria-expanded attributes to support keyboard and screen reader navigation. This improves both INP scores and Googlebot crawl depth.
SEO
Title Tag 'Intelligent Road Management for the US | vialytics Americas' — Geo-Targeted but Missing Primary Keyword Variants
Score
16
Severity
High
Finding
The confirmed page title is 'Intelligent Road Management for the US | vialytics Americas'. While the geo-qualifier 'for the US' is present, the title omits the high-volume search terms that public works directors actually use when researching solutions: 'pavement management software,' 'road condition assessment,' 'pothole detection AI,' 'infrastructure management system.' The title uses vialytics' own product language ('Intelligent Road Management') rather than the buyer's search language. Public works professionals searching Google type queries like 'pavement management software for municipalities' — not 'intelligent road management.'
Recommendation
Rewrite the title tag to lead with buyer-intent keywords: 'Pavement Management Software for Municipalities | AI Road Assessment | vialytics'. Run keyword research in Google Search Console and Ahrefs/SEMrush for the terms actually used by public works directors, city engineers, and infrastructure budget holders in the US. Target: primary keyword in positions 1-5 of the title, brand name at end, character count 50-60.
SEO
Title Tag 'Intelligent Road Management for the US | vialytics Americas' — Geo-Targeted but Missing Primary Keyword Variants
Score
16
Severity
High
Finding
The confirmed page title is 'Intelligent Road Management for the US | vialytics Americas'. While the geo-qualifier 'for the US' is present, the title omits the high-volume search terms that public works directors actually use when researching solutions: 'pavement management software,' 'road condition assessment,' 'pothole detection AI,' 'infrastructure management system.' The title uses vialytics' own product language ('Intelligent Road Management') rather than the buyer's search language. Public works professionals searching Google type queries like 'pavement management software for municipalities' — not 'intelligent road management.'
Recommendation
Rewrite the title tag to lead with buyer-intent keywords: 'Pavement Management Software for Municipalities | AI Road Assessment | vialytics'. Run keyword research in Google Search Console and Ahrefs/SEMrush for the terms actually used by public works directors, city engineers, and infrastructure budget holders in the US. Target: primary keyword in positions 1-5 of the title, brand name at end, character count 50-60.
SEO
Title Tag 'Intelligent Road Management for the US | vialytics Americas' — Geo-Targeted but Missing Primary Keyword Variants
Score
16
Severity
High
Finding
The confirmed page title is 'Intelligent Road Management for the US | vialytics Americas'. While the geo-qualifier 'for the US' is present, the title omits the high-volume search terms that public works directors actually use when researching solutions: 'pavement management software,' 'road condition assessment,' 'pothole detection AI,' 'infrastructure management system.' The title uses vialytics' own product language ('Intelligent Road Management') rather than the buyer's search language. Public works professionals searching Google type queries like 'pavement management software for municipalities' — not 'intelligent road management.'
Recommendation
Rewrite the title tag to lead with buyer-intent keywords: 'Pavement Management Software for Municipalities | AI Road Assessment | vialytics'. Run keyword research in Google Search Console and Ahrefs/SEMrush for the terms actually used by public works directors, city engineers, and infrastructure budget holders in the US. Target: primary keyword in positions 1-5 of the title, brand name at end, character count 50-60.
SEO
Prices Page Has No Actual Prices — 'Get a Quote' for All Three Tiers — Hides from Commercial-Intent Search
Score
20
Severity
High
Finding
The confirmed pricing page (/packages-and-pricing) shows three tiers — Essentials, Pro, Enterprise — all with 'Get a Quote' instead of any price anchor. While custom pricing for government contracts is standard, the complete absence of any pricing signal (e.g. 'starting from $X/year for communities under 10,000 residents') means the page cannot rank for commercial-intent searches like 'pavement management software pricing' or 'road inspection AI cost.' These are high-converting queries from buyers with budget. Competitor Better Roads (explicitly referenced in the site's own banner) likely outranks vialytics on pricing searches.
Recommendation
Add at minimum a pricing anchor or range ('Essentials plans start from $X/year for communities under 10,000 residents — contact us for exact pricing based on your road network size'). This preserves the consultative sales process while enabling the page to capture commercial-intent search traffic. Create a dedicated FAQ section addressing 'How much does pavement management software cost?' and 'Is vialytics more affordable than manual inspection?' — both high-value informational queries.
SEO
Prices Page Has No Actual Prices — 'Get a Quote' for All Three Tiers — Hides from Commercial-Intent Search
Score
20
Severity
High
Finding
The confirmed pricing page (/packages-and-pricing) shows three tiers — Essentials, Pro, Enterprise — all with 'Get a Quote' instead of any price anchor. While custom pricing for government contracts is standard, the complete absence of any pricing signal (e.g. 'starting from $X/year for communities under 10,000 residents') means the page cannot rank for commercial-intent searches like 'pavement management software pricing' or 'road inspection AI cost.' These are high-converting queries from buyers with budget. Competitor Better Roads (explicitly referenced in the site's own banner) likely outranks vialytics on pricing searches.
Recommendation
Add at minimum a pricing anchor or range ('Essentials plans start from $X/year for communities under 10,000 residents — contact us for exact pricing based on your road network size'). This preserves the consultative sales process while enabling the page to capture commercial-intent search traffic. Create a dedicated FAQ section addressing 'How much does pavement management software cost?' and 'Is vialytics more affordable than manual inspection?' — both high-value informational queries.
SEO
Prices Page Has No Actual Prices — 'Get a Quote' for All Three Tiers — Hides from Commercial-Intent Search
Score
20
Severity
High
Finding
The confirmed pricing page (/packages-and-pricing) shows three tiers — Essentials, Pro, Enterprise — all with 'Get a Quote' instead of any price anchor. While custom pricing for government contracts is standard, the complete absence of any pricing signal (e.g. 'starting from $X/year for communities under 10,000 residents') means the page cannot rank for commercial-intent searches like 'pavement management software pricing' or 'road inspection AI cost.' These are high-converting queries from buyers with budget. Competitor Better Roads (explicitly referenced in the site's own banner) likely outranks vialytics on pricing searches.
Recommendation
Add at minimum a pricing anchor or range ('Essentials plans start from $X/year for communities under 10,000 residents — contact us for exact pricing based on your road network size'). This preserves the consultative sales process while enabling the page to capture commercial-intent search traffic. Create a dedicated FAQ section addressing 'How much does pavement management software cost?' and 'Is vialytics more affordable than manual inspection?' — both high-value informational queries.
SEO
Multilingual Setup — .com/.de/.fr Split Domains — Missing hreflang Tags Between Versions
Score
24
Severity
Medium
Finding
The homepage confirms three language versions: vialytics.com (English/US), vialytics.de (German), vialytics.fr (French). The nav shows language switching, but the fetched page HTML does not contain hreflang tags linking the three versions. Without hreflang, Googlebot cannot determine which language version to serve to which country audience. This causes: (1) German users being served the .com English version, (2) Google potentially treating the three domains as duplicate content and diluting link equity across them, (3) missed opportunity to rank locally in the DE and FR markets.
Recommendation
Add hreflang link tags to the <head> of all three domains pointing at each other: <link rel='alternate' hreflang='en-us' href='https://www.vialytics.com/'>, <link rel='alternate' hreflang='de' href='https://www.vialytics.de/'>, <link rel='alternate' hreflang='fr' href='https://www.vialytics.fr/'>, <link rel='alternate' hreflang='x-default' href='https://www.vialytics.com/'>. Also implement this on every corresponding inner page pair. This is standard HubSpot multi-language configuration and can be done via the HubSpot multilanguage content settings.
SEO
Multilingual Setup — .com/.de/.fr Split Domains — Missing hreflang Tags Between Versions
Score
24
Severity
Medium
Finding
The homepage confirms three language versions: vialytics.com (English/US), vialytics.de (German), vialytics.fr (French). The nav shows language switching, but the fetched page HTML does not contain hreflang tags linking the three versions. Without hreflang, Googlebot cannot determine which language version to serve to which country audience. This causes: (1) German users being served the .com English version, (2) Google potentially treating the three domains as duplicate content and diluting link equity across them, (3) missed opportunity to rank locally in the DE and FR markets.
Recommendation
Add hreflang link tags to the <head> of all three domains pointing at each other: <link rel='alternate' hreflang='en-us' href='https://www.vialytics.com/'>, <link rel='alternate' hreflang='de' href='https://www.vialytics.de/'>, <link rel='alternate' hreflang='fr' href='https://www.vialytics.fr/'>, <link rel='alternate' hreflang='x-default' href='https://www.vialytics.com/'>. Also implement this on every corresponding inner page pair. This is standard HubSpot multi-language configuration and can be done via the HubSpot multilanguage content settings.
SEO
Multilingual Setup — .com/.de/.fr Split Domains — Missing hreflang Tags Between Versions
Score
24
Severity
Medium
Finding
The homepage confirms three language versions: vialytics.com (English/US), vialytics.de (German), vialytics.fr (French). The nav shows language switching, but the fetched page HTML does not contain hreflang tags linking the three versions. Without hreflang, Googlebot cannot determine which language version to serve to which country audience. This causes: (1) German users being served the .com English version, (2) Google potentially treating the three domains as duplicate content and diluting link equity across them, (3) missed opportunity to rank locally in the DE and FR markets.
Recommendation
Add hreflang link tags to the <head> of all three domains pointing at each other: <link rel='alternate' hreflang='en-us' href='https://www.vialytics.com/'>, <link rel='alternate' hreflang='de' href='https://www.vialytics.de/'>, <link rel='alternate' hreflang='fr' href='https://www.vialytics.fr/'>, <link rel='alternate' hreflang='x-default' href='https://www.vialytics.com/'>. Also implement this on every corresponding inner page pair. This is standard HubSpot multi-language configuration and can be done via the HubSpot multilanguage content settings.
Geo
US Homepage Serves Only Phone Number — No State/County-Level Content for US Market Segments
Score
28
Severity
Medium
Finding
The homepage is geo-targeted to the US ('Intelligent Road Management for the US | vialytics Americas') but treats the entire US as a single homogeneous market. US pavement management procurement is highly fragmented by state: New Jersey, Connecticut, Georgia, Indiana, and New York are confirmed customer states (Edison NJ, Bethel CT, Sugar Hill GA, Huntington County IN, Brighton NY shown in the homepage trust bar). Each state has different procurement rules, budget cycles, state contract vehicles, and pavement condition index standards. There is no state-specific landing page content despite confirmed US customers across multiple states.
Recommendation
Create state-specific landing pages for the top 5-10 confirmed customer states: /new-jersey-pavement-management, /connecticut-road-management, /georgia-municipality-roads. Each should reference: (1) the state's specific infrastructure funding programmes (e.g. NJDOT Local Aid, ConnDOT Local Bridge Program), (2) any cooperative purchasing contracts vialytics participates in, (3) named local customers in that state. These pages capture high-intent local government searches and support the field sales team with state-specific social proof.
Geo
US Homepage Serves Only Phone Number — No State/County-Level Content for US Market Segments
Score
28
Severity
Medium
Finding
The homepage is geo-targeted to the US ('Intelligent Road Management for the US | vialytics Americas') but treats the entire US as a single homogeneous market. US pavement management procurement is highly fragmented by state: New Jersey, Connecticut, Georgia, Indiana, and New York are confirmed customer states (Edison NJ, Bethel CT, Sugar Hill GA, Huntington County IN, Brighton NY shown in the homepage trust bar). Each state has different procurement rules, budget cycles, state contract vehicles, and pavement condition index standards. There is no state-specific landing page content despite confirmed US customers across multiple states.
Recommendation
Create state-specific landing pages for the top 5-10 confirmed customer states: /new-jersey-pavement-management, /connecticut-road-management, /georgia-municipality-roads. Each should reference: (1) the state's specific infrastructure funding programmes (e.g. NJDOT Local Aid, ConnDOT Local Bridge Program), (2) any cooperative purchasing contracts vialytics participates in, (3) named local customers in that state. These pages capture high-intent local government searches and support the field sales team with state-specific social proof.
Geo
US Homepage Serves Only Phone Number — No State/County-Level Content for US Market Segments
Score
28
Severity
Medium
Finding
The homepage is geo-targeted to the US ('Intelligent Road Management for the US | vialytics Americas') but treats the entire US as a single homogeneous market. US pavement management procurement is highly fragmented by state: New Jersey, Connecticut, Georgia, Indiana, and New York are confirmed customer states (Edison NJ, Bethel CT, Sugar Hill GA, Huntington County IN, Brighton NY shown in the homepage trust bar). Each state has different procurement rules, budget cycles, state contract vehicles, and pavement condition index standards. There is no state-specific landing page content despite confirmed US customers across multiple states.
Recommendation
Create state-specific landing pages for the top 5-10 confirmed customer states: /new-jersey-pavement-management, /connecticut-road-management, /georgia-municipality-roads. Each should reference: (1) the state's specific infrastructure funding programmes (e.g. NJDOT Local Aid, ConnDOT Local Bridge Program), (2) any cooperative purchasing contracts vialytics participates in, (3) named local customers in that state. These pages capture high-intent local government searches and support the field sales team with state-specific social proof.
Accessibility
Navigation CTA Buttons Are PNG Images Without Meaningful Alt Text — Screen Reader Failure
Score
32
Severity
High
Finding
The page source confirms CTA buttons are PNG images served from no-cache.hubspot.com. The alt text for these images is the raw filename or empty — e.g. the 'Contact' button image uses the URL path as its accessible name. PNG image buttons without descriptive alt text are a WCAG 2.1 Level A failure (Success Criterion 1.1.1: Non-text Content). Government websites and municipal software vendors have heightened obligations under Section 508 (US) and BITV 2.0 (Germany). A public works director using a screen reader cannot access the primary CTAs.
Recommendation
Replace PNG image CTAs with HTML button elements or styled anchor tags. If HubSpot smart CTAs must remain as images, ensure every CTA image has an explicit, descriptive alt attribute: alt='Contact vialytics Sales Team' or alt='Get started with vialytics'. Audit all CTA images across the entire site using an automated accessibility checker (axe, WAVE, or HubSpot's built-in accessibility checker) and fix all empty or filename-based alt attributes.
Accessibility
Navigation CTA Buttons Are PNG Images Without Meaningful Alt Text — Screen Reader Failure
Score
32
Severity
High
Finding
The page source confirms CTA buttons are PNG images served from no-cache.hubspot.com. The alt text for these images is the raw filename or empty — e.g. the 'Contact' button image uses the URL path as its accessible name. PNG image buttons without descriptive alt text are a WCAG 2.1 Level A failure (Success Criterion 1.1.1: Non-text Content). Government websites and municipal software vendors have heightened obligations under Section 508 (US) and BITV 2.0 (Germany). A public works director using a screen reader cannot access the primary CTAs.
Recommendation
Replace PNG image CTAs with HTML button elements or styled anchor tags. If HubSpot smart CTAs must remain as images, ensure every CTA image has an explicit, descriptive alt attribute: alt='Contact vialytics Sales Team' or alt='Get started with vialytics'. Audit all CTA images across the entire site using an automated accessibility checker (axe, WAVE, or HubSpot's built-in accessibility checker) and fix all empty or filename-based alt attributes.
Accessibility
Navigation CTA Buttons Are PNG Images Without Meaningful Alt Text — Screen Reader Failure
Score
32
Severity
High
Finding
The page source confirms CTA buttons are PNG images served from no-cache.hubspot.com. The alt text for these images is the raw filename or empty — e.g. the 'Contact' button image uses the URL path as its accessible name. PNG image buttons without descriptive alt text are a WCAG 2.1 Level A failure (Success Criterion 1.1.1: Non-text Content). Government websites and municipal software vendors have heightened obligations under Section 508 (US) and BITV 2.0 (Germany). A public works director using a screen reader cannot access the primary CTAs.
Recommendation
Replace PNG image CTAs with HTML button elements or styled anchor tags. If HubSpot smart CTAs must remain as images, ensure every CTA image has an explicit, descriptive alt attribute: alt='Contact vialytics Sales Team' or alt='Get started with vialytics'. Audit all CTA images across the entire site using an automated accessibility checker (axe, WAVE, or HubSpot's built-in accessibility checker) and fix all empty or filename-based alt attributes.
Accessibility
Autoplay Video Without Pause Control — WCAG 2.1 Failure for Vestibular and Cognitive Disorders
Score
36
Severity
High
Finding
The hero contains an autoplay background video (the MP4 confirmed in the page source). WCAG 2.1 Success Criterion 2.2.2 (Pause, Stop, Hide) requires that any auto-playing motion content lasting more than 5 seconds must have a mechanism to pause, stop, or hide it. There is no visible pause button on the hero video. This affects users with vestibular disorders (motion sickness from video), cognitive disabilities (difficulty focusing with background motion), and users who have enabled 'reduce motion' in their OS accessibility settings. This is also a potential ADA compliance issue for a company selling to US government bodies.
Recommendation
Add a visible pause/play toggle button to the hero video, positioned accessibly (sufficient colour contrast, keyboard-focusable, with an aria-label). Additionally, implement prefers-reduced-motion CSS media query: @media (prefers-reduced-motion: reduce) { video { display: none; } } — this replaces the video with the poster image for users who have requested reduced motion in their OS settings. This is a one-hour fix with significant accessibility impact.
Accessibility
Autoplay Video Without Pause Control — WCAG 2.1 Failure for Vestibular and Cognitive Disorders
Score
36
Severity
High
Finding
The hero contains an autoplay background video (the MP4 confirmed in the page source). WCAG 2.1 Success Criterion 2.2.2 (Pause, Stop, Hide) requires that any auto-playing motion content lasting more than 5 seconds must have a mechanism to pause, stop, or hide it. There is no visible pause button on the hero video. This affects users with vestibular disorders (motion sickness from video), cognitive disabilities (difficulty focusing with background motion), and users who have enabled 'reduce motion' in their OS accessibility settings. This is also a potential ADA compliance issue for a company selling to US government bodies.
Recommendation
Add a visible pause/play toggle button to the hero video, positioned accessibly (sufficient colour contrast, keyboard-focusable, with an aria-label). Additionally, implement prefers-reduced-motion CSS media query: @media (prefers-reduced-motion: reduce) { video { display: none; } } — this replaces the video with the poster image for users who have requested reduced motion in their OS settings. This is a one-hour fix with significant accessibility impact.
Accessibility
Autoplay Video Without Pause Control — WCAG 2.1 Failure for Vestibular and Cognitive Disorders
Score
36
Severity
High
Finding
The hero contains an autoplay background video (the MP4 confirmed in the page source). WCAG 2.1 Success Criterion 2.2.2 (Pause, Stop, Hide) requires that any auto-playing motion content lasting more than 5 seconds must have a mechanism to pause, stop, or hide it. There is no visible pause button on the hero video. This affects users with vestibular disorders (motion sickness from video), cognitive disabilities (difficulty focusing with background motion), and users who have enabled 'reduce motion' in their OS accessibility settings. This is also a potential ADA compliance issue for a company selling to US government bodies.
Recommendation
Add a visible pause/play toggle button to the hero video, positioned accessibly (sufficient colour contrast, keyboard-focusable, with an aria-label). Additionally, implement prefers-reduced-motion CSS media query: @media (prefers-reduced-motion: reduce) { video { display: none; } } — this replaces the video with the poster image for users who have requested reduced motion in their OS settings. This is a one-hour fix with significant accessibility impact.
Content
Pricing Page Questionnaire Copy Is Juvenile — Undermines Government B2B Credibility
Score
40
Severity
Medium
Finding
The confirmed pricing page (/packages-and-pricing) contains an interactive questionnaire with the following copy: 'Do you want to save TONS OF MONEY for your municipality? YES, ABSOLUTELY! I like wasting budget' and 'Do you only work with the BEST EXPERTS? ALWAYS. Mediocrity is fine.' This gamified, hyperbolic tone is appropriate for B2C SaaS but actively harmful in the government procurement context. Municipal budget officers, city managers, and public works directors are accountable to elected officials and taxpayers. 'I like wasting budget' and 'Mediocrity is fine' are joke options that would make a city manager visibly uncomfortable — they are the antithesis of the careful, defensible language government procurement requires. The 'READY TO DOMINATE?' section heading on the homepage compounds this.
Recommendation
Replace the questionnaire with a professional needs-assessment tool: 'Step 1: What is the approximate size of your road network? (Under 50 miles / 50-200 miles / 200+ miles). Step 2: How do you currently assess pavement conditions? (Manual inspection / Periodic contractor surveys / No formal process). Step 3: What is your primary goal? (Reduce outside inspection costs / Improve budget justification / Proactive maintenance planning).' Provide a personalised package recommendation based on answers. This converts the same interactive mechanic into a professional needs-analysis that a city manager can screenshot and share with their supervisor.
Content
Pricing Page Questionnaire Copy Is Juvenile — Undermines Government B2B Credibility
Score
40
Severity
Medium
Finding
The confirmed pricing page (/packages-and-pricing) contains an interactive questionnaire with the following copy: 'Do you want to save TONS OF MONEY for your municipality? YES, ABSOLUTELY! I like wasting budget' and 'Do you only work with the BEST EXPERTS? ALWAYS. Mediocrity is fine.' This gamified, hyperbolic tone is appropriate for B2C SaaS but actively harmful in the government procurement context. Municipal budget officers, city managers, and public works directors are accountable to elected officials and taxpayers. 'I like wasting budget' and 'Mediocrity is fine' are joke options that would make a city manager visibly uncomfortable — they are the antithesis of the careful, defensible language government procurement requires. The 'READY TO DOMINATE?' section heading on the homepage compounds this.
Recommendation
Replace the questionnaire with a professional needs-assessment tool: 'Step 1: What is the approximate size of your road network? (Under 50 miles / 50-200 miles / 200+ miles). Step 2: How do you currently assess pavement conditions? (Manual inspection / Periodic contractor surveys / No formal process). Step 3: What is your primary goal? (Reduce outside inspection costs / Improve budget justification / Proactive maintenance planning).' Provide a personalised package recommendation based on answers. This converts the same interactive mechanic into a professional needs-analysis that a city manager can screenshot and share with their supervisor.
Content
Pricing Page Questionnaire Copy Is Juvenile — Undermines Government B2B Credibility
Score
40
Severity
Medium
Finding
The confirmed pricing page (/packages-and-pricing) contains an interactive questionnaire with the following copy: 'Do you want to save TONS OF MONEY for your municipality? YES, ABSOLUTELY! I like wasting budget' and 'Do you only work with the BEST EXPERTS? ALWAYS. Mediocrity is fine.' This gamified, hyperbolic tone is appropriate for B2C SaaS but actively harmful in the government procurement context. Municipal budget officers, city managers, and public works directors are accountable to elected officials and taxpayers. 'I like wasting budget' and 'Mediocrity is fine' are joke options that would make a city manager visibly uncomfortable — they are the antithesis of the careful, defensible language government procurement requires. The 'READY TO DOMINATE?' section heading on the homepage compounds this.
Recommendation
Replace the questionnaire with a professional needs-assessment tool: 'Step 1: What is the approximate size of your road network? (Under 50 miles / 50-200 miles / 200+ miles). Step 2: How do you currently assess pavement conditions? (Manual inspection / Periodic contractor surveys / No formal process). Step 3: What is your primary goal? (Reduce outside inspection costs / Improve budget justification / Proactive maintenance planning).' Provide a personalised package recommendation based on answers. This converts the same interactive mechanic into a professional needs-analysis that a city manager can screenshot and share with their supervisor.