Tested 2026-05-26 22:15:25 using Chrome 148.0.7778.96 (runtime settings)
Use --filmstrip.showAll to show all filmstrips.
0 s0.1 sCPU Long Task duration 107 ms0.2 sDOM Content Loaded Time 125 ms
0.3 sCPU Long Task duration 99 msFirst Contentful Paint 260 msFirst Visual Change 267 msVisual Complete 85% 267 ms
0.4 s
0.5 sPage Load Time 443 ms
0.6 sVisual Complete 95% 535 ms
0.7 s
0.8 s
0.9 s
1 sLCP <H1> 992 ms
1.1 s
1.2 s
1.3 s
1.4 s
1.5 s
1.6 s
1.7 s
1.8 s
1.9 s
2 s
2.1 s
2.2 s
2.3 s
2.4 s
2.5 s
2.6 s
2.7 s
2.8 s
2.9 s
3 s
3.1 s
3.2 s
3.3 s
3.4 s
3.5 s
3.6 s
3.7 s
3.8 s
3.9 s
4 s
4.1 s
4.2 s
4.3 s
4.4 s
4.5 s
4.6 s
4.7 s
4.8 s
4.9 s
5 s
5.1 s
5.2 s
5.3 s
5.4 s
5.5 sVisual Complete 99% 5.448 s
5.6 s
5.7 sCPU Long Task duration 114 ms
5.8 s
5.9 s
6 s
6.1 s
6.2 s
6.3 s
6.4 s
6.5 s
6.6 s
6.7 sLast Visual Change 6.685 sThe coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices. Tested using Coach-core version 9.2.1.
decodingAsyncThe page has 2 images (out of 2) without a decoding hint. Add decoding="async" to non-critical images so the browser can decode them off the main thread.
Setting decoding="async" on an <img> tells the browser it can decode the image off the main thread, which keeps the page responsive to user interactions while images are being processed. The default ("auto") leaves the choice to the browser. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#decoding
lazyLoadingImagesThe page has 1 below-the-fold image without loading="lazy". Add loading="lazy" so the browser defers downloading and decoding them until the user scrolls them into view.
Adding loading="lazy" to an <img> tells the browser not to download or decode it until it is close to the viewport. For images that the user may never see (deep in the page, behind a tab, in a footer carousel), this saves bandwidth and main-thread time during initial render. The LCP image and any image in the initial viewport should NOT be lazy-loaded — that delays the first paint. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#loading
modernImageFormatsThe page ships 2 images (out of 2) in JPEG/PNG/GIF without a modern alternative. Wrap them in a <picture> with a <source type="image/avif"> or "image/webp" before the legacy <img>, or serve modern formats from your image pipeline directly. AVIF and WebP usually deliver 25–50% smaller files at the same quality.
AVIF and WebP routinely deliver 25–50% smaller files than JPEG and PNG at the same perceived quality, and every browser version still under support understands at least one of them. Ship modern formats either through a <picture> element with <source type="image/avif"> / "image/webp" entries in front of the legacy <img>, or directly from a content-negotiating image pipeline that returns AVIF / WebP when the client accepts it. https://web.dev/articles/serve-images-webp
javascriptSizeThe total JavaScript transfer size is 466.6 kB and the uncompressed size is 1.4 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?
| URL | Transfer | Content |
|---|---|---|
| https://audiogami.com/assets/index-G9G1VO-F.js | 213.4 KB | 667.7 KB |
| https://eu-assets.i.posthog.com/static/array.js | 69.9 KB | 187.3 KB |
| https://gamilab.ch/js/sdk.js | 28.2 KB | 28.0 KB |
| https://eu-assets.i.posthog.com/array/phc_uWtq5rhzYyYWwKdskw2aNA6Mgi4qv6e5vVWNvct4ELMJ/config.js | 725 B | 853 B |
| https://eu-assets.i.posthog.com/static/surveys.js?v=1.376.1 | 33.5 KB | 92.5 KB |
| https://sitebehaviour-cdn.fra1.cdn.digitaloceanspaces.com/index.min.js....com/index.min.js | 16.5 KB | 44.1 KB |
| https://tag.grainql.com/v4/audiogami-l5qnkx.js | 63.1 KB | 205.1 KB |
| https://sitebehaviour-cdn.fra1.cdn.digitaloceanspaces.com/replay-script.js | 30.4 KB | 94.6 KB |
longTasksThe page has 3 CPU long tasks with the total of 320 ms. The total blocking time is 64 ms and 2 long tasks before first contentful paint with total time of 206 ms. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks.
Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler.
faviconThe favicon size is 53.4 kB bytes. That's quite big, can you make it smaller?
It is easy to make the favicon big but please avoid doing that, because every browser will then perform an unnecessarily large download. And make sure the cache headers are set for a long time for the favicon. It is easy to miss since it's another content type.
cacheHeadersThe page has 3 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 31.3 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.
fewFontsThe page has 3 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.
avoidScalingImagesThe page has 2 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them.
It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one.
privateAssetsThe page has 2 requests 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.
spofThe page has 1 request inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head.
A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag.
cacheHeadersLongThe page has 10 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.
compressAssetsThe page has 1 request 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.
| URL | Transfer | Content |
|---|---|---|
| https://gamilab.ch/js/sdk.js | 28.2 KB | 28.0 KB |
inlineCssThe page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens.
In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded.
mimeTypesThe page has 5 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.
thirdPartyThe page do more requests to third party domains (29 requests and 357.1 kB) then first party (5 requests and 394.8 kB). The regex .*audiogami.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
unnecessaryHeadersThere are 15 responses that sets both a max-age and expires header. There are 6 responses 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.
referrerPolicyNo <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
contentSecurityPolicyHeaderSet 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
crossOriginEmbedderPolicyHeaderSet 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
crossOriginOpenerPolicyHeaderSet 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
crossOriginResourcePolicyHeaderSet 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
nelHeaderSet 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
permissionsPolicyHeaderSet 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
referrerPolicyHeaderSet 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/.
reportingEndpointsHeaderSet 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
strictTransportSecurityHeaderSet a strict transport header to make sure the user always use HTTPS.
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.
thirdPartyPrivacyThe page has 15% requests that are 3rd party (5 requests with a size of 105.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 5 surveillance requests and uses 1 surveillance 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.
xContentTypeOptionsHeaderSet 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
thirdPartyCookiesThe page sets 2 third party cookies.
Third party cookies are used to track the user. They are automatically blocked in Safari and Firefox.
Data collected using
Coach-core version 9.2.1. With updated code from
Webappanalyzer 2026-05-04. Use
--browsertime.firefox.includeResponseBodies html or
--browsertime.chrome.includeResponseBodies html to help Wappalyzer find more information about technologies used.
Data collected using Third Party Web version 0.29.2.
0.0s1.0s1.9s2.9s3.8s4.8s5.7s6.7sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div#root > div:eq(1) > main > div:eq(1) > div:eq(1) > div > section#hero > div > div > h1
The LCP element is highlighted in the screenshot. If nothing is highlighted the element was removed before the screenshot or the LCP API couldn't find it.
How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.
No layout shifts were detected on this page.
Want render-blocking and recalculate-style metrics for FCP and LCP, plus CPU long tasks? Run with --cpu.
A long animation frame (LOAF) is a frame that took ≥ 50 ms from input to the next paint. The breakdown shows where that time went. Read more about the Long Animation Frames API.
Showing the top 10 longest animation frames.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 20.4 KB | 148.1 KB | 1 |
| css | 0 b | 17.4 KB | 119.7 KB | 3 |
| javascript | 0 b | 455.6 KB | 1.3 MB | 8 |
| image | 0 b | 85.7 KB | 85.5 KB | 1 |
| font | 0 b | 99.7 KB | 99.6 KB | 3 |
| favicon | 0 b | 52.1 KB | 51.9 KB | 1 |
| json | 1.1 KB | 3.9 KB | 10.3 KB | 10 |
| other | 550 B | 0 b | 0 b | 7 |
| Total | 1.6 KB | 734.8 KB | 1.8 MB | 34 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| audiogami.com | 74 ms | 385.5 KB | 1.0 MB | 5 |
| fonts.googleapis.com | 133 ms | 3.5 KB | 38.6 KB | 2 |
| eu-assets.i.posthog.com | 69 ms | 104.1 KB | 280.6 KB | 3 |
| fonts.gstatic.com | 63 ms | 99.7 KB | 99.6 KB | 3 |
| gamilab.ch | 11 ms | 28.2 KB | 28.0 KB | 1 |
| eu.i.posthog.com | 121 ms | 289 B | 15 B | 1 |
| sitebehaviour-cdn.fra1.cdn.digitaloceanspaces.com | 66 ms | 46.9 KB | 138.7 KB | 2 |
| tag.grainql.com | 84 ms | 63.1 KB | 205.1 KB | 1 |
| event-store.sitebehaviour.com | 1.258 s | N/A | 479 B | 7 |
| clientapis.grainql.com | 1.246 s | 3.2 KB | 9.8 KB | 9 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 0 seconds | 1 year |
| Last modified | 0 seconds | 2 days | 2 years |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 110.0 KB | 3 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 52.1 KB | 1 |
| other | 0 b | 7 |
| json | 3.6 KB | 9 |
| Total | 165.2 KB | 20 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 172.3 KB | 6 |
| image | 0 b | 0 |
| font | 99.7 KB | 3 |
| favicon | 52.1 KB | 1 |
| json | 3.9 KB | 10 |
| other | 0 b | 7 |
| Total | 327.5 KB | 27 |
Render blocking information directly from Chrome.
| Blocking | In body parser blocking | Potentially blocking |
|---|---|---|
| 3 | 0 | 0 |
| URL | Type |
|---|---|
| https://audiogami.co...index-G9G1VO-F.js | nonblocking |
| https://eu-assets.i....m/static/array.js | nonblocking |
| https://tag.grainql....diogami-l5qnkx.js | nonblocking |
| https://fonts.gstati...p50SjIa1ZL7.woff2 | nonblocking |
| https://eu-assets.i....static/surveys.js | nonblocking |
| https://fonts.gstati...BYRbKPxDcwg.woff2 | nonblocking |
| https://sitebehaviou.../replay-script.js | nonblocking |
| https://gamilab.ch/js/sdk.js | nonblocking |
| https://fonts.gstati...r8E7mPbF4Cw.woff2 | nonblocking |
| https://sitebehaviou....com/index.min.js | nonblocking |
| https://audiogami.co...ndex-3x-tGtbJ.css | blocking |
| https://fonts.google...ogleapis.com/css2 | blocking |
| https://fonts.google...ogleapis.com/css2 | blocking |
| https://eu-assets.i....ct4ELMJ/config.js | nonblocking |
Third party requests categorised by Third party web version 0.29.2.
Domains that didn't match any tool in Third party web. If you are sure they are third party domains, please do a PR to that project. You can also fine tune the list using --firstParty.
Calculated using .*audiogami.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 20.4 KB | 148.1 KB | 1 |
| css | 0 b | 14.0 KB | 81.2 KB | 1 |
| javascript | 0 b | 213.4 KB | 667.7 KB | 1 |
| image | 0 b | 85.7 KB | 85.5 KB | 1 |
| font | 0 b | 0 b | 0 b | 0 |
| favicon | 0 b | 52.1 KB | 51.9 KB | 1 |
| Total | N/A | 385.5 KB | 1.0 MB | 5 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 3.5 KB | 38.6 KB | 2 |
| javascript | 0 b | 242.3 KB | 652.4 KB | 7 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 99.7 KB | 99.6 KB | 3 |
| favicon | 0 b | 0 b | 0 b | 0 |
| json | 1.1 KB | 3.9 KB | 10.3 KB | 10 |
| other | 550 B | 0 b | 0 b | 7 |
| Total | 1.6 KB | 348.8 KB | 800.8 KB | 29 |
