01M24PEYNFN4BZ6BAFV7PZ6TW5
Overall score
The website has avoidable performance bottlenecks. Server and loading speed is the biggest problem here.
Browser runtime measurement
These values come from the real page build in the browser and show the differences between desktop and mobile.
Google PageSpeed score
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google sees optimisation potential for this page. · Fetched on 10 Sep 2026 3:42 AM
Act now
messages-m22pKBWF.js – 455.90 KB
File: messages-m22pKBWF.js · Host: scenegenerator.io
https://scenegenerator.io/assets/messages-m22pKBWF.js
club-night-1786805573834.png – 2.13 MB
File: club-night-1786805573834.png · Host: scenegenerator.io
https://scenegenerator.io/imgs/flyer-generator/club-night-1786805573834.png
club-night-1786805573834.png – 2.13 MB
File: club-night-1786805573834.png · Host: scenegenerator.io
https://scenegenerator.io/imgs/flyer-generator/club-night-1786805573834.png
5.75 MB
The HTML directly references 1 CSS files and 36 external JavaScript files.
Recommendation: Reduce unnecessary assets and review the theme and plugin load.
The statically detected JavaScript files add up to around 708.30 KB.
Recommendation: Reduce heavy or unnecessary scripts and load them only when needed.
Determined statically from the HTML source.
HTML and CSS together reference 32 distinct images.
Recommendation: Optimise images, use lazy loading and remove unnecessary media.
The inspected images add up to around 5.75 MB.
Recommendation: Resize and compress images and use modern formats.
Likely LCP image candidate
The largest visible content appears to be an image and can directly affect the page build.
Main causes
Actually loaded in the browser.
Top hosts by data volume
Largest requests
Total: 3.852,2 KB
Total: 5.369,4 KB
Recommendations
36 JavaScript files adding up to around 708.30 KB. Reduce unnecessary scripts, tracking and plugin front-end load, defer them or load them only when needed.
32 images adding up to around 5.75 MB. Large images, missing modern formats and missing lazy loading are a good lever here.
The server response takes around 789 ms. A full page cache, a faster backend and less server-side work will likely have the biggest effect.
club-night-1786805573834.png weighs around 2.13 MB.
Recommendation: Resize hero and above-the-fold images and compress them with modern formats.
The browser main thread was blocked for around 216 ms during page load (Total Blocking Time).
Recommendation: Reduce JavaScript load, defer heavy scripts and break up long tasks.
32 of 39 images have no explicit dimensions and can cause layout shifts (CLS).
Recommendation: Set width and height attributes on img tags.
Scan history
2 public scans of this page
Hosts more prominent on mobile
accounts.google.com
Mobile 13,7 KB · Desktop 0,0 KB · Difference +13,7 KB
accounts.google.com
Mobile 4 · Desktop 2 · Difference +2
fonts.gstatic.com
Explained simply
These short texts put the most important measurements into plain language.
The server response has room for improvement and already delays page rendering noticeably.
Why it matters: TTFB stands for “time to first byte” — the time until the server returns the first data.
Technical value: 789 ms
The page is served compressed, so less data has to be transferred.
Why it matters: Compression reduces the transfer size of HTML, CSS and JavaScript.
Technical value: Content-Encoding: br (Brotli)
The browser is allowed to cache files, which can make repeat visits faster.
Why it matters: Browser caching prevents unchanged files from being downloaded over and over again.
Technical value: CSS: 1/1, JS: 15/15, images: 0/15, fonts: 9/9 | page cache: no, CDN: cloudflare, origin: unknown | HTML Cache-Control: empty (normal for dynamic pages)
32 images were detected. Of those, 30 use lazy loading and 28 use modern formats such as WebP or AVIF.
Why it matters: Images are often the biggest performance factor. Lazy loading and modern formats help the most.
Technical value: PNG: 1, WEBP: 12, JPG: 1, SVG: 1 (15 of 32 measured), measured image weight: 5.75 MB
36 external JavaScript files were detected in the delivered HTML. Further scripts may only be loaded during the real page load through optimisation or lazy-load mechanisms.
Why it matters: Many or large JavaScript files can delay a page’s rendering and interactivity.
Technical value: 36 external files, 0 data URI scripts, 708.30 KB
20 font files were detected. In addition, 0 external font services (e.g. Google Fonts) are embedded.
Why it matters: Many or large web fonts increase loading time and can cause visible layout delays.
Technical value: 20 font files, 0 external font services, groups: bricolage-grotesque-latin-wght-normal-DLoelf7F (1), dm-sans-latin-wght-normal-Xz1IZZA0 (1), inter-cyrillic-ext-wght-normal-BOeWTOD4 (1), measured font weight: 194.06 KB
1 direct CSS files and 1 additional CSS dependencies were detected.
Why it matters: Many stylesheets or imported CSS files increase the number of loaded resources.
Technical value: Direct CSS files: 1, additional dependencies: 1, estimated CSS weight: 162.79 KB
No external services were detected – good for loading time and privacy.
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: 0 external hosts
The first visible content appears after around 464 ms, the most important visible content after around 584 ms. That is a good result.
Why it matters: These values describe when users actually see the first and the most important content.
Technical value: FCP: 464 ms, LCP: 584 ms
Layout stability is good. The measured CLS value is 0.05.
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0.05
The real page load issues relatively many requests: 64 requests with around 3.79 MB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 64 requests, 3.79 MB
Score breakdown
Speed
Cache quality by asset type
Externally loaded services in the browser
These services were actually contacted during the real page build in the browser.
4 requests · 13,7 KB
accounts.google.com
Largest requests during the real page build
This list shows the largest requests from the real browser run and helps you spot notable files and hosts faster.
Technical metrics
Measurement conditions
Connection timing (TTFB: 789 ms)
Tasks that blocked the browser main thread.
Details on individual metrics
In-depth values for assets, images, fonts, CSS and JavaScript. The most important groups are grouped thematically below.
This list shows the largest measured files from the asset check.
This number shows detected hints in the HTML. It is not perfect proof that all images actually use lazy loading.
Only the first 20 entries are shown.
Sample: 15 of 32 images were loaded and measured. Size and count refer only to these images.
Detected font files: 20, External font services: 0. External font services are e.g. Google Fonts or Adobe Typekit, from which concrete font files are only loaded later.
These are stylesheets referenced within other CSS files via @import references.
These are the external script sources detected in the directly delivered HTML. Dynamically loaded scripts are not fully included.
WordPress detection
Optimisation potential
These points are not critical, but can improve the performance, stability or clarity of the page structure.
The server response takes around 789 ms.
Recommendation: Check caching and backend performance.
15 first-party assets have no clear long-lived cache rules.
Recommendation: Serve static files with long-lived Cache-Control values.
club-night-1786805573834.png weighs around 2.13 MB.
Recommendation: Resize and compress this image specifically and serve it in a more modern format.
Detected 20 font files totalling around 194.06 KB.
Recommendation: Load fewer font weights and serve fonts as efficiently as possible.
Already done well
These points already stood out positively in the current scan.
Detected compression: br.
16 @font-face rules with font-display detected.
The website is reachable over HTTPS.
The website is served over HTTP/2.
The website advertises HTTP/3 via the Alt-Svc header.
The website is reachable over IPv6.
Additional hints
Supplementary hints from the scan that can be useful for classification and technical assessment.
CSS pulls in 1 further stylesheet dependencies.
CSS references 20 additional font files.
No clear WordPress indicators were found in the HTML or the asset paths.
Waterfall
Detailed request waterfall from the browser run.
Raw data
Complete scan data as a machine-readable JSON file or tabular export.