Homeeia-international.org
eia-international.org
For press, decks, and citations.
verdict counts19 pass5 warn21 fail30 n/a·method v1.2.0·scanned 2026-04-28
Built by Charity web design· detected via regex (99% confidence)
Web Standards · all applicable pillars passed
The table-stakes layer — every site either meets these or doesn’t. The Web Quality score is computed only when Web Standards passes.
Functional
pass3/3
Preconditions for being scored at all — the site responds, isn't on a phishing blocklist, and isn't a parked / for-sale page.
- Site respondspreconditionHTTP 200
- Not on safe-browsing blocklistnot measured — dbl_query_failed
- No deceptive redirectpreconditionFinal host matches requested (eia-international.org)
- No critical mixed contentNo mixed content detected
Security
fail4/5
The minimum security baseline every site on the modern web should meet — valid TLS, baseline email auth, no exposed admin surfaces.
- Valid TLS certificatessl_days_remaining=364.99985944444444, not_after=2027-04-28T05:00:50.000Z, source=url_scanner
- No exposed sensitive pathsfindings={"path":"/wp-admin","status":200}|{"path":"/wp-login.php","status":200}|{"path":"/admin","status":200}, total_checked=6
- DMARC publishedpresent=true, policy=quarantine
- SPF record presentpresent=true, raw="v=spf1 a mx include:servers.mcsv.net include:spf.protection.outlook.com include:spf.mandrillapp.com ip4:54.240.7.32 include:spf.hornetsecurity.com include:_spf.smtp.mailtrap.live include:_spf.intacct.com -all", qualifier=hardfail
- No WordPress user enumerationexposed=false
Accessibility
fail2/3
The minimum WCAG-aligned accommodations every site owes the humans who land on it — readable contrast, alt text, navigable structure.
- Image alt text coveragelighthouse_score=1, failing_count=0
- Sufficient color contrastlighthouse_score=0, failing_count=7
- Valid heading hierarchylighthouse_score=1
Identity
pass3/3
Whether the site is honest about who runs it and how a visitor can reach a real human.
- Operator is identifiableOrganization schema or About page detected
- At least one contact channelContact channel detected (page link, tel:, widget, or address)
- Branded domain emailbranded=true, provider=generic
In plain English · 7 questions, drilling down to the 98 factors
A reader-first rollup. Each card maps to the underlying factors — click to expand, or scroll for the full technical breakdown.
Can people find this site?
fail486 of 8 failing — expand to see which.2 pass
· 6 fail · 7 n/a
Can people find this site?
fail48- Hidden labels that explain your business to GoogleBehind the scenes, your pages can carry small tags that tell Google whether you're a restaurant, a dentist, or a law firm — and your hours, prices, and reviews. Without them, Google has to guess, and the rich result with stars and photos goes to a competitor instead.
- A clear headline on every pageEvery page should announce, in one obvious sentence, what it's about. When that's missing, Google and skim-reading visitors both lose the thread of what you do.
- Whether your behind-the-scenes labels are validThe hidden tags that describe your business to Google only work if they're written correctly. A typo or wrong format and Google ignores them, so the stars, hours, and prices never show up next to your listing.
- A trail showing where visitors are on your siteThose little 'Home > Services > Teeth Whitening' trails help Google understand how your pages connect, and they often appear right inside your search result. Without them, your listing looks plainer than competitors'.
- Whether you're listed with the Better Business BureauOlder customers and people considering a big-ticket purchase still check the BBB. An accreditation badge — or just a clean profile — quietly answers the question 'is this business real and reachable if something goes wrong?'
- How well your site feeds AI the right factsWhen ChatGPT or Perplexity describes your business, they're pulling from the structured details on your site. The thinner those details, the more the AI guesses — and the more often it gets your hours, prices, or services wrong.
- How your site appears when shared or in search resultsThe headline, blurb, and image that show up when someone posts your site on Facebook, sends it in iMessage, or sees it in Google. If they're missing or wrong, you look unfinished or attract the wrong clicks.
- How easy it is to reach your deepest pagesIf a customer or Google has to click five or six times from your homepage to find a service or product page, most never make it. Important pages should be two or three clicks away, max.
- A map of your site for search enginesGoogle needs a list of every page you want it to find, plus a note about which ones to skip. Without it, parts of your site quietly go missing from search results.
- Common questions answered in a Google-friendly wayWhen your FAQs are formatted the way Google likes, your answers can show up directly in search — sometimes before anyone even clicks. That's free real estate competitors are taking from you.
- Telling Google which language a visitor should seeIf you serve customers in more than one language or country, your site needs to tell Google which version is for whom. Otherwise a Spanish-speaking customer might land on your English page and bounce.
- Visitor privacy on hostile networksHides which website a visitor is opening from coffee-shop WiFi, corporate proxies, and government censors. It's a newer feature, so having it on is a real sign your site is keeping up with the modern web.
- A summary file for AI assistantsChatGPT, Claude, and Perplexity look for a small text file at /llms.txt to understand what your business is and what to say about it. Without it, they guess, and the guess is often wrong.
- Whether you're letting AI assistants read your siteYour site can quietly tell ChatGPT, Claude, and Google's AI to stay out — or to come in. If you're blocking them by accident, you're invisible when customers ask AI for a recommendation in your category.
- A direct line for AI assistants to your businessA small file you can publish lets AI tools talk to your site directly — checking availability, prices, or booking. Without it, you're missing out as customers shift from Googling to asking ChatGPT.
Is it safe to visit?
fail751 of 3 failing — expand to see which.2 pass
· 1 fail · 18 n/a
Is it safe to visit?
fail75- Private files aren't open to the publicThings like login pages, admin panels, and developer files should never be reachable by a stranger typing a guess into their browser. When they are, they become the front door for an attack.
- Your padlock isn't about to expireThe little padlock next to your address bar comes from a certificate that has to be renewed on a schedule. If it lapses, every browser slams a full-screen red warning in front of your customers and they bounce.
- WordPress isn't leaking your usernamesA default WordPress setting publishes a list of every login name on your site, which attackers feed straight into password-guessing tools. Turning it off takes one plugin or one line of config.
- Browser-level protections for visitorsHidden settings your site sends to a visitor's browser to block common attacks like fake login overlays, hijacked sessions, and content sniffing. Modern hosting platforms set them by default; older custom-built sites often don't.
- Your domain can't be quietly hijackedAn extra signature on your domain settings that stops attackers on shared WiFi or shady networks from rerouting your customers to a fake version of your site. Most domain registrars offer it as a one-click toggle.
- Only your approved vendors can issue your padlockA short list at your domain registrar that names which companies are allowed to issue security certificates for your site. Without it, a sloppy or compromised certificate vendor anywhere in the world could mint a fake one for your domain.
- Your site is on the browser-baked-in safe listAn opt-in list shipped inside Chrome, Safari, and Firefox themselves. Once your domain is on it, browsers will never let a visitor fall back to an unencrypted connection — even before they've ever visited you.
- Your site uses up-to-date encryptionOlder versions of the encryption that powers the padlock have known holes and were retired by every major browser years ago. If your server still accepts them, security scanners and payment processors will start flagging you.
- Forgotten subdomains aren't an open doorIf you ever spun up something like blog.yoursite.com or shop.yoursite.com and later abandoned it without cleaning up the DNS, a stranger can sometimes claim that address and put their own content under your name.
- Your domain isn't on a spam blocklistAnti-virus tools, email filters, and corporate firewalls share lists of domains tied to malware or scams. If yours lands on one — even by mistake — your emails go to spam and your site gets blocked at offices and schools.
- The padlock uses strong, modern mathInside every encrypted connection there's a recipe — newer recipes are bank-grade, older ones have known weaknesses. If your server still falls back to the old ones, security scanners and cyber-insurance audits will flag it.
- Old recordings stay locked even if a key leaksIf someone ever steals your server's master key, well-built encryption still protects every conversation that happened before the theft. Without it, an attacker who quietly recorded traffic for years can suddenly read all of it.
- Your padlock isn't using outdated keysThe certificate behind your padlock is signed with a kind of math that has to keep up with the times. Old, short keys are being phased out — sites still using them will start showing warnings in browsers.
- Your padlock loads cleanly on every deviceBrowsers can usually paper over a half-installed certificate, but phones, apps, and older email clients can't — they'll show an error and refuse to connect. This is one of the most common silently-broken setups on the web.
- Visitors connect faster on the first clickA small efficiency where your server checks once that the certificate is still valid and shares the answer with everyone, instead of every visitor's browser making its own trip across the internet to ask. Faster page loads, better privacy.
- Your certificate is publicly loggedEvery legitimate certificate today gets recorded in a public ledger so fake ones get caught quickly. Browsers refuse to trust certificates that skip this step, and yours needs at least two log entries to clear the bar.
- Future-proof against tomorrow's computersResearchers worry that quantum computers, when they arrive, could crack today's encrypted recordings after the fact. The newest encryption recipes already protect against that — and Chrome and Cloudflare turned them on in 2024.
- Your padlock renews on a healthy scheduleShort-lived certificates that auto-renew are the new normal — they prove your renewal automation works and limit the damage if a key ever leaks. Multi-year certificates from old paid vendors are increasingly seen as a smell.
- Strict mode for your padlock checkAn advanced setting that tells browsers to refuse the connection if the freshness check on your certificate goes missing, instead of quietly accepting it. Rarely turned on — when it is, it's a clear sign someone competent runs the server.
- Your padlock comes from a reputable vendorSome certificate vendors have been kicked out of browsers in the past for sloppy practices. Sticking with a well-known name — Let's Encrypt, DigiCert, Cloudflare, Google, Sectigo — means your padlock keeps working on every device for years.
- Your site finishes its handshake quicklyBefore a page can even start loading, the browser and server have a quick back-and-forth to set up the encrypted connection. When that takes too long, every first-time visitor feels the lag — and Google notices it too.
Is it fast?
fail625 of 11 failing — expand to see which.4 pass
· 2 warn · 5 fail · 1 n/a
Is it fast?
fail62- Your site uses the newest connection styleThe latest version of the web's delivery protocol shaves real time off how fast your site feels, especially on spotty mobile networks. It's a free upgrade that better hosts and CDNs already include.
- Reachable on the modern internetA growing share of phone and home networks now use the newer addressing system. Sites stuck on the old one get a small but real ranking nudge against them and load slower for those visitors.
- Your photos are saved in modern formatsOlder photo formats can be five times heavier than newer ones, so your homepage drags on a phone and Google notices. Most hosts and platforms can convert your images automatically.
- Your text shows up while fonts loadIf custom fonts aren't set up right, your headlines stay blank for a second or two — visitors see a flash of nothing where your name should be, then bounce. The fix is one line of code at the font.
- Photos lower on the page wait their turnWhen every image loads at once, the top of your page stalls because the phone is busy fetching pictures nobody can see yet. Loading them as a visitor scrolls is a one-line fix that makes the first screen pop in faster.
- How fast your site loads on a phoneGoogle's mobile-first index means slow sites rank lower in search and lose visitors before the page paints. Most fixes are configuration changes, not rebuilds.
- How fast your site loads on a laptopEven if most visitors are on phones, a sluggish desktop experience hurts the customers most likely to fill out a long form, book a service, or buy something expensive.
- How real visitors actually experience your speedGoogle quietly collects loading times from actual Chrome users on your site and uses that — not lab tests — to decide your search ranking. If real visitors are seeing slow pages, your rankings already feel it.
- Your site uses a modern web connectionAn older connection style makes every image, font, and script load one after another instead of together — so your phone visitors wait longer than they should. Flipping this on is usually a single setting at your host.
- Pages get squeezed before they're sentWithout compression, your visitors download files that are roughly four times bigger than they need to be — burning their data plan and your search ranking. Every modern host supports this; it's almost always just a checkbox.
- Your homepage isn't bloatedA homepage that weighs several megabytes punishes anyone on cell service and silently knocks down your Google ranking. Usually the bulk is one giant hero image or a stack of unused plugins.
- You're not shipping code visitors don't useThemes and page builders often ship piles of features your site never uses, and the visitor's phone has to download all of it anyway. Trimming this is the single biggest speed win on most small-business sites.
Is the business real?
fail555 of 10 failing — expand to see which.3 pass
· 2 warn · 5 fail · 4 n/a
Is the business real?
fail55- Your reviews on TrustpilotFor online stores and B2B services, Trustpilot is often the first place a cautious buyer checks. An empty profile, or no profile at all, makes it easy to walk away from the purchase.
- Your company page on LinkedInB2B buyers, recruits, and reporters all check LinkedIn before reaching out. An empty page, or no page, makes you look smaller and less established than you actually are.
- Your listing on Apple MapsEvery iPhone user who asks Siri for directions or searches Apple Maps is using this. If you're not listed, customers driving toward you literally can't find you.
- Your site can be saved to a phone's home screenWhen this is set up, customers who use your site often can pin it to their home screen like an app — which keeps you a tap away instead of buried in a search. It's a small file, but a missing one signals an older build.
- A contact form people can actually findA visible 'get in touch' form is the easiest way to turn a curious visitor into a lead. If finding one takes more than a few seconds, most people just close the tab.
- Your listing on Google Maps and searchWhen someone Googles your business name, this is the panel that shows your address, hours, photos, phone, and reviews. Without one, a customer ready to walk in the door may end up at a competitor.
- How long your site has been onlinePublic web archives quietly record when your site first appeared and how often it's updated. A site with years of history reads as established; a site that just popped up reads as a pop-up.
- Whether anyone's written about you latelyRecent news mentions — local paper, industry blog, podcast — tell both customers and Google that your business is active and relevant. A long silence reads as a business that's gone quiet.
- How long your domain has existedFirst-time visitors and fraud-detection systems both treat brand-new domains as suspicious by default. A domain registered yesterday tells the same story to humans and to spam filters.
- Whether you have a Wikipedia entryA Wikipedia page is one of the strongest signals to Google and AI assistants that you're a real, notable business. Most small businesses don't have one — but if you're big enough, missing it is a wasted credibility win.
- Your reviews on YelpPlenty of customers still check Yelp before booking, especially for restaurants, salons, and home services. No listing — or worse, a listing with two angry reviews and no replies — sends them to the next result.
- Your listing on Bing and Microsoft MapsBing powers search for millions of Windows users, ChatGPT search, and DuckDuckGo. Without a listing, you're invisible to all of them — and increasingly to AI tools that pull from Bing.
- Your site can work for a moment offlineModern sites can show a useful page even when a customer's phone briefly loses signal — like in an elevator or a bad reception area. Without it, they get a blank error and assume your site is broken.
- Whether your site is set up to take payments onlineIf you sell anything, customers expect to pay on the site without a phone call or invoice email. Missing checkout means lost sales the moment they hesitate.
Does it respect visitor privacy?
unscoredNothing measurable in this scan yet.
Does it respect visitor privacy?
unscored- Cookie consent banner for European visitorsIf anyone from the European Union or California can land on your site, the privacy laws there (GDPR and CCPA) require a banner that lets visitors say no to tracking. Fines start at thousands of dollars and the regulators don't warn you first.
- You have a privacy policy pageEvery state and country with a privacy law requires one, and Google, Apple, and Meta all refuse to run ads from sites without it. Missing this is the fastest way to get an ad account suspended or a lawyer's letter.
- You have a terms of service pageWithout one, you have no written agreement with the people using your site — which makes refund disputes, chargebacks, and copied content much harder to fight. A basic version takes an afternoon and protects you for years.
- How many outside companies you let watch your visitorsEvery analytics, ad, and chat tool you've added quietly shares your visitors' behavior with another company — and you're legally on the hook for what they do with it. Most small-business sites are running twice as many as the owner realizes.
- California privacy opt-out linkCalifornia law requires a clearly labeled "Do Not Sell or Share My Personal Information" link in your footer if you have visitors from California and use ad or analytics tools. The state Attorney General has been actively fining small businesses for missing it.
- What your site actually drops on visitors' phonesTools like Facebook Pixel and Google Ads quietly set tracking cookies the moment someone lands — often before they've agreed to anything. Under European and California law, that gap between landing and consent is what triggers fines.
Can everyone use it?
fail821 of 5 failing — expand to see which.4 pass
· 1 fail · 2 n/a
Can everyone use it?
fail82- Text is dark enough to readPale-gray text on white is the single most-cited problem in accessibility lawsuits. It also loses customers over 50, who already squint at their phones.
- Your site works for visitors with disabilitiesAbout one in four American adults has a disability the courts recognize, and your site is legally required to work for them under the Americans with Disabilities Act (ADA). Lawsuits over this hit small businesses every week, and most settle for $5,000 to $20,000.
- Your buttons and forms are labeled for screen readersWhen a button is just an icon — a magnifying glass, a hamburger menu, a shopping cart — a blind visitor's screen reader has nothing to announce unless someone added a hidden label. Without these, your contact form and checkout are unusable for them, and that's the kind of thing that ends up in a demand letter.
- Your photos have written descriptionsBlind visitors use software that reads pages out loud, and it can only describe a photo if you've written a short caption behind it. Missing alt text is the single most common item cited in accessibility lawsuits — and Google uses the same text to understand your images.
- Your headings are in a sensible orderScreen readers let blind visitors jump heading-to-heading the way you skim with your eyes — but only if the headings are nested in order. Out-of-order headings also confuse Google about what your page is actually about.
- You have an accessibility statementPosting one signals to the courts and to disabled visitors that you're taking accessibility seriously, and it's the first thing a plaintiff's lawyer looks for when deciding whom to sue. Roughly 4,000 small businesses got accessibility lawsuits last year.
- A way to skip past the menuVisitors who navigate by keyboard instead of mouse — usually because of a motor or vision impairment — otherwise have to tab through every nav link on every page just to reach your content. It's a small link at the top, and it's checked in nearly every accessibility audit.
Will email from this domain actually arrive?
fail683 of 8 failing — expand to see which.4 pass
· 1 warn · 3 fail · 5 n/a
Will email from this domain actually arrive?
fail68- A real tool for sending receipts and confirmationsOrder confirmations, password resets, and appointment reminders need to land in the inbox every single time. Sending them through a dedicated service — instead of straight from your website — is the difference between customers getting their receipt and them calling you confused.
- A clickable email link on your siteOn a phone, tapping an email address should open the mail app with everything pre-filled. When it's just text someone has to copy and paste, half of them give up.
- Your email is being forwarded, not hostedInstead of having a real inbox at your domain, mail to your address is being bounced over to a personal Gmail or Yahoo account. It works, but it's fragile — replies often look broken to customers, and the setup tends to fall apart as your business grows.
- What's actually running your emailWe can usually tell whether your email is on Google Workspace, Microsoft 365, your web host, or something custom. The platform behind your email shapes how reliable it is, how well it filters spam, and how easy it is for a new employee to get an inbox.
- Stops scammers from emailing customers as youWithout this, anyone can send phishing email pretending to be from your business — and your customers may receive it as if it really came from you. The fix is a few DNS records your email provider can usually add in under an hour.
- Lists who's allowed to email as your businessThis tells the rest of the internet which mail services — your provider, your booking system, your CRM — are actually permitted to send email from your domain. Without it, your real messages look as suspicious as a stranger's, and your invoices and confirmations start hitting spam.
- You email from your own domain, not GmailCustomers trust hello@yourbusiness.com a lot more than yourbusiness@gmail.com — the free address makes a real company look like a side hustle, and it's one of the fastest ways to lose a lead before they even reply.
- You get reports when someone fakes your emailWhen this is on, mail providers send you a daily summary of who tried to send email pretending to be your business — so you can spot impersonation attempts before customers do. Without it, scammers can spoof you for months and you'd never know.
- Proves your email actually came from youWhen your email arrives, this is the invisible signature that tells Gmail and Outlook it really came from your business and wasn't tampered with along the way. Without it, your messages are more likely to land in spam or get blocked.
- Keeps your email private in transitThese settings tell other mail servers they must use encryption when delivering email to you, so an attacker on the network can't read or quietly redirect it. Most small businesses don't have this turned on yet, and the bigger your domain gets, the more it matters.
- Shows your logo next to your emailsWhen this is set up, Gmail and Apple Mail can display your verified logo in the inbox next to messages from your business — which both looks more professional and helps customers spot real email from you versus impersonators.
- A real tool for sending newslettersIf your business sends marketing email, doing it through a service like Mailchimp or Klaviyo (instead of from your personal inbox) is what keeps you out of spam folders and out of legal trouble with unsubscribe rules.
- Your email setup is under a hidden limitThere's a behind-the-scenes ceiling on how many email tools can be authorized to send as your business at once. When you add too many — newsletter, booking, invoicing, helpdesk — you quietly cross the line and all of them start landing in spam.
Technical breakdown · deeper data behind the verdict
Categories
| Category | Grade | Score | Applicable |
|---|---|---|---|
| Privacy | — | 0/6 | |
| AI-readiness | F | 30 | 1/4 |
| SEO | F | 50 | 7/11 |
| Brand presence | F | 51 | 12/21 |
| Performance | D | 62 | 11/12 |
| Email health | D | 64 | 11/16 |
| Security | C | 75 | 3/21 |
| Accessibility | B | 82 | 5/7 |
Standards compliance
| Standard | Category | Verdict | Why it matters |
|---|---|---|---|
| HTTP/3 | Performance | failed | Real-world wins on mobile, lossy networks, and high-latency users. Cloudflare, Fastly, and CloudFront support it with a single toggle. |
| font-display | Performance | failed | Default browser behaviour blocks text rendering for up to 3 seconds while a web font downloads — that's a Flash of Invisible Text (FOIT) and it tanks LCP, especially on slow connections. `swap` fli… |
| WebP / AVIF | Performance | failed | Images are typically 50–70% of homepage weight. Cutting that in half with format conversion alone moves LCP, mobile data costs, and bounce rate measurably. Most CDNs (Cloudflare Polish, Fastly Imag… |
| Schema.org | SEO | failed | Schema is the single highest-leverage SEO change for AI search era. ChatGPT, Perplexity, Gemini, and Google Knowledge Graph all parse it. No schema = no rich snippets and weak AI citation. |
| Headings | SEO | failed | Search engines weight h1 heavily for page topicality. Screen readers use the heading tree to navigate. Failing this is rarely a render bug — it's almost always a CMS misconfig. |
| Breadcrumbs | SEO | failed | When Google shows breadcrumbs instead of the raw URL, mobile click-through measurably lifts. Breadcrumb schema is one of a shrinking set of rich-result types still supported (FAQ and HowTo lost the… |
| C2PA | AI-readiness | failed | Provenance is the new credibility signal in an AI-generated content world. Major newsrooms (BBC, NYT) and platforms (LinkedIn, TikTok via experiments) verify C2PA manifests; OpenAI signs DALL·E and… |
| WCAG AA | Accessibility | partial | WCAG AA is the conformance target referenced by the ADA, EAA, Section 508, and most procurement contracts. Falling short isn't just a UX problem — it's the standard plaintiffs' lawyers cite in acce… |
Site profile + facts
Classification driving applicability · deep detection
Site facts
8 factors marked n/a by applicability rules — see the factors table for per-factor reasons.
All factors
| # | Factor | Category | Verdict | Score | Evidence |
|---|---|---|---|---|---|
| 7 | Sensitive path exposure (.git, .env, /admin, xmlrpc.php, wp-login.php) | Security | fail | 25 | findings={"path":"/wp-admin","status":200}|{"path":"/wp-login.php","status":200}|{"path":"/admin","status":200}, total_checked=6 |
| 30 | HTTP/3 support | Performance | fail | 30 | supports_h3=false |
| 31 | IPv6 support | Performance | fail | 30 | aaaa_count=0 |
| 32 | Image optimization (WebP/AVIF) | Performance | fail | 30 | id=image-delivery-insight, lighthouse_score=0, displayValue=Est savings of 268 KiB |
| 36 | Font loading strategy (FOUT/FOIT/swap) | Performance | fail | 30 | id=font-display-insight, lighthouse_score=0 |
| 12 | Schema.org structured data presence | SEO | fail | 30 | structured_data_absent |
| 13 | H1 tag presence | SEO | fail | 30 | h1_count=0 |
| 39 | Schema.org type validity (parsed JSON-LD) | SEO | fail | 30 | total=0, valid=0 |
| 40 | Breadcrumb schema | SEO | fail | 30 | present=false |
| 61 | Better Business Bureau accreditation | SEO | fail | 30 | no_link_on_site |
| 45 | JSON-LD richness score for LLMs | AI-readiness | fail | 30 | org_complete=false, has_address=false, has_contact_point=false, has_same_as=false, has_content_type=false, breakdown={"coreOrg":0,"contact":0,"sameAs":0,"contentType":0} |
| 56 | Color contrast (WCAG AA) | Accessibility | fail | 30 | lighthouse_score=0, failing_count=7 |
| 60 | Trustpilot presence + rating | Brand presence | fail | 30 | no_link_on_site |
| 62 | LinkedIn Company Page (presence + employee count + follower count) | Brand presence | fail | 30 | no_link_on_site |
| 64 | Apple Maps presence (Apple Business Connect) | Brand presence | fail | 30 | no_link_on_site |
| 67 | Web App Manifest (manifest.json) | Brand presence | fail | 30 | present=false |
| 83 | Visible contact form on site | Brand presence | fail | 30 | detected=false, count=0 |
| 81 | Transactional email provider detected (from SPF includes) | Email health | fail | 30 | no SPF record |
| 84 | Mailto: direct contact link present | Email health | fail | 30 | Scored |
| 85 | Email forwarding service detected (improvmx, forwardemail, etc.) | Email health | fail | 30 | no MX records |
| 35 | Lazy loading on below-fold images | Performance | fail | 40 | id=image-delivery-insight, lighthouse_score=0, displayValue=Est savings of 268 KiB |
| 19 | Google Business Profile presence + rating | Brand presence | warn | 50 | found=true |
| 8 | Mobile PageSpeed score + Core Web Vitals (LCP, FCP, CLS) | Performance | warn | 63 | performance_score=62, lcp_ms=15989.621219193514, cls=0, components={"perf":62,"lcp":30,"cls":100} |
| 18 | Wayback Machine site age & last snapshot | Brand presence | warn | 65 | first_snapshot=1999-11-28T06:51:23Z, last_snapshot=1999-11-28T06:51:23Z, estimated_age_years=26.4, first_years_ago=26.414573766794685, last_days_ago=9647.92306832176 |
| 33 | Desktop PageSpeed score | Performance | warn | 67 | performance_score=67, lighthouse_score=0.67 |
| 76 | Email provider class (Workspace / 365 / Zoho / self-hosted / shared) | Email health | warn | 70 | provider=unclassified_enterprise, mx=clusterb.ignite.co.uk|clustera.ignite.co.uk, source=mx_classifier |
| 1 | DMARC enforcement | Email health | pass | 80 | present=true, policy=quarantine |
| 20 | News mentions in last 30 days | Brand presence | pass | 85 | news_mentions_count=9 |
| 53 | axe-core / WAVE accessibility scan | Accessibility | pass | 87 | accessibility_category=0.87 |
| 34 | Core Web Vitals from CrUX (Real User Monitoring) | Performance | pass | 90 | overall_category=AVERAGE, lcp_ms=2659, cls_x100=0, inp_ms=153, components={"name":"lcp","raw":2659,"score":70}|{"name":"cls","raw":0,"score":100}|{"name":"inp","raw":153,"score":100} |
| 57 | ARIA labels presence and validity | Accessibility | pass | 92 | total_aria_audits=22, applicable=12, passing=11, failing=aria-tooltip-name |
| 5 | SSL certificate validity & expiration window | Security | pass | 100 | ssl_days_remaining=364.99985944444444, not_after=2027-04-28T05:00:50.000Z, source=url_scanner |
| 6 | WordPress REST API user enumeration exposure | Security | pass | 100 | exposed=false |
| 9 | HTTP/2 support | Performance | pass | 100 | perf_http2=true |
| 10 | Compression (Brotli / gzip) | Performance | pass | 100 | perf_compression=br |
| 37 | Total homepage byte weight | Performance | pass | 100 | html_bytes=0, subresource_bytes=0, total_bytes=0, total_kb=0, sampled=0, total_refs=0 |
| 11 | Title, meta description, OG, Twitter cards, canonical | SEO | pass | 100 | title=true, description=true, og=true, twitter=true, canonical=true |
| 43 | Internal link depth (clicks from homepage to deepest content) | SEO | pass | 100 | max_depth=0, pages_fetched=0, pages_seen=1, capped_at=50 |
| 54 | Image alt text coverage | Accessibility | pass | 100 | lighthouse_score=1, failing_count=0 |
| 55 | Heading hierarchy validity | Accessibility | pass | 100 | lighthouse_score=1 |
| 17 | Domain age (RDAP / WHOIS) | Brand presence | pass | 100 | domain_age_years=26.4 |
| 21 | Wikipedia entity | Brand presence | pass | 100 | found=true, title=Erie International Airport, url=https://en.wikipedia.org/wiki/Erie_International_Airport |
| 3 | SPF record present and valid | Email health | pass | 100 | present=true, raw="v=spf1 a mx include:servers.mcsv.net include:spf.protection.outlook.com include:spf.mandrillapp.com ip4:54.240.7.32 include:spf.hornetsecurity.com include:_spf.smtp.mailtrap.live include:_spf.intacct.com -all", qualifier=hardfail |
| 75 | Branded domain email address (vs free Gmail/Yahoo) | Email health | pass | 100 | branded=true, provider=generic |
| 77 | DMARC aggregate reporting enabled (rua=) | Email health | pass | 100 | has_dmarc_reporting=true, audit_flag=true, derived_from_raw=true, source=derived_from_raw, dmarc_raw="v=DMARC1; p=quarantine; rua=mailto:chrisbuckler@eia-international.org" |
| 4 | Security headers (HSTS, CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy, X-Content-Type-Options) | Security | n/a | — | n/a:This platform doesn't allow site owners to set custom HTTP response headers, so security-headers grading isn't fair |
| 22 | DNSSEC validation | Security | n/a | — | fetch failed |
| 23 | CAA records | Security | n/a | — | fetch failed |
| 26 | HSTS preload list inclusion | Security | n/a | — | fetch failed |
| 28 | Subdomain takeover surface | Security | n/a | — | fetch failed |
| 29 | Spam / phishing blocklist presence | Security | n/a | — | not measured — dbl_query_failed |
| 38 | Largest unused JavaScript bundle | Performance | n/a | — | n/a:no_deferred_scripts |
| 14 | Sitemap.xml + robots.txt presence | SEO | n/a | — | n/a:This platform manages robots.txt centrally and doesn't let site owners customize it |
| 41 | FAQ / HowTo schema (where applicable) | SEO | n/a | — | n/a:not_applicable |
| 42 | hreflang for multi-language sites | SEO | n/a | — | n/a:single_language |
| 15 | llms.txt presence | AI-readiness | n/a | — | n/a:This platform doesn't let site owners publish arbitrary root-path files like /llms.txt |
| 16 | AI crawler robots.txt directives | AI-readiness | n/a | — | n/a:AI crawler directives live inside robots.txt, which this platform doesn't let site owners edit |
| 44 | AI plugin manifest (.well-known/ai-plugin.json) | AI-readiness | n/a | — | fetch failed |
| 46 | Cookie banner presence + CMP detection | Privacy | n/a | — | fetch failed |
| 47 | Privacy policy page presence | Privacy | n/a | — | fetch failed |
| 48 | Terms of service page presence | Privacy | n/a | — | fetch failed |
| 49 | Third-party tracker count | Privacy | n/a | — | fetch failed |
| 50 | CCPA "Do Not Sell or Share My Personal Information" link | Privacy | n/a | — | fetch failed |
| 51 | Cookie scan — actual cookies set on first load | Privacy | n/a | — | fetch failed |
| 52 | Accessibility statement page | Accessibility | n/a | — | fetch failed |
| 58 | Skip-to-content link | Accessibility | n/a | — | fetch failed |
| 59 | Yelp presence + rating + review count | Brand presence | n/a | — | n/a:Yelp listings are scored only for local-business sites |
| 63 | Bing Places | Brand presence | n/a | — | n/a:no_public_url_convention |
| 68 | Service Worker / PWA capability | Brand presence | n/a | — | n/a:Service Worker registration requires header control + a root-scope script, which this platform doesn't allow |
| 70 | Payment processors detected | Brand presence | n/a | — | fetch failed |
| 2 | DKIM signing | Email health | n/a | — | n/a:DKIM is only graded for sites that send mail (branded domain email present) |
| 24 | MTA-STS & TLS-RPT | Email health | n/a | — | fetch failed |
| 25 | BIMI + VMC | Email health | n/a | — | fetch failed |
| 80 | Email Service Provider (ESP) detected | Email health | n/a | — | n/a:ESP detection requires a newsletter signup to be present |
| 82 | SPF lookup count (10-limit deliverability check) | Email health | n/a | — | n/a:no SPF record |
Scores computed under method v1.2.0. See the methodology for the full factor list and per-factor specifications.