Nothing onauto360.clworth reporting.
Watch the inspection.
We navigate your site the way customers would. Idle time is skipped.
How the composite score works
The overall score is a weighted average of the categories: Getting the product 40%, Trust before buying 20%, Mobile 15%, Speed 15%, and Polish and audit 10%. It is never more than 10 points above the Getting the product score, because a product a visitor cannot get cannot score well on anything else, and never more than 25 points above the weakest category, so one badly broken area is not averaged away. Any issue in the main list caps it at 89, so a score above 90 means nothing worth fixing was found.
Each category starts at 100 and stays there when nothing was found in it, whether or not the inspection got that far. Each distinct verified finding deducts 60 points for a serious problem on the path from arriving to paying, 40 for another serious problem, 30, 15 or 8 by high, medium or low severity otherwise, and 4 for an audit finding. Each additional finding below the list takes 2 more points off the overall score, up to 10. Scores stop at zero and round to whole numbers. The formula is fixed and versioned, so the same saved evidence always receives the same score.
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.
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.
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.
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.
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. The same node fails on a second load of the route.
Probie fixes this for you.
Stop customers hitting the same friction. Connect your codebase and Probie reproduces these failures, tests the fix, and opens a pull request for your review.
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.
Enter an address and we will email the report card link.