Overall Score
This is a sleek, technically-competent AI/ML portfolio with a dark theme and solid visual hierarchy, but it's undermined by questionable UX choices, accessibility issues, and a conversion strategy that feels more like a tech demo than a job-hunting vehicle.
The Roast
Mrudula's built herself a portfolio that looks like it belongs in a sci-fi movie—all neon borders and dark mystery—but forgets that recruiters aren't impressed by aesthetics alone; they're terrified of forms with missing labels and links that don't go anywhere. The site screams 'I can build complex ML systems' but whispers 'I might not have tested this on actual humans.' It's technically sharp but user-experience-dull, like a Tesla with no steering wheel—impressive engineering, questionable usability.
🎯 Start Here
Accessibility
Conversion
Trust Signals
SEO
Performance
Design & UX
Mobile
Copy & Messaging
Accessibility
The site has basic ARIA landmarks (nav, main, footer) and all images have alt text, but it's crippled by a missing form label, no skip link, and likely poor color contrast between cyan text and dark backgrounds—a recipe for excluding screen reader users and low-vision visitors.
Issues Found
- 1 form input (likely the Contact section) is missing an associated <label> element, breaking form accessibility for screen readers
- No skip-to-main-content link visible or mentioned, forcing keyboard users to tab through navigation every time they visit
- Cyan (#00D4FF or similar) text on dark navy backgrounds likely fails WCAG AA contrast ratio (should be 4.5:1 for normal text)—suspect it's closer to 3:1
Recommendations
-
Add labels to all form inputs high
Wrap or associate every input field (email, message, etc.) with a <label> element using 'for' or 'aria-labelledby' to ensure screen readers announce field purpose.
-
Add a visible skip-to-main-content link high
Insert an anchor link at the very top (hidden until focused) that jumps to the main content, allowing keyboard users to bypass navigation.
-
Audit and fix color contrast ratios high
Test all text color combinations with a tool like WebAIM Contrast Checker; ensure cyan and light text on dark backgrounds meet WCAG AA (4.5:1) or AAA (7:1) standards.
Conversion
The site has multiple CTAs ('View Architecture', 'Open to AI/ML Roles', 'View GitHub Profile'), but they're scattered, lack context, and don't form a coherent conversion funnel—it's unclear whether the goal is hiring, networking, or showcasing projects.
Issues Found
- No primary CTA hierarchy: buttons for 'View Architecture', 'GitHub', 'LinkedIn', and 'View GitHub Profile' compete for attention without guiding toward a specific action (e.g., 'Hire Me', 'Email Me')
- Contact information is not visible in the screenshots; no clear path to reach out (email, contact form location is unknown)
- 'Open to AI/ML Roles' is a statement, not a CTA—recruiters don't know what to do with it besides... assume they should apply?
Recommendations
-
Define a single primary conversion goal high
Decide if the portfolio is for hiring (make 'Hire Me' or 'Book a Call' the hero CTA), networking (prioritize LinkedIn), or showcasing (lead with 'View My Work'). Remove competing buttons.
-
Make contact information prominent and accessible high
Add an email link or contact form in the header or hero section with copy like 'mrudula@example.com' or 'Get in Touch' button that appears on every page.
-
Create a structured project-to-conversation flow medium
After each case study, add a 'Learn More' or 'Let's Discuss This Project' CTA that links to a contact form or calendar tool, turning portfolio items into lead magnets.
Trust Signals
The portfolio leans heavily on GitHub proof (8 repos, 1 follower) and project case studies, which is good, but lacks human trust signals like testimonials, endorsements, certifications, or time-in-role details that would reassure recruiters she's not a fly-by-night contractor.
Issues Found
- GitHub stats are weak: only 1 follower and 8 public repos; no indication of stars, forks, or community engagement—recruiters might assume low visibility
- No testimonials, LinkedIn endorsements, or quotes from colleagues/managers; case studies lack client names or outcome metrics (e.g., 'improved defect detection by 40%')
- Internship date is oddly future-dated ('Apr 2026 – Jul 2026'), which is confusing and undermines credibility—is this fictional, planned, or a typo?
Recommendations
-
Add quantifiable project outcomes and metrics high
Replace vague descriptions with measurable results: 'Reduced defect detection time by 60%', 'Deployed to 500+ devices', 'Achieved 95.2% mAP on custom dataset'.
-
Fix the internship date and add company/team context high
Clarify the RAMS Digital internship timeline (is it past, future, or current?); include manager name, team size, and specific responsibilities to add authority.
-
Add a testimonials or endorsements section medium
Include 2-3 quotes from professors, managers, or colleagues vouching for her technical skills and work ethic; link to LinkedIn recommendations.
SEO
Meta tags are present and descriptive, but the page lacks schema markup, has thin heading hierarchy (1 H1, 5 H2s, 14 H3s), and misses structured data that would help search engines understand project details, skills, and contact information.
Issues Found
- No JSON-LD schema markup for Person, Organization, or CreativeWork—search engines can't parse skills, projects, or contact info programmatically
- Heading hierarchy is inverted: 14 H3s without clear H2 sections muddy content structure and confuse search crawlers
- URL structure is poor: `/Mrudula.dev-portfolio/` is not SEO-friendly; no semantic URLs for individual projects or sections
Recommendations
-
Add Person and Project schema markup high
Implement JSON-LD for Person (name, skills, contact), Project (title, description, tech stack), and link to GitHub repositories for rich snippet eligibility.
-
Restructure headings to reflect logical hierarchy medium
Use H2 for main sections (About, Work, Skills, Contact) and H3 only for subsections; ensure one H1 per page (already done) but validate H2/H3 nesting.
-
Create a more SEO-friendly URL structure medium
Move from GitHub Pages subdirectory to a custom domain with clean URLs like `/about`, `/projects`, `/contact` for better crawlability and brand authority.
Performance
The page is 6441px tall with only 1 image and minimal external dependencies, suggesting it should load fast, but the lack of performance metrics in the data and heavy DOM nodes (14 H3s, multiple nested cards) suggest potential runtime bottlenecks.
Issues Found
- No perceived performance optimization visible: no lazy loading indicators, no above-the-fold image optimization, no async script loading mentioned
- Large page height (6441px) with card-based layout may cause layout thrashing and slow scroll performance on older devices
- External links (11 internal, 8 external) suggest multiple API calls or third-party embeds (e.g., GitHub stats, LinkedIn) that could block rendering
Recommendations
-
Implement lazy loading for below-the-fold content medium
Use Intersection Observer API to defer rendering of case study cards and skill sections until they're near the viewport.
-
Optimize the hero image and compress assets high
Serve the avatar image in WebP format with responsive sizing (srcset) and compress all PNG/JPG assets to reduce initial load time.
-
Defer non-critical third-party scripts (GitHub, LinkedIn) medium
Load social proof widgets asynchronously after the main content renders to prevent blocking initial paint.
Design & UX
The dark theme with cyan accents is visually striking and on-brand for tech, but the design prioritizes aesthetic polish over intuitive navigation—cards, sections, and CTAs are scattered without clear visual hierarchy or logical flow.
Issues Found
- Inconsistent spacing and alignment: the 'HOW I ENGINEER AI' section cards are oddly cramped on desktop, while case study cards feel overstuffed with text and stats
- No clear visual distinction between interactive elements and static content—buttons, links, and section headings blend together
- Whitespace is underutilized; the page feels dense and compressed despite a 6441px total height
Recommendations
-
Establish a consistent spatial grid high
Use a 16px or 24px baseline grid for all margins, padding, and gaps to improve alignment and visual rhythm across sections.
-
Differentiate interactive elements visually high
Add clear focus states, hover effects, and a distinct button style hierarchy (primary CTAs in cyan, secondary in outlines) to guide user attention.
-
Reduce cognitive load with progressive disclosure medium
Collapse case study details into expandable cards or separate project pages to de-clutter the hero and below-the-fold sections.
Mobile
Mobile layout is responsive and readable (text reflows, navigation collapses to hamburger), but touch targets appear small, card layouts stack awkwardly, and interactive elements lack sufficient padding for thumb-friendly interaction.
Issues Found
- Button sizing: 'View Architecture', GitHub, and LinkedIn buttons appear cramped with minimal padding; likely fail the 44x44px touch target minimum
- Card layouts on mobile: case study cards stack vertically with dense text blocks that are hard to scan; hero card with portrait sits above content rather than beside
- Hamburger menu is present but no indication of menu state (open/closed) or animation feedback visible in mobile screenshots
Recommendations
-
Increase touch target sizes to 48x48px minimum high
Add padding to all buttons and interactive elements so mobile users can tap without precision; test with thumbs, not a pointer.
-
Redesign mobile card layouts for scannability medium
Reduce text density on mobile by truncating case study previews, hiding secondary details behind 'Read More' links, or using collapsible sections.
-
Add visual feedback for hamburger menu state medium
Animate the hamburger icon (e.g., X rotation) when menu opens, highlight active menu item, and ensure menu closes on navigation.
Copy & Messaging
The value proposition is technically clear—'AI/ML Engineer specializing in Computer Vision'—but the messaging lacks emotional resonance or hiring urgency; it reads like a LinkedIn headline extended to paragraphs rather than a persuasive pitch.
Issues Found
- Opening headline 'AI/ML Engineer' is generic and doesn't differentiate her from thousands of other profiles; no unique angle or memorable phrase
- The tagline 'Specializing in Computer Vision, Uncertainty Estimation, and Production ML Pipelines' is jargon-heavy and skips why a recruiter should care
- Call-to-action copy ('View Architecture', 'Open to AI/ML Roles') is passive and doesn't create urgency or excitement
Recommendations
-
Lead with a problem she solves, not a title high
Replace 'AI/ML Engineer' with something like 'I ship production CV systems that work in the real world—not just on Kaggle' to create immediate differentiation.
-
Simplify technical jargon in the intro medium
Translate 'uncertainty estimation and production ML pipelines' into human language: 'I build AI systems you can trust to work when it matters.'
-
Use action-oriented CTA language medium
Change 'View Architecture' to 'See How I Built This' and 'Open to AI/ML Roles' to 'Hire Me' or 'Let's Talk' to increase conversion intent.
Think you can beat 64/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.