HTTP Headers Analyzer
6 / 10
https://seonettools.site
WordPress → LiteSpeed → Browser9 missing headers, 1 warnings, 1 notices
Header
Value
Explanation
x-ua-compatible
ie=edge
Instructs Internet Explorer what compatibility mode to use to render this page. For example,
ie=9
specifies that the page should be rendered as if the user was using Internet Explorer 9, even if they use Internet Explorer 11 or later. It's basically a hack for working around compatibility issues between different versions of Internet Explorer.link
<https://seonettools.site/wp-json/>; rel="https://api.w.org/"
rel="https://api.w.org/"
is where you can learn more about WordPress' REST API. Applications can interact with this WordPress site by sending and receiving JSON objects.cache-control
public, max-age=0
public
means the response may be stored by all caches, including browser caches, CDNs, and shared caches.max-age
specifies the maximum amount of seconds a page is considered valid. The higher max-age
, the longer a page can be cached.Warning Because
max-age
is set to 0 seconds, nothing will ever be cached in shared caches or browsers. Caching is effectively disabled!expires
thu, 26 dec 2024 08:44:24 gmt
This
Notice Because there is a
Expires
date is in the past: the page is considered stale and will be removed from all caches.Notice Because there is a
Cache-Control
header with a max-age
and/or s-maxage
directive, the Expires
header will be ignored. Consider removing Expires
to save bandwidth and processing power.x-litespeed-cache
hit
The page was served from LiteSpeed's cache.
date
thu, 26 dec 2024 11:34:44 gmt
The date and time at which the request was made. A browser uses it for age calculations rather than using its own internal date and time; e.g. when comparing against
Max-Age
or Expires
.server
litespeed
x-turbo-charged-by
litespeed
Some of the software used to generate or serve this page.
strict-transport-security
missing Add a
Strict-Transport-Security
header. The Strict-Transport-Security
header or HSTS header is used to instruct browsers to only use HTTPS, instead of using HTTP. It helps enforce secure communication.content-security-policy
missing Add a
Content-Security-Policy
header. The Content-Security-Policy
header helps browsers prevent cross site scripting (XSS) and data injection attacks.referrer-policy
missing Add a
Referrer-Policy
header. When a visitor navigates from one page to another, browsers often pass along referrer information. The Referrer-Policy
header controls how much referrer information a browser can share. This is important to configure when private information is embedded in the path or query string and passed onto an external destination.permissions-policy
missing Add a
Permissions-Policy
header. Restrict access to device features like the camera, microphone, location, accelerometer and much more.cross-origin-embedder-policy
missing Add a
Cross-Origin-Embedder-Policy
to specify how this page can be loaded by cross-origin resources.cross-origin-opener-policy
missing Add a
Cross-Origin-Opener-Policy
header to opt-in into better browser isolation.cross-origin-resource-policy
missing Add a
Cross-Origin-Resource-Policy
header to specify who can load this page.x-frame-options
missing Add a
X-Frame-Options
header. The X-Frame-Options
header prevents this URL from being embedded in an iframe
. This protects against clickjacking attacks. Alternatively, set a Content-Security-Policy
header with a frame-ancestor
directive.x-permitted-cross-domain-policies
missing Add a
X-Permitted-Cross-Domain-Policies
header to prevent Flash, Adobe Reader and other clients from sharing data across domains.Questions or feedback? Email dries@buytaert.net.