Landing Page Audit · September 03, 2026

mxrquane.github.io/portfolio/

54/100

Coming together

Better than 39% of sites we have audited

50–59 · More working than not — Much of what we measure is holding up. What's left tends to be a handful of things rather than everything.

0 50 100

163 sites audited. Median 57, and the top 10% start at 72. Most land in the 50s.

"You have a genuinely strong technical story and a confident voice — nail the social proof gap and sharpen that CTA and this portfolio could be a real client-acquisition machine."

Share: X LinkedIn Facebook

Export:

Scores and fixes by category

Weakest categories are open. The score and its reasoning are the AI's reading; the fixes underneath come from checks we ran against your page.

› Value Prop 20% of score 62

'I build software that actually ships' with a clear specialisation list (web, desktop, backend, AI) communicates the offer quickly, but there is no stated benefit for the client or indication of who the ideal client is.

› Trust 20% of score 2 fixes 12

Zero testimonials, zero client logos, zero third-party review scores — the social proof score is at the bottom of the ladder; the work section shows project names but no outcomes or client voices.

Customer testimonials with real names

Generic "trusted by" claims aren't trust — named testimonials with real attribution are. Anonymous quotes read as marketing copy.

Do this: Add at least one testimonial with real attribution (full name plus role or company). A single specific, outcome-focused quote outperforms a grid of generic ones.

Industry benchmark: +34% conversions — Nielsen

A missing privacy link is a trust signal in the wrong direction, and it blocks you outright in regulated markets and on app stores.

Do this: Link a privacy policy from the footer. If you collect anything at all, this is table stakes rather than an optional extra.

› Design / UX 13% of score 74

All automated UX checks passed, the page is mobile-friendly, and load time is an excellent 393ms — the visual hierarchy appears clean even if the content density at the contact section is cluttered.

› Copy 12% of score 68

The about section is honest, specific, and human — 'not a demo, a shipped product' is a strong line — but the services descriptions lean feature-heavy rather than outcome-focused for the client.

› CTA 15% of score 42

The 'get in touch' CTA is present and reachable but offers no outcome, no friction-reducer, and competes with five other contact links dumped on the same section with no visual hierarchy.

› Technical 10% of score 3 fixes 38

Page load is an excellent 393ms and accessibility scores 97/100, but missing meta description, Open Graph tags, robots.txt, and sitemap — plus a CSR SPA approach that leaves social crawlers with a blank shell — pull the technical score down meaningfully.

robots.txt present and valid

Without robots.txt, search engines use default crawl behavior — and you lose the ability to point them at your sitemap.

Do this: Add /robots.txt with `User-agent: *` `Allow: /` and a `Sitemap:` line pointing to your sitemap.xml.

Industry benchmark: enables indexing crawl discovery — Google

sitemap.xml present

A sitemap helps search engines find every page worth indexing. Without one, new pages can take weeks to surface in search.

Do this: Generate /sitemap.xml, submit it in Google Search Console, and reference it in robots.txt.

Industry benchmark: +20–50% indexed pages — Google

Meta description 120-160 chars

A weak meta description hurts your organic CTR — it's the pitch Google shows under your search result.

Do this: Write a 120–160 character meta description with a concrete outcome and a soft call to action.

Industry benchmark: +5.8% organic CTR — Backlinko

› Differentiation 5% of score 55

The combination of AI/ML + full-stack + desktop app coverage, plus being mid-Master's in AI Engineering, is genuinely distinctive — but it is buried in the about section rather than leading the page.

› Emotional 5% of score 65

The about section lands emotionally — 'I work best with clear scope, honest timelines, and regular check-ins — not silence until a big reveal' is exactly what anxious clients want to hear, and it feels real.

Technical Analysis

Core Web Vitals

Mobile Vitals

Not analyzed.

Desktop Vitals

Not analyzed.

Technical SEO Files

These files tell search engines and AI crawlers how to read your site. Missing ones mean less organic traffic.

robots.txt Missing

robots.txt not found (HTTP 404) - search engines can't see your crawl preferences

sitemap.xml Missing

No sitemap.xml found - search engines may miss pages

llms.txt Missing

No llms.txt found - consider adding one to guide AI crawlers (emerging best practice)

security.txt Missing

No security.txt found - good practice to help security researchers

Accessibility (WCAG 2.1 static audit)

How usable your page is for visitors with disabilities (~15% of users). Low score = lost customers and legal exposure.

0 critical · 0 major · 1 minor

16/17 checks passed

skip-nav minor

No skip navigation link found. Keyboard users must tab through all nav links to reach content.

2.4.1

Tech Stack Measured

Detected stack Measured

What your site is built with. Matters because your CMS/framework/hosting choice caps how fast you can fix things and what optimizations are even possible.

Hosting / CDN

GitHub Pages high

Page Structure

Hero: Good
Headline: Excellent
Subheadline: Good
CTA: Weak
Social Proof: Missing
Features: Good
Pricing: Missing
FAQ: Missing
Footer: Weak

What Works

Headline punches with personality — 'I build software that actually ships' immediately differentiates from generic 'full-stack developer' portfolios and sets a confident tone that resonates with frustrated clients who've had unreliable contractors.
The about section is a masterclass in freelancer positioning: it names your actual working style ('clear scope, honest timelines, regular check-ins'), references your own shipped product (Zirox) as a proof point, and grounds the AI work in a real academic credential — all in plain English.
Page performance is genuinely excellent: 393ms load time and 97/100 accessibility score are better than most professional agency sites, and full mobile friendliness means clients on their phones get the same experience.
The service breadth (custom desktop, full-stack web, backend/API, AI/ML integration) is specific and well-scoped — you tell clients not just what you do but what you don't do ('not building research models'), which builds trust through honesty.

What Doesn't

Critical

Zero testimonials, zero client logos, zero reviews — the trust score is a flat zero. A prospective client landing here has no way to verify that 'software that actually ships' has actually shipped for anyone other than yourself.

Fix: Add a dedicated social proof section with 2-3 client testimonials (name + project context), or at minimum a 'Projects delivered' counter you can substantiate. Even a short quote from a beta tester of Zirox would help. No social proof at all makes a freelancer look unproven.
Major

The CTA 'get in touch' is the email equivalent of 'I dunno, call us'. It signals no clear next step, no outcome, and no reason to act now rather than later. It also competes with five other contact vectors (email, Telegram, GitHub, LinkedIn, Instagram) all dumped on the contact section at once.

Fix: Replace 'get in touch' with something like 'Tell me about your project' or 'Start a conversation'. Pair it with a one-line risk-reducer nearby: 'Free 30-min scope call — no commitment'. This answers the question every hesitant client has: what happens when I click this?
Major

No meta description, no Open Graph tags — when a potential client shares your URL in Slack or LinkedIn, the preview is a blank card titled 'portfolio'. That is not the first impression a freelancer wants to make.

Fix: Write a 120-160 character meta description that summarises your speciality and target client. Add Open Graph tags (og:title, og:description, og:image) so LinkedIn and Twitter previews show something compelling when a client shares your portfolio URL. Because this is a React CSR app on GitHub Pages, consider adding a static index.html shell with those meta tags pre-rendered, or migrate to a simple SSG approach (e.g. Vite + pre-render plugin) so social crawlers see real content.
Major

The site lives at mxrquane.github.io/portfolio — a github.io subdomain is a prototype URL, not a commercial identity. It quietly undermines every claim of being production-ready.

Fix: Point a custom domain (e.g. marouanehaine.dev) at this GitHub Pages site — it takes 20 minutes and costs ~$12/year. A github.io URL signals 'personal experiment' rather than 'professional I would hire for my business'.
Minor

Missing robots.txt and sitemap.xml mean Google has to guess at your crawl structure. Not catastrophic for a portfolio, but a freelancer who bills themselves as a backend engineer should have these basics covered — it's a credibility signal.

Fix: Add a robots.txt (allow all) and a sitemap.xml listing your main sections. Both are two-file additions that GitHub Pages serves statically. This helps Google index your portfolio so potential clients can find you organically.
Minor

'Cystom Desktop Applications' — your very first service bullet has a typo. Clients hiring for precision software work notice these things immediately.

Fix: Fix the typo 'Cystom Desktop Applications' → 'Custom Desktop Applications' in the services section. A single typo in a list of services is disproportionately damaging for a detail-oriented engineer.