lost end found — building for the internet, one app at a time

Title is 61 characters, over this audit's 60-character review point (a display heuristic, not a Google limit). Google may shorten it in results.

The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.

Front-load the distinctive topic and value so a shortened title still says what the page is. The first 57 characters read: "lost end found — building for the internet, one app at a …"

Description is 176 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).

The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.

Front-load the useful summary because Google may generate or truncate snippets by query and device.

Title found: "lost end found — building for the internet, one app at a time"

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Title "lost end found — building for the internet, one app at a tim…" says more than the site name.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Meta description found: "lost end found is an independent product studio. We design, build and ship software end to…"

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

All 10 indexable sampled pages have distinct titles.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

One canonical declaration found.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No conflicting noindex and cross-page canonical instructions.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No meta-refresh redirect.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No soft-404 pattern on sampled HTTP 200 pages.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

Canonical is a valid https URL. Its host is checked by the canonical consistency check.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

Indexability signals align across 10 sampled URL(s).

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

Flesch reading ease ≈ 53.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.

No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 431 publisher word(s).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

The audited page has about 431 words of main content.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

Text-to-HTML ratio is 15.7%.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

No placeholder text detected on crawled pages.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

No starter-template artifacts detected.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

No og:image tag.

This is what your link looks like when someone drops it into a chat or a feed. Right now the sampled pages don't provide it.

Add a 1200×630 og:image. Without one, a shared link renders as plain text in most apps. Next.js generates one from opengraph-image.tsx.

No og:image tag was found, so there is no image URL to fetch and verify.

This is what your link looks like when someone drops it into a chat or a feed. This check does not apply to the features observed in this sample.

Add <meta property="og:image" content="…"> with an absolute URL. This check then confirms the file actually loads.

No og:image tag was found, so its declared dimensions cannot be reviewed.

This is what your link looks like when someone drops it into a chat or a feed. This check does not apply to the features observed in this sample.

Add the og:image tag first, then declare og:image:width and og:image:height alongside it.

og:title: "lost end found — building for the internet, one app at a time"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:description: "lost end found is an independent product studio. We design, build and ship software end to…"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:url and og:type ("website") are set.

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

twitter:card is "summary".

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:site_name: "lost end found".

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

None of the 9 crawled inner pages declare BreadcrumbList schema.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add BreadcrumbList to inner pages — Google shows breadcrumbs in results and it clarifies site structure.

• https://lostendfound.com/contact/
• https://lostendfound.com/calendar/privacy/
• https://lostendfound.com/work/
• https://lostendfound.com/studio/
• https://lostendfound.com/services/front-end/
• https://lostendfound.com/blog/
• https://lostendfound.com/dmarc/
• https://lostendfound.com/floating-openclaw-chat/
• https://lostendfound.com/design-mirror-for-figma/

2 JSON-LD block(s) found on the homepage.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

All 14 JSON-LD block(s) parse cleanly.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

Identity schema present: WebSite, Organization.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

Content schema found: Offer, SoftwareApplication.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

1 heading level skip: H2 → H4 "Products".

Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.

Use the next level down for each subsection (H2 under H1, H3 under H2). If a heading level was chosen for its font size, keep the level and change the styling instead.

H1 found: "We build for the internet."

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

Exactly one H1 on the homepage.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

H1 reads "We build for the internet.".

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

8 headings, averaging 2.8 words — descriptive.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

4 H2 section(s) structure the page.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

All inspected element IDs are unique within their documents.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

20 of 20 visible images lack width and height attributes: openclaw-hero.png, tasks-hero.png, dmarc-hero.png, ….

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.

Set explicit width and height so the browser reserves the space before the image loads. Without them the page shifts as images arrive, which is what Cumulative Layout Shift measures. next/image sets them for you.

13 of 13 raster images are served only as PNG or JPEG: openclaw-hero.png, tasks-hero.png, dmarc-hero.png, ….

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.

Serve WebP or AVIF versions, which are usually 25–50% smaller at the same quality. Use <picture> with a WebP/AVIF <source> and the original as fallback, or an image CDN or framework image component that converts automatically.

None of the 20 visible images are lazy-loaded (no loading="lazy" and no lazy-loading library markers).

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.

Add loading="lazy" to below-the-fold images so the initial render doesn't wait on them. Keep the hero image eager.

All 20 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

All 12 sampled internal links return < 400.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

38 of 38 links have descriptive text or labels.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

No placeholder links on the audited page.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

All target="_blank" links carry rel="noopener".

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

Homepage links to 16 distinct internal pages.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

23 same-page fragment link(s) have source targets.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

None of the 27 images use srcset.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Serve smaller variants to phones with srcset/sizes (next/image handles this) — mobile users shouldn't download desktop-sized images.

No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Check computed font sizes in a browser across mobile widths.

No ARIA ID references found in the sampled HTML.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Verify rendered accessibility separately.

Viewport configured: "width=device-width, initial-scale=1".

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

The viewport lets users zoom.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

370 source controls have detectable names. Browser accessibility and CSS visibility were not tested.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

No hreflang tags — fine for single-language sites.

The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.

Only add hreflang if you publish the same content in multiple languages/regions.

Language declared: lang="en-GB".

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

Declared language (en) matches detected content language.

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

No apple-touch-icon link.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add a 180×180 apple-touch-icon so iOS home-screen bookmarks show your logo instead of a screenshot.

No web manifest linked.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Optional, but a manifest.json enables install prompts and better mobile integration.

No theme-color meta tag.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.

Favicon declared via <link rel="icon"> (/favicon.ico).

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Nothing to do here.