Scanned sites / johnstonmingmanning.com / 2026-11-01-1626

johnstonmingmanning.com scan from 2026-11-01 16:26:24 UTC DR 11

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

Scan 2026-11-01-1626

Scanned 2026-11-01 16:26:24 UTC, finished 2026-11-01 16:46:07 UTC. Found on page 1 of brave web search results

Site: https://johnstonmingmanning.com/

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

86/ 100Good

On November 1, 2026 the Site Spider crawled 83 pages and 95 assets of johnstonmingmanning.com, starting from https://johnstonmingmanning.com/. It scored 86 out of 100, a good result. 9 of 33 checks found something to fix, led by meta descriptions (60), thin content (29), sitemap coverage (25); 13 checks passed. Most of the points went to meta descriptions (−6), thin content (−2.9), sitemap coverage (−1.9). 11 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, 2 low and 1 info findings. See the security findings ↓

Pages crawled
83
Assets fetched
95
Status
Completed
Checks with issues
9 of 33
CoverageComplete crawl

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

  • Title tags11 issues
    11 of 73 pages have title issues. 7 noindex or canonicalized pages excluded.
    −1.4 points
  • Meta descriptions60 issues
    60 of 73 pages have meta description issues. 7 noindex or canonicalized pages excluded.
    −6 points
  • Headings1 issue
    1 of 73 pages have heading issues. 7 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites2 noted
    0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 4 destinations checked.
  • Redirects3 issues
    9 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses14 noted
    14 URLs did not return a 2xx response. 3 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 80 indexable pages have indexability warnings.
  • Image alt text1 issue
    1 of 426 image references have no alt attribute. 181 use an empty alt (decorative), which is fine.
  • Heavy assets1 issue
    1 asset larger than 500 KB among 95 fetched assets.
    −0.6 points
  • Orphan pages25 issues
    25 pages have no internal links pointing at them.
    −1.3 points
  • Sitemap coverage25 issues
    10 sitemaps listing 73 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 25 reachable only via the sitemap.
    −1.9 points
  • Internal link countsOK
    Internal link counts for 80 pages; none is a dead end or buried.
  • Thin content29 issues
    29 of 73 pages have fewer than 200 words. 7 noindex or canonicalized pages excluded.
    −2.9 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format20 noted
    20 of 83 page URLs are harder to read, share or cache than they need to be.
  • Canonicals7 noted
    7 of 80 pages have a canonical worth checking.
  • Robots directives80 noted
    80 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 structure39 noted
    39 of 73 pages could use the title, heading and snippet space better. 7 noindex or canonicalized pages excluded.
  • Image weight and alt length7 noted
    7 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 80 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    80 of 73 indexable pages carry structured data: BreadcrumbList (80), ListItem (80), WebSite (80), https://www.schema.org/SiteNavigationElement (80), WebPage (63). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 48 pages with enough text to compare.
  • Soft 404sOK
    None of 80 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 positions5 noted
    5 of 48 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 cookiesOK
    1 cookie set by the site; 12 response headers recorded across 178 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 80 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling1 noted
    1 word an English dictionary does not know, on 3 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2499 sites, median 80%, average 78%

johnstonmingmanning.com scores 86%, higher than 76% of the 2499 scanned sites. See the full ranking.

0591180%: 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%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 5 sites51%: 5 sites52%: 8 sites53%: 8 sites54%: 8 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 8 sites60%: 15 sites61%: 12 sites62%: 20 sites63%: 28 sites64%: 21 sites65%: 31 sites66%: 37 sites67%: 36 sites68%: 37 sites69%: 49 sites70%: 48 sites71%: 73 sites72%: 72 sites73%: 74 sites74%: 73 sites75%: 76 sites76%: 88 sites77%: 99 sites78%: 112 sites79%: 98 sites80%: 118 sites81%: 111 sites82%: 112 sites83%: 113 sites84%: 117 sites85%: 93 sites86%: 79 sites87%: 85 sites88%: 61 sites89%: 70 sites90%: 45 sites91%: 53 sites92%: 40 sites93%: 27 sites94%: 21 sites95%: 13 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites86% 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 website has several key areas needing improvement, particularly around redirects, missing metadata, and internal linking. These changes can enhance SEO and user experience significantly.

  1. 1

    Fix Redirects

    Why: Redirects can dilute page authority and impact user experience.

    How: Update the URLs directly instead of relying on redirects for simpler navigation.

    Checks: redirects

  2. 2

    Update Title Tags

    Why: Optimizing title tags improves CTR and helps search engines understand your pages better.

    How: Revise the titles for the 11 pages to keep them under 60 characters.

    Checks: titles

  3. 3

    Enhance Meta Descriptions

    Why: Meta descriptions are crucial for click-through rates from search results.

    How: Write concise and compelling meta descriptions for the 60 pages identified.

    Checks: meta-descriptions

  4. 4

    Add H1 Headings

    Why: Headings are important for SEO and improving content readability.

    How: Add a suitable H1 heading to the page missing it.

    Checks: headings

  5. 5

    Address Orphan Pages

    Why: Orphan pages are not easily discoverable, reducing their SEO impact.

    How: Link the 25 orphan pages from relevant internal pages.

    Checks: orphan-pages

  6. 6

    Revise Thin Content

    Why: Thin pages can hurt your ranking and user engagement.

    How: Enhance the content of the 29 pages to provide more value to visitors.

    Checks: thin-content

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 vulnerabilities that need immediate attention. Key issues include the absence of important headers to protect against various attacks and outdated libraries with known vulnerabilities. Implementing security headers and updating libraries will significantly enhance your site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, initial requests without HTTPS can be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows scripts and styles from any source, increasing risk of XSS.

    Fix: Implement a CSP header like: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without this, pages can be embedded in frames, enabling clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Outdated JavaScript Libraries with VulnerabilitiesMedium

    Why it matters: Using vulnerable versions of jQuery and Bootstrap may expose your site to exploits.

    Fix: Update jQuery to at least 3.5.0 and Bootstrap to at least 4.3.1.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Absence of this header allows browsers to ignore declared types, risking execution of malicious content.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-PolicyLow

    Why it matters: Without it, sensitive URLs may be exposed to third-party sites.

    Fix: Add the header: Referrer-Policy: no-referrer.

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: It limits the use of browser features by scripts, reducing the potential for harmful exploitation.

    Fix: Add the header: Permissions-Policy: accelerometer=(), 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://johnstonmingmanning.com/ → no strict-transport-security
    • https://johnstonmingmanning.com/areas-of-practice/ → no strict-transport-security
    • https://johnstonmingmanning.com/meet-our-team/ → no strict-transport-security
    • https://johnstonmingmanning.com/category/news/ → no strict-transport-security
    • https://johnstonmingmanning.com/careers/ → no strict-transport-security
    • https://johnstonmingmanning.com/about-us/ → no strict-transport-security
    • https://johnstonmingmanning.com/request-a-consult/ → no strict-transport-security
    • https://johnstonmingmanning.com/areas_of_practice/civil-litigation/ → no strict-transport-security
    • https://johnstonmingmanning.com/areas_of_practice/employment-law/ → no strict-transport-security
    • https://johnstonmingmanning.com/areas_of_practice/property-disputes/ → no strict-transport-security
    • https://johnstonmingmanning.com/areas_of_practice/commercial-litigation/ → no strict-transport-security
    • https://johnstonmingmanning.com/areas_of_practice/debtor-creditor-law/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 80 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://johnstonmingmanning.com/ → no content-security-policy
    • https://johnstonmingmanning.com/areas-of-practice/ → no content-security-policy
    • https://johnstonmingmanning.com/meet-our-team/ → no content-security-policy
    • https://johnstonmingmanning.com/category/news/ → no content-security-policy
    • https://johnstonmingmanning.com/careers/ → no content-security-policy
    • https://johnstonmingmanning.com/about-us/ → no content-security-policy
    • https://johnstonmingmanning.com/request-a-consult/ → no content-security-policy
    • https://johnstonmingmanning.com/areas_of_practice/civil-litigation/ → no content-security-policy
    • https://johnstonmingmanning.com/areas_of_practice/employment-law/ → no content-security-policy
    • https://johnstonmingmanning.com/areas_of_practice/property-disputes/ → no content-security-policy
    • https://johnstonmingmanning.com/areas_of_practice/commercial-litigation/ → no content-security-policy
    • https://johnstonmingmanning.com/areas_of_practice/debtor-creditor-law/ → 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://johnstonmingmanning.com/ → no x-frame-options
    • https://johnstonmingmanning.com/areas-of-practice/ → no x-frame-options
    • https://johnstonmingmanning.com/meet-our-team/ → no x-frame-options
    • https://johnstonmingmanning.com/category/news/ → no x-frame-options
    • https://johnstonmingmanning.com/careers/ → no x-frame-options
    • https://johnstonmingmanning.com/about-us/ → no x-frame-options
    • https://johnstonmingmanning.com/request-a-consult/ → no x-frame-options
    • https://johnstonmingmanning.com/areas_of_practice/civil-litigation/ → no x-frame-options
    • https://johnstonmingmanning.com/areas_of_practice/employment-law/ → no x-frame-options
    • https://johnstonmingmanning.com/areas_of_practice/property-disputes/ → no x-frame-options
    • https://johnstonmingmanning.com/areas_of_practice/commercial-litigation/ → no x-frame-options
    • https://johnstonmingmanning.com/areas_of_practice/debtor-creditor-law/ → 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://johnstonmingmanning.com/ → no x-content-type-options
    • https://johnstonmingmanning.com/areas-of-practice/ → no x-content-type-options
    • https://johnstonmingmanning.com/meet-our-team/ → no x-content-type-options
    • https://johnstonmingmanning.com/category/news/ → no x-content-type-options
    • https://johnstonmingmanning.com/careers/ → no x-content-type-options
    • https://johnstonmingmanning.com/about-us/ → no x-content-type-options
    • https://johnstonmingmanning.com/request-a-consult/ → no x-content-type-options
    • https://johnstonmingmanning.com/areas_of_practice/civil-litigation/ → no x-content-type-options
    • https://johnstonmingmanning.com/areas_of_practice/employment-law/ → no x-content-type-options
    • https://johnstonmingmanning.com/areas_of_practice/property-disputes/ → no x-content-type-options
    • https://johnstonmingmanning.com/areas_of_practice/commercial-litigation/ → no x-content-type-options
    • https://johnstonmingmanning.com/areas_of_practice/debtor-creditor-law/ → 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://johnstonmingmanning.com/ → no referrer-policy
    • https://johnstonmingmanning.com/areas-of-practice/ → no referrer-policy
    • https://johnstonmingmanning.com/meet-our-team/ → no referrer-policy
    • https://johnstonmingmanning.com/category/news/ → no referrer-policy
    • https://johnstonmingmanning.com/careers/ → no referrer-policy
    • https://johnstonmingmanning.com/about-us/ → no referrer-policy
    • https://johnstonmingmanning.com/request-a-consult/ → no referrer-policy
    • https://johnstonmingmanning.com/areas_of_practice/civil-litigation/ → no referrer-policy
    • https://johnstonmingmanning.com/areas_of_practice/employment-law/ → no referrer-policy
    • https://johnstonmingmanning.com/areas_of_practice/property-disputes/ → no referrer-policy
    • https://johnstonmingmanning.com/areas_of_practice/commercial-litigation/ → no referrer-policy
    • https://johnstonmingmanning.com/areas_of_practice/debtor-creditor-law/ → 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://johnstonmingmanning.com/ → no permissions-policy
    • https://johnstonmingmanning.com/areas-of-practice/ → no permissions-policy
    • https://johnstonmingmanning.com/meet-our-team/ → no permissions-policy
    • https://johnstonmingmanning.com/category/news/ → no permissions-policy
    • https://johnstonmingmanning.com/careers/ → no permissions-policy
    • https://johnstonmingmanning.com/about-us/ → no permissions-policy
    • https://johnstonmingmanning.com/request-a-consult/ → no permissions-policy
    • https://johnstonmingmanning.com/areas_of_practice/civil-litigation/ → no permissions-policy
    • https://johnstonmingmanning.com/areas_of_practice/employment-law/ → no permissions-policy
    • https://johnstonmingmanning.com/areas_of_practice/property-disputes/ → no permissions-policy
    • https://johnstonmingmanning.com/areas_of_practice/commercial-litigation/ → no permissions-policy
    • https://johnstonmingmanning.com/areas_of_practice/debtor-creditor-law/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    3 libraries with published vulnerabilities: jQuery 1.9.1, jQuery 3.2.1, Bootstrap 4.0.0. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.9.1 in https://johnstonmingmanning.com/wp-content/themes/jmm/js/lib/bootstrap.min.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery 3.2.1 in https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • Bootstrap 4.0.0 in https://johnstonmingmanning.com/wp-content/themes/jmm/js/lib/bootstrap.min.js: CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 4.3.1
  • NoteThird-party scripts

    Scripts run from 3 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.)

    • ajax.googleapis.com (40 script tags)
    • maps.googleapis.com (40 script tags)
    • www.google.com (30 script tags)
8 checks passed
  • OKHTTPS

    All 80 crawled pages were served over HTTPS.

  • OKSoftware version disclosure

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

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

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

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

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

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

Own johnstonmingmanning.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 johnstonmingmanning.com. Removal needs no account and no proof of purchase.