Login

Automated Report

gitprompt.run

Generated on October 3, 2025 · Domain: gitprompt.run

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
gitprompt.run
2025/10/03
63

Overall Score

99

PageSpeed

45

Website Quality

45

Trust & Security

96

Performance

100

SEO

100

Best Practices

98

Accessibility

Performance
96/100
Largest Contentful Paint
23/25
2.4s
2.5s4.0s
First Contentful Paint
10/10
1.4s
1.8s3.0s
Total Blocking Time
30/30
0ms
200ms400ms
Cumulative Layout Shift
25/25
0.00
0.100.25
Speed Index
8/10
3.9s
3.4s5.4s
SEO
100/100
Page isn’t blocked from indexing
40/40
Document has a `<title>` element
10/10
Document has a meta description
10/10
Page has successful HTTP status code
10/10
Links have descriptive text
10/10
Links are crawlable
10/10
Document has a valid `hreflang`
10/10
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
98/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
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
6/6
`[role]`s are contained by their required parent element
6/6
`[aria-*]` attributes have valid values
6/6
`[aria-*]` attributes are valid and not misspelled
6/6
Buttons have an accessible name
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 have a sufficient contrast ratio
4/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 have a discernible name
4/4
No element has a `[tabindex]` value greater than 0
4/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

Site Quality

Title
20/20
GitPrompt - AI Prompt Management
32 chars (ideal 30–60)
Meta Description
6/15
Manage AI prompts as version-controlled components
50 chars (ideal 120–160)
Favicon
3/3
Favicon preview
https://www.google.com/s2/favicons?domain=gitprompt.run&sz=48
present
Viewport meta
8/8
width=device-width, initial-scale=1
correct (width=device-width, initial-scale=1)
robots.txt
0/6
missing (ideal: User-agent: * + Allow: / + Sitemap)
Sitemap
0/7
missing (create sitemap.xml and submit to Google Search Console)
Headings
0/6
H1Turn Your Prompts into APIs.
H3Manage in GitPrompt
H3Use from Anywhere
skipped heading levels (use H1 → H2 → H3 in order)
Schema.org JSON-LD
0/2
missing (consider Organization, Article, Product, or FAQPage schemas)
Canonical URL
0/8
missing (add <link rel='canonical'> to avoid duplicate content)
HTML lang
4/4
en
present
Character encoding
4/4
utf-8
present

Open Graph

Title
0/3
missing (add <meta property='og:title'> for social sharing)
Description
0/3
missing (add <meta property='og:description'> for social sharing)
Image
0/3
missing (add <meta property='og:image'> with 1200x630px image)
URL
0/3
missing (add <meta property='og:url'> with full URL)
Type
0/1
missing (add <meta property='og:type' content='website'>)

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
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
0/25
no domain rating found
1525
Domain Age
0/5
no domain age records found
Registrar
no registrar record found
Country
Unknown

Infrastructure

Provider
Vercel

FAQs

Report-specific answers

Key takeaways for gitprompt.run pulled from this audit.

How often should I refresh the YourWebsiteScore report for gitprompt.run?

The latest audit was captured on October 3, 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 gitprompt.run tackle first?

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

Speed Index (mobile) at 3.9s: reclaim ≈2 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 gitprompt.run 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 gitprompt.run fix first?

Mobile Lighthouse Best Practices score is 100/100. Keep TLS, resource loading, and client-side APIs up-to-date to stay maxed.

Desktop Lighthouse Best Practices score is 100/100. Keep TLS, resource loading, and client-side APIs up-to-date to stay maxed.

Which Lighthouse Accessibility audits should gitprompt.run fix first?

Heading elements are not in a sequentially-descending order (mobile) is missing roughly 2 points. Fixing it will raise the Accessibility score and make gitprompt.run easier to use.

Heading elements are not in a sequentially-descending order (desktop) is missing roughly 2 points. Fixing it will raise the Accessibility score and make gitprompt.run easier to use.

Which Website Quality issues should gitprompt.run fix first?

Meta Description: missing ≈9 points. 50 chars (ideal 120–160). Focus on it to lift gitprompt.run's Website Quality score.

Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift gitprompt.run's Website Quality score.

Sitemap: missing ≈7 points. Missing (create sitemap.xml and submit to Google Search Console). Focus on it to lift gitprompt.run's Website Quality score.

Which Trust & Security fixes should gitprompt.run tackle first?

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

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

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