Automated Report

ainave.com

Generated on October 6, 2025 · Domain: ainave.com

Instant Audit

See your site the way search engines feel it

Launch a free crawl in under 30 seconds and get a ranked hit-list of fixes that lift speed, visibility, and trust.

Start Free Analysis
2025/10/06
84

Overall Score

91

PageSpeed

89

Website Quality

72

Trust & Security

68

Performance

100

SEO

100

Best Practices

92

Accessibility

Performance
68/100
Largest Contentful Paint
6/25
5.2s
2.5s4.0s
First Contentful Paint
6/10
2.8s
1.8s3.0s
Total Blocking Time
23/30
335ms
200ms400ms
Cumulative Layout Shift
25/25
0.01
0.100.25
Speed Index
9/10
3.1s
3.4s5.4s
SEO
100/100
Page isn’t blocked from indexing
31/31
Document has a `<title>` element
8/8
Document has a meta description
8/8
Page has successful HTTP status code
8/8
Links have descriptive text
8/8
Links are crawlable
8/8
robots.txt is valid
8/8
Image elements have `[alt]` attributes
8/8
Document has a valid `hreflang`
8/8
Document has a valid `rel=canonical`
8/8
Best Practices
100/100
Uses HTTPS
18/18
Avoids deprecated APIs
18/18
Avoids third-party cookies
18/18
Allows users to paste into input fields
11/11
Avoids requesting the geolocation permission on page load
4/4
Avoids requesting the notification permission on page load
4/4
Displays images with correct aspect ratio
4/4
Serves images with appropriate resolution
4/4
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
4/4
Document uses legible font sizes
4/4
Page has the HTML doctype
4/4
Properly defines charset
4/4
No browser errors logged to the console
4/4
No issues in the `Issues` panel in Chrome Devtools
4/4
Accessibility
92/100
`[aria-*]` attributes match their roles
5/5
`[aria-hidden="true"]` is not present on the document `<body>`
5/5
`[role]`s have all required `[aria-*]` attributes
5/5
`[aria-*]` attributes have valid values
5/5
`[aria-*]` attributes are valid and not misspelled
5/5
Buttons have an accessible name
5/5
Image elements have `[alt]` attributes
5/5
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
5/5
ARIA attributes are used as specified for the element's role
4/4
`[aria-hidden="true"]` elements do not contain focusable descendents
4/4
Elements use only permitted ARIA attributes
4/4
`[role]` values are valid
4/4
Background and foreground colors do not have a sufficient contrast ratio.
0/4
Document has a `<title>` element
4/4
`<html>` element has a `[lang]` attribute
4/4
`<html>` element has a valid value for its `[lang]` attribute
4/4
Form elements have associated labels
4/4
Links have a discernible name
4/4
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
4/4
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
4/4
No element has a `[tabindex]` value greater than 0
4/4
Touch targets do not have sufficient size or spacing.
0/4
Heading elements appear in a sequentially-descending order
2/2
Uses ARIA roles only on compatible elements
1/1
Deprecated ARIA roles were not used
1/1
Image elements do not have `[alt]` attributes that are redundant text.
1/1

Site Quality

Title
20/20
AINave - Navigate the world of AI with ease
43 chars (ideal 30–60)
Meta Description
15/15
Discover AINave, a vibrant community for AI enthusiasts, developers, and creators. Share insights, collaborate on projects, and shape the future of AI together
159 chars (ideal 120–160)
Favicon
3/3
Favicon preview
https://ainave.com/img/icon.svg
present
Viewport meta
6/8
width=device-width
correct (width=device-width, initial-scale=1)
robots.txt
6/6
User-Agent: * Allow: / # Sitemap Sitemap: http://www.ainave.com/sitemap/sitemap.xml
perfect (User-agent + Allow + Sitemap)
Sitemap
7/7
http://www.ainave.com/sitemap/sitemap.xml
present
Headings
0/6
missing (add H1, H2, H3, H4, H5, H6 tags to structure content)
Schema.org JSON-LD
2/2
Organization
Website
Organization: AINave
3 schemas found
Canonical URL
8/8
https://www.ainave.com
present
HTML lang
4/4
en
present
Character encoding
4/4
utf-8
present

Open Graph

Title
3/3
AINave - Navigate the world of AI with ease
present
Description
3/3
Discover AINave, a vibrant community for AI enthusiasts, developers, and creators. Share insights, collaborate on projects, and shape the future of AI together
present
Image
3/3
Image preview
https://www.ainave.com/img/og/home.jpg
present
URL
3/3
https://www.ainave.com
present
Type
1/1
website
present

Twitter Cards

Card Type
1/1
summary_large_image
present
Title
0/1
missing (add <meta name='twitter:title'> for Twitter sharing)
Description
0/1
missing (add <meta name='twitter:description'> for Twitter sharing)
Image
0/1
missing (add <meta name='twitter:image'> with 1200x630px image)

Security Headers

HTTPS
30/30
HTTPS enabled
HTTP Strict Transport Security
15/15
Strict-Transport-Security: max-age=63072000
Content Security Policy
0/15
missing (should be: Content-Security-Policy: default-src 'self')
Frame Protection
0/5
missing (should be: X-Frame-Options: SAMEORIGIN)
MIME Type Protection
0/5
missing (should be: X-Content-Type-Options: nosniff)

Domain Trust

Domain Rating
25/25
36 (Last sync: 30th July 2025)
1525
Domain Age
2/5
2 years
Registrar
Cloudflare, Inc.
Country
IN

Infrastructure

Provider
Cloudflare

FAQs

Report-specific answers

Key takeaways for ainave.com pulled from this audit.

How often should I refresh the YourWebsiteScore report for ainave.com?

The latest audit was captured on October 6, 2025.

Re-run the analysis after major deployments or at least once a month so you can spot Core Web Vitals, snippet, or security regressions before they affect rankings or conversions.

Which Lighthouse performance improvements should ainave.com tackle first?

Largest Contentful Paint (mobile) at 5.2s: reclaim ≈19 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.

Total Blocking Time (desktop) at 384ms: reclaim ≈17 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.

Total Blocking Time (mobile) at 335ms: reclaim ≈7 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.

Which Lighthouse SEO audits should ainave.com fix first?

Mobile Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.

Desktop Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.

Which Lighthouse Best Practices should ainave.com fix first?

Displays images with incorrect aspect ratio (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep ainave.com aligned with modern browser expectations.

Which Lighthouse Accessibility audits should ainave.com fix first?

Background and foreground colors do not have a sufficient contrast ratio. (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make ainave.com easier to use.

Touch targets do not have sufficient size or spacing. (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make ainave.com easier to use.

Background and foreground colors do not have a sufficient contrast ratio. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make ainave.com easier to use.

Touch targets do not have sufficient size or spacing. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make ainave.com easier to use.

Which Website Quality issues should ainave.com fix first?

Headings: missing ≈6 points. Missing (add H1, H2, H3, H4, H5, H6 tags to structure content). Focus on it to lift ainave.com's Website Quality score.

Viewport meta: missing ≈2 points. Correct (width=device-width, initial-scale=1). Focus on it to lift ainave.com's Website Quality score.

Title: missing ≈1 points. Missing (add <meta name='twitter:title'> for Twitter sharing). Focus on it to lift ainave.com's Website Quality score.

Which Trust & Security fixes should ainave.com tackle first?

Content Security Policy: missing ≈15 points. Missing (should be: Content-Security-Policy: default-src 'self'). Close this gap to raise ainave.com's Trust & Security score.

Frame Protection: missing ≈5 points. Missing (should be: X-Frame-Options: SAMEORIGIN). Close this gap to raise ainave.com's Trust & Security score.

MIME Type Protection: missing ≈5 points. Missing (should be: X-Content-Type-Options: nosniff). Close this gap to raise ainave.com's Trust & Security score.

Instant Audit

See your site the way search engines feel it

Launch a free crawl in under 30 seconds and get a ranked hit-list of fixes that lift speed, visibility, and trust.

Start Free Analysis