leafbrazil

Leaf Software - A software house to build a future.

Next.jsVercel

Report generated on April 5, 2026

leafsoftware.vercel.app
Screenshot of leafsoftware.vercel.app

A note on how to read this

This report is ProdPoke's take on your site — think of it as a first impression from a very opinionated robot. We check real things (load times, broken links, accessibility patterns), but we also try to understand what your site is trying to do and whether the technical details support that goal. Some of our observations might not apply to your specific situation, and that's okay. We're getting sharper with every scan. If something feels off, tell us — it makes us better.

First Impression — How clear is your site?

45
Takes a moment

Leaf Software is "A TECHNOLOGY COMPANY" that appears to provide software development or technology solutions. The page shows "Our Services" section heading and includes action buttons for "Get Started" and "Watch Demo," suggesting it offers services that visitors can learn about or begin using. The specific nature of these services is not detailed on the visible portion of the homepage.

This score measures how quickly a first-time visitor understands what your site does — based on visible headings, navigation, and visual hierarchy alone.

86/ 100

Overall Score

Strong foundation.

Performance

92/100

Large asset: 2323KB — https://leafsoftware.vercel.app/wallpaper.png

medium

Resource is 2323KB (css). Consider compressing or lazy-loading. Took 417ms to load.

Expected: Assets under 500KB
Found: 2323KB

SEO

86/100

Multiple H1 tags (9)

medium

Best practice is one H1 per page. Multiple H1s dilute the page's primary topic signal.

Expected: 1 H1 tag
Found: 9 H1 tags

No robots.txt found

low

robots.txt tells search engines how to crawl your site.

No sitemap.xml found

low

A sitemap helps search engines discover and index all pages on your site.

Accessibility

70/100

9 interactive element(s) without accessible names

high

These elements have no text content, aria-label, aria-labelledby, or title attribute. Screen reader users cannot understand what they do.

Expected: All interactive elements have accessible names
Found: 9 missing: <a>, <input[type=text]>, <input[type=email]>, <input[type=text]>, <textarea[type=textarea]>

4 form input(s) without labels

high

Form inputs without associated labels are difficult for screen reader users and reduce form usability for everyone.

Expected: Every input has a <label> or aria-label
Found: Missing labels: text: Name, email: Email, text: Subject, textarea: Message

Functional

100/100
All clear — no issues found in this category.

Technical Health

Minified React error #418; visit https://react.dev/errors/418?args[]=text&arg...

high

[exception] Minified React error #418; visit https://react.dev/errors/418?args[]=text&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Compliance

84/100

No privacy policy link found

medium

Your site doesn't have a privacy policy link found on this page. This is required by GDPR and most privacy laws when collecting user data.

No cookie consent mechanism detected

medium

Your site doesn't have a cookie consent banner or dialog was detected. If this site uses cookies (including analytics or session cookies), a consent mechanism is required under GDPR for EU visitors.

Key Metrics

Crawlability

Sitemap.xml
Robots.txt
Broken Links0

Standards

HTTPS
Mobile Responsive
Images Missing Alt0

How to Improve

Minified React error #418; visit https://react.dev/errors/418?args[]=text&arg...

[exception] Minified React error #418; visit https://react.dev/errors/418?args[]=text&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

9 interactive element(s) without accessible names

These elements have no text content, aria-label, aria-labelledby, or title attribute. Screen reader users cannot understand what they do.

4 form input(s) without labels

Form inputs without associated labels are difficult for screen reader users and reduce form usability for everyone.

Fix: Multiple H1 tags (9)

Every page should have exactly one H1 heading that clearly describes its main topic. This helps both search engines and users understand your content hierarchy.

Large asset: 2323KB — https://leafsoftware.vercel.app/wallpaper.png

Optimizing asset sizes and reducing render-blocking resources will give your visitors a snappier experience.

This is your site? Get the full picture.

Claim this report to unlock ongoing monitoring, deeper analysis, and actionable alerts.

What is ProdPoke?

Automated analysis generated on April 5, 2026. Not professional advice. Contact us to modify or remove this report.