---
name: verify-minimum-5-distinct-images-on-homepage
description: "Count the useful images on a personal home page. Make sure five real visuals can be seen on a phone too."
category: Website QA Audit
stage: —
definitive_article: /website-qa-audit
status: complete
---

# Verify minimum 5 distinct images on homepage

A personal home page should show real people and work. This guide helps you count useful images without counting the same photo twice. Start with the full page on a phone and a large screen.

**The path:** Full page → Qualifying visuals → Distinct counts → Real gap list.

**Use this when:** A personal-brand home page is checked against the owned minimum-five-content-visuals house standard.

## Inputs
- The canonical home page and declared site role.
- The actual rendered visual inventory on desktop/phone and asset provenance records.
- Results from the relevant source/relevance checks, or access to perform them.
- Supported layout/media edit scope and approved real assets for missing sections.

## First-run prompt

> Count the supplied personal home page’s real useful visuals at desktop and phone widths. Deduplicate underlying content, exclude decoration, verify sources and the separate lead visual, then fix authorized gaps or return exact asset requests. State counts as house-policy results, not ranking proof.

## Steps
1. Confirm the personal-brand house standard applies. Five is a minimum editorial target for that page role, not a Google ranking rule or a reason to force five portraits onto every kind of site.
2. Inspect the entire home page at 1440×860 and 390×844, scrolling through lazy-loaded sections. Record what visitors can actually see, not every downloaded network image.
3. Identify useful content visuals: relevant real photos, real source screenshots or meaningful accurate diagrams allowed by the maintained article standard. Exclude logos, tiny icons, textures, spacers and favicons from this content count.
4. Deduplicate by underlying content. The same photo in two sizes or minor crops counts once; several nodes in one diagram count as one diagram. Distinct actual scenes or useful independent diagrams can count separately.
5. Verify each candidate’s relevance and provenance. Confirmed stock stand-ins or unknown-source proof photos cannot silently fill the total. A declared diagram teaches a concept; it does not pretend to prove a real event.
6. Count qualifying visuals separately for desktop and phone. A useful image hidden on mobile does not count for mobile. The five images can occur across the full page; the first viewport separately needs a meaningful readable lead visual.
7. For a shortfall, specify the actual section and source asset needed. Apply authorized useful asset/layout changes, preserving truthful context and reasonable load behavior. Do not generate cosmetic variants solely to inflate the number.
8. Recheck the normal canonical page and save the itemized counts, sources, viewports and remaining gaps. Passing five does not pass every visual-quality or site-audit check.

## Definition of done (QA checklist)

- [ ] The minimum-five house rule is applied to the intended page role.
- [ ] The counted list excludes decoration and repeats and includes only relevant supported visuals.
- [ ] Desktop and phone totals are based on actual visible full-page content.
- [ ] The first meaningful visual is checked separately from the full-page total.
- [ ] Shortfalls name real assets/sections, and no ranking or completed-proof claim comes from the count alone.

## Example(s)

**Fictional teaching example — no page was counted.** Maple Cycle’s founder page shows a workshop photo twice, a repair close-up, a source interview frame, a useful quote-process diagram and four social icons.

The count is four qualifying visuals: the repeated workshop scene counts once and the icons do not count. If the repair close-up is hidden on the phone, the phone count is three. The teaching fix requests another relevant real scene and restores the missing mobile visual; it does not duplicate the workshop photo again.

## Handoff and Content Factory context

The page owner receives the itemized count and missing assets. [Check section relevance](https://local-service-spotlight.github.io/task-library/?task=check-each-homepage-section-includes-relevant-image#task-check-each-homepage-section-includes-relevant-image) and [Check image provenance](https://local-service-spotlight.github.io/task-library/?task=ensure-no-stock-images-used#task-ensure-no-stock-images-used) provide the supporting quality checks.

This is a supporting quality check for the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. This check does not automatically execute all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Run when building or materially changing the home page. A continuing count monitor needs a real configured job and current asset record.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 2, gating 3 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/website-qa-audit
- Exact task: [Verify minimum 5 distinct images on homepage](https://local-service-spotlight.github.io/task-library/?task=verify-minimum-5-distinct-images-on-homepage#task-verify-minimum-5-distinct-images-on-homepage)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Website QA Audit](https://blitzmetrics.com/website-qa-audit/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Actual full-page visible assets, their rights/provenance and rendered counts require the site.