Page summary

https://api.streamplay.ai

Tested 2026-08-06 13:36:52 using Chrome 150.0.7871.186 (runtime settings)

SummaryWaterfallMetricsRenderingCoachPageXrayCPUThird party

This page is fast to paint, snappy to interact with and visually stable, but loose on best practices and weak on user privacy.

90 / 100
Coach overall
99 / 100
Performance
59 / 100
Best practice
89 / 100
Privacy

How it loaded →

0 → 166 ms · median run
Frame at 0 ms
start
Frame at 200 ms
Complete200 ms
166 ms
First Visual Change
166 ms
Speed Index
166 ms
Visual Complete 85%
166 ms
Last Visual Change
TTFB80 msLCP160 msTBT0 msCLS0.00

What to act on · top recommendations

Avoid extra requests by setting cache headers

90 / 100

The page has 1 request that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 710 B the next access.

Avoid missing and error requests

90 / 100

The page has 1 error response. The page has 1 response with code 404.

Google Web Vitals

min · median · mean · max of 1 run
MetricMinMedianMeanMax
Time To First Byte (TTFB)80 ms80 ms80 ms80 ms
Largest Contentful Paint (LCP)160 ms160 ms160 ms160 ms
Cumulative Layout Shift (CLS)0000

Visual Metrics

min · median · mean · max of 1 run
MetricMinMedianMeanMax
First visual change166 ms166 ms166 ms166 ms
Last visual change166 ms166 ms166 ms166 ms
Speed index166 ms166 ms166 ms166 ms
Visual readiness0 ms0 ms0 ms0 ms
Visual complete 85166 ms166 ms166 ms166 ms
Visual complete 95166 ms166 ms166 ms166 ms
Visual complete 99166 ms166 ms166 ms166 ms

CPU

min · median · mean · max of 1 run
MetricMinMedianMeanMax
Total Blocking Time0 ms0 ms0 ms0 ms
Max Potential FID0 ms0 ms0 ms0 ms
CPU long tasks 0000
CPU last long task happens at0 ms0 ms0 ms0 ms

More metrics

min · median · mean · max of 1 run
MetricMinMedianMeanMax
First paint160 ms160 ms160 ms160 ms
Load event end119 ms119 ms119 ms119 ms

Waterfall

Run 1 SpeedIndex median

First paintFCPLCPDOMContentLoadedDOM interactiveLoadRender-blockingRedirectError

Rendering

Run 1 · median
0.000 s
0s
Download video

Filmstrip

2 frames

Use --filmstrip.showAll to show all filmstrips.

Frame at 0 ms
0 ms
0 %
Frame at 200 ms
200 ms
100 %

Click a frame to seek the video to that moment. The dot marks frames where the page changed visually.

Why was rendering delayed?

Rendering was not meaningfully delayed. First paint landed at 160 ms on a 80 ms first byte.

Want to see how much CSS style-recalculation work delayed FCP and LCP, plus CPU long tasks? Run with --cpu.

Coach

The 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.

Performance advice

99
1 error1 warning
warn(90)Avoid extra requests by setting cache headerscacheHeaders

The page has 1 request that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 710 B 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
error(90)Avoid missing and error requestsresponseOk

The page has 1 error response. The page has 1 response with code 404.

Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it.

Offenders

Best practice advice

59
4 warnings2 info
warn(0)Declare a doctype in your documentdoctype

The page is missing a doctype. Please use <!DOCTYPE html>.

The <!DOCTYPE> declaration is not an HTML tag; it is an instruction to the web browser about what version of HTML the page is written in.

warn(0)Declare the language code for your documentlanguage

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.

infoMeta descriptionmetaDescription

The page is missing a meta description.

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

warn(0)Page titlepageTitle

The page is missing a title.

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

warn(0)Set a sensible viewport meta tagviewport

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

infoAvoid unnecessary headersunnecessaryHeaders

There are 2 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

Privacy advice

89
1 error3 warnings3 info
warn(0)Declare a referrer policy on the documentreferrerPolicy

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

infoSet a Cross-Origin-Embedder-Policy header so cross-origin subresources opt in to being embedded.crossOriginEmbedderPolicyHeader

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
infoSet a NEL header so the browser reports network errors back to you.nelHeader

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
warn(0)Set a Permissions-Policy header to control which browser features the page can use.permissionsPolicyHeader

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
infoDeclare reporting endpoints so the browser can deliver Reporting-API events.reportingEndpointsHeader

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
warn(60)Use a strict Content-Security-Policy header to mitigate cross-site scripting (XSS) attacks.contentSecurityPolicyHeader

The policy allows 'unsafe-inline', which lets the browser execute inline scripts and styles directly from the page. Move to nonces or hashes plus 'strict-dynamic' so that inline injection cannot run.

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

error(80)Set a strict transport header to make sure the user always use HTTPS.strictTransportSecurityHeader

The max-age is lower than one year, which is below the HSTS preload list minimum. Set it to at least 31536000 (one year), and 63072000 (two years) is recommended.

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.

Page info

A snapshot of what the browser actually built for this page: the document, how big and deep the DOM tree is and what it kept in storage. Big, deep trees are slower to style and lay out, so the counts Chrome warns about carry a flag.

Page info

Document

What the page says it is and how large it rendered.

TitleThe document title, shown in the browser tab and used by search results.
Layout viewport1365 × 620 pxThe width the page laid out at, and the full height of the rendered document.

DOM structure

How much markup the browser has to build, style and lay out.

DOM elements7Total HTML elements. Fewer means less for the browser to style, lay out and paint.
Avg DOM depth2How deeply elements are nested on average.
Max DOM depth3The deepest nesting on the page. Deep branches cost more style recalculation.
Iframes0No embedded documents on this page.
Script tags0Number of script elements. More scripts usually means more main-thread work.

Storage and connection

What the page stored on the client, and the network it was tested on.

Local storage0 bData the page saved in localStorage, kept across visits.
Session storage0 bData kept in sessionStorage for this tab session only.
Connection type4GWhat the Network Information API reported for the test connection.

Technologies used to build the page

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.

Detected technologies

3 technologies
  • UbuntuConfidence100
    Operating systems
  • Nginx1.24.0Confidence100
    Web serversReverse proxies
  • HSTSConfidence100
    Security

Data from run 1

Visual Metrics

Visual milestones

all times from navigation start
Speed Index0.17 show quickly the page looked done
First Visual Change0.17 sfirst paint reaches the screen
Last Visual Change0.17 sscreen stops changing
nothing painted yet
First Visual Change · Visual Complete 85% · Visual Complete 95% · Visual Complete 99% · Last Visual Change0.17 s
00.1 s
Content milestones
Perception index
Visual progress
Visual progress at 0 s0.0s
Visual progress at 0.2 s0.2s
FCP0.16s
LCP0.16s
VC850.17s
0.0s0.0s0.1s0.1s0.2s0.2s

Google Web Vitals

from run 1

Largest Contentful Paint

When the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.

160 msLCP render time

Phase breakdown

  • TTFB80 ms
  • Resource load delay0 ms
  • Resource load duration0 ms
  • Element render delay80 ms

Element

Element type
<pre>
Size (w × h)
81720
Load time
0 ms

DOM path

body > pre
LCP

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.

Cumulative Layout Shift

How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.

0.000cumulative layout shift score

No layout shifts were detected on this page.

Browser Metrics

Navigation Timing
Extra timings

Custom metrics collected through JavaScript

There are no custom configured scripts.

Extra metrics collected using scripting

There are no custom extra metrics from scripting.

PageXray

How the page is built.

HTTP versionHTTP/2.0
Total requests2
Total domains1
Transfer size1.9 KB
Content size587 B
Missing compression0

Main document

status 200 · 0 redirects

https://api.streamplay.ai/

HeaderValue
access-control-allow-credentialstrue
content-length535
content-security-policydefault-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
content-typeapplication/json; charset=utf-8
cross-origin-opener-policysame-origin
cross-origin-resource-policysame-origin
dateThu, 06 Aug 2026 13:36:53 GMT
etagW/"217-QaeHX7hQcEsfAwMl7qBqFIzbwh8"
origin-agent-cluster?1
referrer-policyno-referrer
servernginx/1.24.0 (Ubuntu)
strict-transport-securitymax-age=15552000; includeSubDomains
varyOrigin
x-content-type-optionsnosniff
x-dns-prefetch-controloff
x-download-optionsnoopen
x-frame-optionsSAMEORIGIN
x-permitted-cross-domain-policiesnone
x-xss-protection0

Response codes

200
150.0%
404
150.0%

Largest assets on the page (by transfer size)

2 assets
URLTypeTransfer SizeContent Size
https://api.streamplay.ai/json1.2 KB535 B
https://api.streamplay.ai/favicon.icojson710 B52 B

Requests and sizes per content type

1 type

Transfer size1.2 KB

  • json100.0%

Content size535 B

  • json100.0%

Requests1

  • json100.0%
ContentHeader SizeTransfer SizeContent SizeRequests
json0 b1.2 KB535 B1
Total0 b1.2 KB535 B1

Data per domain

1 domain
DomainTotal download timeTransfer SizeContent SizeRequests
api.streamplay.ai92 ms1.9 KB587 B2

Expires & last-modified statistics

typeminmedianmax
Expires0 seconds0 seconds0 seconds

Requests loaded after onLoad event

1 request

Includes requests done after load event end.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript0 b0
image0 b0
font0 b0
favicon0 b0
Total710 B1

Requests loaded after onContentLoad

1 request

Includes requests done after DOM content loaded.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript0 b0
image0 b0
font0 b0
favicon0 b0
Total710 B1

CPU

Get deeper CPU insight with one extra run
Run with --enableProfileRun to see where main-thread time went, blocking time and CPU cost per script, module and function, forced reflows and frame stability. The data is collected in one extra run, so the timing metrics of your measured runs stay untouched.

Long tasks

Tasks ≥ 50 ms blocking the main thread, collected via the Long Task API.

✓ No long tasks observed during this run.

Third party

Third party requests categorised by Third party web version 0.29.2.

No third-party requests detected

Every request on this page resolved to a first-party domain. There are no entries in Third party web to attribute, no third-party tools to enumerate, and no third-party cookies set. If you expected to see entries here you can fine-tune the first-party domain list with --firstParty.

First party requests and sizes per content type

2 requests

Calculated using .*streamplay.* (use --firstParty to configure).

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b0 b0 b0
css0 b0 b0 b0
javascript0 b0 b0 b0
image0 b0 b0 b0
font0 b0 b0 b0
favicon0 b0 b0 b0
json0 b1.2 KB535 B1
TotalN/A1.9 KB587 B2