screenup.eu website review

48 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

59 files are served with short cache lifetimes, so returning visitors download them again (3.9 MB).

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying JavaScript.

96 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 164 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.5 MB in 74 requests on a phone: images 5.9 MB (64), media 3.9 MB (3) and fonts 751 KiB (4). Under 2 MB keeps phones on slow connections fast.

24 images are downloaded at several times the size a phone draws them, for example WTT.png at 3,012 px wide, shown at 140 px. Resized copies would save about 2.5 MB.

jumbo.png weighs 760 KiB. On a phone connection a single image that size takes seconds.

38 images (4.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

7 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.98 g of CO₂e: 358.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must be contained by particular parents: 11 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

There are 3 <h1> headlines (“Elevatethe fan experience.”, “Engage.Entertain.Elevate.” and “Fromspectatorto participant.”). One clear main headline is easier for people and search engines.

Structured data found (Organization, SoftwareApplication and WebSite) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

9 images failed to load on a phone, for example https://screenup.eu/assets/references/slide3.webp.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 855 words of visible text.

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.