Scanned sites / static.app
SEO report for static.app
The latest Site Spider scan of static.app, with 1 scan on record. Each scan is at its own address, for example /domain/static-app/2026-09-29-1322.
Latest scan
Scanned 9/29/2026, 1:22:22 PM, finished 9/29/2026, 1:26:28 PM
Site: https://static.app/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 29, 2026 the Site Spider crawled 110 pages and 217 assets of static.app, starting from https://static.app/. It scored 92 out of 100, an excellent result. 7 of 16 checks found something to fix, led by meta descriptions (44), title tags (25), heavy assets (2); 7 checks passed. Most of the points went to meta descriptions (−3.4), title tags (−2.4), heavy assets (−1.2). 2 checks found something the score does not count, listed as noted. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.
Security review: Medium5 medium, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 110
- Assets fetched
- 217
- Status
- Completed
- Checks with issues
- 7 of 16
327 of 328 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 8 link destinations on other sites were checked.
- Title tags25 issues25 of 100 pages have title issues. 5 noindex or canonicalized pages excluded.−2.4 points
- Meta descriptions44 issues44 of 100 pages have meta description issues. 5 noindex or canonicalized pages excluded.−3.4 points
- HeadingsOK0 of 100 pages have heading issues. 5 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites16 noted0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 8 destinations checked.
- Redirects4 issues4 redirecting URLs, 1 of them chained.−0.2 points
- Non-200 responses1 issue8 URLs did not return a 2xx response. 5 of them are pages, 1 with an error status; the rest are assets or redirects.−0.1 points
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability4 issues4 of 105 indexable pages have indexability warnings.−0.4 points
- Image alt textOK0 of 126 image references have no alt attribute.
- Heavy assets2 issues2 assets larger than 500 KB among 217 fetched assets.−1.2 points
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage1 issue1 sitemap listing 100 URLs: 1 crawled page missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.−0.1 points
- Internal link countsOKInternal link counts for 105 pages.
- Thin contentOK0 of 100 pages have fewer than 200 words. 5 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this site sits among all scanned sites
1378 sites, median 80%, average 79%
static.app scores 92%, higher than 92% of the 1378 scanned sites. See the full ranking.
Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).
Internal link map
Loading the link map...
Fix plan
Written by gpt-4o-mini from the scan findingsThe site has actionable SEO fixes regarding redirects, non-200 responses, title and meta description issues, indexability warnings, and heavy assets. Prioritizing these changes will improve page visibility and user experience.
- 1
Fix Redirects
Why: Improve user access and search engine indexability by reducing unnecessary redirects.
How: Update the URLs to point directly to the final destinations. Eliminate chained redirects.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: Ensure all pages and assets are returning a 2xx status to optimize accessibility.
How: Identify and fix broken links and update or remove pages that return errors.
Checks: status-codes
- 3
Optimize Title Tags
Why: Improve click-through rates by ensuring that title tags are clear and within optimal length.
How: Revise over-length titles (above 60 characters) to be concise and descriptive.
Checks: titles
- 4
Enhance Meta Descriptions
Why: Increase search visibility and appeal through improved meta descriptions.
How: Shorten descriptions longer than 160 characters, ensuring they summarize page content effectively.
Checks: meta-descriptions
- 5
Address Indexability Warnings
Why: Ensure pages are easily indexed by search engines for greater visibility.
How: Review and fix the canonical URLs and add language attributes where missing.
Checks: indexability
- 6
Reduce Heavy Assets
Why: Improve page load times and user experience by optimizing large files.
How: Compress or replace large assets: images, scripts, and stylesheets.
Checks: heavy-assets
Generated automatically; verify each change against your own site before relying on it.
Security review
Written by gpt-4o-mini from 16 checks over the crawlThe website static.app has several critical security headers missing, making it vulnerable to various attacks, including cross-site scripting (XSS) and clickjacking. Immediate action is required to implement these protections and upgrade libraries to ensure user security.
- 0 high
- 5 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport SecurityMedium
Why it matters: Without HSTS, visitors can be intercepted when accessing the site without HTTPS.
Fix: Add the Strict-Transport-Security header: Strict-Transport-Security: max-age=31536000; includeSubDomains.
Evidence: HTTP Strict Transport Security
- 2
Absent Content Security PolicyMedium
Why it matters: Lack of a CSP allows any script to run, increasing XSS risk.
Fix: Implement a Content-Security-Policy header: Content-Security-Policy: default-src 'self';
Evidence: Content Security Policy
- 3
No Clickjacking ProtectionMedium
Why it matters: Pages can be embedded in a frame on other sites, risking user interaction manipulation.
Fix: Add the X-Frame-Options header: X-Frame-Options: DENY.
Evidence: Clickjacking protection
- 4
Missing Cookie FlagsMedium
Why it matters: Cookies are susceptible to theft, leading to account hijacking.
Fix: Update cookies to include: Secure, HttpOnly, SameSite=Strict.
Evidence: Cookie flags
- 5
Vulnerable JavaScript LibraryMedium
Why it matters: jQuery version 3.4.1 has known vulnerabilities that can potentially be exploited.
Fix: Upgrade jQuery to at least version 3.5.0 to patch vulnerabilities.
Evidence: Vulnerable JavaScript libraries
- 6
Missing MIME Sniffing ProtectionLow
Why it matters: Absence of MIME type restrictions can allow browsers to misinterpret file types.
Fix: Implement the X-Content-Type-Options header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 7
Lack of Referrer PolicyLow
Why it matters: Without a Referrer Policy, sensitive URL information may be leaked to external sites.
Fix: Set the Referrer-Policy header: Referrer-Policy: no-referrer.
Evidence: Referrer policy
- 8
No Permissions Policy DefinedInfo
Why it matters: Lack of a Permissions Policy may expose features like the camera or microphone unnecessarily.
Fix: Add the Permissions-Policy header: Permissions-Policy: geolocation=(self), microphone=(), camera=().
Evidence: Permissions policy
What the checks found
- FoundHTTP Strict Transport SecurityMedium
No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.
- https://static.app/ → no strict-transport-security
- https://static.app/download → no strict-transport-security
- https://static.app/pricing → no strict-transport-security
- https://static.app/login → no strict-transport-security
- https://static.app/signup → no strict-transport-security
- https://static.app/help → no strict-transport-security
- https://static.app/html-file-upload → no strict-transport-security
- https://static.app/free-website-hosting → no strict-transport-security
- https://static.app/image-hosting → no strict-transport-security
- https://static.app/static-form → no strict-transport-security
- https://static.app/upload-pdf → no strict-transport-security
- https://static.app/host-zip → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 105 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.
- https://static.app/ → no content-security-policy
- https://static.app/download → no content-security-policy
- https://static.app/pricing → no content-security-policy
- https://static.app/login → no content-security-policy
- https://static.app/signup → no content-security-policy
- https://static.app/help → no content-security-policy
- https://static.app/html-file-upload → no content-security-policy
- https://static.app/free-website-hosting → no content-security-policy
- https://static.app/image-hosting → no content-security-policy
- https://static.app/static-form → no content-security-policy
- https://static.app/upload-pdf → no content-security-policy
- https://static.app/host-zip → no content-security-policy
- FoundClickjacking protectionMedium
No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.
- https://static.app/ → no x-frame-options
- https://static.app/download → no x-frame-options
- https://static.app/pricing → no x-frame-options
- https://static.app/login → no x-frame-options
- https://static.app/signup → no x-frame-options
- https://static.app/help → no x-frame-options
- https://static.app/html-file-upload → no x-frame-options
- https://static.app/free-website-hosting → no x-frame-options
- https://static.app/image-hosting → no x-frame-options
- https://static.app/static-form → no x-frame-options
- https://static.app/upload-pdf → no x-frame-options
- https://static.app/host-zip → no x-frame-options
- FoundMIME sniffing protectionLow
No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.
- https://static.app/ → no x-content-type-options
- https://static.app/download → no x-content-type-options
- https://static.app/pricing → no x-content-type-options
- https://static.app/login → no x-content-type-options
- https://static.app/signup → no x-content-type-options
- https://static.app/help → no x-content-type-options
- https://static.app/html-file-upload → no x-content-type-options
- https://static.app/free-website-hosting → no x-content-type-options
- https://static.app/image-hosting → no x-content-type-options
- https://static.app/static-form → no x-content-type-options
- https://static.app/upload-pdf → no x-content-type-options
- https://static.app/host-zip → no x-content-type-options
- FoundReferrer policyLow
No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.
- https://static.app/ → no referrer-policy
- https://static.app/download → no referrer-policy
- https://static.app/pricing → no referrer-policy
- https://static.app/login → no referrer-policy
- https://static.app/signup → no referrer-policy
- https://static.app/help → no referrer-policy
- https://static.app/html-file-upload → no referrer-policy
- https://static.app/free-website-hosting → no referrer-policy
- https://static.app/image-hosting → no referrer-policy
- https://static.app/static-form → no referrer-policy
- https://static.app/upload-pdf → no referrer-policy
- https://static.app/host-zip → no referrer-policy
- FoundPermissions policyInfo
No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.
- https://static.app/ → no permissions-policy
- https://static.app/download → no permissions-policy
- https://static.app/pricing → no permissions-policy
- https://static.app/login → no permissions-policy
- https://static.app/signup → no permissions-policy
- https://static.app/help → no permissions-policy
- https://static.app/html-file-upload → no permissions-policy
- https://static.app/free-website-hosting → no permissions-policy
- https://static.app/image-hosting → no permissions-policy
- https://static.app/static-form → no permissions-policy
- https://static.app/upload-pdf → no permissions-policy
- https://static.app/host-zip → no permissions-policy
- FoundCookie flagsMedium
2 of 2 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.
- XSRF-TOKEN (set by https://static.app/) lacks Secure, HttpOnly, SameSite
- static_website_hosting_staticapp_session (set by https://static.app/) lacks Secure, SameSite
- FoundVulnerable JavaScript librariesMedium
1 library with published vulnerabilities: jQuery 3.4.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 3.4.1 in https://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js: CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- NoteThird-party scripts
Scripts run from 6 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)
- ajax.googleapis.com (40 script tags)
- worker-proud-shape-68f2.info-9b2.workers.dev (40 script tags)
- cdn.pulsetic.com (40 script tags)
- cdn.firstpromoter.com (40 script tags)
- challenges.cloudflare.com (3 script tags)
- www.google.com (1 script tag)
7 checks passed
- OKHTTPS
All 105 crawled pages were served over HTTPS.
- OKSoftware version disclosure
The Server header names a product without a version, and there is no X-Powered-By header.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
40 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKKeys and secrets in page code
No API keys, tokens or private keys were found in the sampled HTML and scripts.
- OKExposed files and listings
None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.
- OKSensitive paths in robots.txt
robots.txt does not point at admin, backup or private paths.
A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.
Earlier scans of static.app
No other scans of this site yet.
Sites scoring near static.app
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- wholebeingmassage.com93/100 · rank 82 · 45 pages
- calgarylandscaping.com93/100 · rank 82 · 32 pages
- www.thedapperdoughnut.ca92/100 · rank 90 · 13 pages
- www.thebridgerealty.com92/100 · rank 90 · 5,000 pages
- schadedistributing.com92/100 · rank 90 · 5,000 pages
- www.highcalldevelopment.com92/100 · rank 90 · 5 pages
This report was produced by the DIY SEO Hub Site Spider crawling static.app from its pages as published, the way a search engine does. It shows summary figures only.
Own static.app?
- Claim this site to manage the listing, hide it from the public lists, or keep it.
- Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming static.app. Removal needs no account and no proof of purchase.