HTTP 2001312 ms response491.5 KB4,729 words88 images377 links
85/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
20
Passed
0
Critical
9
Warnings
Category Scores
Technical SEO
100/100
GOOD
On-Page SEO
76/100
NEEDS WORK
Content
100/100
GOOD
Performance
92/100
GOOD
Security
60/100
NEEDS WORK
Mobile & UX
100/100
GOOD
E-E-A-T
85/100
GOOD
Structured Data
70/100
NEEDS WORK
PageSpeed Insights (lab)
Mobile
49
Perf
84
A11y
0
BP
92
SEO
LCP
4.5 s
CLS
0.048
TBT
850 ms
FCP
3.4 s
Desktop
45
Perf
81
A11y
0
BP
92
SEO
LCP
4.8 s
CLS
0.014
TBT
580 ms
FCP
1.1 s
Issues & Findings
Every issue includes the problem, why it matters, and a concrete fix.
On-Page SEO (3 issues)
WARNINGTitle too long (64 chars)⏱ 10 min
ProblemThe <title> tag is longer than 60 characters.
Why it mattersGoogle truncates titles around 60 characters in SERPs — anything past that is invisible to searchers and may also signal weak editorial discipline.
How to fixTrim the title to ≤60 characters. Lead with the keyword; move the brand to the end or drop it if space is tight.
WARNINGMultiple H1 tags (4)⏱ 20 min
ProblemThe page has more than one <h1> tag.
Why it mattersMultiple H1s split the topical signal and indicate the page has no single main subject. Modern HTML5 allows multiple H1s in <article>/<section>, but search engines still prefer one per page.
How to fixKeep one <h1>; demote the others to <h2> or <h3> to reflect the actual content hierarchy.
WARNING4 image(s) missing alt text ×4
Alt text improves accessibility and image SEO.
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`.