Scanned sites / www.whitewillowphotos.com / 2026-10-02-2200
www.whitewillowphotos.com scan from 10/2/2026, 10:00:19 PM
A newer scan exists. See the latest report for www.whitewillowphotos.com.
Scan 2026-10-02-2200
Scanned 10/2/2026, 10:00:19 PM, finished 10/3/2026, 12:02:29 AM. Found on page 5 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.
On October 2, 2026 the Site Spider crawled 134 pages and 994 assets of www.whitewillowphotos.com, starting from https://www.whitewillowphotos.com/. It scored 83 out of 100, a good result. 10 of 16 checks found something to fix, led by heavy assets (70), meta descriptions (67), links to other sites (9); 4 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−4.9), links to other sites (−3.3). 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: High1 high, 3 medium, 3 low and 1 info findings. See the security findings ↓
- Pages crawled
- 134
- Assets fetched
- 994
- Status
- Completed
- Checks with issues
- 10 of 16
1,128 of 1,135 discovered URLs were fetched, 4,229 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. 97 link destinations on other sites were checked.
- Title tags17 issues17 of 84 pages have title issues. 26 noindex or canonicalized pages excluded.−1.5 points
- Meta descriptions67 issues67 of 84 pages have meta description issues. 26 noindex or canonicalized pages excluded.−4.9 points
- Headings48 issues48 of 84 pages have heading issues. 26 noindex or canonicalized pages excluded.−2.6 points
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites9 issues9 destinations answered with an error, 29 could not be determined (timeouts, rate limits or refusals), of 97 destinations checked.−3.3 points
- Redirects9 issues24 redirecting URLs, 1 of them chained.−0.3 points
- Non-200 responses25 noted25 URLs did not return a 2xx response. 24 of them are pages, 0 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 103 indexable pages have indexability warnings. 7 pages noindex by design.
- Image alt text12 issues12 of 1770 image references have no alt attribute. 908 use an empty alt (decorative), which is fine.
- Heavy assets70 issues70 assets larger than 500 KB among 994 fetched assets.−6 points
- Orphan pages10 issues10 pages have no internal links pointing at them.−0.4 points
- Sitemap coverage24 issues9 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 countsOKInternal link counts for 110 pages.
- Thin content7 issues7 of 84 pages have fewer than 200 words. 26 noindex or canonicalized pages excluded.−0.5 points
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1957 sites, median 80%, average 79%
www.whitewillowphotos.com scores 83%, higher than 62% of the 1957 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 has several SEO issues affecting visibility. Prioritize fixing redirects, title tags, meta descriptions, and headings to improve performance. Also, address orphan pages and heavy assets to enhance user experience.
- 1
Fix Redirects
Why: Redirects can dilute link equity and harm user experience.
How: Identify and resolve chained and broken redirects by updating URL references.
Checks: redirects
- 2
Revise Title Tags
Why: Improper length can impact click-through rates.
How: Adjust 17 pages with titles over 60 characters to ensure they are concise.
Checks: titles
- 3
Enhance Meta Descriptions
Why: Meta descriptions affect search visibility and click-through rates.
How: Craft unique meta descriptions for 67 pages with issues to better summarize the content.
Checks: meta-descriptions
- 4
Address Missing Headings
Why: H1 headers are crucial for semantic structure and SEO.
How: Add H1 tags to the 25 pages that currently lack them to improve content hierarchy.
Checks: headings
- 5
Link Orphan Pages
Why: Orphan pages are isolated, reducing their discoverability and impact.
How: Create internal links to the 10 orphan pages from relevant content to enhance their visibility.
Checks: orphan-pages
- 6
Compress Heavy Assets
Why: Large images can slow down page load times, affecting user experience and SEO.
How: Compress or replace the 70 heavy assets over 500 KB with optimized versions.
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 website has several security issues that need to be addressed. Key problems include pages accessible over plain HTTP, missing security headers like HTTP Strict Transport Security and Content Security Policy, and revealing software versions. Addressing these will enhance your site's protection against potential attacks.
- 1 high
- 3 medium
- 3 low
- 1 info
- 1
HTTP Pages ExposedHigh
Why it matters: Two pages are accessible over HTTP, allowing attackers to intercept and modify content.
Fix: Redirect all HTTP traffic to HTTPS to secure your pages.
Evidence: HTTPS
- 2
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users may be vulnerable to interception if they attempt to reach your site using HTTP.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.
Evidence: HTTP Strict Transport Security
- 3
No Content Security Policy (CSP)Medium
Why it matters: Absence of a CSP increases the risk of XSS attacks by allowing scripts from any source.
Fix: Implement a CSP header, e.g., Content-Security-Policy: default-src 'self';.
Evidence: Content Security Policy
- 4
Missing X-Frame-OptionsMedium
Why it matters: Lack of this header leaves the site vulnerable to clickjacking attacks.
Fix: Add the header: X-Frame-Options: deny.
Evidence: Clickjacking protection
- 5
Missing X-Content-Type-OptionsLow
Why it matters: This header prevents browsers from interpreting files as a different MIME type.
Fix: Add the header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 6
Missing Referrer PolicyLow
Why it matters: Not restricting referrer information exposes user data to other sites.
Fix: Add the header: Referrer-Policy: no-referrer.
Evidence: Referrer policy
- 7
Server Version Information RevealedLow
Why it matters: Disclosing server and framework versions makes it easier for attackers to target known vulnerabilities.
Fix: Hide software version by removing or changing the headers: Server: and X-Powered-By:.
Evidence: Software version disclosure
- 8
Missing Permissions PolicyInfo
Why it matters: Without this policy, potentially harmful features remain enabled on your site.
Fix: Add the header: Permissions-Policy: interest-cohort=().
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 (1128 responses)
- x-powered-by: PHP/7.4.33 (56 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.
- www.mikewilliamsphotography.com83/100 · rank 649 · 10 pages
- kodiakheating.com83/100 · rank 649 · 11 pages
- oblawoffice.ca83/100 · rank 649 · 269 pages
- cityyardworks.ca83/100 · rank 649 · 13 pages
- kinectivemassageandwellness.com83/100 · rank 649 · 34 pages
- www.studiosalonboise.com83/100 · rank 649 · 41 pages
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.