Scanned sites / www.fickleroilcompany.com / 2026-09-28-0000

www.fickleroilcompany.com scan from 2026-09-28 00:00:01 UTC DR 0

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

Scan 2026-09-28-0000

Scanned 2026-09-28 00:00:01 UTC, finished 2026-09-28 00:05:00 UTC. Found on page 1 of chatgpt for browser (api usage) results

Site: https://www.fickleroilcompany.com/contact

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

83/ 100Good

On September 28, 2026 the Site Spider crawled 13 pages and 238 assets of www.fickleroilcompany.com, starting from https://www.fickleroilcompany.com/contact. It scored 83 out of 100, a good result. 4 of 27 checks found something to fix, led by indexability (13), heavy assets (35), title tags (1); 16 checks passed. Most of the points went to indexability (−10), heavy assets (−6), title tags (−0.8). 7 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: Medium3 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
13
Assets fetched
238
Status
Completed
Checks with issues
4 of 27
CoverageComplete crawl

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

  • Title tags1 issue
    1 of 1 page have title issues. 12 noindex or canonicalized pages excluded.
    −0.8 points
  • Meta descriptionsOK
    0 of 1 page have meta description issues. 12 noindex or canonicalized pages excluded.
  • HeadingsOK
    0 of 1 page have heading issues. 12 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites11 noted
    0 destinations answered with an error, 5 could not be determined (timeouts, rate limits or refusals), of 16 destinations checked.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses4 noted
    4 URLs did not return a 2xx response. 0 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.
  • Indexability13 issues
    13 of 13 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 242 image references have no alt attribute.
  • Heavy assets35 issues
    35 assets larger than 500 KB among 238 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverageOK
    1 sitemap listing 12 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Internal link countsOK
    Internal link counts for 13 pages; none is a dead end or buried.
  • Thin content1 issue
    1 of 1 page have fewer than 200 words. 12 noindex or canonicalized pages excluded.
    −0.6 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 13 page URLs are plain lowercase addresses without parameters.
  • Canonicals12 noted
    12 of 13 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 13 pages are open to search engines.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure1 noted
    1 of 1 page could use the title, heading and snippet space better. 12 noindex or canonicalized pages excluded.
  • Image weight and alt length179 noted
    179 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • 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 13 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; 11 response headers recorded across 251 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 13 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 51 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

2909 sites, median 80%, average 79%

www.fickleroilcompany.com scores 83%, higher than 61% of the 2909 scanned sites. See the full ranking.

0761520%: 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%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites83% 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 (rules v4). 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.

Your site has a good health score, but there are important issues to address, particularly with indexability, title tags, and heavy assets. Improving these elements will enhance user experience and SEO performance.

  1. 1

    Fix Title Tag Length

    Why: The title tag is too short, affecting SEO quality.

    How: Update the title to be more descriptive and at least 50 characters long.

    Checks: titles

  2. 2

    Resolve Canonical Issues

    Why: Incorrect canonical URLs can confuse search engines regarding your content's primary version.

    How: Correct the canonical tags on affected pages to point to their proper URLs without trailing slashes.

    Checks: indexability

  3. 3

    Reduce Heavy Assets Size

    Why: Heavy assets can slow down your site, impacting user experience.

    How: Optimize or compress the identified heavy assets to reduce their size.

    Checks: heavy-assets

  4. 4

    Revise Thin Content

    Why: The homepage has insufficient text, which can hinder SEO performance.

    How: Add more relevant content to increase the word count above 200 words.

    Checks: thin-content

  5. 5

    Address Non-200 Responses

    Why: Missing assets can lead to broken experiences on the site.

    How: Fix or remove links to the assets returning errors.

    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 website lacks essential security headers that can protect user data and enhance security against various attacks. Immediate attention is required to implement these headers and update outdated libraries to mitigate potential vulnerabilities.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, attackers can intercept data on initial requests from users who type the URL without HTTPS.

    Fix: Add the following header in your server configuration: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows unrestricted loading of scripts and resources, increasing vulnerability to attacks like XSS.

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

    Evidence: Content Security Policy

  3. 3

    Outdated JavaScript LibrariesMedium

    Why it matters: Using vulnerable versions of jQuery and Bootstrap can expose the site to various attacks.

    Fix: Upgrade jQuery to at least 3.5.0 and Bootstrap to at least 3.4.1.

    Evidence: Vulnerable JavaScript libraries

  4. 4

    No Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive information from URLs can be leaked to external sites.

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

    Evidence: Referrer policy

  5. 5

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Using scripts from other domains without integrity checks poses risk if those domains are compromised.

    Fix: Consider defining a Content-Security-Policy that whitelists approved script sources.

    Evidence: Third-party scripts

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Lack of permissions policy can leave browser features accessible to potentially harmful scripts.

    Fix: Add: Permissions-Policy: geolocation=(self), microphone=(), camera=()

    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://www.fickleroilcompany.com/contact → no strict-transport-security
    • https://www.fickleroilcompany.com/ → no strict-transport-security
    • https://www.fickleroilcompany.com/about → no strict-transport-security
    • https://www.fickleroilcompany.com/staff → no strict-transport-security
    • https://www.fickleroilcompany.com/bulk-fuel → no strict-transport-security
    • https://www.fickleroilcompany.com/distributing → no strict-transport-security
    • https://www.fickleroilcompany.com/fics-plaza → no strict-transport-security
    • https://www.fickleroilcompany.com/fics → no strict-transport-security
    • https://www.fickleroilcompany.com/dinomart → no strict-transport-security
    • https://www.fickleroilcompany.com/indian-creek-campground → no strict-transport-security
    • https://www.fickleroilcompany.com/golden-spike-casino → no strict-transport-security
    • https://www.fickleroilcompany.com/job-openings → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 13 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.fickleroilcompany.com/contact → no content-security-policy
    • https://www.fickleroilcompany.com/ → no content-security-policy
    • https://www.fickleroilcompany.com/about → no content-security-policy
    • https://www.fickleroilcompany.com/staff → no content-security-policy
    • https://www.fickleroilcompany.com/bulk-fuel → no content-security-policy
    • https://www.fickleroilcompany.com/distributing → no content-security-policy
    • https://www.fickleroilcompany.com/fics-plaza → no content-security-policy
    • https://www.fickleroilcompany.com/fics → no content-security-policy
    • https://www.fickleroilcompany.com/dinomart → no content-security-policy
    • https://www.fickleroilcompany.com/indian-creek-campground → no content-security-policy
    • https://www.fickleroilcompany.com/golden-spike-casino → no content-security-policy
    • https://www.fickleroilcompany.com/job-openings → no content-security-policy
  • 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://www.fickleroilcompany.com/contact → no referrer-policy
    • https://www.fickleroilcompany.com/ → no referrer-policy
    • https://www.fickleroilcompany.com/about → no referrer-policy
    • https://www.fickleroilcompany.com/staff → no referrer-policy
    • https://www.fickleroilcompany.com/bulk-fuel → no referrer-policy
    • https://www.fickleroilcompany.com/distributing → no referrer-policy
    • https://www.fickleroilcompany.com/fics-plaza → no referrer-policy
    • https://www.fickleroilcompany.com/fics → no referrer-policy
    • https://www.fickleroilcompany.com/dinomart → no referrer-policy
    • https://www.fickleroilcompany.com/indian-creek-campground → no referrer-policy
    • https://www.fickleroilcompany.com/golden-spike-casino → no referrer-policy
    • https://www.fickleroilcompany.com/job-openings → 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://www.fickleroilcompany.com/contact → no permissions-policy
    • https://www.fickleroilcompany.com/ → no permissions-policy
    • https://www.fickleroilcompany.com/about → no permissions-policy
    • https://www.fickleroilcompany.com/staff → no permissions-policy
    • https://www.fickleroilcompany.com/bulk-fuel → no permissions-policy
    • https://www.fickleroilcompany.com/distributing → no permissions-policy
    • https://www.fickleroilcompany.com/fics-plaza → no permissions-policy
    • https://www.fickleroilcompany.com/fics → no permissions-policy
    • https://www.fickleroilcompany.com/dinomart → no permissions-policy
    • https://www.fickleroilcompany.com/indian-creek-campground → no permissions-policy
    • https://www.fickleroilcompany.com/golden-spike-casino → no permissions-policy
    • https://www.fickleroilcompany.com/job-openings → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 2.1.3 in https://www.fickleroilcompany.com/js/jquery-2.1.3.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 2.0.4 in https://www.fickleroilcompany.com/js/plugins.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
    • Bootstrap 3.3.1 in https://www.fickleroilcompany.com/js/bootstrap.min.js: CVE-2016-10735, CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 3.4.1
  • 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.)

    • kit.fontawesome.com (13 script tags)
    • challenges.cloudflare.com (2 script tags)
    • edge-js.pages.dev (2 script tags)
    • connect.facebook.net (4 script tags)
9 checks passed, 1 not applicable
  • OKHTTPS

    All 13 crawled pages were served over HTTPS.

  • OKClickjacking protection

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

  • OKMIME sniffing protection

    x-content-type-options is set on all 13 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.

  • OKForms over HTTPS

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

  • Not applicableCookie flags

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

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

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