HTTP 2001661 ms response156.4 KB3,804 words20 images51 links
77/100
Needs Improvement
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
20
Passed
0
Critical
9
Warnings
Category Scores
Technical SEO
100/100
GOOD
On-Page SEO
92/100
GOOD
Content
100/100
GOOD
Performance
92/100
GOOD
Security
60/100
NEEDS WORK
Mobile & UX
100/100
GOOD
E-E-A-T
35/100
POOR
Structured Data
40/100
POOR
PageSpeed Insights (lab)
Mobile
95
Perf
100
A11y
0
BP
100
SEO
LCP
2.3 s
CLS
0
TBT
60 ms
FCP
1.5 s
Desktop
97
Perf
96
A11y
0
BP
100
SEO
LCP
0.9 s
CLS
0
TBT
80 ms
FCP
0.4 s
Site Crawl
17
Pages crawled
0
Broken links
17
Pages with issues
Issues & Findings
Every issue includes the problem, why it matters, and a concrete fix.
On-Page SEO (1 issue)
WARNINGMeta description too long (211 chars)⏱ 10 min
ProblemMeta description is longer than 160 characters.
Why it mattersGoogle truncates descriptions around 160 characters; the most important sentence ends up clipped.
How to fixTrim the description to ≤160 characters. Front-load the value prop and keyword; cut adjectives.
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).
Security (5 issues)
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`.
E-E-A-T (2 issues)
WARNINGNo About page detected⏱ 2 hrs
ProblemNo /about, /about-us, or equivalent page linked from the homepage.
Why it mattersGoogle's Quality Raters Guidelines explicitly look for About pages to assess Expertise, Authoritativeness, and Trust (E-E-A-T). YMYL (Your Money or Your Life) topics especially need this.
How to fixCreate an About page with: who the company/author is, what they do, where they're based, who the founders are (with photos and bios), and how to contact them.
WARNINGNo Privacy Policy detected⏱ 2 hrs
ProblemNo /privacy, /privacy-policy, or equivalent page linked from the homepage.
Why it mattersA privacy policy is legally required if you collect any personal data (cookies count) under GDPR, CCPA, and similar. Its absence is both an E-E-A-T negative and a regulatory risk.
How to fixPublish a Privacy Policy covering: what data you collect, why, how long you keep it, who you share it with, and how users exercise their rights. Link it from the footer.