The demo site: Atelier Démo
A fictional store with one product page, no accounts, orders or data collection. We control both versions and their assets. The before version has deliberately introduced issues; the links let you inspect the pages and their source in your browser. Demo pages are in French.
Three findings explained
SEO: very short title
Related Argos check : html.title
The title ‘Sac’ is only 3 characters long. The HTML check flags a very short title; it does not evaluate editorial relevance. A descriptive title helps identify a page in a browser tab or search result.
Before · HTML evidence
<title>Sac</title>
After · HTML correction
<title>Sac en coton réutilisable | Atelier Démo</title>
How to verify
Compare the title tags in both sources, then rerun the HTML check. Manually confirm that the title describes the product. This does not prove better Google rankings.
SEO: missing description
Related Argos check : html.meta.description.present
The before version has no meta description. The check can identify that absence. The correction provides a coherent summary, but a search engine may choose a different snippet.
Before · HTML evidence
<!-- No meta description -->
After · HTML correction
<meta name="description" content="Découvrez le sac en coton réutilisable Atelier Démo, ses dimensions et ses conseils d’entretien.">
How to verify
Find meta name="description" in the corrected source. Argos checks this technical signal; review the text for clarity and consistency with the content.
Accessibility: image without alternative text
Related Argos check : html.images.alt_coverage
The only image in the before version has no alt attribute: 1 out of 1 images lack an alternative. The HTML check detects the missing attribute. We add a description for this informative image; a decorative image would need alt="".
Before · HTML evidence
<img src="/demo/atelier/sac.svg" width="320" height="240">
After · HTML correction
<img src="/demo/atelier/sac.svg" width="320" height="240" alt="Sac en coton écru avec deux anses">
How to verify
Compare image attributes: 0 out of 1 images have a missing alt attribute after correction. Then assess the text with a human review and a screen reader; an attribute alone does not prove accessibility.
How should you prioritize these corrections?
- Confirm all three pieces of evidence on the product page and the checks actually completed. Here, no real purchase journey exists and no security risk has been assessed.
- Add alternative text for the informative image, then write the title and description. These simple changes can ship together; their order depends on your visitors and goals.
- Validate the delivered HTML, rerun an audit of the same page, then manually review content and keyboard access. On a real store, a blocked purchase would come before these improvements.
What this example does not demonstrate
Evidence covers only three HTML checks. HTTP headers, TLS, security services, browser measurements and Lighthouse scores are not measured here. The overall score is therefore intentionally absent. Both demo pages remain noindex to keep the fictional store out of search; this is intentional and unchanged after correction.
Your reports remain accessible through their private link and excluded from indexing. This public page is a separate editorial resource with no access to user reports.
When should you choose Argos?
What does Argos check on a page, and what are its limits?
Argos brings together the HTTP response, headers, HTML tags, browser measurements and available analysis services. Findings are grouped into performance, security, SEO and accessibility. It examines one public URL: it does not crawl the whole site, test signed-in areas or certify security or accessibility. Check coverage and unavailable modules before drawing conclusions.
What does Argos add to PageSpeed Insights or Lighthouse?
| Tool | Choose it to | Keep in mind |
|---|
| Argos | Get an initial cross-disciplinary diagnosis and actions to discuss with your provider: HTML, HTTP, TLS, browser and Lighthouse signals when available. | Argos uses its own score weights. Its score cannot be compared directly with Lighthouse and does not represent real visits. |
|---|
| PageSpeed Insights | Examine mobile and desktop performance using Lighthouse diagnostics and CrUX usage data when available. | Field data may be missing or apply to the origin instead of the page. Also review user journeys and server configuration. |
|---|
| Lighthouse | Investigate performance, accessibility, best practices and SEO diagnostics, then repeat measurements under controlled conditions. | Lab measurements vary and automated checks cannot validate real user journeys alone. |
|---|
References: PageSpeed Insights · Lighthouse
How do you turn a report into a correction order?
- First confirm that each finding applies: the analyzed page, evidence, completed module, context and intended behavior.
- Address blocked journeys and confirmed risks, then high-impact fixes that require little effort. Assign an owner and a validation criterion to each action.
- Analyze the same URL again under comparable conditions, then check the journey manually. A better score alone does not prove more sales or leads.
For a small business: start with the service page leading to a quote request. Check keyboard access and actual form submission, then address SEO tags and loading. Argos provides technical signals; it does not confirm delivery of a quote request or assess sales copy.
For a store: start with a representative product page. Manually check variant selection, adding to the cart and payment; fix blockers before optimizing images and tags. Audit key public pages separately: Argos does not simulate an order or test customer accounts.
See evidence and corrections in the public example report