We found 5 issueson auto360.clworth fixing.
Watch the inspection.
We navigate your site the way customers would. Idle time is skipped.
Three response header and cookie protections are missing
The response from https://www.auto360.cl/ is missing CSP frame-ancestors or X-Frame-Options and Cross-Origin-Resource-Policy. sbjs_session lack Secure or HttpOnly.
Try it: Run curl -I https://www.auto360.cl/ and check for frame-ancestors or X-Frame-Options and Cross-Origin-Resource-Policy, then inspect the sbjs_session cookie flags in DevTools under Application, Cookies.
The homepage loads a vulnerable Swiper version
The homepage loads Swiper 8.4.5 from https://www.auto360.cl/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper.min.js?ver=8.4.5, bundled with the Elementor plugin. That version is known vulnerable to a prototype pollution issue tracked as CVE-2026-27212 and GHSA-hmx5-qpq5-p643 (CWE-1321), affecting Swiper >=6.5.1 and <12.1.2, where the indexOf() guard in extendDefaults() can be neutralized by polluting Array.prototype.indexOf. The advisory lists 12.1.2 as the fixed release.
Try it: Open https://www.auto360.cl/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper.min.js?ver=8.4.5 and read the version banner at the top of the file.
Vehicle card links have no accessible name
On the home page, the vehicle listing cards under "Autos publicados recientemente" wrap their image in an anchor with no accessible text. Nodes such as #vehica-car-95977 > .vehica-car-card__inner > .vehica-car-card-link and #vehica-car-95956 > .vehica-car-card__inner > .vehica-car-card-link point to /autos-disponibles/95977/ and /autos-disponibles/95956/ but carry no inner text, aria-label, or aria-labelledby, so they are in the tab order with no name. This fails the axe-core rule link-name at impact level serious (WCAG 2.4.4, 4.1.2), and screen reader and keyboard users reach a link announced only by its URL.
Try it: Load the home page, tab to a car card image link under "Autos publicados recientemente", and check the announced name or inspect the anchor for text or aria-label.
Newsletter intro text fails contrast on the home page
On the home page, the newsletter paragraph in .elementor-element-8f12fb6 ("Suscríbete a nuestro newsletter y está al tanto de todas nuestras promociones en repuestos, mantenciones y más.") renders white #ffffff on the blue #1a96ca panel at 16px normal weight. The measured contrast ratio is 3.35:1, below the 4.5:1 that WCAG 2 AA requires for body text. axe-core flags this as rule color-contrast at impact level serious. The same node fails on a second load of the route.
Try it: Open the home page, scroll to the newsletter signup block, and sample the paragraph text (#ffffff) against its blue background (#1a96ca) in a contrast checker.
The WhatsApp button covers the listing prices
On the mobile home page, the floating WhatsApp button sits on top of the price block in the "Audi A4 Blindado 1.4 TSI 2019" card under "Autos publicados recientemente:". The financed price renders as "$36.790.00" with the last character clipped by the green circle, and the cash price under "Contado:" is cut to "$36.990.0", so the trailing digits of both figures are unreadable. The button is fixed to the lower right of the viewport, so the overlap follows the page as it scrolls and lands on whichever card sits at that height.
Try it: Open auto360.cl on a phone, scroll to "Autos publicados recientemente:" and look at the price lines of the first car card behind the green WhatsApp button.
The scan found no self-serve signup or purchase path to try on this project.
Probie fixes this for you.
This report came from one visit. When installed on your project, Probie watches real sessions, reproduces failures, and opens tested fixes as pull requests.
Sign up and get this fixedFree inspection
What should Probie inspect next?
Enter a project URL. There is nothing to install.
Probie checks every issue twice, respects robots.txt, and backs off at bot challenges.