FIVEO1.COM WEBSITE PERFORMANCE, ACCESSIBILITY, SECURITY, SEO AND AGENTIC BROWSING REPORT Report Date: October 7, 2026 Website: https://fiveo1.com/ Prepared for United States professional and technical review Website Identification Fiveo1.com Organization: Fiveo1 Representative: Evan Winter Executive Technical Summary The October 7, 2026 PageSpeed Insights assessment of Fiveo1.com was conducted using the mobile configuration with an emulated Moto G Power, Lighthouse 13.5.0 and Slow 4G network throttling. Principal scores: Performance: 83 Accessibility: 72 Best Practices: 100 SEO: 92 Agentic Browsing: 2 of 4 The website demonstrates strong overall technical performance in several areas. Cumulative Layout Shift is 0, Total Blocking Time is 10 milliseconds, First Contentful Paint is 1.7 seconds, Best Practices is 100, and the document is available for indexing. The principal performance limitation is not server response time. The principal limitation identified by the assessment is delayed rendering of the Largest Contentful Paint element. The Location Map heading was identified as the LCP element, with an element render delay of approximately 3,380 milliseconds. The principal accessibility issues are insufficient color contrast on the LIFE button, missing alternative text on slideshow images, inadequate touch target dimensions or spacing, and a heading hierarchy beginning with an H3 without the required preceding heading structure. The assessment also identified an image at /B7458292.jpg carrying the alternative text value "fuck". This value should be replaced with an accurate, descriptive alternative text value appropriate to the image and its purpose. The SEO score is 92. The principal automated SEO deficiency is the absence of alternative text on the slideshow images. The Best Practices score is 100 despite several unscored security-related observations. PageSpeed identified the absence of an enforced Content Security Policy, HSTS, Trusted Types enforcement and Cross-Origin Opener Policy. The Agentic Browsing score is 2 of 4. The primary deficiencies are an improperly structured llms.txt file and an invalid ai-catalog.json schema. Performance Mobile Performance Score: 83 Testing Environment Device emulation: Moto G Power Network: Slow 4G Audit software: Lighthouse 13.5.0 Audit date: October 7, 2026 Core Web Vitals and Performance Metrics First Contentful Paint: 1.7 seconds (Good) Largest Contentful Paint: 3.9 seconds (Needs Improvement) Total Blocking Time: 10 milliseconds (Good) Cumulative Layout Shift: 0 (Good) Speed Index: 5.6 seconds (Needs Improvement) Largest Contentful Paint The LCP element identified by Lighthouse is the Location Map H3 element. The element is rendered with the following structure: h3 style="margin-top:0; border-bottom:1px solid #2a2d33; padding-bottom:8px;" The LCP timing is 3.9 seconds. The reported breakdown identifies approximately 3,380 milliseconds as element render delay. Time to first byte is reported as 0 milliseconds. The assessment therefore identifies client-side rendering and resource sequencing as the principal factor affecting LCP rather than slow initial server response. Image Delivery Estimated potential savings: 426 KiB. The principal identified image is /B7458292.jpg. Displayed dimensions: approximately 77 by 96 pixels Actual image dimensions: approximately 719 by 717 pixels Reported transfer size: approximately 427.6 KiB The image is substantially larger than its displayed dimensions. The assessment recommends more efficient image delivery through appropriate image dimensions, compression and modern image formats such as WebP or AVIF where compatible with the site's requirements. Render-Blocking Resources Estimated potential savings: approximately 610 milliseconds. Identified resources: /style.css — first-party, approximately 7.9 KiB, approximately 150 milliseconds blocking impact Leaflet CSS from unpkg.com — approximately 4.2 KiB, approximately 750 milliseconds blocking impact The Leaflet stylesheet represents the largest individual render-blocking resource identified by this audit. Network Dependency The maximum reported critical path latency is approximately 1,365 milliseconds. The principal sequence is: https://fiveo1.com/ followed by /style.css followed by leaflet.css followed by leaflet.js No origins were preconnected at the time of testing. The assessment indicates that the browser must establish and process these dependencies before completing the relevant rendering sequence. Cache Policy The audit identifies approximately 1 KiB of potential savings associated with cache lifetime configuration. The reported cache lifetime for style.css is 7 days. A longer cache lifetime may reduce repeat network requests for unchanged static resources where the site's deployment and update process permits longer caching. JavaScript The assessment identifies approximately 35 KiB of potential savings from unused JavaScript. Leaflet.js is approximately 41.4 KiB, with approximately 34.5 KiB identified as unused under the tested page conditions. Related Leaflet modules identified by the audit include Map.js, GridLayer.js and Canvas.js. The audit also identifies approximately 4 KiB of potential savings from JavaScript minification. The referenced inline JavaScript is approximately 12.1 KiB. Network Payload Total network payload during the test was approximately 3,743 KiB. The largest identified image was /B7458292.jpg at approximately 427.6 KiB. Several additional JPEG images were approximately 151.5 KiB each. The total payload is therefore materially influenced by image delivery rather than JavaScript execution alone. Main Thread The assessment identified two long main-thread tasks. Total Blocking Time remains low at 10 milliseconds, indicating that the long tasks did not produce a substantial blocking penalty under this particular test configuration. Third-Party Resources The principal third-party origin identified was unpkg.com. Reported transfer size: approximately 47 KiB Reported main thread time: approximately 45 milliseconds Leaflet JavaScript accounts for approximately 42 KiB of the transfer. Leaflet CSS accounts for approximately 4 KiB. Passed Performance Audits Layout shift culprits Document request latency Avoidance of redirects Server response Text compression DOM size optimization Duplicated JavaScript detection Font display Forced reflow INP breakdown LCP request discovery Legacy JavaScript Mobile viewport configuration CSS minification Unused CSS reduction User Timing marks and measures Accessibility Accessibility Score: 72 The automated accessibility assessment identified four principal deficiencies. Color Contrast The LIFE button was identified as failing the required background and foreground color contrast ratio. Element: button id="goLiveBtn" class="header-btn-life" LIFE The text and background colors should be adjusted to meet the applicable WCAG contrast requirement while retaining the site's functional appearance. Image Alternative Text The slideshow images do not have alt attributes. Identified elements: body.index-page > div#slideshow > img#imgA body.index-page > div#slideshow > img#imgB Alternative text should accurately describe the image where the image conveys information. If an image is purely decorative, the appropriate implementation is an empty alt attribute rather than omission of the attribute. Inappropriate Alt Text The audit identified the image /B7458292.jpg with the alternative text "fuck". This value is not an appropriate description of an image and should be replaced with accurate descriptive alternative text or an empty alt value if the image is strictly decorative. This correction also affects the site's SEO evaluation because image alternative text is used in automated search and accessibility audits. Touch Targets The assessment identifies touch targets that do not provide sufficient size or spacing. Interactive controls should provide adequate target dimensions and separation for mobile users, particularly on the tested mobile viewport. Heading Structure The Location Map element is implemented as an H3. The audit reports that heading elements are not arranged in a sequential descending hierarchy. The document should establish the appropriate H1 and subsequent heading structure before an H3 is used. The correction should preserve the semantic organization of the document rather than changing heading levels solely to alter visual size. Accessibility Items That Passed Accessible document structure Accessible button naming Form labels Absence of user-scalable no configuration Document title Valid HTML language attribute Discernible link names Main landmark SEO SEO Score: 92 The website is available for indexing. The document contains a title. The HTML element contains a valid language attribute. The viewport configuration does not prevent normal user scaling. The principal automated SEO deficiency identified is the missing alt attributes on the slideshow images. The audit also recommends manual validation of structured data through an appropriate structured data testing system. Best Practices Best Practices Score: 100 The automated Best Practices category produced a score of 100. The audit nevertheless identified several security-related items as unscored observations. Content Security Policy No Content Security Policy was detected in enforcement mode. A properly configured Content Security Policy can restrict unauthorized script, object, frame, style and resource execution and reduce exposure to certain classes of cross-site scripting attacks. HSTS No HTTP Strict Transport Security header was detected. An HSTS policy instructs compatible browsers to use HTTPS for subsequent connections to the domain. Trusted Types No Content Security Policy Trusted Types directive was detected. Trusted Types can provide an additional browser-enforced control against certain DOM-based cross-site scripting patterns when the site's JavaScript architecture supports the policy. Cross-Origin Opener Policy No Cross-Origin Opener Policy was detected. COOP can provide browser isolation controls between the site and separately opened browsing contexts. Agentic Browsing Agentic Browsing Score: 2 of 4 The PageSpeed assessment evaluates machine-readable resources and website characteristics intended to support automated browsing systems and WebMCP-related functionality. llms.txt The site's llms.txt file does not meet the tested recommendations. The audit reports that the file is missing a required H1 heading and does not contain links. The file should therefore be structured according to the current llms.txt convention being targeted by the site and should provide a clear H1 followed by useful linked resources. AI Catalog The ai-catalog.json resource was reported as having an invalid schema. The JSON structure should be validated against the schema expected by the site's intended agentic browsing implementation. Accessibility Tree The accessibility tree passed the Agentic Browsing accessibility audit. This indicates that the automated accessibility representation of the tested page was structurally readable by the assessment system. Cumulative Layout Shift The Agentic Browsing assessment also passed the cumulative layout shift requirement. CLS was measured at 0. WebMCP The assessment did not assign a score to WebMCP form coverage or registered WebMCP tools. No conclusion about WebMCP functionality should therefore be drawn from the 2 of 4 Agentic Browsing score alone. Browser Compatibility and Libraries Detected JavaScript library: Leaflet 1.9.4 The assessment detected commonly supported browser capabilities including print-color-adjust, scrollbar-width, backdrop-filter, not, slot, will-change, grid, flexbox, and requestAnimationFrame. The assessment identifies these features as supported across the tested browser compatibility baseline. Priority Technical Corrections 1. The highest measurable performance correction is reduction of the 3.9-second LCP by addressing the approximately 3,380-millisecond element render delay associated with the Location Map section. 2. The next performance correction is optimization of B7458292.jpg and other oversized JPEG resources. 3. The Leaflet CSS resource should be evaluated for local hosting, loading strategy and whether it is required before initial content rendering. 4. Leaflet JavaScript should be evaluated for deferred loading and whether all currently loaded functionality is required during initial page rendering. 5. The slideshow images should receive appropriate alt attributes. 6. The existing alt value "fuck" on B7458292.jpg should be replaced with accurate descriptive text or an empty alt attribute where appropriate. 7. The LIFE button color contrast should be corrected. 8. Mobile touch target dimensions and spacing should be corrected. 9. The heading hierarchy should be corrected so the Location Map heading follows an appropriate document heading structure. 10. The seven-day style.css cache lifetime should be reviewed. 11. The llms.txt document should be corrected to contain the required H1 and links. 12. The ai-catalog.json document should be corrected to conform to its intended schema. 13. Security headers should be evaluated and implemented according to the site's actual application requirements, including Content Security Policy, HSTS, Trusted Types and Cross-Origin Opener Policy. Current Measured Position Fiveo1.com currently records a mobile Performance score of 83, Accessibility score of 72, Best Practices score of 100, SEO score of 92 and Agentic Browsing score of 2 out of 4 in the October 7, 2026 PageSpeed Insights assessment. The strongest measured areas are server response, layout stability, blocking time, basic SEO availability, document structure and general Best Practices compliance. The principal measured technical work remaining concerns initial rendering of the Location Map, image efficiency, render-blocking resources, mobile accessibility, semantic heading structure, machine-readable agent resources and selected HTTP security controls.