Back
Scan complete

shevadzikra.vercel.app

1 page · 0.2s · Scanned just now

0/ 100
AI automation score

Mostly human-written

42% confidence

How to read this score
0–35 · Mostly human35–65 · Mixed signals65–100 · Mostly AI

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.

What we scanned
Page title
Shevadzikra | Junior Frontend Developer
Meta description
Generated by create next app
Language
en
Built with
Next.js
What we saw

The page is extremely thin at 72 words, making confident scoring difficult. What text exists contains real proper nouns — a personal name ("SHEVADZIKRA"), real client names ("PT Kharisma Trans Jember", "Tanjung Papuma"), and a genuine regional anchor ("based in Indonesia") — all strong human signals. The only AI signal is the default Next.js meta description ("Generated by create next app"), which is a scaffolding leftover rather than AI-authored content. Confidence is low due to the very sparse word count.

Top findings
  • Clear signalStructure

    Default Next.js meta description left in place — signals the page was never fully configured after scaffolding

    Evidence
    • Generated by create next appmeta
    Try this

    Replace the default meta description with a 1–2 sentence summary of who you are and what you do.

  • Worth notingContent

    Word count is only 72 words — too thin to establish a strong personal voice or rank for anything

    Evidence
    • A passionate tech enthusiast based in Indonesia. I love crafting smooth, visually appealing websites while exploring how AI can push the bounds of innovation.body
    Try this

    Expand each project entry with 2–3 sentences describing your specific contribution, the tech used, and the outcome.

  • Worth notingStructure

    No H1 present on the page — the hero name and title are not marked up as a primary heading

    Evidence
    • SHEVADZIKRAbody
    • Junior Frontend Developerbody
    Try this

    Wrap your name or role in an H1 tag to establish a clear document hierarchy.

What's working

Signals of human authorship the page is doing well.

  • Content

    Real client and project names (Tanjung Papuma, PT Kharisma Trans Jember) confirm hand-written, experience-specific copy.

  • Imagery

    All 23 images have alt text — suggests a human reviewed and described each image intentionally.

SEO auditFair
71/100
AI breakdown by category
  • Content28

    Real name, real location (Indonesia), real project names (Tanjung Papuma, PT Kharisma Trans Jember) — specific and personal, not LLM-generated filler

  • Structure45

    Next.js scaffold with default meta ("Generated by create next app"), standard portfolio sections (hero, skills, projects, certs, CTA, footer) but minimal templating

  • Imagery30

    23 images all with alt text present; no stock-photo or AI-generation signals evident from filenames or descriptions

  • Tone20

    Brief, personal intro with genuine regional identity ("based in Indonesia") and first-person voice — short but not generic LLM marketing-speak

By the numbers
  • Words72
  • Images23
  • Alt coverage100%
  • Internal links0
  • External links9
  • Schema blocks0
  • HTML size33 KB
SEO audit detail
  • Meta tags
    Missing canonical
    Why 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 structure
    No H1
    Why 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 readiness
    Responsive
    Why 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 signals
    0.2s · 33 KB
    Why 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 markup
    No JSON-LD
    Why 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 links
    No internal links
    Why 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 text
    All have alt
    Why 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.

Heading outline

Every H1, H2, and H3 we found on the page, in document order.

Show heading outline
  1. H2Direct Links
  2. H2Follow Me

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.