ZU2B Pulse — How It Works Mockup
How It Works

Twelve metrics. One honest grade.

ZU2B Pulse scans your website the way a real visitor — and a search engine — would. No fluff, no vague scores. Just a letter grade for each dimension of your site and a ranked list of what to fix first.

Scan your site now
12Metrics checked
~15sScan time
A–FGrade scale
Top 5Fixes surfaced
The Process

From URL to report in four steps.

No setup, no account, no waiting. Paste a URL and get a full graded report.

1
Submit

Enter your URL.

Paste any public URL — website, bio link, landing page, or online store. No account required — just a URL and a click.

Takes 2 seconds
2
Crawl

We fetch and inspect your site.

Our scanner loads your homepage the way a real browser would — executing JavaScript, loading assets, and measuring every network request. We also check DNS records, SSL certificates, and server response headers.

3
Score

Each metric gets a letter grade.

We score 12 dimensions of your site independently, then combine them into an overall grade. Grades use the A–F scale with +/- modifiers so you can see exactly where you stand — not just a vague number out of 100.

A through F, with modifiers
4
Report

Plain-language fixes, ranked by impact.

Every report surfaces the top 5 things to fix, ordered by how much they’ll move your score. Each fix includes a concrete target — a specific file size, response time, or character count — so you know exactly what “fixed” looks like.

Actionable, not abstract
The Metrics

What we measure, and why it matters.

Each of the 12 metrics is graded independently. A strong performance score won’t hide a broken SSL certificate.

Performance
How fast your page loads for real users.
Checks: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), Cumulative Layout Shift (CLS), Time to First Byte (TTFB) — estimated from server response time and page weight. For precise values use Google Lighthouse or PageSpeed Insights.
Google uses Core Web Vitals as a ranking signal. Slow sites lose visitors before they read a single word.
LCP under 2.5s · TTFB under 200ms
On-Page SEO
Whether your page content is optimized for search engines.
Checks: Title tag, meta description, heading hierarchy, canonical URL, image alt text, keyword usage, internal linking.
Missing or duplicate meta tags directly reduce click-through rates from search results. Poor on-page signals mean lower rankings even on a technically sound site.
Title 50–60 chars · Description 150–160 chars
Security
Whether your site protects visitors and their data.
Checks: SSL/TLS certificate validity, HTTPS enforcement, HSTS header, mixed-content warnings, security response headers.
Browsers flag HTTP sites as “Not Secure.” Google penalizes them. Visitors leave.
Valid SSL · HTTPS everywhere · HSTS enabled
Mobile
How well your site works on phones and tablets.
Checks: Viewport meta tag, tap target sizes, font legibility, horizontal scroll, mobile render time.
Over 60% of web traffic is mobile. A site that works on desktop but breaks on phones is losing more than half its audience.
Tap targets ≥ 44×44px · No horizontal scroll
Accessibility
Whether your site is usable by everyone, including people with disabilities.
Checks: Image alt text, form labels, color contrast ratios, keyboard navigation, ARIA roles.
Accessibility is both a legal requirement in many jurisdictions and a quality signal — accessible sites are easier for everyone to use.
WCAG 2.1 AA · Contrast ratio ≥ 4.5:1
DNS
Whether your domain is configured correctly.
Checks: A/AAAA records, MX records, SPF/DKIM/DMARC presence, TTL values, nameserver health.
Misconfigured DNS causes email delivery failures, intermittent downtime, and slow page loads for visitors in certain regions.
SPF + DKIM + DMARC all present
Server Response Time
How quickly your server responds to the first request.
Checks: Time to First Byte (TTFB), server processing time, DNS lookup latency, connection time.
A slow server adds latency before a single byte of your page loads — and TTFB is a direct input into Google’s Core Web Vitals scoring.
TTFB under 200ms · Connection under 100ms
Core Web Vitals
Google’s specific set of user experience metrics — estimated from server response time and page weight.
Checks: LCP (loading), INP (interactivity), CLS (visual stability) — estimated against Google’s published thresholds. For precise values use Lighthouse or PageSpeed Insights.
Core Web Vitals are a confirmed Google ranking factor. Failing them can suppress your search visibility even if everything else looks fine.
LCP < 2.5s · INP < 200ms · CLS < 0.1
Broken Links
Whether any links on your page lead nowhere.
Checks: All anchor hrefs on the page are fetched and checked for 4xx/5xx responses.
Broken links frustrate visitors, signal neglect to search engines, and can cause crawlers to miss important pages.
Zero 404s · Zero 5xx errors
Technical SEO
Whether your site’s technical foundation supports search crawling and indexing.
Checks: robots.txt, XML sitemap, canonical tags, redirect chains, crawlability, structured data, page indexability.
Technical issues like blocked crawlers, missing sitemaps, or broken redirects can prevent search engines from indexing your pages entirely — regardless of content quality.
Sitemap present · robots.txt valid · No redirect loops
Search Engine Visibility
How well your site appears across major search engines.
Checks: Indexability signals, robots directives, canonical tags, structured data presence, Open Graph tags, and a preview of how your site may appear across Google, Bing, DuckDuckGo, Yahoo, and Yandex.
A site that ranks on Google but is accidentally blocked on Bing or missing structured data is leaving organic traffic on the table.
Indexable · Structured data present · OG tags complete
Browser Compatibility
Whether your site works correctly across modern browsers and devices.
Checks: Responsive viewport, charset declaration, HTTPS, MIME sniffing prevention, X-Frame-Options, content security policy, deprecated HTML, and touch-friendly targets.
A site that breaks in Safari or Edge loses real visitors. Browser compatibility signals also affect how crawlers render and index your pages.
Valid viewport · No deprecated tags · Security headers present
AI Search Readiness (estimated)
Whether AI assistants like ChatGPT, Perplexity, and Claude can find, read, and cite your site.
Checks: robots.txt rules for AI crawlers (GPTBot, PerplexityBot, ClaudeBot, Google-Extended), JSON-LD structured data presence and @type quality, semantic HTML and text density, and /llms.txt presence.
AI-powered search is growing fast. Sites that block AI crawlers or lack structured data are invisible to AI-generated answers — a new and increasingly important traffic source.
No AI bots blocked · JSON-LD present · Semantic HTML · llms.txt (optional)
FAQ

Common questions.

Everything you need to know about how the scanner works.

Scan your site →
Is this free to use?+
Yes — running a scan and viewing your full report is completely free. No account, no credit card, no catch. Free users can share a one-time report link via email capture. Pro and Agency plans add scan history, permanent shareable report links, and the embeddable scanner widget.
How accurate are the grades?+
Grades are based on real measurements taken at scan time. Performance metrics (LCP, INP, CLS) are estimated from server response time and page weight — not a full browser render. SEO checks follow Google’s published guidelines. Security checks follow OWASP and Mozilla Observatory standards.
Scores reflect your site at the moment of the scan. A slow server response at 2am will look different from a scan at noon.
Does scanning my site affect its performance?+
No. Our scanner makes the same requests a single visitor would make — one page load, a handful of asset requests, and a few header checks. It is indistinguishable from a normal visit.
Why does my grade differ from Google PageSpeed Insights?+
ZU2B Pulse grades 12 dimensions of your site, not just performance. A site can score A on performance and still get a B overall because of SEO gaps or security issues. PageSpeed Insights only measures performance and Core Web Vitals.
Can I scan a page other than the homepage?+
Yes — paste any public URL: a specific page, a bio link, a landing page, an online store, or even a social profile. Pulse scores what a visitor or search engine can publicly see. Note that some platforms such as Instagram, TikTok, Facebook, and LinkedIn limit what automated scanners can access — in many cases, that public visibility is exactly what impacts discoverability and user experience.
How do I fix the issues in my report?+
Each report includes a Top 5 Fixes section with plain-language instructions and a concrete target for each issue. The Smart Suggestions section adds context about why each issue matters and what “fixed” looks like in measurable terms.
How often should I scan my site?+
After any significant change — a new page, a plugin update, a hosting migration, or a design refresh. For active sites, a monthly scan is a reasonable baseline.
Why did my score change between scans?+
Performance scores reflect real conditions at the exact moment of the scan — and those conditions shift. Server load, CDN cache state, and third-party scripts (ads, analytics, chat widgets) all vary throughout the day. A scan at 2am on a quiet server will often look faster than one at noon under peak traffic.
Structural checks — SEO tags, SSL, security headers, mobile layout, accessibility — are stable and will not change between scans unless you change your site. Only performance metrics (speed, estimated LCP, TTFB) are time-sensitive. For the most comparable data over time, scan at a consistent time of day.

Ready to see how your site scores?

Free, instant, no account required.

Eraiki. Elkartu. Loratu.™ — a ZU2B product
Run a free scan
© 2026 PillarCopia Operating LLC, DBA ZU2B. All Rights Reserved.
Eraiki. Elkartu. Loratu.™