Scanned sites / www.whitewillowphotos.com / 2026-11-02-1441
www.whitewillowphotos.com scan from 2026-11-02 14:41:51 UTC DR 10
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-11-02-1441
Scanned 2026-11-02 14:41:51 UTC, finished 2026-11-02 16:17:02 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.
On November 2, 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
977 of 987 discovered URLs were fetched, 1 failed. The crawl reached 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 sites10 issues10 destinations answered with an error, 27 could not be determined (timeouts, rate limits or refusals), of 97 destinations checked.−3.6 points
- Redirects9 issues24 redirecting URLs, 1 of them chained.−0.3 points
- Non-200 responses52 noted52 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 assets166 issues166 assets larger than 500 KB among 843 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 counts23 notedInternal link counts for 110 pages; 23 worth a look.
- 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.
- URL format31 noted31 of 134 page URLs are harder to read, share or cache than they need to be.
- Canonicals25 noted25 of 110 pages have a canonical worth checking.
- Robots directives110 noted110 pages carry a robots directive; 0 carry none.
- Anchor text32 noted32 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure21 noted21 of 84 pages could use the title, heading and snippet space better. 26 noindex or canonicalized pages excluded.
- Image weight and alt length292 noted292 images over 100 KB; 0 with alt text over 100 characters.
- Response anomalies2 noted2 URLs answered in a way worth looking at.
- HTML and head validationOKAll 110 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
- hreflangOKNo page declares hreflang.
- Structured dataOK110 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 noted13 pages in 3 groups read almost the same as another page (95% alike or more).
- Soft 404sOKNone of 110 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 positions3 noted3 of 76 linked pages are linked only from the template, never from another page's content.
- Pagination6 noted10 pages in pagination sequences; 6 with problems.
- Headers and cookiesOK0 cookies set by the site; 13 response headers recorded across 977 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 110 pages; 48 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.
- Spelling42 noted42 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
2608 sites, median 80%, average 78%
www.whitewillowphotos.com scores 79%, higher than 46% of the 2608 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 improvements to enhance its performance, particularly with redirects, title tags, meta descriptions, headings, and heavy assets. Addressing these will boost user experience and search visibility.
- 1
Fix Redirects
Why: Reduce unnecessary redirects to improve site speed and user experience.
How: Identify and remove or fix broken redirects. Make sure all pages redirect correctly to their intended URLs.
Checks: redirects
- 2
Address Non-200 Responses
Why: Resolve issues with pages and assets not returning a proper response.
How: Review and update or remove URL links leading to non-responsive pages or assets.
Checks: status-codes
- 3
Optimize Title Tags
Why: Improper title lengths negatively affect SEO performance.
How: Revise 17 pages with titles over 60 characters to keep them concise and impactful.
Checks: titles
- 4
Enhance Meta Descriptions
Why: Improving meta descriptions can increase click-through rates from search results.
How: Write or revise the meta descriptions for the 67 problem pages to ensure they're informative and unique.
Evidence: 21 pages have no meta description at all.
21 pages affected
Checks: meta-descriptions
- 5
Correct Heading Structure
Why: Proper headings improve content structure and SEO.
How: Add H1 tags to the 48 pages missing them, ensuring each page has a clear main heading.
Checks: headings
- 6
Optimize Heavy Assets
Why: Large assets can slow down page loading times.
How: Reduce the file size of sizable images, especially those over 5 MB.
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 crawlYour website has several security issues that could expose sensitive information or allow for attacks. The most severe problems include unsecured pages served over HTTP, lack of security headers, and information disclosure about server software. Addressing these issues is vital to protect your visitors and data.
- 1 high
- 3 medium
- 3 low
- 1 info
- 1
Insecure HTTP PagesHigh
Why it matters: Two pages are accessible over unsecured HTTP, allowing potential interception.
Fix: Redirect all traffic from HTTP to HTTPS using a server-side redirect.
Evidence: HTTPS
- 2
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: HSTS prevents protocol downgrade attacks by enforcing HTTPS connections.
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: Without CSP, any script can run from any source, increasing risks of attacks.
Fix: Implement a CSP header. Example: Content-Security-Policy: default-src 'self';
Evidence: Content Security Policy
- 4
No Clickjacking ProtectionMedium
Why it matters: Lack of X-Frame-Options allows other sites to frame your pages, posing clickjacking risks.
Fix: Add X-Frame-Options: SAMEORIGIN header.
Evidence: Clickjacking protection
- 5
Missing MIME Sniffing ProtectionLow
Why it matters: Without protection, browsers might execute files based on content instead of declared type.
Fix: Implement X-Content-Type-Options: nosniff header.
Evidence: MIME sniffing protection
- 6
No Referrer PolicyLow
Why it matters: Lack of a referrer policy may expose the full URLs visited to third parties.
Fix: Add Referrer-Policy: no-referrer
Evidence: Referrer policy
- 7
Server Version DisclosureLow
Why it matters: Exposing server details makes it easier for attackers to exploit known vulnerabilities.
Fix: Remove or hide the Server and X-Powered-By headers.
Evidence: Software version disclosure
- 8
Missing Permissions PolicyInfo
Why it matters: Not limiting permissions could allow malicious scripts to access sensitive features.
Fix: Include a Permissions-Policy header that denies features you don't use.
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.
- gtplumbingfargo.comDR 280/100 · rank 1195 · 28 pages
- apslandscaping.caDR 380/100 · rank 1195 · 15 pages
- amanblaze.inDR 080/100 · rank 1195 · 22 pages
- www.whalencpa.comDR 1679/100 · rank 1314 · 2,816 pages
- www.theelmsdentalcentre.comDR 179/100 · rank 1314 · 17 pages
- kurielaw.caDR 2779/100 · rank 1314 · 191 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 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.