Scanned sites / www.whitewillowphotos.com / 2026-11-03-0426

www.whitewillowphotos.com scan from 2026-11-03 04:26:56 UTC DR 10

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-11-03-0426

Scanned 2026-11-03 04:26:56 UTC, finished 2026-11-03 07:14:35 UTC. Found on page 4 of brave web search results

Site: https://www.whitewillowphotos.com/

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

79/ 100Good

On November 3, 2026 the Site Spider crawled 134 pages and 843 assets of www.whitewillowphotos.com, starting from https://www.whitewillowphotos.com/. It scored 79 out of 100, a good result. 10 of 33 checks found something to fix, led by heavy assets (166), meta descriptions (67), links to other sites (10); 10 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−4.9), links to other sites (−3.6). 13 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: High1 high, 3 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
134
Assets fetched
843
Status
Completed
Checks with issues
10 of 33
CoverageComplete crawl

977 of 987 discovered URLs were fetched, 3 failed. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 97 link destinations on other sites were checked.

  • Title tags17 issues
    17 of 84 pages have title issues. 26 noindex or canonicalized pages excluded.
    −1.5 points
  • Meta descriptions67 issues
    67 of 84 pages have meta description issues. 26 noindex or canonicalized pages excluded.
    −4.9 points
  • Headings48 issues
    48 of 84 pages have heading issues. 26 noindex or canonicalized pages excluded.
    −2.6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites10 issues
    10 destinations answered with an error, 37 could not be determined (timeouts, rate limits or refusals), of 97 destinations checked.
    −3.6 points
  • Redirects9 issues
    24 redirecting URLs, 1 of them chained.
    −0.3 points
  • Non-200 responses54 noted
    54 URLs did not return a 2xx response. 24 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 103 indexable pages have indexability warnings. 7 pages noindex by design.
  • Image alt text12 issues
    12 of 1770 image references have no alt attribute. 908 use an empty alt (decorative), which is fine.
  • Heavy assets166 issues
    166 assets larger than 500 KB among 843 fetched assets.
    −6 points
  • Orphan pages10 issues
    10 pages have no internal links pointing at them.
    −0.4 points
  • Sitemap coverage24 issues
    9 sitemaps listing 98 URLs: 1 crawled page missing, 15 listed URLs broken or redirecting, 8 reachable only via the sitemap.
    −1.3 points
  • Internal link counts23 noted
    Internal link counts for 110 pages; 23 worth a look.
  • Thin content7 issues
    7 of 84 pages have fewer than 200 words. 26 noindex or canonicalized pages excluded.
    −0.5 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format31 noted
    31 of 134 page URLs are harder to read, share or cache than they need to be.
  • Canonicals25 noted
    25 of 110 pages have a canonical worth checking.
  • Robots directives110 noted
    110 pages carry a robots directive; 0 carry none.
  • Anchor text32 noted
    32 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure21 noted
    21 of 84 pages could use the title, heading and snippet space better. 26 noindex or canonicalized pages excluded.
  • Image weight and alt length292 noted
    292 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • HTML and head validationOK
    All 110 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    110 of 84 indexable pages carry structured data: WebSite (110), Organization (110), BreadcrumbList (110), ListItem (110), WPHeader (110). 0 pages with errors a rich result would fail on.
  • Near duplicates13 noted
    13 pages in 3 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 110 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions3 noted
    3 of 76 linked pages are linked only from the template, never from another page's content.
  • Pagination6 noted
    10 pages in pagination sequences; 6 with problems.
  • Headers and cookiesOK
    0 cookies set by the site; 13 response headers recorded across 977 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 110 pages; 48 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not 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 checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling42 noted
    42 words an English dictionary does not know, on 58 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2704 sites, median 80%, average 78%

www.whitewillowphotos.com scores 79%, higher than 45% of the 2704 scanned sites. See the full ranking.

0631260%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 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%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 9 sites56%: 7 sites57%: 16 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 33 sites66%: 40 sites67%: 40 sites68%: 39 sites69%: 50 sites70%: 46 sites71%: 78 sites72%: 74 sites73%: 82 sites74%: 77 sites75%: 87 sites76%: 96 sites77%: 107 sites78%: 123 sites79%: 109 sites80%: 124 sites81%: 120 sites82%: 123 sites83%: 118 sites84%: 126 sites85%: 102 sites86%: 90 sites87%: 91 sites88%: 77 sites89%: 72 sites90%: 52 sites91%: 56 sites92%: 40 sites93%: 28 sites94%: 23 sites95%: 14 sites96%: 17 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 76 sites79% 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

Your website has several issues to address, including redirects, non-200 responses, and missing meta descriptions. Implementing these fixes will improve your site's performance and visibility.

  1. 1

    Fix Redirects

    Why: Redirects can hinder SEO and slow down site performance.

    How: Update the 24 redirecting URLs to point directly to the final destinations. Resolve the 1 chained redirect.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: 54 URLs failing to return 2xx response can affect user experience and SEO.

    How: Review and fix the 54 URLs causing non-200 responses, focusing on assets and redirects.

    Checks: status-codes

  3. 3

    Update Title Tags

    Why: 17 pages have length issues with titles, impacting SEO and click-through rates.

    How: Modify the title tags for the 17 pages, keeping them under 60 characters.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: 67 pages with meta description issues can reduce engagement.

    How: Create a compelling meta description for the 21 pages lacking one.

    Evidence: 21 pages have no meta description at all.

    21 pages affected

    Checks: meta-descriptions

  5. 5

    Address Heading Issues

    Why: 48 pages with heading issues can confuse search engines and impact SEO.

    How: Add H1 tags to the affected pages where missing.

    Checks: headings

  6. 6

    Shrink Heavy Assets

    Why: 166 assets over 500 KB can slow down page loads.

    How: Optimize or resize the large images to improve loading speed.

    Evidence: 8.1 MB of image, loaded by 4 pages, so every visitor to any of them downloads it.

    4 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    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

The website has several critical security issues, including HTTP pages that lack encryption, missing security headers, and exposed server details. Immediate action is needed to protect user data and enhance site security.

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

    HTTP pages without HTTPSHigh

    Why it matters: Two pages responded over plain HTTP, exposing them to interception.

    Fix: Redirect HTTP traffic to HTTPS using a 301 redirect for all pages.

    Evidence: HTTPS

  2. 2

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, visitors may be intercepted before making secure connections.

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

    Evidence: HTTP Strict Transport Security

  3. 3

    No Content Security PolicyMedium

    Why it matters: Lack of CSP allows arbitrary script execution, increasing XSS risk.

    Fix: Add a Content-Security-Policy header, e.g., `Content-Security-Policy: default-src 'self';` to all pages.

    Evidence: Content Security Policy

  4. 4

    Missing Clickjacking ProtectionMedium

    Why it matters: Pages can be embedded in frames, making them vulnerable to clickjacking attacks.

    Fix: Add the header `X-Frame-Options: DENY` to all pages.

    Evidence: Clickjacking protection

  5. 5

    No MIME Sniffing ProtectionLow

    Why it matters: Users may unknowingly execute malicious scripts due to MIME type confusion.

    Fix: Add the header `X-Content-Type-Options: nosniff` to all pages.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Full URLs, potentially sensitive, are sent when users navigate away from your site.

    Fix: Add a Referrer-Policy header, e.g., `Referrer-Policy: no-referrer` to all pages.

    Evidence: Referrer policy

  7. 7

    Exposed Server Version InformationLow

    Why it matters: Revealing server details helps attackers exploit known vulnerabilities.

    Fix: Consider configuring your server to hide version information or use security best practices to mitigate known threats.

    Evidence: Software version disclosure

  8. 8

    No Permissions PolicyInfo

    Why it matters: Browser features could be misused by injected scripts without restrictions.

    Fix: Add a Permissions-Policy header, e.g., `Permissions-Policy: interest-cohort=()`, to all pages.

    Evidence: Permissions policy

What the checks found

  • FoundHTTPSHigh

    2 pages answered 200 over plain HTTP with no redirect to HTTPS, while 108 were served over HTTPS. Anyone on the network path can read or alter these pages.

    • http://www.whitewillowphotos.com/contact/ → 200 over http
    • http://www.whitewillowphotos.com/blog-grid/ → 200 over http
  • 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.whitewillowphotos.com/ → no strict-transport-security
    • https://www.whitewillowphotos.com/engagementphotoswinnipeg/ → no strict-transport-security
    • https://www.whitewillowphotos.com/portfolio/ → no strict-transport-security
    • https://www.whitewillowphotos.com/contact/ → no strict-transport-security
    • https://www.whitewillowphotos.com/destination-wedding-photographer-cost/ → no strict-transport-security
    • https://www.whitewillowphotos.com/iceland-elopement/ → no strict-transport-security
    • https://www.whitewillowphotos.com/weddingphotographerincalgary/ → no strict-transport-security
    • https://www.whitewillowphotos.com/photographer-vancouver-island/ → no strict-transport-security
    • https://www.whitewillowphotos.com/about-us/ → no strict-transport-security
    • https://www.whitewillowphotos.com/category/blogs/ → no strict-transport-security
    • https://www.whitewillowphotos.com/events/ → no strict-transport-security
    • https://www.whitewillowphotos.com/blog-grid/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 110 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.whitewillowphotos.com/ → no content-security-policy
    • https://www.whitewillowphotos.com/engagementphotoswinnipeg/ → no content-security-policy
    • https://www.whitewillowphotos.com/portfolio/ → no content-security-policy
    • https://www.whitewillowphotos.com/contact/ → no content-security-policy
    • https://www.whitewillowphotos.com/destination-wedding-photographer-cost/ → no content-security-policy
    • https://www.whitewillowphotos.com/iceland-elopement/ → no content-security-policy
    • https://www.whitewillowphotos.com/weddingphotographerincalgary/ → no content-security-policy
    • https://www.whitewillowphotos.com/photographer-vancouver-island/ → no content-security-policy
    • https://www.whitewillowphotos.com/about-us/ → no content-security-policy
    • https://www.whitewillowphotos.com/category/blogs/ → no content-security-policy
    • https://www.whitewillowphotos.com/events/ → no content-security-policy
    • https://www.whitewillowphotos.com/blog-grid/ → 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.whitewillowphotos.com/ → no x-frame-options
    • https://www.whitewillowphotos.com/engagementphotoswinnipeg/ → no x-frame-options
    • https://www.whitewillowphotos.com/portfolio/ → no x-frame-options
    • https://www.whitewillowphotos.com/contact/ → no x-frame-options
    • https://www.whitewillowphotos.com/destination-wedding-photographer-cost/ → no x-frame-options
    • https://www.whitewillowphotos.com/iceland-elopement/ → no x-frame-options
    • https://www.whitewillowphotos.com/weddingphotographerincalgary/ → no x-frame-options
    • https://www.whitewillowphotos.com/photographer-vancouver-island/ → no x-frame-options
    • https://www.whitewillowphotos.com/about-us/ → no x-frame-options
    • https://www.whitewillowphotos.com/category/blogs/ → no x-frame-options
    • https://www.whitewillowphotos.com/events/ → no x-frame-options
    • https://www.whitewillowphotos.com/blog-grid/ → 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.whitewillowphotos.com/ → no x-content-type-options
    • https://www.whitewillowphotos.com/engagementphotoswinnipeg/ → no x-content-type-options
    • https://www.whitewillowphotos.com/portfolio/ → no x-content-type-options
    • https://www.whitewillowphotos.com/contact/ → no x-content-type-options
    • https://www.whitewillowphotos.com/destination-wedding-photographer-cost/ → no x-content-type-options
    • https://www.whitewillowphotos.com/iceland-elopement/ → no x-content-type-options
    • https://www.whitewillowphotos.com/weddingphotographerincalgary/ → no x-content-type-options
    • https://www.whitewillowphotos.com/photographer-vancouver-island/ → no x-content-type-options
    • https://www.whitewillowphotos.com/about-us/ → no x-content-type-options
    • https://www.whitewillowphotos.com/category/blogs/ → no x-content-type-options
    • https://www.whitewillowphotos.com/events/ → no x-content-type-options
    • https://www.whitewillowphotos.com/blog-grid/ → 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.whitewillowphotos.com/ → no referrer-policy
    • https://www.whitewillowphotos.com/engagementphotoswinnipeg/ → no referrer-policy
    • https://www.whitewillowphotos.com/portfolio/ → no referrer-policy
    • https://www.whitewillowphotos.com/contact/ → no referrer-policy
    • https://www.whitewillowphotos.com/destination-wedding-photographer-cost/ → no referrer-policy
    • https://www.whitewillowphotos.com/iceland-elopement/ → no referrer-policy
    • https://www.whitewillowphotos.com/weddingphotographerincalgary/ → no referrer-policy
    • https://www.whitewillowphotos.com/photographer-vancouver-island/ → no referrer-policy
    • https://www.whitewillowphotos.com/about-us/ → no referrer-policy
    • https://www.whitewillowphotos.com/category/blogs/ → no referrer-policy
    • https://www.whitewillowphotos.com/events/ → no referrer-policy
    • https://www.whitewillowphotos.com/blog-grid/ → 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.whitewillowphotos.com/ → no permissions-policy
    • https://www.whitewillowphotos.com/engagementphotoswinnipeg/ → no permissions-policy
    • https://www.whitewillowphotos.com/portfolio/ → no permissions-policy
    • https://www.whitewillowphotos.com/contact/ → no permissions-policy
    • https://www.whitewillowphotos.com/destination-wedding-photographer-cost/ → no permissions-policy
    • https://www.whitewillowphotos.com/iceland-elopement/ → no permissions-policy
    • https://www.whitewillowphotos.com/weddingphotographerincalgary/ → no permissions-policy
    • https://www.whitewillowphotos.com/photographer-vancouver-island/ → no permissions-policy
    • https://www.whitewillowphotos.com/about-us/ → no permissions-policy
    • https://www.whitewillowphotos.com/category/blogs/ → no permissions-policy
    • https://www.whitewillowphotos.com/events/ → no permissions-policy
    • https://www.whitewillowphotos.com/blog-grid/ → 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: Apache (977 responses)
    • x-powered-by: PHP/7.4.33 (82 responses)
  • NoteThird-party scripts

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

    • stats.wp.com (80 script tags)
    • www.googletagmanager.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
  • OKMixed content

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

  • OKForms over HTTPS

    63 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

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

  • 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.whitewillowphotos.com

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

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

Own www.whitewillowphotos.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.whitewillowphotos.com. Removal needs no account and no proof of purchase.