portfolionew-sooty-eight.vercel.app
1 page · 0.2s ·
Mixed signals
15% 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.
The crawl returned zero words, headings, images and links. The only content is the title "Vijit Vishnoi" on a Vercel-hosted portfolio, which is too little to judge authorship, so the score is a low-confidence guess.
No governance risks detected
- Page title
- Vijit Vishnoi
- Meta description
- —
- Canonical URL
- —
- Robots directive
- Not set — search engines default to index, follow
- Language
- en
How the page presents itself in a Google result and as a shared link, rebuilt from the tags we crawled.
Vijit Vishnoi
- Title · 13 characters
- No meta description — Google will pull an arbitrary snippet instead
Vijit Vishnoi
- No og:image — shared links render as bare text with no picture
- No Open Graph title — the share card falls back to the page title
- Worth notingStructure
The crawl returned no content, probably because the page is client-rendered, so authorship can't be judged.
Evidence- “Vijit Vishnoi”meta
Try thisServer-render or pre-render the page so crawlers can read your headings and text.
- Content0
No body text was captured, so there is no prose to evaluate
- Structure45
Empty crawl with no headings or links, likely a client-rendered Vercel app; layout cannot be judged
- Imagery0
No images were found in the crawl
- Tone0
No text was captured, so voice cannot be assessed
- Words0
- Images0
- Alt coverage100%
- Images without size0
- Internal links0
- External links0
- Schema blocks0
- HTML size1 KB
- Text-to-HTML0%
- Meta tagsMissing 2 tagsWhy 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 title, a meta description and a canonical link are all present, with exactly one description tag, placed where Google reads it. Their lengths are shown in the report's search preview.
Fix. Add the missing tags inside the page head and delete any second description tag. Keep images and iframes below your meta tags, because Google stops reading the head at the first one. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.
- Heading structureNo H1Why 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. A missing H1, or several, blurs what the page is about.
Passing looks like. Exactly one H1, and at least one H2.
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 the mobile version of a page. Without a responsive viewport, phones render the page zoomed out, which makes it hard to read and use.
Passing looks like. A viewport meta tag set to width=device-width. The scan reads the HTML and doesn't render the page, so it can't check touch targets or font sizes.
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.2s · 0 KBWhy this matters
Why it matters. Response time, page weight and images that load without a reserved size all show up in Core Web Vitals. Slow pages, and layouts that jump as images arrive, cost visitors and rankings.
Passing looks like. The HTML arrives in under 1.5 s and weighs under 500 KB, the page has fewer than 30 images, and no more than two images lack width and height. These are signals from one HTML fetch, not a PageSpeed Insights measurement.
Fix. Speed up the server response and trim the HTML. Give every image width and height attributes, or a CSS aspect-ratio, so the layout doesn't jump, and serve compressed images sized to the viewport.
- 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 JSON-LD block is present. The check doesn't validate the block or its types, so test it with Google's Rich Results Test too.
Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.
- Broken linksNo internal linksWhy 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 loads successfully, after following redirects. Timeouts and network errors count as broken.
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 textNo imagesWhy 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. Nearly every image has non-empty alt text. An empty alt="" counts as missing here, even on a decorative image.
Fix. Audit images in /assets and CMS uploads. Write alts that describe what's in the image, not what it links to.
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.