I will do website QA testing with a bug and usability report
About this Gig
Is your website losing customers to bugs you can't see?
I'm a QA engineer with 3+ years in fintech, including work for banking and fintech clients in the DACH region, where bugs are expensive and standards are high. I bring that same standard to your website.
A broken button is easy to spot. A confusing checkout isn't. I test every page across all major browsers for what's broken, and I personally review what's simply frustrating for real users. You get both.
You'll receive a detailed PDF report with:
- Functional bugs: what's broken and where
- UI/UX and usability issues: what's confusing or frustrating
- Annotated screenshots and screen recordings
- Clear reproduction steps your developers can follow
Tested on Chrome, Firefox and Safari, on desktop and mobile
Ready to make your site rock-solid? Pick a package above, or message me first if you're unsure which one fits.
Testing application:
Website
Development technology:
HTML & CSS
•
Java
•
SQL
Device:
PC
•
Mac
FAQ
What's your background?
Im Jakub, QA Engineer with 3 years of professional experience. I come from fintech, an industry that's ruthless about bugs. Years of that make you spot the things most people walk right past. Now I do the same for websites and web apps.
Do you test on my live site?
I test like a regular visitor, so there's nothing heavy hitting your server or disrupting your users. If some pages are behind a login, a test account with proper permissions is all I need to get started.
Do you test mobile apps?
This gig is desktop web testing. If you mean how your site looks on a phone, that's covered under responsiveness. If you mean a native mobile app, message me first, that's a different setup.
What exactly do I get?
More than a bug list. You get a readable PDF: what's wrong, why it matters, how to reproduce it, and what I'd tackle first. Made so your devs can act on it, not decode it.
Does the Fix-Priority Roadmap mean you fix the bugs?
No, fixing is your team's job. What I give you is the priority: which bugs actually hurt, which can wait, and where to start. That's often the hardest part to figure out, and it's what saves you time.
Can you test regularly, not just once?
Definitely. If you ship often, a regular check each release keeps things clean and saves you the big pre-launch issues. Message me and we'll find a rhythm that works.
Where are you based? / What time zone are you in?
I'm based in Central Europe (CET). That means I overlap with both US and European working hours, so you'll usually get a quick reply during your day.
How many bugs will you find?
Depends entirely on your site, a clean one might have a handful, a rough one dozens. I don't chase numbers to look busy. I find what actually matters and report every real issue I hit.

