Render | The cloud for builders

Title found: "Render | The cloud for builders"

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 is 31 characters, inside this audit's 15–60 review range.

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 "Render | The cloud for builders" 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: "Deploy and scale any app or agent from your first user to your billionth. Build faster on …"

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.

Description is 140 characters and inside this audit's 70–160 preview range.

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.

Placeholder text found: "coming soon". First occurrence: "…Shared filesystems are coming soon…" on https://render.com/shared-filesystems.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. Right now the sampled pages don't provide it.

Replace every placeholder before anything else on this list. Published placeholder text tells a reader the page is unfinished, and AdSense reviewers treat it the same way.

• https://render.com/shared-filesystems

The audited page has about 11 words of main content (navigation, header and footer excluded).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. Right now the sampled pages don't provide it.

Add substance: what the site is, who it's for, what problems it solves. This audit measures visible HTML; it does not measure rankings, traffic, or content originality. Note: if your content renders only via client-side JS, crawlers without JS (and this checker) can't see it — prefer server rendering.

Visible text is 2.2% of the HTML markup (scripts and styles excluded).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.

Text-to-HTML ratio is not a ranking factor, but a very low value often means deeply nested markup or content that only appears after JavaScript runs. Check the source-content checks before changing anything.

Title ("Render | The cloud for builders") and H1 ("Your fastest path to production for any workload") share no significant words.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.

Align them around the same core topic — mixed signals confuse both rankers and readers.

Not enough English prose to estimate readability (it needs about 100 words in three or more sentences).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.

Nothing to change for this check.

No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 11 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.

og:image:width / og:image:height are missing.

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Declare them (1200×630 recommended) so platforms render the preview immediately on first share instead of after re-scraping.

og:url is missing.

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Add og:url to complete the Open Graph basics.

og:title: "Render | The cloud for builders"

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: "Deploy and scale any app or agent from your first user to your billionth. Build faster on …"

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:image is set: "https://cdn.sanity.io/images/hvk0tap5/production/a3528e77b010804af14908fab79f826d66437620-%E2%80%A6"

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:image returns 200 (image/png).

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_large_image".

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: "Render".

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://render.com/about
• https://render.com/contact
• https://render.com/privacy
• https://render.com/sandboxes
• https://render.com/workflows
• https://render.com/docs/web-services
• https://render.com/shared-filesystems
• https://render.com/agents
• https://render.com/startups

3 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, Person.

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, FAQPage, SoftwareApplication, CollectionPage.

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.

H1 found: "Your fastest path to production for any workload"

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.

Heading hierarchy is sequential across 29 headings.

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 "Your fastest path to production for any workload".

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

Nothing to do here.

29 headings, averaging 4.1 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.

6 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.

2 of 2 visible images lack width and height attributes: 3685abbe6f2a9417bdffaad312cf6bada5565e35…, da728ea56fa69ca14fa79e6eec8825b88f535eda….

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.

Only 2 visible image(s) on the page, too few for lazy loading to change the initial load.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.

Nothing to change here. Once the page carries several images, add loading="lazy" to the ones below the fold.

All 2 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.

2 of 2 raster images have a WebP/AVIF source or come from a format-negotiating image service.

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.

3 external link(s) open in a new tab without rel="noopener".

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.

Current browsers already treat target="_blank" as noopener, so the remaining risk is limited to older browsers. Adding rel="noopener" keeps the opened page from controlling yours there too.

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.

118 of 119 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.

Homepage links to 57 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.

32 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.

8 of 1257 source controls lack a detectable name.

Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.

Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.

• https://render.com/docs/web-services

The viewport limits zoom: "width=device-width, initial-scale=1, maximum-scale=1".

Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.

Remove user-scalable=no and any maximum-scale below 2. People with low vision need to zoom to at least 200% (WCAG 1.4.4). Recent iOS ignores the restriction, but Android browsers apply it.

ARIA references point at IDs that do not exist on 1 sampled page(s), e.g. aria-controls="radix-_R_2jav5tpf9db_-content-files", aria-controls="radix-_R_2jav5tpf9db_-content-execute", aria-controls="radix-_R_2jav5tpf9db_-content-fork".

Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.

Connect ARIA references to unique existing IDs. If JavaScript adds the targets, verify the rendered accessibility tree.

• https://render.com/sandboxes

None of the 78 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.

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

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.

Not enough text on the page to tell which language it is written in.

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.

Nothing to change for this check. Confirm the lang attribute names the language most of the page is written in.

Language declared: lang="en".

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"> (/icon.svg?icon.00d01gt742wgb.svg?dpl=0c3ab04312c7).

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

Nothing to do here.