Scanned sites / loxias.ai / 2026-11-06-1826
loxias.ai scan from 2026-11-06 18:26:17 UTC DR 21
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-11-06-1826
Scanned 2026-11-06 18:26:17 UTC, finished 2026-11-06 20:59:50 UTC
Site: https://loxias.ai/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On November 6, 2026 the Site Spider crawled 4989 pages and 460 assets of loxias.ai, starting from https://loxias.ai/. It scored 96 out of 100, an excellent result. 10 of 33 checks found something to fix, led by heavy assets (6), meta descriptions (162), title tags (134); 11 checks passed. Most of the points went to heavy assets (−3.6), title tags (−0.3), meta descriptions (−0.3). 12 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. 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: Medium3 medium, 3 low and 2 info findings. See the security findings ↓
- Pages crawled
- 4989
- Assets fetched
- 460
- Status
- Completed
- Checks with issues
- 10 of 33
5,449 of 5,461 discovered URLs were fetched, 1 blocked by robots.txt, 1,544 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 211 link destinations on other sites were checked.
- Title tags134 issues134 of 183 pages have title issues. 4791 noindex or canonicalized pages excluded.−0.3 points
- Meta descriptions162 issues162 of 183 pages have meta description issues. 4791 noindex or canonicalized pages excluded.−0.3 points
- Headings2 issues2 of 183 pages have heading issues. 4791 noindex or canonicalized pages excluded.
- Broken links8 issues16 internal links point at 8 broken URLs.
- Links to other sites2 issues2 destinations answered with an error, 116 could not be determined (timeouts, rate limits or refusals), of 211 destinations checked.
- Redirects6 issues8 redirecting URLs, 2 of them chained.
- Non-200 responses8 issues16 URLs did not return a 2xx response. 15 of them are pages, 8 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability34 issues34 of 218 indexable pages have indexability warnings. 4756 pages noindex by design. 1 noindex page is listed in the sitemap, which asks search engines both to visit and to ignore it.−0.1 points
- Image alt textOK0 of 58060 image references have no alt attribute. 2 use an empty alt (decorative), which is fine.
- Heavy assets6 issues6 assets larger than 500 KB among 460 fetched assets. 7 documents over that size are listed but not counted: downloads are not page weight.−3.6 points
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage2 issues6 sitemaps listing 216 URLs: 0 crawled pages missing, 1 listed URL broken or redirecting, 0 reachable only via the sitemap.
- Internal link counts376 notedInternal link counts for 500 pages; 376 worth a look.
- Thin contentOK0 of 183 pages have fewer than 200 words. 4791 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format4,727 noted4727 of 4989 page URLs are harder to read, share or cache than they need to be.
- Canonicals4,791 noted4791 of 4974 pages have a canonical worth checking.
- Robots directives4,974 noted4974 pages carry a robots directive; 0 carry none.
- Anchor text20 noted20 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure120 noted120 of 183 pages could use the title, heading and snippet space better. 4791 noindex or canonicalized pages excluded.
- Image weight and alt length126 noted40 images over 100 KB; 86 with alt text over 100 characters.
- Response anomalies2 noted2 URLs answered in a way worth looking at.
- HTML and head validationOKAll 4974 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
- hreflang12,844 noted4824 of 4974 pages with hreflang have problems: 12844 findings.
- Structured dataOK4974 of 183 indexable pages carry structured data: BreadcrumbList (4972), ListItem (4972), Organization (4934), WebSite (4934), CollectionPage (4752). 0 pages with errors a rich result would fail on.
- Near duplicatesOKNo near duplicates among 183 pages with enough text to compare.
- Soft 404sOKNone of 4974 pages answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positions4 noted4 of 183 linked pages are linked only from the template, never from another page's content.
- PaginationOKNo page declares rel=next or rel=prev pagination.
- Headers and cookies2 noted2 cookies set by the site, 2 missing a protective flag; 14 response headers recorded across 5449 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 4974 pages; 4914 hold almost none (10 or less).
- JavaScript renderingNot checkedNot checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
- PageSpeed InsightsNot checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling119 noted119 words an English dictionary does not know, on 68 pages. Product names and jargon will appear here too.
Where this scan sits among all scanned sites
2873 sites, median 80%, average 79%
loxias.ai scores 96%, higher than 93% of the 2873 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 findingsYour site's health is excellent, but key fixes are needed for broken links, redirects, and content optimization. Focus on resolving these to enhance user experience and SEO performance.
- 1
Fix Broken Links
Why: 16 internal links point to broken URLs, affecting user experience and SEO.
How: Update or remove links to https://loxias.ai/es/new-loxias/ and https://loxias.ai/new-loxias/. Ensure they point to live content.
Checks: broken-links
- 2
Reduce Redirects
Why: Ensure better user experience and faster page loads by fixing 8 redirecting URLs.
How: Eliminate chained redirects and point seasonal redirects directly to final URLs.
Checks: redirects
- 3
Address Non-200 Responses
Why: 16 URLs are not returning a 2xx response, hindering access to content.
How: Identify causes of errors and fix or remove the problematic URLs.
Checks: status-codes
- 4
Optimize Title Tags
Why: 134 pages have title issues leading to potential SEO drawbacks.
How: Review and update title tags for duplicates and ensure they accurately reflect page content.
Checks: titles
- 5
Revise Meta Descriptions
Why: 162 pages have meta description issues which can reduce click-through rates.
How: Update meta descriptions for clarity and uniqueness, ensuring they are under the character limit.
Checks: meta-descriptions
- 6
Compress Heavy Assets
Why: Reducing the size of large assets can improve page load speeds.
How: Shrink or replace heavy documents and images larger than 500 KB to enhance performance.
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 crawlYour site has several security issues that need attention, particularly regarding protections against unauthorized access and data leaks. We recommend implementing strict transport security and setting proper headers to enhance overall security.
- 0 high
- 3 medium
- 3 low
- 2 info
- 1
Missing HSTS HeaderMedium
Why it matters: No HTML page sends HTTP Strict Transport Security (HSTS). Visitors could be intercepted on their first request if they type the site address without https://.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains
Evidence: HTTP Strict Transport Security
- 2
Missing X-Frame-Options HeaderMedium
Why it matters: Only 4 of 4974 HTML pages send X-Frame-Options. This increases susceptibility to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY
Evidence: Clickjacking protection
- 3
Missing Secure Cookie FlagsMedium
Why it matters: Cookies lack HttpOnly, Secure, and SameSite flags, potentially exposing them to theft and misuse.
Fix: Set Secure, HttpOnly, SameSite attributes for both cookies: wmc_ip_info and wmc_current_currency.
Evidence: Cookie flags
- 4
Missing X-Content-Type-Options HeaderLow
Why it matters: Without the X-Content-Type-Options: nosniff header, browsers may misinterpret files, leading to script execution risks.
Fix: Add the header: X-Content-Type-Options: nosniff
Evidence: MIME sniffing protection
- 5
Missing Referrer-Policy HeaderLow
Why it matters: No Referrer-Policy can expose the full URL of your pages during navigation, which might include sensitive data.
Fix: Add the header: Referrer-Policy: no-referrer
Evidence: Referrer policy
- 6
Third-Party Scripts Without Integrity ChecksLow
Why it matters: Running scripts from another domain without Subresource Integrity poses a risk if that domain is compromised.
Fix: Consider using a Content-Security-Policy to define trusted sources for scripts instead.
Evidence: Third-party scripts
- 7
Missing Permissions-Policy HeaderInfo
Why it matters: Absence of a Permissions-Policy can leave unsupported features enabled, potentially allowing injected scripts more access.
Fix: Add the header: Permissions-Policy: deny camera; deny microphone; deny geolocation
Evidence: Permissions policy
- 8
Sensitive Paths in robots.txtInfo
Why it matters: The robots.txt file lists a sensitive path (/wp-admin/) which can assist attackers in targeting your site.
Fix: Implement proper access controls for /wp-admin/ instead of relying on robots.txt.
Evidence: Sensitive paths in robots.txt
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://loxias.ai/ → no strict-transport-security
- https://loxias.ai/traditional-reports/ → no strict-transport-security
- https://loxias.ai/automated-reports/ → no strict-transport-security
- https://loxias.ai/industry/ → no strict-transport-security
- https://loxias.ai/sparks/ → no strict-transport-security
- https://loxias.ai/license/all-ears/ → no strict-transport-security
- https://loxias.ai/license/nebula-social/ → no strict-transport-security
- https://loxias.ai/license/pythia/ → no strict-transport-security
- https://loxias.ai/license/brandwatch/ → no strict-transport-security
- https://loxias.ai/license/socialinsider/ → no strict-transport-security
- https://loxias.ai/our-methodology/ → no strict-transport-security
- https://loxias.ai/about/ → no strict-transport-security
- FoundClickjacking protectionMedium
4 of 4974 HTML pages send 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://loxias.ai/ → no x-frame-options
- https://loxias.ai/traditional-reports/ → no x-frame-options
- https://loxias.ai/automated-reports/ → no x-frame-options
- https://loxias.ai/industry/ → no x-frame-options
- https://loxias.ai/sparks/ → no x-frame-options
- https://loxias.ai/license/all-ears/ → no x-frame-options
- https://loxias.ai/license/nebula-social/ → no x-frame-options
- https://loxias.ai/license/pythia/ → no x-frame-options
- https://loxias.ai/license/brandwatch/ → no x-frame-options
- https://loxias.ai/license/socialinsider/ → no x-frame-options
- https://loxias.ai/our-methodology/ → no x-frame-options
- https://loxias.ai/about/ → 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://loxias.ai/ → no x-content-type-options
- https://loxias.ai/traditional-reports/ → no x-content-type-options
- https://loxias.ai/automated-reports/ → no x-content-type-options
- https://loxias.ai/industry/ → no x-content-type-options
- https://loxias.ai/sparks/ → no x-content-type-options
- https://loxias.ai/license/all-ears/ → no x-content-type-options
- https://loxias.ai/license/nebula-social/ → no x-content-type-options
- https://loxias.ai/license/pythia/ → no x-content-type-options
- https://loxias.ai/license/brandwatch/ → no x-content-type-options
- https://loxias.ai/license/socialinsider/ → no x-content-type-options
- https://loxias.ai/our-methodology/ → no x-content-type-options
- https://loxias.ai/about/ → 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://loxias.ai/ → no referrer-policy
- https://loxias.ai/traditional-reports/ → no referrer-policy
- https://loxias.ai/automated-reports/ → no referrer-policy
- https://loxias.ai/industry/ → no referrer-policy
- https://loxias.ai/sparks/ → no referrer-policy
- https://loxias.ai/license/all-ears/ → no referrer-policy
- https://loxias.ai/license/nebula-social/ → no referrer-policy
- https://loxias.ai/license/pythia/ → no referrer-policy
- https://loxias.ai/license/brandwatch/ → no referrer-policy
- https://loxias.ai/license/socialinsider/ → no referrer-policy
- https://loxias.ai/our-methodology/ → no referrer-policy
- https://loxias.ai/about/ → 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://loxias.ai/ → no permissions-policy
- https://loxias.ai/traditional-reports/ → no permissions-policy
- https://loxias.ai/automated-reports/ → no permissions-policy
- https://loxias.ai/industry/ → no permissions-policy
- https://loxias.ai/sparks/ → no permissions-policy
- https://loxias.ai/license/all-ears/ → no permissions-policy
- https://loxias.ai/license/nebula-social/ → no permissions-policy
- https://loxias.ai/license/pythia/ → no permissions-policy
- https://loxias.ai/license/brandwatch/ → no permissions-policy
- https://loxias.ai/license/socialinsider/ → no permissions-policy
- https://loxias.ai/our-methodology/ → no permissions-policy
- https://loxias.ai/about/ → 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.
- wmc_ip_info (set by https://loxias.ai/robots.txt) lacks Secure, HttpOnly, SameSite
- wmc_current_currency (set by https://loxias.ai/robots.txt) lacks Secure, HttpOnly, SameSite
- NoteThird-party scripts
Scripts run from 1 other domain 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.)
- www.googletagmanager.com (35 script tags)
- NoteSensitive paths in robots.txt
robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.
- Disallow: /wp-admin/
8 checks passed
- OKHTTPS
All 4974 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set on 4 of 4974 pages.
- 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
19 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKVulnerable JavaScript libraries
2 library versions recognised, none with known vulnerabilities.
- 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.
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.
Sites scoring near loxias.ai
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- drops.shDR 497/100 · rank 162 · 52 pages
- destacamos.netDR 1497/100 · rank 162 · 5,000 pages
- www.alaskacremation.comDR 1597/100 · rank 162 · 18 pages
- seoclusterizer.comDR 596/100 · rank 178 · 386 pages
- www.fhchiro.comDR 596/100 · rank 178 · 86 pages
- www.786vcpa.caDR 2196/100 · rank 178 · 404 pages
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
This report was produced by the DIY SEO Hub Site Spider crawling loxias.ai from its pages as published, the way a search engine does. It shows summary figures only.
Own loxias.ai?
- 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 loxias.ai. Removal needs no account and no proof of purchase.