We found 2 issuescosting you truston pdftomp3.com.
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.
Pricing sells credits but never says what a credit buys
Visitors choosing a paid plan cannot work out how much audio $4.99, $12.99 or $89.99 gets them, or how it compares with the free plan.
On /pricing/, the paid plans come in credits ("150 credits per week", "600 credits per month"), but the free plan is measured in words ("up to 3000 words per month"). The only explanation, in the FAQ, says credits are used for "document processing, audio creation, asking questions and live conversations". Nothing on the page converts a credit into words, pages or minutes of audio. A buyer meets this exactly when picking a plan, so they cannot tell whether 600 credits covers one book or many, or whether 150 credits is more or less than the free 3000 words.
Try it: Open /pricing/, go through the Weekly, Monthly and Yearly tabs and read the "How much usage is included?" FAQ. Look for any line that turns credits into words, pages or minutes.
The phone Tips panel's close button is hidden under the header
Phone visitors who open Tips in the sample player cannot get back to the player or the upload box without reloading the page.
On a 390px phone screen, tapping "Tips" in the home page sample player opens a full-screen panel that covers the player and the upload area. The panel's "Close listening tips" button sits directly under the sticky header's menu button, so a tap in that corner opens the project menu instead, and the panel has no other close control. A phone visitor in the middle of the first demo meets this before uploading a PDF.
Try it: Open https://pdftomp3.com/ at iPhone width, scroll to the Sample document player and tap Tips. Then try to close the panel from its top right corner.
The example share buttons are 16px wide on phones
On /examples/, the share button on each example row, such as "Share How the Price System Works" and "Share I, Pencil", measures 16px by 44px on a phone. That is narrower than the 24px minimum in WCAG 2.5.8, and the space around it is also below 24px. The play buttons a visitor uses to hear the samples are separate controls and are not affected.
The home page is missing five security response headers
The response from https://pdftomp3.com/ is missing Strict-Transport-Security, Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, Referrer-Policy, and Cross-Origin-Resource-Policy.
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.