Scanned sites / www.fickleroilcompany.com / 2026-09-28-0000
www.fickleroilcompany.com scan from 9/28/2026, 12:00:01 AM
Scan 2026-09-28-0000
Scanned 9/28/2026, 12:00:01 AM, finished 9/28/2026, 12:05:00 AM. 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.
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. 5 of 16 checks found something to fix, led by indexability (13), heavy assets (35), links to other sites (5); 9 checks passed. Most of the points went to indexability (−10), heavy assets (−6), links to other sites (−2). 2 checks 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: Medium3 medium, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 13
- Assets fetched
- 238
- Status
- Completed
- Checks with issues
- 5 of 16
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 issue1 of 1 page have title issues. 12 noindex or canonicalized pages excluded.−0.8 points
- Meta descriptionsOK0 of 1 page have meta description issues. 12 noindex or canonicalized pages excluded.
- HeadingsOK0 of 1 page have heading issues. 12 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites5 issues5 destinations answered with an error, 5 could not be determined (timeouts, rate limits or refusals), of 16 destinations checked.−2 points
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responses4 noted4 URLs did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability13 issues13 of 13 indexable pages have indexability warnings.−10 points
- Image alt textOK0 of 242 image references have no alt attribute.
- Heavy assets35 issues35 assets larger than 500 KB among 238 fetched assets.−6 points
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverageOK1 sitemap listing 12 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
- Internal link countsOKInternal link counts for 13 pages.
- Thin content1 issue1 of 1 page have fewer than 200 words. 12 noindex or canonicalized pages excluded.−0.6 points
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1318 sites, median 80%, average 79%
www.fickleroilcompany.com scores 83%, higher than 62% of the 1318 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsYour 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
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
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
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
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
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 crawlThe 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
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
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
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
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
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
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.
- mergedeck.com84/100 · rank 387 · 200 pages
- www.advocateslaw.com83/100 · rank 446 · 496 pages
- www.brightondentalstudio.com83/100 · rank 446 · 111 pages
- sleepwakeclinic.com83/100 · rank 446 · 103 pages
- www.theaffordableway.com83/100 · rank 446 · 655 pages
- www.beddingtondentalclinic.com83/100 · rank 446 · 158 pages
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.