A QA Lead and a Hiring Manager for 1 Portfolio
A broken link on your portfolio during a job hunt is a silent no. Nobody emails you to say your contact form is dead, they just close the tab. So I put 2 readers into 1 pass: a hiring manager who judges what the page says about me, and a QA lead who refuses to believe a word of it until the links, the form and the load time all check out.
What it actually is
/portfolio-audit takes a live URL and nothing else - no repo, no code access. It looks at the site the way the world does. It reads it like a hiring manager: is there a real about-me, are the projects actually shown with live and repo links, does the writing say anything. Then it stress-tests it like a QA lead: it crawls every link (nav, project, social, resume, email) and reports the ones that 404, it probes the contact form on the happy path and the sad path, it runs Lighthouse for speed, and it checks HTTPS, security headers, and whether the domain looks owned or still sits on a *.vercel.app default.
The checklist is the one a recruiter runs without knowing they run it: resume link that opens, GitHub and LinkedIn that resolve, a way to reach you, a page that loads before they lose interest, and a mobile view that does not fall apart. It grades a dozen lenses A to F and ranks the fixes. It never submits the form for real and never touches the site.
That is the difference from /repo-audit. Repo audit has the code and grades how the thing is built. Portfolio audit has only the URL and grades how the thing lands. Both matter, and they fail for different reasons.
In practice
I pointed it at my own site, feeling pretty good about it. It found a link that 404'd, a contact form that silently failed on 1 path, and a couple of images that loaded slow enough to hurt. Design stuff? Fine. It was the boring plumbing that was broken - the exact stuff I never test because I only ever click the happy path.
What I learned
The things that sink a portfolio are almost never the design. They're the dead link, the form that eats a message, the page that takes 4 seconds. Unglamorous, invisible, and fatal. I'd rather a robot find them on a Tuesday than a recruiter find them mid-decision.
The skill behind this is open source. Clone the 1 folder you need from bunlongheng/audits, point it at your own work, and point it at your own site before a hiring manager does.