nayagoogle.com

nayagoogle.com ↗ · 🇺🇸 United States · Community picks

#168/168 top ranked in United States · #339/341 worldwide

Scanned

The quick verdict

1 broken link to fix.

Link health
86.96/100

Ranks first

Quality checklist
50.00/100

Breaks ties

Broken links
1

Confirmed in sample

11 links verified · 0 unknown · 6 selected source pages · 100% of selected destinations verified. Sample only. Unknown links are not counted as broken.

Share on X Start a battle

What to fix first

View all priorities →
  1. Fix 1 broken link

    Start with navigation and internal links so visitors can reach your pages.

  2. Canonical URL

    Declare one valid HTTP(S) canonical URL for each indexable page. It may point to another URL when intentional.

  3. Main heading

    Add a descriptive H1 identifying the main topic.

Fix with your coding assistant

Copy a ready-to-use prompt with the issues and affected URLs.

How this result qualifies

Verified internal navigation

At least 10 internal destinations were verified. Unknown items do not disqualify the site; confirmed checklist failures reduce quality.

86.96/100 link health · 50.00/100 quality · 11 internal destinations

New comparison baseline. A change in coverage is not a verified improvement.

The diagnostic report below may cover additional pages and external links. Only the stored competitive sample determines the ranking. At least 10 verified internal links are required; unavailable checklist items do not exclude a site. How scoring works

View full reportConfirmed issues, suggested fixes and the evidence behind them.

Extended diagnostic evidence

1 confirmed broken links in 21 verified. 0 discovered links could not be verified.

100% of discovered links verified. These diagnostic counts may include pages and external links outside the ranked sample. Unknown links are not counted as broken.

Broken links
1
Links verified
21
Unverifiable
0

not counted

Pages read
11

Broken links

1 internal · 0 external

Latest competitive sample and evidence · 50.00/100 quality

At least 10 internal destinations were verified. Unknown items do not disqualify the site; confirmed checklist failures reduce quality. Each item is evaluated independently; unavailable readings do not veto the result.

6 selected source URLs · 11 internal destinations. 11 evaluated · 0 unknown · 0 using previous evidence. The expanded diagnostic report follows below.

Some checklist evidence is unavailable: Root sitemap available. 0 check(s) use previous evidence, for at most eight days from their last reliable reading. Other unknown observations have no scoring vote.

SEO
56.67/100
Accessibility
33.33/100
Structure
55.56/100
Sharing
61.11/100
Selected pages
  • https://nayagoogle.com/
  • https://nayagoogle.com/add-quizz
  • https://nayagoogle.com/ask
  • https://nayagoogle.com/edit?post-article=new
  • https://nayagoogle.com/signup
  • https://nayagoogle.com/trending
Internal link verdicts and weights
  • ok · weight 6 · https://nayagoogle.com/
  • broken · weight 6 · https://nayagoogle.com/add-quizz
  • ok · weight 6 · https://nayagoogle.com/ask
  • ok · weight 6 · https://nayagoogle.com/edit?post-article=new
  • ok · weight 6 · https://nayagoogle.com/signup
  • ok · weight 6 · https://nayagoogle.com/trending
  • ok · weight 2 · https://nayagoogle.com/privacy
  • ok · weight 2 · https://nayagoogle.com/signin
  • ok · weight 2 · https://nayagoogle.com/signin?return=https%253A%252F%252Fnayagoogle.com%252Fask
  • ok · weight 2 · https://nayagoogle.com/signin?return=https%253A%252F%252Fnayagoogle.com%252Fedit%253Fpost-article%253Dnew
  • ok · weight 2 · https://nayagoogle.com/terms-and-conditions
Scoring checks
  • Page title: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: Naya Google

    https://nayagoogle.com/ask: ASK - Naya Google

    https://nayagoogle.com/edit?post-article=new: Edit - Naya Google

    https://nayagoogle.com/signup: Create New Account - Naya Google

  • Distinct page titles: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: No title

    https://nayagoogle.com/: Naya Google

    https://nayagoogle.com/ask: ASK - Naya Google

    https://nayagoogle.com/edit?post-article=new: Edit - Naya Google

    https://nayagoogle.com/signup: Create New Account - Naya Google

  • Meta description: failed · 1/6 applicable observations

    https://nayagoogle.com/: No meta description

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: No meta description

    https://nayagoogle.com/edit?post-article=new: No meta description

    https://nayagoogle.com/signup: No meta description

  • Canonical URL: failed · 0/6 applicable observations

    https://nayagoogle.com/: No canonical URL

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: No canonical URL

    https://nayagoogle.com/edit?post-article=new: No canonical URL

    https://nayagoogle.com/signup: No canonical URL

  • Main heading: failed · 0/6 applicable observations

    https://nayagoogle.com/: 0 H1 element(s)

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: 0 H1 element(s)

    https://nayagoogle.com/edit?post-article=new: 0 H1 element(s)

    https://nayagoogle.com/signup: 0 H1 element(s)

  • Heading hierarchy: failed · 0/6 applicable observations

    https://nayagoogle.com/: 0 skipped heading level(s)

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: 0 skipped heading level(s)

    https://nayagoogle.com/edit?post-article=new: 0 skipped heading level(s)

    https://nayagoogle.com/signup: 1 skipped heading level(s)

  • Main landmark: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: 1 main landmarks

    https://nayagoogle.com/ask: 1 main landmarks

    https://nayagoogle.com/edit?post-article=new: 1 main landmarks

    https://nayagoogle.com/signup: 1 main landmarks

  • Document language: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: en

    https://nayagoogle.com/ask: en

    https://nayagoogle.com/edit?post-article=new: en

    https://nayagoogle.com/signup: en

  • Image alternatives declared: failed · 0/6 applicable observations

    https://nayagoogle.com/: 1 of 2 images lack an alt attribute

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: 2 of 3 images lack an alt attribute

    https://nayagoogle.com/edit?post-article=new: 2 of 3 images lack an alt attribute

    https://nayagoogle.com/signup: 1 of 2 images lack an alt attribute

  • Form controls named: failed · 0/6 applicable observations

    https://nayagoogle.com/: 1 of 1 controls have no HTML label

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: 1 of 1 controls have no HTML label

    https://nayagoogle.com/edit?post-article=new: 1 of 1 controls have no HTML label

    https://nayagoogle.com/signup: 1 of 5 controls have no HTML label

  • Buttons named: failed · 0/6 applicable observations

    https://nayagoogle.com/: 1 of 1 buttons have no HTML name

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: 1 of 2 buttons have no HTML name

    https://nayagoogle.com/edit?post-article=new: 1 of 2 buttons have no HTML name

    https://nayagoogle.com/signup: 1 of 4 buttons have no HTML name

  • Links named: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: 0 of 7 links have no HTML name

    https://nayagoogle.com/ask: 0 of 8 links have no HTML name

    https://nayagoogle.com/edit?post-article=new: 0 of 8 links have no HTML name

    https://nayagoogle.com/signup: 0 of 10 links have no HTML name

  • Mobile viewport: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: width=device-width, initial-scale=1.0

    https://nayagoogle.com/ask: width=device-width, initial-scale=1.0

    https://nayagoogle.com/edit?post-article=new: width=device-width, initial-scale=1.0

    https://nayagoogle.com/signup: width=device-width, initial-scale=1.0

  • HTTPS page: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: https://nayagoogle.com/

    https://nayagoogle.com/ask: https://nayagoogle.com/ask

    https://nayagoogle.com/edit?post-article=new: https://nayagoogle.com/edit?post-article=new

    https://nayagoogle.com/signup: https://nayagoogle.com/signup

  • No insecure embedded resources: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: 0 HTTP embedded resource URL(s)

    https://nayagoogle.com/ask: 0 HTTP embedded resource URL(s)

    https://nayagoogle.com/edit?post-article=new: 0 HTTP embedded resource URL(s)

    https://nayagoogle.com/signup: 0 HTTP embedded resource URL(s)

  • Open Graph title: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: Naya Google

    https://nayagoogle.com/ask: ASK - Naya Google

    https://nayagoogle.com/edit?post-article=new: Edit - Naya Google

    https://nayagoogle.com/signup: Create New Account - Naya Google

  • Open Graph description: failed · 1/6 applicable observations

    https://nayagoogle.com/: No og:description

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: No og:description

    https://nayagoogle.com/edit?post-article=new: No og:description

    https://nayagoogle.com/signup: No og:description

  • Open Graph type: failed · 0/6 applicable observations

    https://nayagoogle.com/: No og:type

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: No og:type

    https://nayagoogle.com/edit?post-article=new: No og:type

    https://nayagoogle.com/signup: No og:type

  • Open Graph URL: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: https://nayagoogle.com

    https://nayagoogle.com/ask: https://nayagoogle.com/ask

    https://nayagoogle.com/edit?post-article=new: https://nayagoogle.com/edit

    https://nayagoogle.com/signup: https://nayagoogle.com/signup

  • Open Graph image URL: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: https://nayagoogle.com/samagri/logos/ong-l.jpg

    https://nayagoogle.com/ask: https://nayagoogle.com/samagri/logos/ong-l.jpg

    https://nayagoogle.com/edit?post-article=new: https://nayagoogle.com/samagri/logos/ong-l.jpg

    https://nayagoogle.com/signup: https://nayagoogle.com/samagri/logos/ong-l.jpg

  • Open Graph image description: failed · 0/6 applicable observations

    https://nayagoogle.com/: No sharing image description

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/ask: No sharing image description

    https://nayagoogle.com/edit?post-article=new: No sharing image description

    https://nayagoogle.com/signup: No sharing image description

  • Social card type: failed · 5/6 applicable observations

    https://nayagoogle.com/add-quizz: Selected source returned a confirmed 404/410.

    https://nayagoogle.com/: summary

    https://nayagoogle.com/ask: summary

    https://nayagoogle.com/edit?post-article=new: summary

    https://nayagoogle.com/signup: summary

  • Homepage favicon available: passed · 1/1 applicable observations

    https://nayagoogle.com/asset/s1/logos/ong.png: HTTP 200; image/png

  • Homepage sharing image available: passed · 1/1 applicable observations

    https://nayagoogle.com/samagri/logos/ong-l.jpg: HTTP 200; image/jpeg

  • Root sitemap available: passed · 1/1 applicable observations

    https://nayagoogle.com/sitemap.xml: HTTP 200; sitemap root found

  • Rendered color contrast: unverified · 0/1 applicable observations

    https://nayagoogle.com/: Requires a browser or human assessment; excluded from points.

  • Keyboard and focus behavior: unverified · 0/1 applicable observations

    https://nayagoogle.com/: Requires a browser or human assessment; excluded from points.

Sample reference: ff8b0e500b00cecb60b7396760061ed7ad22783eabb357427a7b34e6f8a9f595

Full standard report · free for everyone. This is a bounded sample, not an audit of every page.

Navigation / footer

1

Homepage

0

Inner page

0

Diagnostic checklist

15 passed · 13 need work · 4 not verified. Open a check for the evidence and suggested fix.

SEO
36.00
Accessibility
40.00
Structure
66.67
Sharing
67.78
AI access
15.00
Performance
100.00

Measured performance

2071 ms median to homepage response headers. Measurements: 747, 2137, 2071 ms.

Same crawler, three sequential requests, DNS and TLS included. Timing is diagnostic only and never decides a position. This is server/network response, not browser loading or Core Web Vitals.

Static checks inspect crawler-visible HTML; they do not certify accessibility or code quality.

SEO3 to improve
Page titlePassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Give each page a descriptive, non-empty <title>.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Distinct page titlesNeeds work

7/10 applicable observations passed. 0.70/1 checklist weight earned.

How to improve: Use a title that describes the purpose of this page rather than repeating the same title across URLs.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Meta descriptionNeeds work

1/10 applicable observations passed. 0.10/1 checklist weight earned.

How to improve: Add a non-empty meta name="description" that summarizes this page.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Canonical URLNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Declare one valid HTTP(S) canonical URL for each indexable page. It may point to another URL when intentional.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Root sitemap availableNot verified

0/1 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Make the sitemap accessible to the crawler, then rescan.

Accessibility3 to improve
Document languagePassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Declare a valid language tag on the html element, such as en or pt-BR.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Image alternatives declaredNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Add alt text to informative images. Use alt="" for decorative images. This check does not judge text quality.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Form controls namedNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Associate a label with each visible form control, or provide a non-empty aria-label / valid aria-labelledby.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Buttons namedNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Give every button visible text or an accessible name, including icon-only buttons.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Rendered color contrastNot verified

0/1 applicable observations passed. Informational; excluded from points.

How to improve: Check foreground/background contrast in the rendered page.

Keyboard and focus behaviorNot verified

0/1 applicable observations passed. Informational; excluded from points.

How to improve: Test every interactive control with a keyboard and inspect focus visibility.

Structure2 to improve
Main headingNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Add a descriptive H1 identifying the main topic.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Heading hierarchyNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Nest headings logically without skipping a level, starting with H1.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Main landmarkPassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Mark the main content with one <main> or role="main" landmark.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Mobile viewportPassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Add meta name="viewport" with width=device-width and do not disable user zoom.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

HTTPS pagePassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Serve the page over HTTPS with a valid certificate.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

No insecure embedded resourcesPassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Use HTTPS for embedded script, image, stylesheet, frame, audio and video URLs.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Sharing3 to improve
Open Graph titlePassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Provide a non-empty og:title meta property.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Open Graph descriptionNeeds work

1/10 applicable observations passed. 0.10/1 checklist weight earned.

How to improve: Provide a non-empty og:description meta property.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Open Graph typeNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Declare og:type, such as website or article.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Open Graph URLPassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Set og:url to an absolute HTTP(S) URL for this content.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Open Graph image URLPassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Set og:image to an absolute HTTP(S) image URL. Homepage image availability is checked separately.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Open Graph image descriptionNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Describe the sharing image with og:image:alt.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Social card typePassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Declare twitter:card as summary or summary_large_image for a website card.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Homepage favicon availablePassed

1/1 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Serve a non-empty public image with an image Content-Type.

Homepage sharing image availablePassed

1/1 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Serve a non-empty public image with an image Content-Type.

AI access2 to improve
Content in initial HTMLNeeds work

3/10 applicable observations passed. 0.30/1 checklist weight earned.

How to improve: Render meaningful main content on the server so readers can access it without executing JavaScript.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Structured data syntaxNeeds work

0/10 applicable observations passed. 0.00/1 checklist weight earned.

How to improve: Provide JSON-LD with @context and @type (or a typed @graph). Match the markup to the visible content; syntax alone does not validate its meaning.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Performance0 to improve
HTML transfer budgetPassed

10/10 applicable observations passed. 1.00/1 checklist weight earned.

How to improve: Keep the uncompressed HTML at or below 500 KB. Remove duplicated inline payloads and unnecessary markup.

Showing up to five examples, with failed observations first. Full per-page observations are listed below and available in the report API.

Repeated homepage HTTP responsePassed

1/1 applicable observations passed. Informational; excluded from points.

How to improve: Improve server response and CDN caching. Median of three requests; diagnostic only, never a ranking tiebreak.

Browser loading and Core Web VitalsNot verified

0/1 applicable observations passed. Informational; excluded from points.

How to improve: Measure LCP, INP and CLS with browser and field tools.

Checklist quality-v3. Competitive weights: Structure 30%, Accessibility markup 30%, SEO 25%, Sharing 15%. AI access and performance are diagnostic only. This expanded report may include pages outside the competitive sample. Unverified scored checks earn no points; not-applicable and manual checks are excluded. Full methodology and references.

Page health

From the 11 pages we read. Full details in the report.

Missing titles

0

Duplicate titles

3

Missing descriptions

9

Missing H1

10

Multiple H1

0

Avg response

1,756 ms

Slowest pages

HTTP response time measured by our crawler; not browser loading speed.

Pages inspected (11)

All 11 pages from this scan.

PageStatusTitleH1ms
https://nayagoogle.com/200Naya Google
Page checklist evidence
  • title: passedNaya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed0 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed1 of 2 images lack an alt attribute
  • labels: failed1 of 1 controls have no HTML label
  • buttons: failed1 of 1 buttons have no HTML name
  • links-named: passed0 of 7 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedNaya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: failed0 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed5,477 bytes of HTML; budget 500,000
01,879
https://nayagoogle.com/add-quizz404—0750
https://nayagoogle.com/ask200ASK - Naya Google
Page checklist evidence
  • title: passedASK - Naya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed0 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed2 of 3 images lack an alt attribute
  • labels: failed1 of 1 controls have no HTML label
  • buttons: failed1 of 2 buttons have no HTML name
  • links-named: passed0 of 8 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/ask
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedASK - Naya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/ask
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: failed50 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed5,764 bytes of HTML; budget 500,000
0751
https://nayagoogle.com/edit?post-article=new200Edit - Naya Google
Page checklist evidence
  • title: passedEdit - Naya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed0 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed2 of 3 images lack an alt attribute
  • labels: failed1 of 1 controls have no HTML label
  • buttons: failed1 of 2 buttons have no HTML name
  • links-named: passed0 of 8 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/edit?post-article=new
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedEdit - Naya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/edit
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: failed83 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed5,988 bytes of HTML; budget 500,000
03,011
https://nayagoogle.com/signup200Create New Account - Naya Google
Page checklist evidence
  • title: passedCreate New Account - Naya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed1 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed1 of 2 images lack an alt attribute
  • labels: failed1 of 5 controls have no HTML label
  • buttons: failed1 of 4 buttons have no HTML name
  • links-named: passed0 of 10 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/signup
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedCreate New Account - Naya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/signup
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: passed262 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed7,689 bytes of HTML; budget 500,000
03,064
https://nayagoogle.com/trending200Trending on Naya Google
Page checklist evidence
  • title: passedTrending on Naya Google
  • description: passedExplore latest trending articles and questions on NayaGoogle.com.
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed1 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed1 of 2 images lack an alt attribute
  • labels: failed1 of 1 controls have no HTML label
  • buttons: failed1 of 1 buttons have no HTML name
  • links-named: passed0 of 7 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/trending
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedTrending on Naya Google
  • og-description: passedExplore latest trending articles and questions on NayaGoogle.com.
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/trending
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: failed23 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed6,000 bytes of HTML; budget 500,000
0753
https://nayagoogle.com/signin?return=https%253A%252F%252Fnayagoogle.com%252Fask200Sign In - Naya Google
Page checklist evidence
  • title: passedSign In - Naya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed1 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed1 of 2 images lack an alt attribute
  • labels: failed1 of 3 controls have no HTML label
  • buttons: failed1 of 3 buttons have no HTML name
  • links-named: passed0 of 9 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/signin?return=https%253A%252F%252Fnayagoogle.com%252Fask
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedSign In - Naya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/signin
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: failed90 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed6,848 bytes of HTML; budget 500,000
02,316
https://nayagoogle.com/signin?return=https%253A%252F%252Fnayagoogle.com%252Fedit%253Fpost-article%253Dnew200Sign In - Naya Google
Page checklist evidence
  • title: passedSign In - Naya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed1 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed1 of 2 images lack an alt attribute
  • labels: failed1 of 3 controls have no HTML label
  • buttons: failed1 of 3 buttons have no HTML name
  • links-named: passed0 of 9 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/signin?return=https%253A%252F%252Fnayagoogle.com%252Fedit%253Fpost-article%253Dnew
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedSign In - Naya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/signin
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: failed90 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed6,910 bytes of HTML; budget 500,000
0746
https://nayagoogle.com/terms-and-conditions200Terms And Conditions - Naya Google
Page checklist evidence
  • title: passedTerms And Conditions - Naya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed1 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed1 of 3 images lack an alt attribute
  • labels: failed1 of 1 controls have no HTML label
  • buttons: failed1 of 1 buttons have no HTML name
  • links-named: passed0 of 35 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/terms-and-conditions
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedTerms And Conditions - Naya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/terms-and-conditions
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: passed25376 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed34,532 bytes of HTML; budget 500,000
02,266
https://nayagoogle.com/privacy200Privacy Policies - Naya Google
Page checklist evidence
  • title: passedPrivacy Policies - Naya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed1 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed1 of 3 images lack an alt attribute
  • labels: failed1 of 1 controls have no HTML label
  • buttons: failed1 of 1 buttons have no HTML name
  • links-named: passed0 of 17 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/privacy
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedPrivacy Policies - Naya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/privacy
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: passed7023 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed14,876 bytes of HTML; budget 500,000
02,016
https://nayagoogle.com/signin200Sign In - Naya Google
Page checklist evidence
  • title: passedSign In - Naya Google
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed1 skipped heading level(s)
  • main: passed1 main landmarks
  • lang: passeden
  • alt: failed1 of 2 images lack an alt attribute
  • labels: failed1 of 3 controls have no HTML label
  • buttons: failed1 of 3 buttons have no HTML name
  • links-named: passed0 of 9 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1.0
  • https: passedhttps://nayagoogle.com/signin
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: passedSign In - Naya Google
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: passedhttps://nayagoogle.com/signin
  • og-image: passedhttps://nayagoogle.com/samagri/logos/ong-l.jpg
  • og-alt: failedNo sharing image description
  • twitter-card: passedsummary
  • readable: failed90 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 1 blocks have valid JSON-LD structure
  • html-size: passed6,742 bytes of HTML; budget 500,000
0753

Mobile page report

nayagoogle.com

https://nayagoogle.com/

Measured · 9/12/2026, 5:57:38 AM UTC

Speed
38
Accessibility
92
SEO basics
91
Main content (LCP)
7.0 s
Layout shifts (CLS)
0.029
Blocking time (TBT)
2,540 ms

Your next improvements

Measured findings to investigate, ordered by audit score.

1. Background and foreground colors do not have a sufficient contrast ratio.

Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.12/color-contrast).

ul.navigation > li > a.navLink > span · <span>
div.feed > div.question-indiv > div.m-q-b > p.time · <p class="time ">
div.feed > div.question-indiv > div.m-q-b > p.time · <p class="time">
2. Document does not have a meta description

Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/).

3. Network dependency tree

[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

4. Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.12/list).

header > div.big-container > nav.flex > ul.navigation · <ul class="navigation">
5. Max Potential First Input Delay

The maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more about the Maximum Potential First Input Delay metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-max-potential-fid/).

6. Forced reflow

A forced reflow occurs when JavaScript queries geometric properties (such as `offsetWidth`) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.

7. LCP breakdown

Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.

8. Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more about the Total Blocking Time metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-total-blocking-time/).

Fix with your coding assistant

Copy a ready-to-use prompt with the issues and affected URLs.

Battle scoring rules

The arena winner follows the verified ranking: internal link health first, then the published two-decimal quality score. Both sites need two agreeing standard observations. Browser performance, accessibility and SEO are complementary diagnostics and do not move the ranking or decide its winner. Page-only battles compare compatible rounds; performance differences up to five points draw, and equal round wins remain a tie. Missing measurements never count as zero. Browser audits do not certify accessibility. Saved results keep their measured evidence; start a rematch for a newer comparison.