Scanned sites / statelinepropaneoil.com / 2026-09-17-1200
statelinepropaneoil.com scan from 9/17/2026, 12:00:01 PM
Scan 2026-09-17-1200
Scanned 9/17/2026, 12:00:01 PM, finished 9/17/2026, 12:00:09 PM. Found on page 3 of chatgpt for browser (api usage) results
Site: https://statelinepropaneoil.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 17, 2026 the Site Spider crawled 1 page and 2 assets of statelinepropaneoil.com, starting from https://statelinepropaneoil.com/. It scored 100 out of 100, an excellent result. All 14 checks passed: nothing needs fixing.
Security review: Medium4 medium, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 1
- Assets fetched
- 2
- Status
- Completed
- Checks with issues
- 0 of 14
- Title tagsOK0 of 0 pages have title issues. 1 noindex or canonicalized page excluded.
- Meta descriptionsOK0 of 0 pages have meta description issues. 1 noindex or canonicalized page excluded.
- HeadingsOK0 of 0 pages have heading issues. 1 noindex or canonicalized page excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responsesOK0 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 0 indexable pages have indexability warnings. 1 page noindex by design.
- Image alt textOK0 of 0 image references have no alt attribute.
- Heavy assetsOK0 assets larger than 500 KB among the 2 heaviest.
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverageOK1 sitemap listing 0 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
- Thin contentOK0 of 0 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1063 sites, median 82%, average 80%
statelinepropaneoil.com scores 100%, higher than 99% of the 1063 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 website is well-optimized with a perfect health score. Consider improving site performance by optimizing your assets, though no larger assets were found. Maintaining this standard will help ensure ongoing success.
- 1
Monitor Asset Sizes
Why: Though currently no heavy assets exist, regular checks ensure you stay within optimal limits.
How: Set up alerts or regular checks for asset sizes above 500 KB.
Checks: heavy-assets
- 2
Optimize Large Assets (If Identified in Future)
Why: Reducing large asset sizes improves load speed, enhancing user experience and SEO.
How: Use tools like ImageOptim for images or Gzip for CSS/JavaScript compression.
Checks: heavy-assets
- 3
Regularly Update Sitemap
Why: A current sitemap helps search engines index your pages more effectively.
How: Ensure your sitemap is up-to-date with all relevant page URLs.
Checks: heavy-assets
- 4
Utilize a CDN
Why: Using a Content Delivery Network can speed up asset delivery across different locations.
How: Select a CDN provider, integrate it with your site to cache and serve assets.
Checks: heavy-assets
- 5
Conduct Periodic Performance Audits
Why: Ongoing audits will help detect and resolve issues before they impact SEO.
How: Schedule regular audits using tools like GTmetrix or Google PageSpeed Insights.
Checks: heavy-assets
- 6
Ensure Mobile Optimization
Why: Mobile-friendly sites improve user experience and search rankings.
How: Test mobile responsiveness regularly using Google's Mobile-Friendly Test tool.
Checks: heavy-assets
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 statelinepropaneoil.com has several security configurations missing, which could expose it to various attacks or data leakage. Implementing recommended headers will help mitigate these risks.
- 0 high
- 4 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors can be intercepted on the first request if they omit 'https://'.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: No CSP means the site is vulnerable to script injection and data theft.
Fix: Add the header: Content-Security-Policy: default-src 'self'
Evidence: Content Security Policy
- 3
Missing Clickjacking Protection (X-Frame-Options)Medium
Why it matters: Without this protection, the site can be embedded in a malicious frame.
Fix: Add the header: X-Frame-Options: DENY
Evidence: Clickjacking protection
- 4
Cookies Missing Secure and HttpOnly FlagsMedium
Why it matters: These flags prevent unauthorized access to cookies, enhancing security.
Fix: Set cookie flags to: Secure, HttpOnly, SameSite=Lax on the 'nevercache-b39818' cookie.
Evidence: Cookie flags
- 5
Missing MIME Sniffing Protection (X-Content-Type-Options)Low
Why it matters: This makes the site vulnerable to certain types of attacks targeting content types.
Fix: Add the header: X-Content-Type-Options: nosniff
Evidence: MIME sniffing protection
- 6
Missing Referrer PolicyLow
Why it matters: Without this policy, sensitive URL information is sent to other sites.
Fix: Add the header: Referrer-Policy: no-referrer
Evidence: Referrer policy
- 7
Missing Permissions PolicyInfo
Why it matters: This could limit the capabilities of unwanted scripts on your site.
Fix: Add the header: Permissions-Policy: camera=(), microphone=(), 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://statelinepropaneoil.com/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 1 HTML page 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://statelinepropaneoil.com/ → 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://statelinepropaneoil.com/ → 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://statelinepropaneoil.com/ → 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://statelinepropaneoil.com/ → 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://statelinepropaneoil.com/ → no permissions-policy
- FoundCookie flagsMedium
1 of 1 cookie are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.
- nevercache-b39818 (set by https://statelinepropaneoil.com/) lacks Secure, HttpOnly, SameSite
7 checks passed, 2 not applicable
- OKHTTPS
All 1 crawled page were served over HTTPS.
- 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.
- 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.
- OKThird-party scripts
The sampled pages load no scripts from other domains.
- OKSensitive paths in robots.txt
robots.txt does not point at admin, backup or private paths.
- Not applicableForms over HTTPS
No forms were found on the sampled pages.
- Not applicableVulnerable JavaScript libraries
No recognisable library versions were found in the sampled scripts.
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.
This report was produced by the DIY SEO Hub Site Spider crawling statelinepropaneoil.com from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.