Login

Automated Report

peekx.app

Generated on October 3, 2025 · Domain: peekx.app

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
peekx.app
2025/10/03
56

Overall Score

85

PageSpeed

37

Website Quality

45

Trust & Security

62

Performance

92

SEO

79

Best Practices

90

Accessibility

Performance
62/100
Largest Contentful Paint
7/25
5.1s
2.5s4.0s
First Contentful Paint
10/10
1.5s
1.8s3.0s
Total Blocking Time
15/30
577ms
200ms400ms
Cumulative Layout Shift
25/25
0.00
0.100.25
Speed Index
5/10
5.6s
3.4s5.4s
SEO
92/100
Page isn’t blocked from indexing
34/34
Document has a `<title>` element
8/8
Document does not have a meta description
0/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
Best Practices
79/100
Uses HTTPS
18/18
Avoids deprecated APIs
18/18
Uses third-party cookies
0/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
Issues were logged in the `Issues` panel in Chrome Devtools
0/4
Accessibility
90/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
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
5/5
`[role]`s are contained by their required parent element
5/5
`[aria-*]` attributes do not have valid values
0/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
3/3
`[aria-hidden="true"]` elements do not contain focusable descendents
3/3
Elements use only permitted ARIA attributes
3/3
`[role]` values are valid
3/3
Background and foreground colors do not have a sufficient contrast ratio.
0/3
Document has a `<title>` element
3/3
`<frame>` or `<iframe>` elements have a title
3/3
`<html>` element has a `[lang]` attribute
3/3
`<html>` element has a valid value for its `[lang]` attribute
3/3
Links have a discernible name
3/3
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
3/3
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
3/3
No element has a `[tabindex]` value greater than 0
3/3
Touch targets have sufficient size and spacing.
3/3
Heading elements are not in a sequentially-descending order
0/1

Site Quality

Title
5/20
PeekX
5 chars (ideal 30–60)
Meta Description
0/15
missing (add <meta name='description'> with 120-160 chars)
Favicon
3/3
Favicon preview
https://peekx.app/favicon.ico
present
Viewport meta
8/8
width=device-width, initial-scale=1
correct (width=device-width, initial-scale=1)
robots.txt
4/6
User-Agent: * Allow: /
good (User-agent + Allow, missing Sitemap)
Sitemap
7/7
https://peekx.app/sitemap.xml
present
Headings
2/6
H1Real viewer reactions.82% faster highlight turnarounds.
H2See PeekX in action
H2Turn chat chaos into highlight reels your fans already love
H330-second highlight shortlist
H3Plans built for highlight junkies
H3Context editors actually trust
H3Stop playing fair with manual hunts or generic AI
H1Pricing
H3Free
H3Starter
H3Pro
H2PeekX turns live chat chaos into ready-to-post magic
H3PeekX listens to the chaos for you
H3Editors skip the 6-hour scrub
H3Deliver moments your fans already love
H1Frequently asked questions
H4How does PeekX analyze my YouTube videos?
H4What types of insights can I get from the live chat analysis?
H4How do I get started with analyzing my YouTube videos?
H4How reliable is the peak moment detection?
multiple H1 (use only one <h1> tag per page)
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
no country record found

Infrastructure

Provider
Vercel

FAQs

Report-specific answers

Key takeaways for peekx.app pulled from this audit.

How often should I refresh the YourWebsiteScore report for peekx.app?

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 peekx.app tackle first?

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

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

Total Blocking Time (mobile) at 577ms: reclaim ≈15 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 peekx.app fix first?

Document does not have a meta description (mobile) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how peekx.app appears in search.

Document does not have a meta description (desktop) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how peekx.app appears in search.

Which Lighthouse Best Practices should peekx.app fix first?

Uses third-party cookies (mobile) is missing roughly 18 points. Fixing it will raise the Best Practices score and keep peekx.app aligned with modern browser expectations.

Issues were logged in the `Issues` panel in Chrome Devtools (mobile) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep peekx.app aligned with modern browser expectations.

Browser errors were logged to the console (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep peekx.app aligned with modern browser expectations.

Which Lighthouse Accessibility audits should peekx.app fix first?

`[aria-*]` attributes do not have valid values (mobile) is missing roughly 5 points. Fixing it will raise the Accessibility score and make peekx.app easier to use.

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

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

`[aria-*]` attributes do not have valid values (desktop) is missing roughly 5 points. Fixing it will raise the Accessibility score and make peekx.app easier to use.

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

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

Which Website Quality issues should peekx.app fix first?

Title: missing ≈15 points. 5 chars (ideal 30–60). Focus on it to lift peekx.app's Website Quality score.

Meta Description: missing ≈15 points. Missing (add <meta name='description'> with 120-160 chars). Focus on it to lift peekx.app's Website Quality score.

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

Which Trust & Security fixes should peekx.app tackle first?

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

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

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