A · Very good

Page SEO Inspection

https://sayforth.app/
Crawled 19 Nov, 05:14 UTC (2 hr ago)
HTTP 200 49 KB 103 ms TTFB
Download PDF

PDF export is a paid feature

A PDF of the full report, ready to send to a client or a colleague, comes with Basic at $19 a month and every plan above it, along with saved history. The report itself stays free to read.

See the plans
On-Page Checklist 83% Complete
Primary focus: Largest Contentful Paint is 5.2s (lab data), above the 2.5s target and in the poor range. Fix now →
Filter:

Full diagnostics

Every check that ran, grouped by what it affects. Problems appear first in each group.

Meta Tags & Search Snippet Simulator

The tags that decide how this page is titled and described in search results.

✓ 2100% · excellent
Live snippet simulation
Title width: 395px / 580px
S Sayforth sayforth.app
Speaking Practice App for iPhone · Sayforth

Sayforth is a 30-day speaking practice app for iPhone: one coached spoken answer a day, drawn as a line, one change for tomorrow. Free to start.

Title tag 395px of 580px

The title length is well judged.

Rendered width

Desktop395px/ 580px
Mobile356px/ 920px

Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 43.

Meta description 144 characters

The meta description length is well judged.

Crawling & indexing

Whether search engines can reach, read and index this page at all.

! 1✓ 1694% · excellent
www and https versions 2 found

2 other spellings of this address do not lead here, so search engines can treat them as separate pages and split the ranking between them.

https://www.sayforth.app/ answers HTTP 200 itself
http://www.sayforth.app/ → 301 → https://www.sayforth.app/
How to fix
How to fix
Redirect every spelling (http and https, with and without www) to https://sayforth.app/ with a single 301.
HTTP status HTTP 200

The page returns 200 OK.

Redirect chain

The URL resolves without redirects.

Robots directives

No directive prevents indexing.

Canonical tag

The canonical correctly references this page.

https://sayforth.app/
Language

Language is declared as "en".

lang="en"
hreflang

No hreflang annotations, which is correct for a single-language page.

Viewport

The viewport is configured for mobile.

width=device-width, initial-scale=1
Character encoding

The page declares UTF-8 encoding.

Favicon

A favicon is declared.

Mixed content

All resources load securely.

URL length 21 characters

The URL is 21 characters.

URL readability

The URL is clean and readable.

URL depth 0 levels deep

The page is 0 levels deep.

URL parameters

The URL has no query parameters.

robots.txt 0 KB

robots.txt is present and does not block crawling.

XML sitemap 67 URLs

A sitemap is published, listing 67 URLs.

Lists 67 URLs

Missing pages (404) HTTP 404

A page that does not exist returns HTTP 404, so search engines drop dead addresses.

Content & metadata

What the page says it is about, and how it reads.

✓ 11100% · excellent
Word count 929 Substantive
Headings 15 Structured
H1 tags 1 Exactly one
Text ratio 10.7% Text vs markup
Heading outline 15 headings
H1 Say it better in 30 days.
H2 Your answer, as one line.
H2 The room dims. Then it listens.
H2 Read in five seconds. One change, not a report.
H2 Same question, 30 days apart.
H2 Load and Launch. A crate puzzle.
H2 Your recordings stay on your iPhone. We never upload your audio. Only the text of what yo…
H2 The research behind the program
H2 This is where we start.Nothing to get right.
H3 Be first to know when Sayforth is live.
H4 Product
H4 Company
H4 Contact
H2 Cookies on sayforth.app
Open Graph tags

Open Graph tags are present.

Twitter card

twitter:card is set to summary_large_image.

H1 tag

The page has exactly one h1.

Say it better in 30 days.
Heading hierarchy

The heading outline descends in order.

Content length 929 words

The page has roughly 929 words.

Text-to-HTML ratio 10.7% text

Text is 10.7% of the page source.

Table headers

No data tables on this page, so there are no columns to label.

Keyword placement

The page's prominent terms appear in its title, description or headings.

Where these terms appear

TermCountDensityTitleDescriptionHeadings
day173.14%✕✓✓
point142.58%✕✕✕
line122.21%✕✓✓
sayforth112.03%✓✓✓
main112.03%✕✕✕
Keyword repetition

No term is repeated unnaturally often.

Keyword cloud

The page's most frequent terms, from 542 words of content.

What this page is about

Term size reflects how often it appears. Density is not a ranking factor, this is a view of the page's subject, not a target to hit.

daypointlinesayforthmainemailanswerfirstappsecondslaunchiphonesaydayssoftenercoachingquestioncookiesnevernotifypausewordspausesknowlevelsliveworksanalyticssupportchangestorestartclocklongwhyspeakquietvoicefinishopens
Share image 1200 × 630 px

The share image loads and is 1200 × 630 pixels, the right size and shape for a large card.

AI & answer readiness

Whether answer engines and AI overviews can extract and trust this page.

i 4✓ 660% · fair
AI crawlers 10/10 All allowed
Readable without JS Yes Served complete
Identity 1/2 Partly declared
Quotable signals 2/4 Schema, date, author, answers
Content freshness

The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.

How to fix
How to fix
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
Answer schema

No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.

How to fix
How to fix
Mark up question-and-answer content as FAQPage, or step-by-step content as HowTo.
Page subject

No structured data describes what this page is about.

Found: Organization, WebSite, MobileApplication
None of these declare the page's subject.

3 types: Organization, WebSite, MobileApplication

How to fix
How to fix
Describe the page with the type that fits it, Article for writing, Product for a product, FAQPage for questions and answers. Boilerplate like Organization and BreadcrumbList identifies the site, not the page.
llms.txt for AI agents

No llms.txt. AI coding agents have no curated map of this site.

https://sayforth.app/llms.txt returned nothing
How to fix
How to fix
A markdown file at /llms.txt listing your most useful pages with one-line descriptions. It does not affect how AI assistants cite you in answers, and nobody has shown that it does. What it helps is agents reading your documentation directly: Anthropic supports it, Perplexity uses it to choose pages, and Cursor, Continue and Cline navigate docs with it. Worth doing for a documentation or API site, and safe to skip otherwise.
Answer readiness 2 found

2 headings are followed by a snippet-shaped answer.

Attribution

Attribution signals present: privacy policy, about page.

privacy policy, about page

Extractable structure 929 words

929 words across 15 headings, 7 lists and 0 tables.

Publisher identity

The page names who is behind it: Sayforth.

Readable without JavaScript

The page reads the same with and without JavaScript.

AI crawler access 10 checked

Every AI crawler checked is allowed to read this page.

Speed & delivery

What makes the page slow, and what the loading experience measures.

✕ 1! 1i 1✓ 1077% · needs work
Rendered page
The page as it rendered on a mobile viewport during the performance test
Mobile, measured
The page as it rendered on a desktop viewport
Desktop, measured
LCP Poor
5.18s

Largest Contentful Paint

Target ≤ 2.5s

What this measures

How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".

What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.

INP Good
21ms

Interaction to Next Paint

Target ≤ 200ms

What this measures

How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.

What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.

CLS Good
0

Cumulative Layout Shift

Target ≤ 0.1

What this measures

How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.

What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.

FCP Good
0.93s

First Contentful Paint

Target ≤ 1.8s

What this measures

How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.

What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.

TTFBNo data
n/a

Real-user response time

Target ≤ 800ms

Needs real-user data from Chrome UX Report

Browser caching 862 KB re-downloaded

2 files have cache lifetimes short enough that returning visitors download 862 KB again.

Short cache lifetimes

FileCache lifetimeSize
sayforth.app/harbor-day.mp4none858 KB
static.cloudflareinsights.com/…823e78c4301a35b7e07294d873017920888140921d10 KB

1 expire within the hour

How to fix
How to fix
Serve static assets with a long max-age and a content hash in the filename, so a new version gets a new URL rather than a short expiry.
Inline styles 53 found

53 elements carry inline style attributes, which cannot be cached and inflate the document.

How to fix
How to fix
Move repeated styles into a cacheable stylesheet.
Time to first byte

Time to first byte is 103 ms.

Render-blocking resources 2 found

2 render-blocking resources in the head.

HTML size 49 KB

The HTML document is 49 KB.

Deprecated tags

No deprecated HTML tags are used.

Compression

The response is compressed with zstd.

Content-Encoding: zstd
Page weight 23 requests · 1.6 MB

The page loads 23 requests totalling 1.6 MB.

What loaded, by type

Type RequestsTransferred
media1858 KB
image10of 16 declared303 KB
script3202 KB
font3193 KB
stylesheet228 KB
document115 KB
other33 KB

Of these, 3 requests (191 KB) come from third-party domains. The HTML declares 16 images but only 10 loaded, the rest are lazy-loaded and fetched when scrolled to.

Third-party services 3 services · 191 KB

3 third-party services load on this page, adding 191 KB.

Third-party services

Service TransferredMain thread
Google Tag Manager180 KB104ms
Cloudflare10 KB10ms
Google Analytics1 KBunder 1ms

0.1s of main-thread time

Security

Transport security, reputation and the response headers that protect visitors.

i 3✓ 1077% · good
Email addresses in the page 1 found

1 email address is written into the page as plain text, where harvesting bots collect them for spam and phishing.

[email protected]
How to fix
How to fix
Use a contact form, or show the address through a script or as an image. If the address must stay, give it a strong spam filter.
Content Security Policy

The Content-Security-Policy allows unsafe-inline or unsafe-eval, which undermines much of its protection.

default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://www.googletagmanager.com https://static.cloudflareinsights.com https://challen…
How to fix
How to fix
Use nonces or hashes instead of unsafe-inline.
security.txt

No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.

https://sayforth.app/.well-known/security.txt
How to fix
How to fix
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
HSTS

HTTPS is enforced with Strict-Transport-Security.

max-age=15552000
MIME sniffing

MIME sniffing is disabled.

Clickjacking protection

The page is protected against framing.

Referrer policy

Referrer-Policy is "strict-origin-when-cross-origin".

strict-origin-when-cross-origin
Permissions policy

A Permissions-Policy limits which browser features the page and its embeds can use.

Cookie flags

The page sets no cookies, so there are none to expose.

Version disclosure

No software versions are disclosed in headers or the page.

TLS certificate 89 days left

The TLS certificate is valid for another 89 days, issued by Google Trust Services.

89 days remaining
Google Web Risk

Not listed by Google Web Risk for malware, phishing or unwanted software.

TLS version TLS 1.3

Connections use TLS 1.3.

Server & domain

The server and the domain behind the page: protocol, network, registration and email records.

i 1✓ 788% · good
DMARC policy

sayforth.app has no DMARC record, so mail servers have no instruction for mail that fails SPF or DKIM. Gmail and Yahoo require one from bulk senders.

How to fix
How to fix
Publish a TXT record at _dmarc.sayforth.app, starting with v=DMARC1; p=none; rua=mailto:[email protected] to collect reports, then tighten to quarantine or reject.
HTTP/2 HTTP/2

Served over HTTP/2, which loads a page's files in parallel over one connection.

HTTP/3 HTTP/3

Announces HTTP/3, which browsers switch to on a later visit for faster connections on poor networks.

CDN Cloudflare

Served through Cloudflare, a CDN, so visitors get the page from a server near them.

Domain expiry 304 days left

sayforth.app is registered until 19 Sep 2027 with Namecheap Inc.

304 days remaining
Domain age Under a year old

sayforth.app was registered on 19 Sep 2026, under a year ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

IPv6

sayforth.app has an IPv6 address, so IPv6-only networks reach it directly.

SPF record

sayforth.app publishes an SPF record: v=spf1 include:_spf.mx.cloudflare.net ~all

ads.txt

No ad network loads on this page, so ads.txt is not needed.

Links, media & schema

Links, images and structured data.

! 3✓ 975% · good
Social share preview From this page's Open Graph tags
Anchor text 2 found

2 links use non-descriptive anchor text, which tells neither readers nor engines where it leads.

All 2 point at the same destination, one template reused down the page.

LineLink
262, 275"Details" → privacy#website ×2<a href="privacy#website">Details</a>
How to fix
How to fix
Describe the destination: "read our grinder guide" rather than "click here".
In-page anchors

1 in-page link points to a section that does not exist, so clicking it goes nowhere.

#cookie-settings
How to fix
How to fix
Add the matching id, or correct the link.
Responsive images 11 found

11 large images are served at one fixed size, so phones download desktop-sized files.

Shown as 10 unique sources; the counts show how often each repeats.

LineImage source
89img/boat.svg<img src="img/boat.svg" alt="" width="915" height="1077" decoding="async">
104img/app-recording.webp<img src="img/app-recording.webp" width="640" height="1391" alt="The Recording screen on iPhone: the question on a dark ground, a warm recording dot, the time, one teal line that moves with your voice, and the button Done." loading="lazy" decoding="async">
104img/app-welcome.webp<img src="img/app-welcome.webp" width="640" height="1391" alt="The Sayforth welcome screen on iPhone: a sailboat in a harbor, the line Say it better in 30 days, and the button Answer one question." fetchpriority="high" decoding="async">
104, 134img/app-notes.webp ×2<img src="img/app-notes.webp" width="640" height="1391" alt="Your coach's notes in the app: a bound notebook page with torn paper edges. Your main point underlined in teal, how it sounded, and your one change: Break up the long sentence." loading="lazy" decoding="async">
159img/approach.svg<img src="img/approach.svg" width="1294" height="1000" alt="A green island with a small village of red and yellow roofs, round trees, a striped lighthouse and a wooden pier" loading="lazy" decoding="async">
159img/sand-sea.svg<img src="img/sand-sea.svg" width="1143" height="807" alt="A sunlit desert island with palm trees, a turquoise oasis, a tent and a stone gate" loading="lazy" decoding="async">
159img/storm-passage.svg<img src="img/storm-passage.svg" width="1042" height="826" alt="A dark rocky island with a striped lighthouse and a curved stone harbor wall" loading="lazy" decoding="async">
159img/lantern-canals.svg<img src="img/lantern-canals.svg" width="1092" height="838" alt="A canal city island with colorful rooftops, teal canals, small bridges and a blue clock tower" loading="lazy" decoding="async">
159img/polar-night.svg<img src="img/polar-night.svg" width="1182" height="864" alt="A snowy ice island with three lit wooden cabins, pine trees, crates and a small pier" loading="lazy" decoding="async">
187img/harbor-night-wide.webp<img class="cs-art" src="img/harbor-night-wide.webp" alt="" width="1584" height="672" loading="lazy" decoding="async">
How to fix
How to fix
<img src="hero.jpg" srcset="hero-400.jpg 400w, hero-800.jpg 800w" sizes="(max-width: 600px) 400px, 800px">
Structured data

Structured data is valid: Organization, WebSite, MobileApplication.

Organization, WebSite, MobileApplication

3 types: Organization, WebSite, MobileApplication

Rich result eligibility

Eligible for rich results via Organization.

Organization

1 type: Organization

Link distribution 50 resources

50 internal and 0 external links.

50 internal, 0 external

50 internal, 0 external

Link rel attributes

Outbound link rel attributes look appropriate.

Image alt text

All images carry an alt attribute.

Image dimensions

All images declare width and height.

Image formats

No heavy legacy image formats found.

6 already in a modern format

Image loading

Image loading strategy looks sound.

Broken links 15 checked

All 15 checked links resolve.

What to fix first

Ranked by impact against effort, the top of this list buys the most for the least work.

1
✕ Critical Largest Contentful Paint is 5.2s (lab data), above the 2.5s target and in the poor range.
Optimise the hero image, remove render-blocking CSS and JS, and improve server response time.
moderate
2
! Recommended 2 other spellings of this address do not lead here, so search engines can treat them as separate pages and split the ranking between them.
Redirect every spelling (http and https, with and without www) to https://sayforth.app/ with a single 301.
quick fix
3
! Recommended 1 in-page link points to a section that does not exist, so clicking it goes nowhere.
Add the matching id, or correct the link.
quick fix
4
! Recommended 2 links use non-descriptive anchor text, which tells neither readers nor engines where it leads.
Describe the destination: "read our grinder guide" rather than "click here".
quick fix
5
! Recommended 2 files have cache lifetimes short enough that returning visitors download 862 KB again.
Serve static assets with a long max-age and a content hash in the filename, so a new version gets a new URL rather than a short expiry.
quick fix
6
! Recommended 11 large images are served at one fixed size, so phones download desktop-sized files.
<img src="hero.jpg" srcset="hero-400.jpg 400w, hero-800.jpg 800w" sizes="(max-width: 600px) 400px, 800px">
moderate
7
· Notice The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
quick fix
8
· Notice No structured data describes what this page is about.
Describe the page with the type that fits it, Article for writing, Product for a product, FAQPage for questions and answers. Boilerplate like Organization and BreadcrumbList identifies the site, not the page.
quick fix
9
· Notice sayforth.app has no DMARC record, so mail servers have no instruction for mail that fails SPF or DKIM. Gmail and Yahoo require one from bulk senders.
Publish a TXT record at _dmarc.sayforth.app, starting with v=DMARC1; p=none; rua=mailto:[email protected] to collect reports, then tighten to quarantine or reject.
quick fix
10
· Notice No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.
Mark up question-and-answer content as FAQPage, or step-by-step content as HowTo.
moderate
11
· Notice No llms.txt. AI coding agents have no curated map of this site.
A markdown file at /llms.txt listing your most useful pages with one-line descriptions. It does not affect how AI assistants cite you in answers, and nobody has shown that it does. What it helps is agents reading your documentation directly: Anthropic supports it, Perplexity uses it to choose pages, and Cursor, Continue and Cline navigate docs with it. Worth doing for a documentation or API site, and safe to skip otherwise.
quick fix
12
· Notice No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
quick fix

Score breakdown

How each area scored. Categories that could not be measured are excluded rather than counted as zero.

Indexability & Crawling39 checks · 6 issues
86
On-Page Content & Structure22 checks · 3 issues
96
Core Web Vitals13 checks · 3 issues
73
Schema & Rich Snippets2 checks · 0 issues
100
Media & Links10 checks · 3 issues
83
Overall scoreGrade A · 71/88 passed
87