Scanned sites / www.greasemonkey.com / 2026-10-02-1900

www.greasemonkey.com scan from 10/2/2026, 7:00:15 PM

Scan 2026-10-02-1900

Scanned 10/2/2026, 7:00:15 PM, finished 10/3/2026, 12:19:34 AM. Found on page 3 of brave web search results

Site: https://www.greasemonkey.com/

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

87/ 100Good

On October 2, 2026 the Site Spider crawled 1507 pages and 1003 assets of www.greasemonkey.com, starting from https://www.greasemonkey.com/. It scored 87 out of 100, a good result. 12 of 16 checks found something to fix, led by sitemap coverage (1,462), title tags (528), meta descriptions (398); 3 checks passed. Most of the points went to sitemap coverage (−5.9), title tags (−3.5), meta descriptions (−2.1). 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 and 1 low findings. See the security findings ↓

Pages crawled
1507
Assets fetched
1003
Status
Completed
Checks with issues
12 of 16
CoverageJob finished, partial coverage

2,510 of 2,510 discovered URLs were fetched, 18,518 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, 1687 left unchecked.

  • Title tags528 issues
    528 of 1462 pages have title issues. 31 noindex or canonicalized pages excluded.
    −3.5 points
  • Meta descriptions398 issues
    398 of 1462 pages have meta description issues. 31 noindex or canonicalized pages excluded.
    −2.1 points
  • Headings5 issues
    5 of 1462 pages have heading issues. 31 noindex or canonicalized pages excluded.
  • Broken links3 issues
    4 internal links point at 3 broken URLs.
  • Links to other sites2 issues
    2 destinations answered with an error, 11 could not be determined (timeouts, rate limits or refusals), 1687 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.1 points
  • Redirects11 issues
    12 redirecting URLs, 3 of them chained.
  • Non-200 responses3 issues
    15 URLs did not return a 2xx response. 14 of them are pages, 3 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability31 issues
    31 of 1493 indexable pages have indexability warnings.
    −0.2 points
  • Image alt text6 issues
    6 of 24908 image references have no alt attribute. 32 use an empty alt (decorative), which is fine.
  • Heavy assets2 issues
    2 assets larger than 500 KB among 1003 fetched assets.
    −1.2 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage1,462 issues
    1 sitemap listing 0 URLs: 1462 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.9 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin contentOK
    0 of 1462 pages have fewer than 200 words. 31 noindex or canonicalized pages excluded.
  • Duplicate content3 issues
    1 group of pages with identical HTML.

Where this scan sits among all scanned sites

1883 sites, median 80%, average 79%

www.greasemonkey.com scores 87%, higher than 79% of the 1883 scanned sites. See the full ranking.

0541080%: 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%: 2 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 4 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 7 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 14 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 16 sites63%: 16 sites64%: 11 sites65%: 21 sites66%: 21 sites67%: 36 sites68%: 30 sites69%: 26 sites70%: 39 sites71%: 40 sites72%: 56 sites73%: 52 sites74%: 49 sites75%: 61 sites76%: 73 sites77%: 72 sites78%: 88 sites79%: 68 sites80%: 91 sites81%: 108 sites82%: 85 sites83%: 86 sites84%: 86 sites85%: 63 sites86%: 73 sites87%: 63 sites88%: 64 sites89%: 54 sites90%: 35 sites91%: 36 sites92%: 28 sites93%: 15 sites94%: 13 sites95%: 12 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 sites87% 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 some issues that require attention, including broken links, redirects, non-200 responses, and title/meta description problems. Addressing these will improve user experience and SEO performance.

  1. 1

    Fix Broken Links

    Why: Broken links hinder user navigation and negatively affect SEO.

    How: Update or remove links pointing to 404 pages. Ensure correct URLs are used.

    Checks: broken-links

  2. 2

    Resolve Redirect Issues

    Why: Chained redirects can slow page loading and confuse search engines.

    How: Simplify redirects by pointing directly to final URLs for smooth navigation.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: Pages not returning 2xx codes can lead to poor user experiences.

    How: Identify the URLs not responding and fix the underlying issues (e.g., errors).

    Checks: status-codes

  4. 4

    Improve Title Tags

    Why: Unique title tags are essential for SEO and user engagement.

    How: Revise duplicated and long titles to ensure they are unique and within 60 characters.

    Checks: titles

  5. 5

    Enhance Meta Descriptions

    Why: Unique meta descriptions can improve click-through rates from search results.

    How: Create distinct meta descriptions for pages to avoid duplication.

    Checks: meta-descriptions

  6. 6

    Update Sitemap

    Why: A complete sitemap improves indexing and search visibility.

    How: Ensure all relevant URLs are listed in your sitemap to assist search engines.

    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 website has some security issues that need attention. There's a vulnerable version of jQuery present, and an exposed Google API key that should be restricted to prevent unauthorized use. Additionally, some third-party scripts lack security controls, which could pose risks.

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

    Vulnerable jQuery Library DetectedMedium

    Why it matters: Using jQuery 3.0.1 exposes your site to known vulnerabilities, including XSS risks.

    Fix: Upgrade jQuery to version 3.5.0 or newer.

    Evidence: Vulnerable JavaScript libraries

  2. 2

    Exposed Google API KeyMedium

    Why it matters: A public Google API key can be misused unless properly restricted.

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

    Evidence: Keys and secrets in page code

  3. 3

    Missing Subresource Integrity on Third-Party ScriptsLow

    Why it matters: Scripts from external domains could be altered, compromising your site.

    Fix: Implement Content-Security-Policy to specify trusted script sources.

    Evidence: Third-party scripts

What the checks found

  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 3.0.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 3.0.1 in https://www.greasemonkey.com/wp-content/plugins/gravityforms/js/placeholders.jq…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…zQ (39 chars) in https://www.greasemonkey.com/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (2510 responses)
    • x-powered-by: WP Engine (1510 responses)
  • 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.)

    • www.google.com (3 script tags)
    • portal.autoops.com (2 script tags)
    • booking.cinch.io (2 script tags)
12 checks passed
  • OKHTTPS

    All 1493 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKReferrer policy

    referrer-policy is set on all 1493 HTML pages.

  • OKPermissions policy

    permissions-policy is set on all 1493 HTML pages.

  • 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

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

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

Own www.greasemonkey.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.greasemonkey.com. Removal needs no account and no proof of purchase.
www.greasemonkey.com scan 2026-10-02-1900 | DIY SEO Hub