SITEPULSE / INFORMATION & CAPABILITIES

From URL to a clear plan.

Start with one check. See category results, find weak spots and decide what to improve first.

Le texte complet ci-dessous est en anglais.

Illustration of identified issues and technical solutions

TECHNICAL SIGNALS. PRACTICAL MEANING.

Find the issue. Choose the next step.

Your report helps you understand what was found, why it matters and what deserves attention first.

A CLOSER LOOK

From numbers to your next step.

A look inside the report: category scores, loading metrics and specific findings. The small question mark explains each metric.

Analyse your website
SitePulse report screenshot showing scores and metric explanations
Actual SitePulse interface with sample data, not a measurement of your website.

What you submit

Use the public HTTPS address of your homepage or another accessible page. No installation or password is needed. Avoid personal tokens, private administration paths or sign-in details. For a client website, first ensure you have permission.

How the check works

SitePulse validates the address, identifies the public host, retrieves the page and collects technical signals. SSL, SEO, security configuration and resource checks follow. External metrics such as PageSpeed depend on an active integration and the provider’s response.

How to read the score

Categories are scored using available evidence. Missing sources are marked unavailable and excluded from the overall weighting. The overall result provides orientation; individual findings are the basis for choosing work. Compare checks under similar conditions.

What to do after the report

Start with high-risk, well-supported findings. Back up before changing anything, apply fixes and run another analysis. Each new check is a separate snapshot that helps determine whether a change had the intended effect.