We found 1 issuecosting you truston getskip.ai.
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 centros page gives two different provider counts
Customers have to decide which of your promises to trust.
On /centros the hero headline reads "+200 prestadores donde tu reembolso corre solo", while the list further down the same page is labelled "163 centros integrados". Both figures describe the integrated provider network on one route, so the page states two different sizes for it. The headline number cannot be reconciled with the count rendered above the listing.
Try it: Open /centros, read the hero headline, then scroll to the label above the provider list and compare the two counts.
The header logo overlaps the section heading on mobile
On /prestadores at a 390px viewport, the header "skip" wordmark and logo mark paint directly over the section heading and the first line of the intro paragraph. The heading line "de "Copago"" is crossed by the wordmark's descender and the mark's rays, and "Desarrollamos dos productos específicos" runs under the bottom of the wordmark, so all three strings are hard to read in that band. The overlap sits in the top 230px of the viewport at this scroll position and appears the same on a fresh load.
The header overlaps the stats heading on mobile
On /prestadores at a 390px wide viewport, the sticky header sits directly on top of the first stat block. The "skip" wordmark covers the start of the line that reads "...esados por Atiéndete Ahora, Paga Después by Skip", and the "Quiero integrarme" button and its pill background cover the "millones" suffix of the "+$130" figure and the right end of that same line. Both the header text and the stat text are unreadable where they intersect.
Four routes share the page title "Skip"
Four distinct routes on getskip.ai render the identical document title "Skip": /, /prestadores, /onboarding, and /cnpl. Each of these is a separate page with its own content, so search results, browser tabs, and bookmarks give no way to tell them apart. The titles are set identically in the rendered head of each route.
Four routes share one meta description
The routes /, /prestadores, /onboarding and /cnpl all serve the identical meta description: "AI para simplificar la vida de pacientes y prestadores de salud. Reembolsos automatizados y copago virtual." These are distinct pages covering the landing page, the provider section, onboarding and CNPL, so search results and link previews for each carry the same summary text with nothing that distinguishes them.
Five security response headers are missing
The response from https://www.getskip.ai/ is missing Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, X-Content-Type-Options: nosniff, Referrer-Policy, and Cross-Origin-Resource-Policy.
Chat mockup text fails the AA contrast threshold
The WhatsApp style chat mockup in the hero on / has text below the WCAG AA contrast threshold. The message timestamps render #667781 on #DCF8C6 at 4.04:1, the attachment line "498 kB · PDF" renders #667781 on #D1ECBC at 3.63:1, and the red "PDF" badge renders white on #EA4335 at 3.92:1, all against a required 4.5:1 at those sizes (9px and 8px).
A hero mockup marked as an image contains focusable elements
On the home page of getskip.ai, the hero phone mockup is a div carrying role="img" with the aria-label "Pantalla de la plataforma Skip mostrando $145.100 reembolsados en el mes y la lista de gastos aprobados.", and it contains focusable descendants. Assistive technology presents the container as a single image while keyboard users can still tab into elements inside it, so the exposed structure and the focus order disagree. Six similar findings on the same route were suppressed behind this one.
The logo strip on /prestadores leaves a tall empty band
On /prestadores at mobile width, the "Confían en Skip" logo strip renders only two partner logos and then about 300 css pixels of blank white before the next colored section starts, close to half the 664 pixel viewport. The leftmost logo is also cut off at the left edge of the screen, with part of its mark outside the visible area. The band sits between two rendered sections rather than at the end of the page, so the strip reads as a row that failed to fill.
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.