Scanned sites / www.mikewilliamsphotography.com / 2026-10-03-0537

www.mikewilliamsphotography.com scan from 10/3/2026, 5:37:44 AM

Scan 2026-10-03-0537

Scanned 10/3/2026, 5:37:44 AM, finished 10/3/2026, 7:39:38 AM. Found on page 5 of brave web search results

Site: https://www.mikewilliamsphotography.com/

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

83/ 100Good

On October 3, 2026 the Site Spider crawled 10 pages and 465 assets of www.mikewilliamsphotography.com, starting from https://www.mikewilliamsphotography.com/. It scored 83 out of 100, a good result. 8 of 16 checks found something to fix, led by meta descriptions (9), thin content (7), links to other sites (9); 6 checks passed. Most of the points went to meta descriptions (−8), thin content (−6.2), links to other sites (−3.6). 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 2 info findings. See the security findings ↓

Pages crawled
10
Assets fetched
465
Status
Completed
Checks with issues
8 of 16
CoverageComplete crawl

475 of 483 discovered URLs were fetched, 8 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 36 link destinations on other sites were checked.

  • Title tags1 issue
    1 of 9 pages have title issues.
    −1.1 points
  • Meta descriptions9 issues
    9 of 9 pages have meta description issues.
    −8 points
  • Headings1 issue
    1 of 9 pages have heading issues.
    −0.7 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites9 issues
    9 destinations answered with an error, 20 could not be determined (timeouts, rate limits or refusals), of 36 destinations checked.
    −3.6 points
  • Redirects1 issue
    2 redirecting URLs, 0 of them chained.
    −0.4 points
  • Non-200 responses2 noted
    2 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 9 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 167 image references have no alt attribute. 130 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 465 fetched assets.
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −0.4 points
  • Sitemap coverage1 issue
    2 sitemaps listing 9 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −0.7 points
  • Internal link countsOK
    Internal link counts for 9 pages.
  • Thin content7 issues
    7 of 9 pages have fewer than 200 words.
    −6.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1955 sites, median 80%, average 79%

www.mikewilliamsphotography.com scores 83%, higher than 62% of the 1955 scanned sites. See the full ranking.

0561120%: 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%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 2 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 4 sites46%: 3 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 7 sites54%: 7 sites55%: 4 sites56%: 7 sites57%: 7 sites58%: 15 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 17 sites63%: 16 sites64%: 11 sites65%: 22 sites66%: 22 sites67%: 37 sites68%: 30 sites69%: 27 sites70%: 39 sites71%: 41 sites72%: 59 sites73%: 53 sites74%: 51 sites75%: 62 sites76%: 78 sites77%: 74 sites78%: 91 sites79%: 72 sites80%: 92 sites81%: 112 sites82%: 86 sites83%: 89 sites84%: 88 sites85%: 72 sites86%: 77 sites87%: 67 sites88%: 66 sites89%: 56 sites90%: 37 sites91%: 38 sites92%: 30 sites93%: 17 sites94%: 13 sites95%: 12 sites96%: 8 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 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

Several SEO issues need addressing to improve site visibility. Focus on adding meta descriptions, headings, fixing the sitemap, and enhancing thin content.

  1. 1

    Add Meta Descriptions

    Why: All pages lack meta descriptions, crucial for SEO and click-through rates.

    How: Write concise and relevant meta descriptions for all 9 pages, summarizing their content.

    Checks: meta-descriptions

  2. 2

    Ensure H1 Presence

    Why: A missing H1 can confuse search engines about page content.

    How: Add a clear, descriptive H1 tag to the relevant page.

    Checks: headings

  3. 3

    Correct Sitemap Accessibility

    Why: One important page is only reachable via the sitemap, restricting its visibility.

    How: Add internal links to the 'Terms of Use' page from relevant pages.

    Checks: sitemap-coverage

  4. 4

    Enhance Thin Content

    Why: 7 pages have fewer than 200 words, reducing their SEO value.

    How: Add more informative content to these pages to exceed 200 words.

    Checks: thin-content

  5. 5

    Fix Redirects

    Why: Redirects can dilute link equity and confuse users.

    How: Update links pointing to 'Terms of Use' to the final URL without the trailing slash.

    Checks: redirects

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

The website has multiple security vulnerabilities, including missing headers for protection against man-in-the-middle attacks, clickjacking, and content injection. Immediate action is needed to strengthen security measures.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted when accessing the site without HTTPS.

    Fix: Add the header `Strict-Transport-Security: max-age=31536000; includeSubDomains` to all responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: A missing CSP allows potential script and content injection from any source.

    Fix: Add `Content-Security-Policy: default-src 'self';` to all HTML responses.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, the site is susceptible to clickjacking attacks.

    Fix: Include `X-Frame-Options: DENY` or `SAMEORIGIN` in HTTP responses.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: Using jQuery 1.9.1 introduces multiple vulnerabilities, including XSS risks.

    Fix: Upgrade jQuery to at least version 3.5.0 to mitigate these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: This increases the risk of MIME-sniffing attacks.

    Fix: Add `X-Content-Type-Options: nosniff` to all HTML responses.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-Policy HeaderLow

    Why it matters: No restriction on the referrer can expose sensitive URL details.

    Fix: Include `Referrer-Policy: no-referrer` in HTTP responses.

    Evidence: Referrer policy

  7. 7

    Unsecured Third-Party ScriptsLow

    Why it matters: Lack of Subresource Integrity could expose the site to vulnerabilities via third-party scripts.

    Fix: Consider implementing a CSP to control script origins or use Subresource Integrity where possible.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions-Policy HeaderInfo

    Why it matters: Without it, potentially harmful features could be misused by malicious scripts.

    Fix: Add `Permissions-Policy: camera=(), microphone=(), geolocation=()` to responses.

    Evidence: Permissions policy

  9. 9

    Sensitive Paths in robots.txtInfo

    Why it matters: Public listing of sensitive paths can aid an attacker in targeting the site.

    Fix: Implement proper access controls for the listed paths 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://www.mikewilliamsphotography.com/ → no strict-transport-security
    • https://www.mikewilliamsphotography.com/families/ → no strict-transport-security
    • https://www.mikewilliamsphotography.com/graduates/ → no strict-transport-security
    • https://www.mikewilliamsphotography.com/weddings/ → no strict-transport-security
    • https://www.mikewilliamsphotography.com/commercial/ → no strict-transport-security
    • https://www.mikewilliamsphotography.com/portraits/ → no strict-transport-security
    • https://www.mikewilliamsphotography.com/about/ → no strict-transport-security
    • https://www.mikewilliamsphotography.com/contact/ → no strict-transport-security
    • https://www.mikewilliamsphotography.com/terms-of-use/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 9 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.mikewilliamsphotography.com/ → no content-security-policy
    • https://www.mikewilliamsphotography.com/families/ → no content-security-policy
    • https://www.mikewilliamsphotography.com/graduates/ → no content-security-policy
    • https://www.mikewilliamsphotography.com/weddings/ → no content-security-policy
    • https://www.mikewilliamsphotography.com/commercial/ → no content-security-policy
    • https://www.mikewilliamsphotography.com/portraits/ → no content-security-policy
    • https://www.mikewilliamsphotography.com/about/ → no content-security-policy
    • https://www.mikewilliamsphotography.com/contact/ → no content-security-policy
    • https://www.mikewilliamsphotography.com/terms-of-use/ → 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.mikewilliamsphotography.com/ → no x-frame-options
    • https://www.mikewilliamsphotography.com/families/ → no x-frame-options
    • https://www.mikewilliamsphotography.com/graduates/ → no x-frame-options
    • https://www.mikewilliamsphotography.com/weddings/ → no x-frame-options
    • https://www.mikewilliamsphotography.com/commercial/ → no x-frame-options
    • https://www.mikewilliamsphotography.com/portraits/ → no x-frame-options
    • https://www.mikewilliamsphotography.com/about/ → no x-frame-options
    • https://www.mikewilliamsphotography.com/contact/ → no x-frame-options
    • https://www.mikewilliamsphotography.com/terms-of-use/ → 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.mikewilliamsphotography.com/ → no x-content-type-options
    • https://www.mikewilliamsphotography.com/families/ → no x-content-type-options
    • https://www.mikewilliamsphotography.com/graduates/ → no x-content-type-options
    • https://www.mikewilliamsphotography.com/weddings/ → no x-content-type-options
    • https://www.mikewilliamsphotography.com/commercial/ → no x-content-type-options
    • https://www.mikewilliamsphotography.com/portraits/ → no x-content-type-options
    • https://www.mikewilliamsphotography.com/about/ → no x-content-type-options
    • https://www.mikewilliamsphotography.com/contact/ → no x-content-type-options
    • https://www.mikewilliamsphotography.com/terms-of-use/ → 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.mikewilliamsphotography.com/ → no referrer-policy
    • https://www.mikewilliamsphotography.com/families/ → no referrer-policy
    • https://www.mikewilliamsphotography.com/graduates/ → no referrer-policy
    • https://www.mikewilliamsphotography.com/weddings/ → no referrer-policy
    • https://www.mikewilliamsphotography.com/commercial/ → no referrer-policy
    • https://www.mikewilliamsphotography.com/portraits/ → no referrer-policy
    • https://www.mikewilliamsphotography.com/about/ → no referrer-policy
    • https://www.mikewilliamsphotography.com/contact/ → no referrer-policy
    • https://www.mikewilliamsphotography.com/terms-of-use/ → 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.mikewilliamsphotography.com/ → no permissions-policy
    • https://www.mikewilliamsphotography.com/families/ → no permissions-policy
    • https://www.mikewilliamsphotography.com/graduates/ → no permissions-policy
    • https://www.mikewilliamsphotography.com/weddings/ → no permissions-policy
    • https://www.mikewilliamsphotography.com/commercial/ → no permissions-policy
    • https://www.mikewilliamsphotography.com/portraits/ → no permissions-policy
    • https://www.mikewilliamsphotography.com/about/ → no permissions-policy
    • https://www.mikewilliamsphotography.com/contact/ → no permissions-policy
    • https://www.mikewilliamsphotography.com/terms-of-use/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 1.9.1 in https://www.mikewilliamsphotography.com/wp-content/cache/wpfc-minified/2puvogpj…: CVE-2015-9251 (XSS via cross-domain AJAX), 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.)

    • static.addtoany.com (9 script tags)
    • www.googletagmanager.com (9 script tags)
    • www.google.com (9 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 6 paths 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: /admin/
    • Disallow: /includes/
    • Disallow: /config/
    • Disallow: /backup/
    • Disallow: /wp-admin/
    • Disallow: /wp-includes/
6 checks passed, 1 not applicable
  • OKHTTPS

    All 9 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

    27 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.mikewilliamsphotography.com

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.mikewilliamsphotography.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.mikewilliamsphotography.com?

  • 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.mikewilliamsphotography.com. Removal needs no account and no proof of purchase.
www.mikewilliamsphotography.com scan 2026-10-03-0537 | DIY SEO Hub