Rescan Report
Share Report
Copy Report Link
Rescan Report
Share Report
Copy Report Link
Export Report
45/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability59%Agent Easeof Use45%Security& Trust63%GEO, AIO, AEO62%SEO92%Performance35%Accessibility0%
  • AI Discoverability 59 out of 100
  • Agent Ease of Use 45 out of 100
  • Security & Trust 63 out of 100
  • GEO, AIO and AEO 62 out of 100
  • SEO 92 out of 100
  • Performance 35 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

EE Times - Connecting The Global Electronics Industry favicon

EE Times - Connecting The Global Electronics Industry

EE Times offers reliable electronics news, electrical engineering resources, podcasts, and industry events from Award-winning journalists. Visit to learn more.

Next step

Turn this report into a fix workflow

1 failed check is ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
59
Needs work2800
Discoverability
40
Priority fix400
Content Readiness
73
Needs work2100
Bot Access Control
63
Needs work300
Agent Ease of Use
45
Priority fix310View details
API
67
Needs work200
Auth
48
Priority fix100
Google Agentic Browsing
33
Priority fix010View details
GEO, AIO and AEO
62
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
63
Needs work1410View details
Security & Trust
63
Needs work1410View details
Performance
35
Priority fix1100
Performance
35
Priority fix1100
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

60 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Applicable HTML response is missing an enforcing Content-Security-Policy header.

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

40/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Applicable HTML response is missing an enforcing Content-Security-Policy header.

Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.

Agent Ease of UseGoogle Agentic BrowsingBrowser audit

Accessibility tree is not well-formed

100 Fail

Check name

Accessibility tree is not well-formed

Score

0/100

Status

fail

Device

desktop

Category

Google Agentic Browsing

Fix guidance

A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.

Evidence
{
  "description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}

AccessibilityAccessibilityBrowser audit

Certain ARIA roles must contain particular children

100 Fail

Check name

Certain ARIA roles must contain particular children

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Certain ARIA roles must contain particular children

Evidence
{
  "ruleId": "aria-required-children",
  "impact": "critical",
  "description": "Ensure elements with an ARIA role that require child roles contain them",
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag131",
    "EN-301-549",
    "EN-9.1.3.1",
    "RGAAv4",
    "RGAA-9.3.1"
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        "nav"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 81
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: ul, li[tabindex]"
    }
  ]
}

Sign in to see 54 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
45/100Level 2, Agent-LimitedCurrent report