Page summary

The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page.

Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance.

The main document gets redirected 1 time(s). Remove those redirect and make the page faster!

You should never ever redirect the main document, because it will make the page load slower for the user. Well, you should redirect the user if the user tries to use HTTP and there's an HTTPS version of the page. The coach checks for that. :)

Offenders

• https://elevaseo.com/

The total JavaScript transfer size is 593.9 kB and the uncompressed size is 2.1 MB. This is totally crazy! There is really room for improvement here.

A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?

Offenders

First contentful paint can be improved (2.156 s). It is in the Google Web Vitals needs improvement range, slower than 1.8 seconds.

The First Contentful Paint (FCP) metric measures the time from when the page starts loading to when any part of the page content is rendered on the screen. For this metric, "content" refers to text, images (including background images), <svg> elements, or non-white <canvas> elements.

The page has 5 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 10.4 kB the next access.

The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request.

Offenders

• https://elevaseo.com/
• https://analytics.elevaseo.app/op1.js?v=1.5.1
• https://www.elevaseo.com/services?_rsc=EylmaytQesAzsSpi
• https://www.elevaseo.com/contact?_rsc=EylmaytQesAzsSpi
• https://www.elevaseo.com/?_rsc=-FKW1KsA7p7dueVx

The page has 2 requests that are served uncompressed. You could save a lot of bytes by sending them compressed instead.

In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.

Offenders

The page has 2 font requests. Do you really need them? What value does the fonts give the user?

How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive.

Offenders

• https://www.elevaseo.com/_next/static/media/797e433ab948586e-s.p.09zddjkbdep5a.w...zddjkbdep5a.woff2
• https://www.elevaseo.com/_next/static/media/caa3a2e1cccd8315-s.p.09~u27dqhyhd6.w...~u27dqhyhd6.woff2

The page has 1 request with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.

If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private.

Offenders

• https://www.googletagmanager.com/gtag/js?id=G-T5SXH37NM6

The page has 3 misconfigured mime types.

It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk.

Offenders

• https://www.elevaseo.com/services?_rsc=EylmaytQesAzsSpi
• https://www.elevaseo.com/contact?_rsc=EylmaytQesAzsSpi
• https://www.elevaseo.com/?_rsc=-FKW1KsA7p7dueVx

The page has 2 requests that have a shorter cache time than one year (but still a cache time).

Setting a cache header is good. Setting a long cache header (a year) is even better because the asset will stay in the browser cache across visits. For content-hashed URLs (e.g. app.4af2.css) you can safely use Cache-Control: max-age=31536000, immutable. For unversioned URLs that may change, use a revalidating strategy instead.

Offenders

• https://www.googletagmanager.com/gtag/js?id=G-T5SXH37NM6
• https://www.elevaseo.com/favicon.ico?favicon.0x3dzn~oxb6tn.ico

The page is missing a language definition in the HTML tag. Define it with <html lang="YOUR_LANGUAGE_CODE">

According to the W3C recommendation you should declare the primary language for each Web page with the lang attribute inside the <html> tag https://www.w3.org/International/questions/qa-html-language-declarations#basics.

The page is missing a meta description.

Use a page description to make the page more relevant to search engines.

The page is missing a title.

Use a title to make the page more relevant to search engines.

The page is missing a viewport meta tag. Add <meta name="viewport" content="width=device-width, initial-scale=1"> so the browser lays the page out at the device width.

The viewport meta tag tells the browser how to lay out the page on small screens. Without it (or without width=device-width) the page is rendered at a desktop fallback width and scaled down, which makes text unreadable on mobile. Disabling zoom (user-scalable=no, maximum-scale<=1) is also an accessibility regression. https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag

There are 1 response that sets both a max-age and expires header. There are 1 response that sets a pragma no-cache header (that is a request header). There are 27 responses that sets a server header.

Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.

Offenders

• https://elevaseo.com/
• https://www.elevaseo.com/
• https://www.elevaseo.com/_next/static/media/797e433ab948586e-s.p.09zddjkbdep5a.w...zddjkbdep5a.woff2
• https://www.elevaseo.com/_next/static/media/caa3a2e1cccd8315-s.p.09~u27dqhyhd6.w...~u27dqhyhd6.woff2
• https://www.elevaseo.com/_next/static/chunks/11_3o6xh_he9w.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/06k~j1z-btd31.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/0r_-65m65iin-.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/turbopack-0rg9jsifbbx.x.js...-0rg9jsifbbx.x.js
• https://www.googletagmanager.com/gtag/js?id=G-T5SXH37NM6
• https://www.googletagmanager.com/gtag/js?id=G-T5SXH37NM6
• https://www.elevaseo.com/_next/static/chunks/0ar_kmbyjhcse.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/029-~81fltiow.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/0110zgm.jji2n.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/0bo-gfp.ka~xk.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/0bar6hml8e3.i.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/0jjg0gzwwp437.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/09v01if2yq9.9.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/0~-afli~du4l4.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/02_awuak2zz9u.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/0lcmwtlmicds..js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/18aie270-lood.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/_next/static/chunks/0wh~76pgcrvj..js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/favicon.ico?favicon.0x3dzn~oxb6tn.ico
• https://www.elevaseo.com/_next/static/chunks/14d~ek4m69y6w.js?dpl=dpl_HXL6sbYpnSzWyinVJ9ey1DhaHbJA
• https://www.elevaseo.com/services?_rsc=EylmaytQesAzsSpi
• https://www.elevaseo.com/contact?_rsc=EylmaytQesAzsSpi
• https://www.elevaseo.com/?_rsc=-FKW1KsA7p7dueVx
• https://www.google-analytics.com/g/collect...ics.com/g/collect
• https://www.google-analytics.com/g/collect...ics.com/g/collect

The page is using Google Analytics meaning you share your users private information with Google. You should use analytics that care about user privacy, something like https://matomo.org.

Google Analytics share private user information with Google that your user hasn't agreed on sharing.

No <meta name="referrer"> tag was found on the page. Set a Referrer-Policy response header (preferred) or add a meta tag, for example <meta name="referrer" content="strict-origin-when-cross-origin">.

Without an explicit referrer policy the browser falls back to the user-agent default and may leak the full URL of the previous page (including query strings) to every cross-origin request. Set a Referrer-Policy response header (preferred) or a <meta name="referrer"> tag in the document. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

The page embeds 1 resource from companies that profit from user surveillance. Consider privacy-respecting alternatives.

Embedding scripts or iframes from companies whose business model is surveillance capitalism (Google, Facebook, etc.) leaks detailed user data on every page view, often before the user has had a chance to consent. See https://en.wikipedia.org/wiki/Surveillance_capitalism for background. Prefer privacy-respecting alternatives where possible.

Offenders

• https://www.googletagmanager.com/gtag/js?id=G-T5SXH37NM6

Set a Content-Security-Policy header to mitigate cross-site scripting attacks. You can start with a Content-Security-Policy-Report-Only header, which only reports violations rather than blocking them.

A Content-Security-Policy response header tells the browser which sources of script, style, and other content are allowed. The most effective form is a strict CSP using nonces or hashes together with strict-dynamic; the worst is a missing header, with unsafe-inline and unsafe-eval close behind. https://web.dev/articles/strict-csp

Offenders

• https://www.elevaseo.com/

Set a Cross-Origin-Embedder-Policy header (typically require-corp or credentialless) on the document response to control cross-origin embedding.

Cross-Origin-Embedder-Policy (COEP) makes the page refuse to load cross-origin subresources unless they explicitly opt in via CORP or CORS. Together with Cross-Origin-Opener-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy

Offenders

• https://www.elevaseo.com/

Set a Cross-Origin-Opener-Policy header (typically same-origin) on the document response to isolate the page from cross-origin windows.

Cross-Origin-Opener-Policy (COOP) lets a page sever its window-group ties to cross-origin documents that opened it or that it opens. Together with Cross-Origin-Embedder-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy

Offenders

• https://www.elevaseo.com/

Set a Cross-Origin-Resource-Policy header (same-origin, same-site or cross-origin) on the document response to limit who may embed it.

Cross-Origin-Resource-Policy (CORP) is a per-response opt-in that tells the browser which origins are allowed to embed the resource. It blocks cross-origin or cross-site no-cors embedding (img, script, iframe, etc.) and is one of the building blocks of cross-origin isolation. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Resource-Policy

Offenders

• https://www.elevaseo.com/

Set a NEL header (paired with Reporting-Endpoints) to collect connection-level error reports from the field.

The NEL (Network Error Logging) response header tells the browser to record connection-level failures (DNS, TLS, HTTP errors) and ship them to a reporting endpoint. NEL pairs with the Reporting-Endpoints / Report-To header — the page declares the endpoint group and NEL points at it. Together they give you visibility into errors that never reach your origin server. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/NEL

Offenders

• https://www.elevaseo.com/

Set a Permissions-Policy header to control which browser features the page can use.

The Permissions-Policy response header (the successor to Feature-Policy) lets a site explicitly opt in or out of powerful browser features such as camera, microphone, geolocation, payment and clipboard. Setting a strict policy reduces the attack surface and limits what embedded third parties can do. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy

Offenders

• https://www.elevaseo.com/

Set a referrer-policy header to make sure you do not leak user information.

Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. https://scotthelme.co.uk/a-new-security-header-referrer-policy/.

Offenders

• https://www.elevaseo.com/

Set a Reporting-Endpoints header (or the legacy Report-To header) so CSP reports, NEL data and other Reporting-API events have an endpoint to land at.

The Reporting-Endpoints response header (the successor to Report-To) names the URLs that browsers should POST reports to. Without it, CSP report-to directives, Cross-Origin-Opener-Policy reports, NEL data and other Reporting-API events have nowhere to go. The legacy Report-To header is still accepted for older Chromium versions. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Reporting-Endpoints

Offenders

• https://www.elevaseo.com/

The page has 7% requests that are 3rd party (2 requests with a size of 161.6 kB). The page also have request to companies that harvest data from users and do not respect users privacy (see https://en.wikipedia.org/wiki/Surveillance_capitalism). The page do 1 tag-manager request and uses 1 tag-manager tool. The page do 2 surveillance requests and uses 2 surveillance tools. The page do 1 analytics request and uses 1 analytics tool.

Using third party requests shares user information with that third party. Please avoid that! The project https://github.com/patrickhulce/third-party-web is used to categorize first/third party requests.

Offenders

• https://www.googletagmanager.com/gtag/js?id=G-T5SXH37NM6
• https://www.google-analytics.com/g/collect...ics.com/g/collect

Set X-Content-Type-Options: nosniff on the document response to prevent MIME-sniffing.

X-Content-Type-Options: nosniff prevents browsers from interpreting files as a different MIME type than what is declared in the Content-Type header. This blocks a class of cross-site scripting and content-type confusion attacks and should be set on every response. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options

Offenders

• https://www.elevaseo.com/

A strict transport header is set but miss out on setting includeSubDomains

The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security.