Valto DigitalLet’s talk

Valto Criteria 1.0 · October 5, 2026

How we score a website. In 100 points, all in the open.

You paste your website address, we read it the way Google does and give you a score from 0 to 100. Here is every point we check, what it is worth and why it matters to your business. Nothing hidden: the checker uses exactly this.

Check your site for freeSee the 24 points

01The formula/ 04

Six questions, each with its weight.

  1. 2001Security and trustDoes the browser let your clients in without warning them?
  2. 2502Findable on GoogleCan Google understand, index and show each page?
  3. 1003Shareable and understoodDoes it look right when shared, and can AI assistants read it?
  4. 1504Server speedDoes the server respond fast and send little?
  5. 2005ContactDo people who arrive with a question have somewhere to ask it?
  6. 1006Measurement and accessDo you know who visits, and can anyone use it on a phone?

Three rules

  1. 01

    Only what can be checked from outside

    We read the HTML and headers of up to four pages, like any new visitor who doesn’t accept cookies. What needs a real browser or human judgement doesn’t go into the score.

  2. 02

    What can’t be measured doesn’t count against you

    If a piece of data isn’t available, the point is marked “no data” and left out. The score is calculated on what was measured, and the report says how many points that was.

  3. 03

    Some failures cancel out the rest

    An invalid certificate or a site closed to Google caps the score, however well the rest does: no visitor gets to see the rest.

02The points/ 04

What we check, how and why.

01

Security and trust

Does the browser let your clients in without warning them?

20 points

  • Valid HTTPS certificate

    8 points
    How it’s measured
    We connect over HTTPS and check the certificate is valid, current and for that domain.
    When it counts
    Valid, or nothing. If it fails, the score can’t go above 39.
    Why it matters
    With an invalid certificate the browser tells your client the site isn’t safe before letting them in.

  • From http to https

    4 points
    How it’s measured
    We request the http:// version of the homepage and check whether it redirects to https://.
    When it counts
    Redirects: full. Answers unencrypted: nothing. If port 80 doesn’t answer, no data.
    Why it matters
    People who type your address without “https” must end up on the secure version, not an unencrypted copy.

  • HTTPS enforced (HSTS)

    3 points
    How it’s measured
    We look for the Strict-Transport-Security header on the homepage response.
    When it counts
    Present: full.
    Why it matters
    It tells the browser never to use the unencrypted version again, not even through an old link.

  • Protection headers

    3 points
    How it’s measured
    X-Content-Type-Options: nosniff, and frame-ancestors in the CSP or X-Frame-Options.
    When it counts
    Both: full. One: half.
    Why it matters
    They stop another page from framing yours to trick your clients, and the browser from misreading files.

  • No mixed content

    2 points
    How it’s measured
    We look for scripts, images, frames and stylesheets loaded over http:// inside https:// pages.
    When it counts
    No page with mixed content: full.
    Why it matters
    The browser blocks those resources or drops the padlock, and the page looks broken or unsafe.
02

Findable on Google

Can Google understand, index and show each page?

25 points

  • Page titles

    5 points
    How it’s measured
    We read the <title> tag of each page checked.
    When it counts
    10 to 70 characters on every page (the brand alone is fine on the homepage, up to 70): full. Present but too short or too long counts half.
    Why it matters
    It’s the blue link people click on Google. If it’s missing or cut off, they click another.

  • Description for Google

    5 points
    How it’s measured
    We look for <meta name="description"> with text on each page checked.
    When it counts
    Proportional to the pages that have it.
    Why it matters
    Without its own description, Google makes up the text shown under your name.

  • Main heading (H1)

    4 points
    How it’s measured
    We look for an <h1> with text on each page checked.
    When it counts
    Proportional to the pages that have it.
    Why it matters
    It’s the first thing search engines read to understand each page.

  • Open to search engines

    5 points
    How it’s measured
    We look for noindex in the robots tag and the X-Robots-Tag header, and whether robots.txt closes the whole site.
    When it counts
    No page closed: full. If the homepage or the whole site is closed, the score can’t go above 49.
    Why it matters
    A site closed to Google doesn’t show up on Google, however well built. It often happens when a test version goes live.

  • Canonical address declared

    2 points
    How it’s measured
    We look for <link rel="canonical"> on each page checked.
    When it counts
    Proportional to the pages that declare it.
    Why it matters
    It tells Google which version counts when the same page opens under several addresses.

  • Sitemap

    2 points
    How it’s measured
    We look for it in robots.txt and at /sitemap.xml.
    When it counts
    Found: full.
    Why it matters
    It’s the list of pages you hand Google so none slips through.

  • Structured data

    2 points
    How it’s measured
    We look for valid JSON-LD blocks on the pages checked.
    When it counts
    At least one valid block: full.
    Why it matters
    They tell Google and AI assistants, without guessing, what business you are, where and how to reach you.
03

Shareable and understood

Does it look right when shared, and can AI assistants read it?

10 points

  • Share preview

    4 points
    How it’s measured
    We look for og:title and og:image on each page checked.
    When it counts
    Proportional to the pages that have both.
    Why it matters
    It’s what shows when someone pastes your link on WhatsApp or social media: without it, a bare link.

  • Language declared and correct

    3 points
    How it’s measured
    We read the lang attribute on <html> and compare it with the language of the text.
    When it counts
    Declared and matching: full. Declared but not checkable: full. Missing or mismatched: half or nothing.
    Why it matters
    Search engines, translators and screen readers get the right signal.

  • Text readable without JavaScript

    3 points
    How it’s measured
    We count the words in the homepage HTML before any script runs.
    When it counts
    150 or more: full. 50 to 149: half. Fewer: nothing.
    Why it matters
    Many AI assistants and crawlers don’t run JavaScript: if the text only appears afterwards, the page is empty to them.
04

Server speed

Does the server respond fast and send little?

15 points

  • Server’s first response

    10 points
    How it’s measured
    Median time to first byte (TTFB) of the pages checked, measured from our server.
    When it counts
    Up to 800 ms: full. Up to 1,800 ms: half. Only deducted if at least two pages exceed 800 ms.
    Why it matters
    It’s the wait before anything starts to show. Google considers 0.8 seconds or less good.

  • Compression

    3 points
    How it’s measured
    We check whether the homepage arrives compressed (gzip, Brotli or Zstandard).
    When it counts
    Compressed: full.
    Why it matters
    The same page weighs three to ten times less: it arrives sooner on mobile data.

  • Redirects on arrival

    2 points
    How it’s measured
    We count the hops to reach the homepage from https://domain/.
    When it counts
    None or one: full. Two or more: nothing.
    Why it matters
    Each hop is another round trip before loading even starts.
05

Contact

Do people who arrive with a question have somewhere to ask it?

20 points

  • A way to reach you

    12 points
    How it’s measured
    We look for a form, a WhatsApp link, a phone, an email or a contact page in what we checked.
    When it counts
    Found: full.
    Why it matters
    People who arrive with a question and nowhere to ask it go to someone else.

  • Contact from the homepage

    8 points
    How it’s measured
    The same, but on the homepage: WhatsApp, phone, email or a form without searching.
    When it counts
    On the homepage: full.
    Why it matters
    Most people land on the homepage and decide there. One click less is one more enquiry.
06

Measurement and access

Do you know who visits, and can anyone use it on a phone?

10 points

  • Analytics installed

    4 points
    How it’s measured
    We look for Google Analytics, Tag Manager, Meta, Clarity and twenty other tools in the HTML.
    When it counts
    Seen: full. If there’s a cookie notice and none shows, no data: it usually loads after consent.
    Why it matters
    Without analytics you don’t know how many people visit, where they come from or whether they write.

  • Ready for mobile

    2 points
    How it’s measured
    We look for <meta name="viewport"> with width=device-width on each page.
    When it counts
    Proportional to the pages that have it.
    Why it matters
    Without that line, phones show the desktop version shrunk down.

  • Zoom allowed

    2 points
    How it’s measured
    We check whether the viewport blocks zoom (user-scalable=no or maximum-scale=1).
    When it counts
    Proportional to the pages that allow it.
    Why it matters
    People who need to enlarge text to read it can.

  • Images described

    2 points
    How it’s measured
    We count images without an alt attribute. An empty alt is correct for decorative images and doesn’t count against you.
    When it counts
    Proportional to the images that have it.
    Why it matters
    It describes the image to people who can’t see it and tells Google what it shows.

03The score/ 04

Four bands and two caps.

  1. 90 to 100

    Solid

    What can be measured from outside is in order. Next comes judgement: content, design and conversion.

  2. 75 to 89

    On track

    The foundation is good. Specific fixes raise the score without rebuilding anything.

  3. 50 to 74

    Important gaps

    There are failures costing visits or enquiries. They can almost always be fixed on the site you have.

  4. 0 to 49

    Urgent

    Something blocks the basics: getting in without warnings, showing up on Google or being able to reach you.

Caps

  • Invalid HTTPS certificate: the score can’t go above 39.
  • Homepage or site closed to search engines: the score can’t go above 49.

04What it doesn’t measure/ 04

What the score doesn’t tell you, said plainly.

  • Speed on your client’s phone

    We measure the server’s first response from ours. The real experience on a phone on mobile data (Core Web Vitals) needs a browser and goes into the diagnostic review.

  • Whether the text persuades

    A site can score 100 and sell nothing. Whether the message is clear, the price understandable and the design trustworthy is judgement, not arithmetic.

  • Contrast and full accessibility

    We check zoom, the viewport and image text. Contrast, keyboard use and screen readers need to be reviewed by hand.

  • The server’s security on the inside

    We see the certificate and the headers anyone can see. What’s inside (passwords, backups, content management versions) can’t be seen from outside.

All of that goes into the diagnostic review (RD$12,000, 3 business days). See the diagnostic review

Ours first

We applied it to valtodigitalrd.com first: paste it into the checker and see its score and what it’s missing. If a point can’t be met without cheating, we’d rather it showed.

Versions

  • 1.0 · October 5, 2026 First published version: six dimensions, 24 points and two caps.

How does yours score?

Free, in a few seconds, without giving your name or email.

Check your site for free
Message us on WhatsApp