HTTP 2001379 ms response436.6 KB5,969 words76 images84 links
92/100
Good
Executive Summary
This audit evaluated 29 signals across on-page SEO, technical SEO, performance, security, mobile rendering, structured data and E-E-A-T trust signals.
29
Total checks
21
Passed
0
Critical
8
Warnings
Category Scores
Technical SEO
100/100
GOOD
On-Page SEO
92/100
GOOD
Content
100/100
GOOD
Performance
92/100
GOOD
Security
52/100
POOR
Mobile & UX
100/100
GOOD
E-E-A-T
100/100
GOOD
Structured Data
100/100
GOOD
Site Crawl
16
Pages crawled
1
Broken links
16
Pages with issues
Issues & Findings
Every issue includes the problem, why it matters, and a concrete fix.
On-Page SEO (1 issue)
WARNING2 image(s) missing alt text ×2
Alt text improves accessibility and image SEO.
Security (6 issues)
WARNINGMixed content detected⏱ 1 hr
ProblemThe page is served over HTTPS but loads at least one resource (image, script, style) over HTTP.
Why it mattersBrowsers block mixed-content scripts and stylesheets and flag mixed-content images with a security warning. Some browsers show a broken padlock that destroys user trust.
How to fixFind every http:// URL in the page source and change to https:// (or use protocol-relative //). Most CMSes have a "search and replace in DB" tool for legacy posts.
WARNINGMissing X-Frame-Options header⏱ 30 min
ProblemA security or SEO header is missing from the page response.
Why it mattersModern browsers and crawlers expect security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). Missing them weakens defense-in-depth, sometimes blocks rich integrations, and signals to crawlers that the site isn't maintained.
How to fixAdd the named header in your web server config (nginx `add_header`, Apache `Header set`) or application middleware. Start with: `Strict-Transport-Security: max-age=31536000; includeSubDomains`, `X-Content-Type-Options: nosniff`, `Referrer-Policy: strict-origin-when-cross-origin`.
WARNINGMissing Strict-Transport-Security header⏱ 30 min
ProblemA security or SEO header is missing from the page response.
Why it mattersModern browsers and crawlers expect security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). Missing them weakens defense-in-depth, sometimes blocks rich integrations, and signals to crawlers that the site isn't maintained.
How to fixAdd the named header in your web server config (nginx `add_header`, Apache `Header set`) or application middleware. Start with: `Strict-Transport-Security: max-age=31536000; includeSubDomains`, `X-Content-Type-Options: nosniff`, `Referrer-Policy: strict-origin-when-cross-origin`.
WARNINGMissing X-Content-Type-Options header⏱ 30 min
ProblemA security or SEO header is missing from the page response.
Why it mattersModern browsers and crawlers expect security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). Missing them weakens defense-in-depth, sometimes blocks rich integrations, and signals to crawlers that the site isn't maintained.
How to fixAdd the named header in your web server config (nginx `add_header`, Apache `Header set`) or application middleware. Start with: `Strict-Transport-Security: max-age=31536000; includeSubDomains`, `X-Content-Type-Options: nosniff`, `Referrer-Policy: strict-origin-when-cross-origin`.
WARNINGMissing Content-Security-Policy header⏱ 30 min
ProblemA security or SEO header is missing from the page response.
Why it mattersModern browsers and crawlers expect security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). Missing them weakens defense-in-depth, sometimes blocks rich integrations, and signals to crawlers that the site isn't maintained.
How to fixAdd the named header in your web server config (nginx `add_header`, Apache `Header set`) or application middleware. Start with: `Strict-Transport-Security: max-age=31536000; includeSubDomains`, `X-Content-Type-Options: nosniff`, `Referrer-Policy: strict-origin-when-cross-origin`.
WARNINGMissing Referrer-Policy header⏱ 30 min
ProblemA security or SEO header is missing from the page response.
Why it mattersModern browsers and crawlers expect security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). Missing them weakens defense-in-depth, sometimes blocks rich integrations, and signals to crawlers that the site isn't maintained.
How to fixAdd the named header in your web server config (nginx `add_header`, Apache `Header set`) or application middleware. Start with: `Strict-Transport-Security: max-age=31536000; includeSubDomains`, `X-Content-Type-Options: nosniff`, `Referrer-Policy: strict-origin-when-cross-origin`.
Performance (1 issue)
WARNINGResponse compression not detected⏱ 20 min
ProblemNo Content-Encoding header (gzip, br, deflate) on the page response.
Why it mattersWithout compression, HTML/CSS/JS payloads are 3–5× larger than needed — slower TTFB, slower LCP, and wasted bandwidth.
How to fixEnable gzip and/or brotli at the web server level (nginx: `gzip on;` + `brotli on;`; Apache: mod_deflate / mod_brotli; Cloudflare: enabled by default).