Scanned sites / www.jtccpas.com / 2026-10-02-0442

www.jtccpas.com scan from 10/2/2026, 4:42:20 AM

Scan 2026-10-02-0442

Scanned 10/2/2026, 4:42:20 AM, finished 10/2/2026, 8:40:30 AM. Found on page 1 of brave web search results

Site: https://www.jtccpas.com/

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

77/ 100Good

On October 2, 2026 the Site Spider crawled 1295 pages and 998 assets of www.jtccpas.com, starting from https://www.jtccpas.com/. It scored 77 out of 100, a good result. 14 of 16 checks found something to fix, led by heavy assets (15), meta descriptions (922), title tags (697); 1 check passed. Most of the points went to heavy assets (−6), meta descriptions (−5.8), title tags (−5.5). 1 check 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: Medium2 medium, 1 low and 1 info findings. See the security findings ↓

Pages crawled
1295
Assets fetched
998
Status
Completed
Checks with issues
14 of 16
CoverageJob finished, partial coverage

2,293 of 2,296 discovered URLs were fetched, 3 blocked by robots.txt, 2,621 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. 300 link destinations on other sites were checked, 417 left unchecked.

  • Title tags697 issues
    697 of 1261 pages have title issues. 5 noindex or canonicalized pages excluded.
    −5.5 points
  • Meta descriptions922 issues
    922 of 1261 pages have meta description issues. 5 noindex or canonicalized pages excluded.
    −5.8 points
  • Headings456 issues
    456 of 1261 pages have heading issues. 5 noindex or canonicalized pages excluded.
    −2.2 points
  • Broken links13 issues
    70 internal links point at 13 broken URLs.
    −0.2 points
  • Links to other sites61 issues
    61 destinations answered with an error, 41 could not be determined (timeouts, rate limits or refusals), 417 were left unchecked by the per-scan cap, of 300 destinations checked.
    −1.9 points
  • Redirects16 issues
    16 redirecting URLs, 1 of them chained.
    −0.1 points
  • Non-200 responses13 issues
    29 URLs did not return a 2xx response. 29 of them are pages, 13 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability18 issues
    18 of 1261 indexable pages have indexability warnings. 5 pages noindex by design. 1 noindex page is listed in the sitemap, which asks search engines both to visit and to ignore it.
    −0.1 points
  • Image alt text784 issues
    784 of 3741 image references have no alt attribute. 555 use an empty alt (decorative), which is fine.
    −1.3 points
  • Heavy assets15 issues
    15 assets larger than 500 KB among 998 fetched assets.
    −6 points
  • Orphan pages4 issues
    4 pages have no internal links pointing at them.
  • Sitemap coverage458 issues
    1 sitemap listing 810 URLs: 453 crawled pages missing, 1 listed URL broken or redirecting, 3 reachable only via the sitemap.
    −2.2 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin content2 issues
    2 of 1261 pages have fewer than 200 words. 5 noindex or canonicalized pages excluded.
  • Duplicate content2 issues
    1 group of pages with identical HTML.

Where this scan sits among all scanned sites

1827 sites, median 80%, average 79%

www.jtccpas.com scores 77%, higher than 36% of the 1827 scanned sites. See the full ranking.

0531050%: 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%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 7 sites50%: 4 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 5 sites57%: 7 sites58%: 12 sites59%: 6 sites60%: 10 sites61%: 12 sites62%: 16 sites63%: 16 sites64%: 11 sites65%: 21 sites66%: 19 sites67%: 35 sites68%: 29 sites69%: 26 sites70%: 38 sites71%: 38 sites72%: 53 sites73%: 51 sites74%: 49 sites75%: 59 sites76%: 73 sites77%: 69 sites78%: 86 sites79%: 65 sites80%: 90 sites81%: 105 sites82%: 84 sites83%: 84 sites84%: 85 sites85%: 61 sites86%: 68 sites87%: 56 sites88%: 63 sites89%: 52 sites90%: 33 sites91%: 35 sites92%: 28 sites93%: 14 sites94%: 13 sites95%: 12 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 sites77% 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's health score is good, but issues with broken links, metadata, and redirects need addressing. Prioritize fixing broken links, titles, meta descriptions, and redirects for improved SEO performance.

  1. 1

    Fix Broken Links

    Why: 70 internal links point to broken URLs, impacting user experience.

    How: Identify broken URLs and update or remove them from the site.

    Checks: broken-links

  2. 2

    Optimize Title Tags

    Why: 216 pages share duplicate titles, leading to poor SEO.

    How: Assign unique titles for each page to enhance search visibility.

    Checks: titles

  3. 3

    Enhance Meta Descriptions

    Why: 922 pages have meta description issues, affecting click-through rates.

    How: Create unique meta descriptions for affected pages to boost engagement.

    Checks: meta-descriptions

  4. 4

    Resolve Redirect Issues

    Why: 16 URLs redirect, with chained redirects degrading performance.

    How: Simplify redirects and ensure they point correctly to their final destination.

    Checks: redirects

  5. 5

    Address Non-200 Responses

    Why: 29 URLs return non-200 responses, hindering accessibility.

    How: Investigate and rectify pages returning 404 errors or redirects.

    Checks: status-codes

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 site lacks a Content Security Policy, which could allow unwanted content to load. A Google API key is exposed and should be restricted. Third-party scripts lack integrity protection, increasing vulnerability. Sensitive paths in the robots.txt may disclose private areas of the site.

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

    Missing Content Security PolicyMedium

    Why it matters: Without a Content Security Policy, the site is vulnerable to cross-site scripting (XSS) attacks.

    Fix: Implement a Content Security Policy header such as `Content-Security-Policy: default-src 'self';`.

    Evidence: Content Security Policy

  2. 2

    Exposed Google API KeyMedium

    Why it matters: An unprotected Google API key can be exploited, leading to unauthorized usage and potential billing issues.

    Fix: Restrict the API key in the Google Cloud console by setting HTTP referrer restrictions.

    Evidence: Keys and secrets in page code

  3. 3

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from other domains could be compromised, affecting your site if integrity settings are not applied.

    Fix: Implement Subresource Integrity with each third-party script tag or a Content Security Policy that securely whitelisted these domains.

    Evidence: Third-party scripts

  4. 4

    Sensitive Paths Listed in robots.txtInfo

    Why it matters: Publicly listing sensitive paths can aid attackers in attempting to access private areas.

    Fix: Remove or protect sensitive paths; instead, use proper access controls for these directories.

    Evidence: Sensitive paths in robots.txt

What the checks found

  • FoundContent Security PolicyMedium

    None of the 1266 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.jtccpas.com/ → no content-security-policy
    • https://www.jtccpas.com/services/acquisitions-and-mergers/ → no content-security-policy
    • https://www.jtccpas.com/services/bookkeeping/ → no content-security-policy
    • https://www.jtccpas.com/services/business-setup/ → no content-security-policy
    • https://www.jtccpas.com/services/business-exit-strategy/ → no content-security-policy
    • https://www.jtccpas.com/services/compilations/ → no content-security-policy
    • https://www.jtccpas.com/services/tax-planning/ → no content-security-policy
    • https://www.jtccpas.com/services/forecasting-and-budgeting/ → no content-security-policy
    • https://www.jtccpas.com/services/payroll-processing/ → no content-security-policy
    • https://www.jtccpas.com/services/tax-resolution/ → no content-security-policy
    • https://www.jtccpas.com/services/tax-return-preparation/ → no content-security-policy
    • https://www.jtccpas.com/team/ → no content-security-policy
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…Nk (39 chars) in https://www.jtccpas.com/contact/: 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 4 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.)

    • www.googletagmanager.com (40 script tags)
    • cdn.jsdelivr.net (40 script tags)
    • form.123formbuilder.com (9 script tags)
    • maps.googleapis.com (1 script tag)
  • 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/
10 checks passed, 2 not applicable
  • OKHTTPS

    All 1266 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 1266 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 1266 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 1266 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 1266 HTML pages.

  • OKPermissions policy

    permissions-policy is set on all 1266 HTML pages.

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

  • OKVulnerable JavaScript libraries

    1 library version 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.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

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

Own www.jtccpas.com?

www.jtccpas.com scan 2026-10-02-0442 | DIY SEO Hub