Scanned sites / picstory.ca / 2026-11-01-0551

picstory.ca scan from 2026-11-01 05:51:56 UTC DR 7

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

Scan 2026-11-01-0551

Scanned 2026-11-01 05:51:56 UTC, finished 2026-11-01 10:35:26 UTC. Found on page 4 of brave web search results

Site: https://picstory.ca/

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

64/ 100Needs work

On November 1, 2026 the Site Spider crawled 215 pages and 4031 assets of picstory.ca, starting from https://picstory.ca/. It scored 64 out of 100, a result that needs work. 12 of 33 checks found something to fix, led by meta descriptions (178), heavy assets (410), thin content (134); 9 checks passed. Most of the points went to meta descriptions (−7.5), heavy assets (−6), thin content (−5.6). 12 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
215
Assets fetched
4031
Status
Completed
Checks with issues
12 of 33
CoverageJob finished, partial coverage

4,246 of 4,269 discovered URLs were fetched, 12 blocked by robots.txt, 2,616 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. 50 link destinations on other sites were checked.

  • Title tags16 issues
    16 of 178 pages have title issues. 12 noindex or canonicalized pages excluded.
    −0.8 points
  • Meta descriptions178 issues
    178 of 178 pages have meta description issues. 12 noindex or canonicalized pages excluded.
    −7.5 points
  • Headings80 issues
    80 of 178 pages have heading issues. 12 noindex or canonicalized pages excluded.
    −2.5 points
  • Broken links21 issues
    22 internal links point at 21 broken URLs.
    −2.2 points
  • Links to other sites7 issues
    7 destinations answered with an error, 22 could not be determined (timeouts, rate limits or refusals), of 50 destinations checked.
    −1.5 points
  • Redirects3 issues
    14 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses21 issues
    36 URLs did not return a 2xx response. 25 of them are pages, 21 with an error status; the rest are assets or redirects.
    −1.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability14 issues
    14 of 178 indexable pages have indexability warnings. 12 pages noindex by design. 2 noindex pages are listed in the sitemap, which asks search engines both to visit and to ignore them.
    −0.7 points
  • Image alt textOK
    0 of 3860 image references have no alt attribute. 3123 use an empty alt (decorative), which is fine.
  • Heavy assets410 issues
    410 assets larger than 500 KB among 4031 fetched assets.
    −6 points
  • Orphan pages147 issues
    147 pages have no internal links pointing at them.
    −3.1 points
  • Sitemap coverage151 issues
    15 sitemaps listing 178 URLs: 3 crawled pages missing, 1 listed URL broken or redirecting, 145 reachable only via the sitemap.
    −4.8 points
  • Internal link counts26 noted
    Internal link counts for 190 pages; 26 worth a look.
  • Thin content134 issues
    134 of 178 pages have fewer than 200 words. 12 noindex or canonicalized pages excluded.
    −5.6 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format31 noted
    31 of 215 page URLs are harder to read, share or cache than they need to be.
  • Canonicals22 noted
    22 of 190 pages have a canonical worth checking.
  • Robots directives190 noted
    190 pages carry a robots directive; 0 carry none.
  • Anchor text31 noted
    31 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure49 noted
    49 of 178 pages could use the title, heading and snippet space better. 12 noindex or canonicalized pages excluded.
  • Image weight and alt length112 noted
    112 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 190 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    3 of 178 indexable pages carry structured data: BreadcrumbList (3), ListItem (3), Product (1), Offer (1), Organization (1). 0 pages with errors a rich result would fail on.
  • Near duplicates23 noted
    23 pages in 6 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 190 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 positions18 noted
    18 of 33 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookies2 noted
    2 cookies set by the site, 2 missing a protective flag; 17 response headers recorded across 4246 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 190 pages; 174 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.
  • Spelling163 noted
    163 words an English dictionary does not know, on 52 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2465 sites, median 80%, average 78%

picstory.ca scores 64%, higher than 9% of the 2465 scanned sites. See the full ranking.

0591170%: 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%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 5 sites51%: 6 sites52%: 9 sites53%: 7 sites54%: 8 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 28 sites64%: 22 sites65%: 31 sites66%: 35 sites67%: 35 sites68%: 36 sites69%: 48 sites70%: 47 sites71%: 72 sites72%: 73 sites73%: 72 sites74%: 71 sites75%: 75 sites76%: 87 sites77%: 98 sites78%: 112 sites79%: 95 sites80%: 117 sites81%: 110 sites82%: 115 sites83%: 112 sites84%: 113 sites85%: 93 sites86%: 73 sites87%: 81 sites88%: 60 sites89%: 69 sites90%: 44 sites91%: 51 sites92%: 39 sites93%: 27 sites94%: 21 sites95%: 12 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites64% 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 site has multiple issues affecting SEO performance. Prioritize fixing broken links, missing meta descriptions, and titles. Consider addressing the sitemap and heading issues for better indexability.

  1. 1

    Fix Broken Links

    Why: 22 internal links lead to broken URLs, harming user experience and SEO.

    How: Check each broken link and either restore the destination or remove the reference.

    Evidence: https://picstory.ca/Downloads/240915.zip answers 404, and one page links to it with anchor text such as "Download".

    1 page affected

    Depends on: If the destination was deleted on purpose, remove the links rather than redirecting to an unrelated page.

    Checks: broken-links

  2. 2

    Add Missing Meta Descriptions

    Why: Meta descriptions are vital for search rankings and click-through rates.

    How: Create unique meta descriptions for each of the 178 pages.

    Checks: meta-descriptions

  3. 3

    Improve Title Tags

    Why: 16 pages have title issues, which can impact search visibility.

    How: Revise short titles to be more descriptive and within optimal length.

    Checks: titles

  4. 4

    Revise Sitemap Coverage

    Why: Inaccurate sitemap entries reduce content visibility on search engines.

    How: Update the sitemap to remove noindex URLs and include missing pages.

    Evidence: 2 URLs: sitemap url is noindex.

    2 pages affected

    Checks: sitemap-coverage

  5. 5

    Add Missing Headings

    Why: 80 pages lack proper headings, which can affect content structure and SEO.

    How: Add H1 tags to pages without them to improve SEO and organization.

    Checks: headings

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 gaps that need addressing. The most critical issues include the lack of HTTP Strict Transport Security, missing protective frame and cookie headers, and exposing server version information. These vulnerabilities can lead to interception of user data and other attacks. Immediate action is recommended.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted when they access your website first through HTTP.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, the site can be embedded in a frame, allowing clickjacking attacks.

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

    Evidence: Clickjacking protection

  3. 3

    Missing HttpOnly and Secure Flags on CookiesMedium

    Why it matters: Cookies without protection can be accessed by scripts or transmitted over insecure connections.

    Fix: Set the cookie flags: HttpOnly, Secure, SameSite=Strict for all cookies.

    Evidence: Cookie flags

  4. 4

    Leaked Google API KeyMedium

    Why it matters: Exposing this API key can lead to unauthorized usage and billing issues.

    Fix: Restrict the API key by referrer and settings in Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    Exposed Server Version InformationLow

    Why it matters: Revealing the server version can help attackers identify vulnerabilities.

    Fix: Remove the X-Powered-By header and configure your server to hide version information.

    Evidence: Software version disclosure

  6. 6

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this, there's a risk of MIME sniffing, which can lead to script execution attacks.

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

    Evidence: MIME sniffing protection

  7. 7

    Mixed Content IssuesLow

    Why it matters: Loading resources over HTTP on HTTPS pages can lead to interception of these resources.

    Fix: Ensure all resources use HTTPS URLs rather than HTTP.

    Evidence: Mixed content

  8. 8

    Permissions Policy MissingInfo

    Why it matters: A missing permissions policy can leave unused features accessible to attackers.

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

    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://picstory.ca/ → no strict-transport-security
    • https://picstory.ca/about/about-me/ → no strict-transport-security
    • https://picstory.ca/about/studio/ → no strict-transport-security
    • https://picstory.ca/services/baby/ → no strict-transport-security
    • https://picstory.ca/services/hanbok/ → no strict-transport-security
    • https://picstory.ca/services/family/ → no strict-transport-security
    • https://picstory.ca/services/profile/ → no strict-transport-security
    • https://picstory.ca/services/9188-2/ → no strict-transport-security
    • https://picstory.ca/services/id/ → no strict-transport-security
    • https://picstory.ca/faq/ → no strict-transport-security
    • https://picstory.ca/contact/ → no strict-transport-security
    • https://picstory.ca/shop/ → no strict-transport-security
  • FoundClickjacking protectionMedium

    12 of 190 HTML pages send 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://picstory.ca/ → no x-frame-options
    • https://picstory.ca/about/about-me/ → no x-frame-options
    • https://picstory.ca/about/studio/ → no x-frame-options
    • https://picstory.ca/services/baby/ → no x-frame-options
    • https://picstory.ca/services/hanbok/ → no x-frame-options
    • https://picstory.ca/services/family/ → no x-frame-options
    • https://picstory.ca/services/profile/ → no x-frame-options
    • https://picstory.ca/services/9188-2/ → no x-frame-options
    • https://picstory.ca/services/id/ → no x-frame-options
    • https://picstory.ca/faq/ → no x-frame-options
    • https://picstory.ca/contact/ → no x-frame-options
    • https://picstory.ca/shop/ → 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://picstory.ca/ → no x-content-type-options
    • https://picstory.ca/about/about-me/ → no x-content-type-options
    • https://picstory.ca/about/studio/ → no x-content-type-options
    • https://picstory.ca/services/baby/ → no x-content-type-options
    • https://picstory.ca/services/hanbok/ → no x-content-type-options
    • https://picstory.ca/services/family/ → no x-content-type-options
    • https://picstory.ca/services/profile/ → no x-content-type-options
    • https://picstory.ca/services/9188-2/ → no x-content-type-options
    • https://picstory.ca/services/id/ → no x-content-type-options
    • https://picstory.ca/faq/ → no x-content-type-options
    • https://picstory.ca/contact/ → no x-content-type-options
    • https://picstory.ca/shop/ → no x-content-type-options
  • FoundPermissions policyInfo

    181 of 190 HTML pages send 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://picstory.ca/wp-login.php?redirect_to=https%3A%2F%2Fpicstory.ca%2F20240807%2F9652%2F → no permissions-policy
    • https://picstory.ca/wp-login.php?action=lostpassword → no permissions-policy
    • https://picstory.ca/wp-login.php → no permissions-policy
    • https://picstory.ca/wp-login.php?redirect_to=https%3A%2F%2Fpicstory.ca%2Fproofing%2F241214%2F → no permissions-policy
    • https://picstory.ca/wp-login.php?redirect_to=https%3A%2F%2Fpicstory.ca%2Fproofing%2F250607%2F → no permissions-policy
    • https://picstory.ca/wp-login.php?redirect_to=https%3A%2F%2Fpicstory.ca%2Fproofing%2F250914%2F → no permissions-policy
    • https://picstory.ca/wp-login.php?redirect_to=https%3A%2F%2Fpicstory.ca%2Fproofing%2F250921%2F → no permissions-policy
    • https://picstory.ca/wp-login.php?redirect_to=https%3A%2F%2Fpicstory.ca%2Fproofing%2F250927%2F → no permissions-policy
    • https://picstory.ca/wp-login.php?redirect_to=https%3A%2F%2Fpicstory.ca%2Fproofing%2F260214%2F → 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: LiteSpeed (4246 responses)
    • x-powered-by: PHP/8.5.12 (233 responses)
  • FoundCookie flagsMedium

    2 of 2 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • wordpress_test_cookie (set by https://picstory.ca/wp-login.php?redirect_to=https%3A%2F%2Fpicstory.ca%2F202408…) lacks SameSite
    • wp_woocommerce_session_39b5ede6a4861249a1610b620a220108 (set by https://picstory.ca/cart/) lacks SameSite
  • FoundMixed contentLow

    813 resources on HTTPS pages are loaded over plain HTTP.

    • https://picstory.ca/ loads image http://picstory.ca/wp-content/uploads/2015/06/icon.png
    • https://picstory.ca/ loads image http://picstory.ca/wp-content/uploads/2015/06/logo_B.png
    • https://picstory.ca/ loads image http://picstory.ca/wp-content/uploads/2015/06/main01.jpg
    • https://picstory.ca/ loads image http://picstory.ca/wp-content/uploads/2015/06/main02.jpg
    • https://picstory.ca/ loads image http://picstory.ca/wp-content/uploads/2015/06/main03.jpg
    • https://picstory.ca/about/about-me/ loads image http://picstory.ca/wp-content/uploads/2015/06/icon.png
    • https://picstory.ca/about/about-me/ loads image http://picstory.ca/wp-content/uploads/2015/06/logo_B.png
    • https://picstory.ca/about/about-me/ loads image http://picstory.ca/wp-content/uploads/2015/06/about_me.jpg
    • https://picstory.ca/about/studio/ loads image http://picstory.ca/wp-content/uploads/2015/06/icon.png
    • https://picstory.ca/about/studio/ loads image http://picstory.ca/wp-content/uploads/2015/06/logo_B.png
    • https://picstory.ca/services/baby/ loads image http://picstory.ca/wp-content/uploads/2015/06/icon.png
    • https://picstory.ca/services/baby/ loads image http://picstory.ca/wp-content/uploads/2015/06/logo_B.png
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…0Q (39 chars) in https://picstory.ca/about/studio/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteThird-party scripts

    Scripts run from 1 other domain 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.)

    • maps.google.com (3 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/
6 checks passed
  • OKHTTPS

    All 190 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKReferrer policy

    A referrer policy is set through a <meta name="referrer"> tag.

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

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

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

Own picstory.ca?