We found 4 issuescosting you truston berrypm.app.
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 signup form says 3 free days, but pricing promises 15
Visitors who click "Start 15-day trial" see a 3-day trial on the signup form, right when they decide whether to create an account.
On /pricing, the Starter and Growth buttons read "Start 15-day trial", and the page says "Every new workspace starts with 15 days of Growth" in both the subtitle and the FAQ. Those buttons open /auth. On its Create account tab, the line under Company name says "Starts a new workspace with 3 free days." A buyer meets this contradiction at the signup step, right after the pricing page offered them a 15-day trial.
Try it: Open /pricing and click "Start 15-day trial". On /auth, click the Create account tab and read the line under Company name.
The home page pitches a workspace plan but pricing charges per user
Buyers comparing costs are told three different things about how they will be billed, and they also read that billing is not connected.
The home page Subscribe box offers "One monthly plan for the whole workspace" and says "Billing is not connected yet." under its See pricing button. The pricing page lists Starter at "₹449 per user / month" and Growth at "₹799 per user / month" under the headline "Pay for capabilities, not headcount", and its FAQ says you pay "Only per person on paid plans." A buyer checking the price meets three billing models that conflict, plus a note telling them they cannot pay yet.
Try it: Open berrypm.app and read the Subscribe box. Then click See pricing and compare the headline with the "per user / month" prices and the FAQ answer.
The phone header has no link to pricing or features
Phone visitors who want to check the price before signing up have to scroll the home page to find a pricing link.
On a 390px phone screen, the home page header shows only the BerryPM logo and a Sign in button. It has no menu toggle and no Features or Pricing links. The two buttons above the fold are "Open the workspace" and "Explore all features", so a buyer who wants the price at the pricing step has to scroll down to find the in-page pricing button.
Try it: Open berrypm.app on a phone or in a 390px-wide browser window and look at the header. Only the logo and Sign in appear, with no menu and no Pricing link.
On phones, the plan table shows Starter and Growth limits as one word
On /pricing at phone width, the Compare plans table has no gap between the Starter and Growth cells in the People, Active projects and Sprints per project rows, so each row reads "UnlimitedUnlimited". The rows below, such as File storage, are spaced normally. Buyers meet this table at the pricing step while they decide between plans.
Try it: Open /pricing at 390px width and scroll to the Compare plans table. Look at the People and Active projects rows under Starter and Growth.
The signup page opens as a sign-in form for new visitors
/auth opens with a "Welcome back" heading and the line "Sign in to your workspace to continue." The Sign in tab is selected and the main button says "Sign in". Account creation sits in the unselected "Create account" tab beside it. This is the signup step, so every new buyer starting the 15-day Growth trial meets it and has to switch modes before they can register.
The home page took 4.8s to show its main content on a phone
On a phone viewport, the largest content on / painted at 4.8 seconds. Google classes anything over 4 seconds as poor. A second load came in under that threshold, so this delay is intermittent, and it affects the first page a visitor reads before opening the workspace or checking pricing.
The 36px header logo downloads as a 174 KB 512px PNG
The BerryPM mark in the home page header is a 512x512 PNG that transfers 174,472 bytes and displays at 36x36 at a device pixel ratio of 1. It is not the largest contentful paint element, and the logo renders correctly.
The header logo ships as a 174 KB file for a 36 pixel slot
On /features the header logo BerryPM_mark.png is a 512 by 512 image that is 174,472 bytes and renders at 36 by 36 pixels on a 1x display. The same size and transfer were measured on a second load. It is not the largest contentful element, so the feature content still appears without waiting for it.
The 32px header logo downloads as a 174 KB 512px PNG
On /pricing, the header logo BerryPM_mark.png is 512x512 pixels and 174,472 bytes, but it displays at 32x32 at a device pixel ratio of 1. The same measurement came back on a second load. It is not the largest contentful paint element, and LCP measured 2432 ms and 2084 ms.
The home page head has no canonical URL
The home page at / has no link rel="canonical" in its head. The title, description, icon and Open Graph image are all present and load correctly. Only the canonical declaration is missing.
The sign-in fields on /auth have no autocomplete hints
On /auth, the "Work email" field (type email) and the "Password" field (type password) in the sign-in form have no autocomplete attribute and no name attribute. Because they lack the "username" and "current-password" tokens, browsers and password managers have to guess at these fields when filling saved credentials.
The home page lacks a Cross-Origin-Resource-Policy header
The response from https://berrypm.app/ is missing 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.