PROBIE
Fix these issues
Report readyDispatch 21

Nothing onshinkansen.financeworth reporting.

Probie inspected shinkansen.finance the way a new customer would. 5 pages, desktop and phone, 12 minutes. Sep 16, 2026.

5 pages visited127 controls found81 clicked
shinkansen.finance's report cardSep 16, 2026

Nothing serious broke.

0 issues
See the breakdown
Probie doesn't stop at the report.Sign up and turn these findings into tested pull requests.
Fix these issues →
Probie on site

Watch the inspection.

We navigate your site the way customers would. Idle time is skipped.

Inspect your own site
scores · out of 100
100Getting the productEvery step checked between arriving and paying worked.
100Trust before buyingNo contradictions or broken pages found before buying.
100MobileNo verified phone layout problems on the pages a buyer needs.
100SpeedNo verified slow pages or slow responses on the pages a buyer needs.
80Polish and auditThe third projection card is cut off on mobile
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.

issues
No issues found in the pages and actions checked.
additional findings
Medium

The third projection card is cut off on mobile

On /seguros at a 390px viewport, the projection summary row shows three cards but the third one runs past the right edge of its container and is cropped after about 30px. Its dashed green border is sliced vertically and its labels render as "SA", "PR" and a lone "M", so the projected balance is unreadable. The first two cards, "ÚLTIMO SALDO" and "POR PAGAR", fit inside the container, and there is no visible way to reach the rest of the third card.

Medium

Three security response headers are missing

The response from https://shinkansen.finance/ is missing Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, and Cross-Origin-Resource-Policy.

Medium

Carousel step buttons have no accessible name

The step indicator buttons in the "Somos la infraestructura end-to-end" section on / are empty elements with no accessible name. Screen reader and keyboard users reach the controls but get no indication of what step each one selects.

Medium

File labels in the before graphic fail contrast

In the "DE... situación actual" graphic on /inversiones, the 7px monospace file labels inside the stacked cards fall below the WCAG AA 4.5:1 threshold. The "banco1.cl" label is at 3.15:1 (#4271ad on #152339), "cartola.pdf" at 3.07:1 (#a64d4c on #2c1614), and "planilla.xlsx" at 4.17:1. The same failure appears on /seguros and /lending, and at that size the labels are effectively unreadable on screen.

Medium

The BCP logo is cut off at the right screen edge

On /treasury at a 390px viewport, the BCP logo in the "Confían en nosotros" logo strip runs past the right edge of the screen. The trailing chevron of the mark is sliced at the viewport boundary, and the strip's left logo, BANCO BICE, sits shifted so the row is not centered. The logo row is wider than the viewport, so the content overflows horizontally.

from report to pull request

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 fixed
PRFixes, one PR at a time
probie/fix-1+12−4checks passing

Free 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.

Send this report to an inbox.

Enter an address and we will email the report card link.