Scanned sites / www.aspendigital.nl / 2026-09-29-1042

www.aspendigital.nl scan from 9/29/2026, 10:42:10 AM

Scan 2026-09-29-1042

Scanned 9/29/2026, 10:42:10 AM, finished 9/29/2026, 11:03:13 AM

Site: https://www.aspendigital.nl/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

83/ 100Good

On September 29, 2026 the Site Spider crawled 193 pages and 692 assets of www.aspendigital.nl, starting from https://www.aspendigital.nl/. It scored 83 out of 100, a good result. 9 of 16 checks found something to fix, led by heavy assets (30), meta descriptions (122), title tags (75); 5 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−5.3), title tags (−4.1). 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
193
Assets fetched
692
Status
Completed
Checks with issues
9 of 16
CoverageComplete crawl

885 of 886 discovered URLs were fetched, 1 failed. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 55 left unchecked.

  • Title tags75 issues
    75 of 181 pages have title issues. 2 noindex or canonicalized pages excluded.
    −4.1 points
  • Meta descriptions122 issues
    122 of 181 pages have meta description issues. 2 noindex or canonicalized pages excluded.
    −5.3 points
  • Headings7 issues
    7 of 181 pages have heading issues. 2 noindex or canonicalized pages excluded.
    −0.2 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites4 issues
    4 destinations answered with an error, 6 could not be determined (timeouts, rate limits or refusals), 55 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.9 points
  • Redirects10 issues
    11 redirecting URLs, 2 of them chained.
    −0.2 points
  • Non-200 responses13 noted
    13 URLs did not return a 2xx response. 10 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 181 indexable pages have indexability warnings. 2 pages noindex by design.
  • Image alt text487 issues
    487 of 2898 image references have no alt attribute. 557 use an empty alt (decorative), which is fine.
    −1 points
  • Heavy assets30 issues
    30 assets larger than 500 KB among 692 fetched assets.
    −6 points
  • Orphan pages9 issues
    9 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage10 issues
    7 sitemaps listing 182 URLs: 0 crawled pages missing, 1 listed URL broken or redirecting, 9 reachable only via the sitemap.
    −0.3 points
  • Internal link countsOK
    Internal link counts for 183 pages.
  • Thin contentOK
    0 of 181 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1353 sites, median 80%, average 79%

www.aspendigital.nl scores 83%, higher than 62% of the 1353 scanned sites. See the full ranking.

039780%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 1 site36%: 1 site37%: 1 site38%: 1 site39%: 0 sites40%: 1 site41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 3 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 2 sites50%: 3 sites51%: 5 sites52%: 6 sites53%: 5 sites54%: 5 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 9 sites59%: 5 sites60%: 8 sites61%: 10 sites62%: 14 sites63%: 12 sites64%: 8 sites65%: 14 sites66%: 14 sites67%: 27 sites68%: 24 sites69%: 14 sites70%: 32 sites71%: 29 sites72%: 39 sites73%: 33 sites74%: 41 sites75%: 40 sites76%: 49 sites77%: 45 sites78%: 59 sites79%: 48 sites80%: 68 sites81%: 78 sites82%: 67 sites83%: 61 sites84%: 60 sites85%: 45 sites86%: 49 sites87%: 48 sites88%: 49 sites89%: 36 sites90%: 29 sites91%: 31 sites92%: 18 sites93%: 8 sites94%: 10 sites95%: 5 sites96%: 7 sites97%: 3 sites98%: 1 site99%: 2 sites100%: 50 sites83% here100%90%80%70%60%50%40%30%20%10%0%

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...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

There are several SEO issues to address, particularly with redirects, title tags, and meta descriptions. Improving these will enhance user experience and search rankings.

  1. 1

    Fix Redirect Chains

    Why: Reducing redirect chains improves loading speed and user experience.

    How: Update the URLs to direct users to the final destination without intermediate redirects.

    Checks: redirects

  2. 2

    Correct Non-200 Responses

    Why: Ensuring all pages return a 200 status enhances visibility and user interaction.

    How: Investigate and resolve the status issues on the 10 affected pages.

    Checks: status-codes

  3. 3

    Revise Title Tags

    Why: Improving title tags boosts SEO and click-through rates.

    How: Create unique, descriptive titles for the 75 pages with issues.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Optimized meta descriptions can improve search result visibility.

    How: Write clear, engaging meta descriptions for 122 pages where there are issues.

    Checks: meta-descriptions

  5. 5

    Add Missing Headings

    Why: Headings help structure content and improve SEO.

    How: Add H1 headings to the 7 pages missing them.

    Checks: headings

  6. 6

    Optimize Heavy Assets

    Why: Reducing file sizes can improve page load speeds.

    How: Compress or resize the identified large images and videos.

    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 crawl

Your website has several security issues, primarily the absence of crucial HTTP response headers that protect against various attacks. It's essential to implement these headers to enhance the security of your web application and its visitors.

  • 0 high
  • 4 medium
  • 3 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Lack of HSTS allows man-in-the-middle attacks when users access the site without HTTPS.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without CSP, malicious scripts can be executed from unauthorized sources, increasing the risk of XSS attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of this header permits clickjacking attacks by allowing your site to be framed by malicious sites.

    Fix: Add the header: X-Frame-Options: DENY

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: Using jQuery 3.1.2 exposes your site to known vulnerabilities which could be exploited.

    Fix: Update jQuery from 3.1.2 to at least 3.5.0

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may interpret files as a different MIME type, leading to potential attacks.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-Policy HeaderLow

    Why it matters: No referrer policy exposes potentially sensitive URL paths when users navigate away from your site.

    Fix: Add the header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

    Why it matters: Exposing your server version makes it easier for attackers to exploit known vulnerabilities.

    Fix: Hide or remove server headers; consider using: server: [Your Server Name]

    Evidence: Software version disclosure

  8. 8

    Missing Permissions-Policy HeaderInfo

    Why it matters: Lack of this header risks unwanted access to browser features by potentially malicious scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=()

    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://www.aspendigital.nl/ → no strict-transport-security
    • https://www.aspendigital.nl/expertises/ → no strict-transport-security
    • https://www.aspendigital.nl/expertises/seo/ → no strict-transport-security
    • https://www.aspendigital.nl/expertises/sea/ → no strict-transport-security
    • https://www.aspendigital.nl/expertises/content/ → no strict-transport-security
    • https://www.aspendigital.nl/expertises/linkbuilding/ → no strict-transport-security
    • https://www.aspendigital.nl/expertises/social-ads/ → no strict-transport-security
    • https://www.aspendigital.nl/expertises/data-tooling/ → no strict-transport-security
    • https://www.aspendigital.nl/voor-wie/ondernemingen/ → no strict-transport-security
    • https://www.aspendigital.nl/voor-wie/marketingbureaus/ → no strict-transport-security
    • https://www.aspendigital.nl/voor-wie/webdevelopment-bureaus/ → no strict-transport-security
    • https://www.aspendigital.nl/groeiverhalen/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 183 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://www.aspendigital.nl/ → no content-security-policy
    • https://www.aspendigital.nl/expertises/ → no content-security-policy
    • https://www.aspendigital.nl/expertises/seo/ → no content-security-policy
    • https://www.aspendigital.nl/expertises/sea/ → no content-security-policy
    • https://www.aspendigital.nl/expertises/content/ → no content-security-policy
    • https://www.aspendigital.nl/expertises/linkbuilding/ → no content-security-policy
    • https://www.aspendigital.nl/expertises/social-ads/ → no content-security-policy
    • https://www.aspendigital.nl/expertises/data-tooling/ → no content-security-policy
    • https://www.aspendigital.nl/voor-wie/ondernemingen/ → no content-security-policy
    • https://www.aspendigital.nl/voor-wie/marketingbureaus/ → no content-security-policy
    • https://www.aspendigital.nl/voor-wie/webdevelopment-bureaus/ → no content-security-policy
    • https://www.aspendigital.nl/groeiverhalen/ → 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://www.aspendigital.nl/ → no x-frame-options
    • https://www.aspendigital.nl/expertises/ → no x-frame-options
    • https://www.aspendigital.nl/expertises/seo/ → no x-frame-options
    • https://www.aspendigital.nl/expertises/sea/ → no x-frame-options
    • https://www.aspendigital.nl/expertises/content/ → no x-frame-options
    • https://www.aspendigital.nl/expertises/linkbuilding/ → no x-frame-options
    • https://www.aspendigital.nl/expertises/social-ads/ → no x-frame-options
    • https://www.aspendigital.nl/expertises/data-tooling/ → no x-frame-options
    • https://www.aspendigital.nl/voor-wie/ondernemingen/ → no x-frame-options
    • https://www.aspendigital.nl/voor-wie/marketingbureaus/ → no x-frame-options
    • https://www.aspendigital.nl/voor-wie/webdevelopment-bureaus/ → no x-frame-options
    • https://www.aspendigital.nl/groeiverhalen/ → 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://www.aspendigital.nl/ → no x-content-type-options
    • https://www.aspendigital.nl/expertises/ → no x-content-type-options
    • https://www.aspendigital.nl/expertises/seo/ → no x-content-type-options
    • https://www.aspendigital.nl/expertises/sea/ → no x-content-type-options
    • https://www.aspendigital.nl/expertises/content/ → no x-content-type-options
    • https://www.aspendigital.nl/expertises/linkbuilding/ → no x-content-type-options
    • https://www.aspendigital.nl/expertises/social-ads/ → no x-content-type-options
    • https://www.aspendigital.nl/expertises/data-tooling/ → no x-content-type-options
    • https://www.aspendigital.nl/voor-wie/ondernemingen/ → no x-content-type-options
    • https://www.aspendigital.nl/voor-wie/marketingbureaus/ → no x-content-type-options
    • https://www.aspendigital.nl/voor-wie/webdevelopment-bureaus/ → no x-content-type-options
    • https://www.aspendigital.nl/groeiverhalen/ → 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://www.aspendigital.nl/ → no referrer-policy
    • https://www.aspendigital.nl/expertises/ → no referrer-policy
    • https://www.aspendigital.nl/expertises/seo/ → no referrer-policy
    • https://www.aspendigital.nl/expertises/sea/ → no referrer-policy
    • https://www.aspendigital.nl/expertises/content/ → no referrer-policy
    • https://www.aspendigital.nl/expertises/linkbuilding/ → no referrer-policy
    • https://www.aspendigital.nl/expertises/social-ads/ → no referrer-policy
    • https://www.aspendigital.nl/expertises/data-tooling/ → no referrer-policy
    • https://www.aspendigital.nl/voor-wie/ondernemingen/ → no referrer-policy
    • https://www.aspendigital.nl/voor-wie/marketingbureaus/ → no referrer-policy
    • https://www.aspendigital.nl/voor-wie/webdevelopment-bureaus/ → no referrer-policy
    • https://www.aspendigital.nl/groeiverhalen/ → 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://www.aspendigital.nl/ → no permissions-policy
    • https://www.aspendigital.nl/expertises/ → no permissions-policy
    • https://www.aspendigital.nl/expertises/seo/ → no permissions-policy
    • https://www.aspendigital.nl/expertises/sea/ → no permissions-policy
    • https://www.aspendigital.nl/expertises/content/ → no permissions-policy
    • https://www.aspendigital.nl/expertises/linkbuilding/ → no permissions-policy
    • https://www.aspendigital.nl/expertises/social-ads/ → no permissions-policy
    • https://www.aspendigital.nl/expertises/data-tooling/ → no permissions-policy
    • https://www.aspendigital.nl/voor-wie/ondernemingen/ → no permissions-policy
    • https://www.aspendigital.nl/voor-wie/marketingbureaus/ → no permissions-policy
    • https://www.aspendigital.nl/voor-wie/webdevelopment-bureaus/ → no permissions-policy
    • https://www.aspendigital.nl/groeiverhalen/ → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: nginx (885 responses)
    • x-powered-by: PleskLin (682 responses)
    • x-powered-by: PHP/8.3.35, PleskLin (201 responses)
    • x-powered-by: PHP/8.3.35 (1 response)
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 3.1.2. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 3.1.2 in https://www.aspendigital.nl/wp-content/plugins/gravityforms/js/placeholders.jqu…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • NoteThird-party scripts

    Scripts run from 3 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.)

    • cdn.jsdelivr.net (50 script tags)
    • static.hsappstatic.net (40 script tags)
    • js-eu1.hs-scripts.com (40 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/
5 checks passed, 1 not applicable
  • OKHTTPS

    All 183 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    48 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.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

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 www.aspendigital.nl

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling www.aspendigital.nl from its pages as published, the way a search engine does. It shows summary figures only.

Own www.aspendigital.nl?

  • 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 www.aspendigital.nl. Removal needs no account and no proof of purchase.
www.aspendigital.nl scan 2026-09-29-1042 | DIY SEO Hub