Scanned sites / jficpa.com / 2026-09-13-1532

jficpa.com scan from 2026-09-13 15:32:26 UTC DR 0

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

Scan 2026-09-13-1532

Scanned 2026-09-13 15:32:26 UTC, finished 2026-09-13 15:51:57 UTC. Found on page 4 of brave web search results

Site: https://jficpa.com/

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

72/ 100Needs work

On September 13, 2026 the Site Spider crawled 12 pages and 201 assets of jficpa.com, starting from https://jficpa.com/. It scored 72 out of 100, a result that needs work. 7 of 27 checks found something to fix, led by title tags (10), meta descriptions (11), sitemap coverage (6); 14 checks passed. Most of the points went to title tags (−9.1), meta descriptions (−8), sitemap coverage (−3.3). 6 checks found something the score does not count, listed as noted. 10 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, 5 medium and 1 low findings. See the security findings ↓

Pages crawled
12
Assets fetched
201
Status
Completed
Checks with issues
7 of 27
CoverageComplete crawl

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

  • Title tags10 issues
    10 of 11 pages have title issues.
    −9.1 points
  • Meta descriptions11 issues
    11 of 11 pages have meta description issues.
    −8 points
  • Headings4 issues
    4 of 11 pages have heading issues.
    −2.2 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesOK
    0 destinations answered with an error, of 2 destinations checked.
  • Redirects1 issue
    1 redirecting URL, 0 of them chained.
    −0.4 points
  • Non-200 responses3 noted
    3 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 11 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 50 image references have no alt attribute.
  • Heavy assets4 issues
    4 assets larger than 500 KB among 201 fetched assets.
    −2.4 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage6 issues
    No sitemap found. Tried: https://jficpa.com/sitemap.xml (404), https://jficpa.com/wp-sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −3.3 points
  • Internal link countsOK
    Internal link counts for 11 pages; none is a dead end or buried.
  • Thin content4 issues
    4 of 11 pages have fewer than 200 words.
    −2.9 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 12 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 11 pages have a canonical worth checking.
  • Robots directives11 noted
    11 pages carry a robots directive; 0 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure11 noted
    11 of 11 pages could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 11 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 10 response headers recorded across 213 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 11 pages; 0 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 Insights5 noted
    Mobile performance 77 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2455 sites, median 80%, average 78%

jficpa.com scores 72%, higher than 22% of the 2455 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%: 71 sites72%: 73 sites73%: 72 sites74%: 69 sites75%: 75 sites76%: 88 sites77%: 97 sites78%: 111 sites79%: 95 sites80%: 117 sites81%: 110 sites82%: 115 sites83%: 110 sites84%: 113 sites85%: 93 sites86%: 73 sites87%: 79 sites88%: 60 sites89%: 69 sites90%: 42 sites91%: 51 sites92%: 40 sites93%: 26 sites94%: 21 sites95%: 12 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites72% 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

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

The site requires attention for several SEO issues that could enhance visibility. Key priorities involve fixing redirects, improving titles and meta descriptions, addressing headings, creating a sitemap, and boosting content length.

  1. 1

    Fix Redirects

    Why: Improve user experience and ensure proper indexing.

    How: Update the link to point directly to the final URL without a redirect.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 errors can hinder site indexing and user access.

    How: Identify the 3 URLs returning errors and fix them to return a 200 status.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Critical for SEO rankings and click-through rates.

    How: Rewrite titles to be unique, concise (under 60 characters), and relevant for each page.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Essential for search visibility and enticing clicks from SERPs.

    How: Create unique meta descriptions for each page, under 160 characters.

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: Correct headings improve SEO and content structure.

    How: Ensure each page has one H1 tag and use H2, H3 as appropriate.

    Checks: headings

  6. 6

    Create a Sitemap

    Why: A sitemap helps search engines index your site effectively.

    How: Create a sitemap.xml file and place it at the root of your website.

    Checks: sitemap-coverage

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 security review of your website reveals critical issues such as the transmission of pages over unencrypted HTTP, lack of necessary security headers, and mixed content load. These vulnerabilities could expose your visitors' data and the integrity of your site. Addressing these will significantly enhance your site's security.

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

    HTTP Pages ExposedHigh

    Why it matters: 6 pages respond over HTTP, allowing interception.

    Fix: Redirect all HTTP traffic to HTTPS by configuring your web server.

    Evidence: HTTPS

  2. 2

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Absence of HSTS allows initial connections over HTTP.

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

    Evidence: HTTP Strict Transport Security

  3. 3

    No Content Security PolicyMedium

    Why it matters: Lack of CSP increases vulnerability to XSS attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self';.

    Evidence: Content Security Policy

  4. 4

    No Clickjacking ProtectionMedium

    Why it matters: Pages can be embedded in frames, risking user interactions.

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

    Evidence: Clickjacking protection

  5. 5

    Mixed Content IssuesMedium

    Why it matters: Resources loaded over HTTP can be intercepted or modified.

    Fix: Update all resource links to use HTTPS.

    Evidence: Mixed content

  6. 6

    Unencrypted Form SubmissionMedium

    Why it matters: Forms on HTTP can expose sensitive data during submission.

    Fix: Ensure forms are served only over HTTPS.

    Evidence: Forms over HTTPS

  7. 7

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without this header, incorrect MIME types may execute code.

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

    Evidence: MIME sniffing protection

What the checks found

  • FoundHTTPSHigh

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

    • http://jficpa.com/ → 200 over http
    • http://jficpa.com/services/ → 200 over http
    • http://jficpa.com/about-us/ → 200 over http
    • http://jficpa.com/privacy-policy/ → 200 over http
    • http://jficpa.com/client-login/ → 200 over http
    • http://jficpa.com/contact-us/ → 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://jficpa.com/ → no strict-transport-security
    • https://jficpa.com/about-us/ → no strict-transport-security
    • https://jficpa.com/services/ → no strict-transport-security
    • https://jficpa.com/client-login/ → no strict-transport-security
    • https://jficpa.com/contact-us/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 11 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://jficpa.com/ → no content-security-policy
    • http://jficpa.com/ → no content-security-policy
    • https://jficpa.com/about-us/ → no content-security-policy
    • https://jficpa.com/services/ → no content-security-policy
    • https://jficpa.com/client-login/ → no content-security-policy
    • https://jficpa.com/contact-us/ → no content-security-policy
    • http://jficpa.com/services/ → no content-security-policy
    • http://jficpa.com/about-us/ → no content-security-policy
    • http://jficpa.com/privacy-policy/ → no content-security-policy
    • http://jficpa.com/client-login/ → no content-security-policy
    • http://jficpa.com/contact-us/ → 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://jficpa.com/ → no x-frame-options
    • http://jficpa.com/ → no x-frame-options
    • https://jficpa.com/about-us/ → no x-frame-options
    • https://jficpa.com/services/ → no x-frame-options
    • https://jficpa.com/client-login/ → no x-frame-options
    • https://jficpa.com/contact-us/ → no x-frame-options
    • http://jficpa.com/services/ → no x-frame-options
    • http://jficpa.com/about-us/ → no x-frame-options
    • http://jficpa.com/privacy-policy/ → no x-frame-options
    • http://jficpa.com/client-login/ → no x-frame-options
    • http://jficpa.com/contact-us/ → 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://jficpa.com/ → no x-content-type-options
    • http://jficpa.com/ → no x-content-type-options
    • https://jficpa.com/about-us/ → no x-content-type-options
    • https://jficpa.com/services/ → no x-content-type-options
    • https://jficpa.com/client-login/ → no x-content-type-options
    • https://jficpa.com/contact-us/ → no x-content-type-options
    • http://jficpa.com/services/ → no x-content-type-options
    • http://jficpa.com/about-us/ → no x-content-type-options
    • http://jficpa.com/privacy-policy/ → no x-content-type-options
    • http://jficpa.com/client-login/ → no x-content-type-options
    • http://jficpa.com/contact-us/ → no x-content-type-options
  • FoundMixed contentMedium

    5 resources on HTTPS pages are loaded over plain HTTP, 5 of them scripts or stylesheets that browsers block or that can be tampered with in transit.

    • https://jficpa.com/ loads stylesheet http://jficpa.com/wp-content/uploads/elementor/google-fonts/css/poppins.css?ver=1742291339
    • https://jficpa.com/about-us/ loads stylesheet http://jficpa.com/wp-content/uploads/elementor/google-fonts/css/poppins.css?ver=1742291339
    • https://jficpa.com/services/ loads stylesheet http://jficpa.com/wp-content/uploads/elementor/google-fonts/css/poppins.css?ver=1742291339
    • https://jficpa.com/client-login/ loads stylesheet http://jficpa.com/wp-content/uploads/elementor/google-fonts/css/poppins.css?ver=1742291339
    • https://jficpa.com/contact-us/ loads stylesheet http://jficpa.com/wp-content/uploads/elementor/google-fonts/css/poppins.css?ver=1742291339
  • FoundForms over HTTPSMedium

    2 forms would send what visitors type over plain HTTP, where it can be read or changed on the way.

    • http://jficpa.com/services/ has 1 form on a page served over plain HTTP
    • http://jficpa.com/contact-us/ has 2 forms on a page served over plain HTTP
  • 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.)

    • www.google.com (11 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/
4 checks passed, 3 not applicable
  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKVulnerable JavaScript libraries

    2 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 applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

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

Own jficpa.com?