ilyasmohaimel.github.io
1 page · 0.1s · Scanned just now
Mostly human-written
72% confidence
The score is a fingerprint of automation, not a quality judgment. A high score means the page reads as machine-generated. It doesn't mean the page is bad.
- Page title
- Ilyas Mohaimel | Frost
- Meta description
- Premium editorial portfolio for Ilyas Mohaimel, also known as Frost: systems builder, troubleshooter, Linux user, self-hosting tinkerer, and practical AI workflow builder.
- Final URL
- https://ilyasmohaimel.github.io/
- Language
- en

This is a personal portfolio with strong human authorship signals. The content contains specific technical credentials, named locations, and a distinctive voice with self-aware humor and idiosyncratic phrasing ("weird little details most people ignore", "clear enough to understand, reliable enough to trust, and personal enough to feel worth using"). The structure is intentionally asymmetric—H2s are mixed narrative and sectional, breaking the template boilerplate pattern typical of AI page builders. The single image and minimal visual treatment suggest human oversight rather than AI-generated placeholder filling.
- Worth notingStructure
Typography error in H2 'LET'S BUILDSOMETHING USEFUL' lacks space before 'SOMETHING'
Evidence- “LET'S BUILDSOMETHING USEFULTOGETHER”H2
Try thisAdd space: 'LET'S BUILD SOMETHING USEFUL' to improve readability and professionalism
- Clear signalImagery
Portfolio contains only 1 image despite claiming 'Premium editorial portfolio' and 'Digital Creator' role
Evidence- “Premium editorial portfolio for Ilyas Mohaimel”meta
- “DIGITAL CREATOR”body
Try thisAdd project screenshots, process images, or custom illustrations to demonstrate visual work and editorial quality
Signals of human authorship the page is doing well.
- Tone
Distinctive first-person voice with self-aware humor and grounded perspective ('the kind of debugging that happens when a system becomes part of daily life')
- Content
Specific credentials and technical depth (6+ years Linux, DET 120, CS degree path 2026) ground the portfolio in real achievements
- Content28
Strong personal voice, specific technical details (Duolingo 120, DET score), and self-directed anecdotes override occasional generic phrases
- Structure22
Asymmetric layout with irregular section ordering (H2s interrupted by narrative H2s like "Curiosity is the constant"), numbered work process, non-boilerplate spacing
- Imagery35
Only 1 image on entire portfolio (uncommon for a visual designer's site), no alt missing but underutilization suggests human neglect rather than AI generation
- Tone18
Distinct first-person voice with self-deprecating humor ("the kind of debugging that happens when a system becomes part of daily life"), regional anchoring (Casablanca), and informal register
- Words700
- Images1
- Alt coverage100%
- Internal links9
- External links3
- Schema blocks0
- HTML size26 KB
- Meta tagsAll presentWhy this matters
Why it matters. Title and description are the two strings Google shows in search results. They decide whether anyone clicks. A canonical tag tells Google which URL is the source of truth when the same content lives at multiple paths.
Passing looks like. A non-empty title under 60 characters, a meta description under 160, and a self-referencing canonical link.
Fix. Add the missing tags inside the page head. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.
- Heading structure1 H1, 8 H2Why this matters
Why it matters. Headings are how crawlers and assistive tech understand a page's outline. One H1 names the page. H2s break it into sections. Skipped levels and missing H1s confuse both.
Passing looks like. Exactly one H1, at least one H2, and no skipped levels (no H1 to H3 jumps).
Fix. Replace the missing or duplicate H1 with a single, descriptive heading. Promote section titles to H2. Demote sub-points to H3.
- Mobile readinessResponsiveWhy this matters
Why it matters. Google indexes mobile-first. A page without a responsive viewport renders zoomed-out on phones, fails Core Web Vitals on touch, and loses its mobile ranking.
Passing looks like. A meta viewport tag with width=device-width and a layout that reflows under 600px.
Fix. Add a viewport meta tag set to width=device-width and initial-scale=1, then audit your largest blocks at mobile widths.
- Page speed signals0.1s · 26 KBWhy this matters
Why it matters. Page weight and response time directly feed Core Web Vitals. Slow LCP and oversized HTML hurt rankings more than people expect.
Passing looks like. First-byte under 1.5s, HTML payload under 500 KB, fewer than 30 images on the initial render.
Fix. Trim render-blocking scripts, defer non-critical CSS, and serve compressed images sized to the viewport. Move heavy components below the fold.
- Schema markupNo JSON-LDWhy this matters
Why it matters. JSON-LD structured data is how you earn rich results: review stars, FAQ accordions, breadcrumbs, article cards. Skip it and Google has nothing structured to pull from when it builds your SERP card.
Passing looks like. At least one valid JSON-LD block matching schema.org types relevant to the page (Article, Product, FAQPage, Organization).
Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.
- Broken links0/1 broken in sampleWhy this matters
Why it matters. Broken internal links waste crawl budget, degrade UX, and signal to Google that the site isn't well-maintained. They also cap how deep crawlers reach.
Passing looks like. Every internal link in the sample returns 2xx or 3xx. No dead anchors, no stale paths.
Fix. Use the link list above to spot the broken paths. Either restore the missing pages or update the links to point at live URLs.
- Image alt textAll have altWhy this matters
Why it matters. Alt text is what screen readers read aloud, and what Google reads instead of pixels. Skip it and you lose on both fronts.
Passing looks like. Every meaningful image has a descriptive alt attribute. Decorative images can use alt="" to be skipped intentionally.
Fix. Audit images in /assets and CMS uploads. Write alts that describe what's in the image, not what it links to.
Every H1, H2, and H3 we found on the page, in document order.
Show heading outline
- H1ILYASMOHAIMEL
- H2SELECTED WORK
- H2EDUCATION & SKILLS
- H2WORK PROCESS
- H2Curiosity is the constant.
- H2CURRENT FOCUS
- H2EXPERIENCE & TECHNICAL AREAS
- H2Outdoors keeps my thinking sharp.
- H2LET'S BUILDSOMETHING USEFUL
- H3AUTOMATED MORNING BRIEF
- H3FROSTSERVER
- H3AI AUTOMATION STACK
- H3EDUCATION
- H3SKILLS
- H3DISCOVER
- H3TEST
- H3BUILD
- H3DEBUG
- H3IMPROVE
- H3AI workflows that are actually useful
- H3Prepping for a CS degree
- H3Self-hosting and system tuning
- H3Deeper software/systems direction
- H3Linux & Desktop Environments
- H3Self-hosting & Homelab
- H3AI Automation & Agents
- H3Troubleshooting Mindset
- H3Cybersecurity & Programming
- H3Study Tools & Web Building
We HEAD-check up to five internal links to spot broken paths quickly.
Show sampled links
Was this report useful?
Share this scan
Every CrawlRanker scan gets a public, shareable URL. Send it to a client, post it in a thread, or benchmark a competitor.
Preview scan. SEO checks are live. AI scoring is in beta.