Login

Automated Report

indiewait.com

Generated on September 26, 2025 · Domain: indiewait.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
Favicon
indiewait.com
2025/09/26
72

Overall Score

91

PageSpeed

80

Website Quality

45

Trust & Security

75

Performance

100

SEO

100

Best Practices

79

Accessibility

Performance
75/100
Largest Contentful Paint
12/25
4.1s
2.5s4.0s
First Contentful Paint
2/10
4.1s
1.8s3.0s
Total Blocking Time
30/30
0ms
200ms400ms
Cumulative Layout Shift
25/25
0.00
0.100.25
Speed Index
7/10
4.9s
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
79/100
`[aria-*]` attributes match their roles
6/6
`[aria-hidden="true"]` is not present on the document `<body>`
6/6
`[role]`s have all required `[aria-*]` attributes
6/6
`[aria-*]` attributes have valid values
6/6
`[aria-*]` attributes are valid and not misspelled
6/6
Buttons do not have an accessible name
0/6
Image elements have `[alt]` attributes
6/6
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
6/6
ARIA attributes are used as specified for the element's role
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
Links do not have a discernible name
0/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
Select elements do not have associated label elements.
0/4
Touch targets have sufficient size and spacing.
4/4
Heading elements are not in a sequentially-descending order
0/2
Uses ARIA roles only on compatible elements
1/1
Deprecated ARIA roles were not used
1/1
Image elements have `[alt]` attributes that are redundant text.
0/1

Site Quality

Title
12/20
IndieWait - Discover and showcase the next indie project before they launch
75 chars (ideal 30–60)
Meta Description
15/15
A directory for waitlists. Discover and showcase the next indie project being built by solo developers or small teams before they launch.
137 chars (ideal 120–160)
Favicon
3/3
Favicon preview
https://indiewait.com/favicon-16x16.png
present
Viewport meta
8/8
width=device-width, initial-scale=1, shrink-to-fit=no
correct (width=device-width, initial-scale=1)
robots.txt
6/6
Sitemap: https://indiewait.com/sitemap.xml User-agent: * Disallow:
perfect (User-agent + Allow + Sitemap)
Sitemap
7/7
https://indiewait.com/sitemap.xml
present
Headings
0/6
H3FREE for the first 100 submissions!
H2Categories
H2Waitlists
H3Can I log in or create an account?
H3What happens after I submit my project?
H3Is there a fee to list my project?
H3Can I change my project details after submission?
H3What happens if I abandon my project or waitlist?
H3What happens if waitlist campaign ends for my project?
H3Have a waitlist?
H4Browse
H4IndieWait
H1 missing (add one <h1> tag for main title)
Schema.org JSON-LD
0/2
missing (consider Organization, Article, Product, or FAQPage schemas)
Canonical URL
8/8
https://indiewait.com
present
HTML lang
4/4
en
present
Character encoding
4/4
utf-8
present

Open Graph

Title
3/3
IndieWait - Discover and showcase the next indie project before they launch
present
Description
3/3
A directory for waitlists. Discover and showcase the next indie project being built by solo developers or small teams before they launch.
present
Image
3/3
Image preview
https://indiewait.com/og-image.png
present
URL
3/3
https://indiewait.com
present
Type
1/1
website
present

Twitter Cards

Card Type
0/1
missing
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
0/15
missing (should be: Strict-Transport-Security: max-age=31536000; includeSubDomains)
Content Security Policy
15/15
Content-Security-Policy: upgrade-insecure-requests
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
0/25
no domain rating found
1525
Domain Age
0/5
0 years
Registrar
Ascio Technologies, Inc
Country
EE

Infrastructure

Provider
no hosting or CDN provider detected

FAQs

Report-specific answers

Key takeaways for indiewait.com pulled from this audit.

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

The latest audit was captured on September 26, 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 indiewait.com tackle first?

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

First Contentful Paint (mobile) at 4.1s: reclaim ≈8 points. Reduce render-blocking CSS/JS and stream initial HTML so meaningful content appears earlier.

Speed Index (mobile) at 4.9s: reclaim ≈3 points. Trim render-blocking resources, preconnect to critical domains, and focus on above-the-fold rendering to accelerate visual completion.

Which Lighthouse SEO audits should indiewait.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 indiewait.com fix first?

Serves images with low resolution (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep indiewait.com aligned with modern browser expectations.

Which Lighthouse Accessibility audits should indiewait.com fix first?

Buttons do not have an accessible name (mobile) is missing roughly 6 points. Fixing it will raise the Accessibility score and make indiewait.com easier to use.

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 indiewait.com easier to use.

Links do not have a discernible name (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make indiewait.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 indiewait.com easier to use.

Links do not have a discernible name (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make indiewait.com easier to use.

Select elements do not have associated label elements. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make indiewait.com easier to use.

Which Website Quality issues should indiewait.com fix first?

Title: missing ≈8 points. 75 chars (ideal 30–60). Focus on it to lift indiewait.com's Website Quality score.

Headings: missing ≈6 points. H1 missing (add one <h1> tag for main title). Focus on it to lift indiewait.com's Website Quality score.

Schema.org JSON-LD: missing ≈2 points. Missing (consider Organization, Article, Product, or FAQPage schemas). Focus on it to lift indiewait.com's Website Quality score.

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

Domain Rating: missing ≈25 points. No domain rating found. Close this gap to raise indiewait.com's Trust & Security score.

HTTP Strict Transport Security: missing ≈15 points. Missing (should be: Strict-Transport-Security: max-age=31536000; includeSubDomains). Close this gap to raise indiewait.com's Trust & Security score.

Frame Protection: missing ≈5 points. Missing (should be: X-Frame-Options: SAMEORIGIN). Close this gap to raise indiewait.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