testesbenner.com website review

3 images could be 886 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.8 s faster on a phone.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

About 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 470 ms faster on a phone.

8 third-party services load with your homepage (userguiding.com, Google Tag Manager and Klaviyo and others), adding 2.7 MB and 1.9 s of main-thread time.

17 files are served with short cache lifetimes, so returning visitors download them again (444 KiB).

userguiding.com costs a phone 687 ms of main-thread work and 1.2 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 781 ms on a phone.

About 131 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 620 ms faster on a phone.

Google Tag Manager costs a phone 662 ms of main-thread work and 708 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

11 long tasks block the main thread while loading, the longest for 424 ms. During a long task the page ignores taps.

A phone's processor spends 3.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your server takes 881 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

bonanza.com costs a phone 46 ms of main-thread work and 404 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Polyfills for old browsers add 97 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “daftar LIGA178”.

The page becomes fully interactive after 23.2 s. Good is under 3.8 s.

Visually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 959 ms in total while the page loads. Good is under 200 ms.

The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.4 MB in 119 requests on a phone: scripts 2.5 MB (64), images 1.6 MB (22) and stylesheets 145 KiB (6). Under 2 MB keeps phones on slow connections fast.

ligagas.jpg weighs 890 KiB. On a phone connection a single image that size takes seconds.

2 images (985 KiB) 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.

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

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 frames have no title, so screen-reader users cannot tell what they contain.

2 tap targets are too small or too close together to hit reliably with a finger.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 160 pages on testesbenner.com and 57 external pages.

The robots meta tag says “index, follow, nosnippet”, which tells Google, Bing and the AI answers built on them not to quote this page.

There is no https://manaenadu.com/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.

Your homepage links to https://manaenadu.com/users/create_intro_user, https://manaenadu.com/booths/my_booth_redirect, https://manaenadu.com/vercado_webstores, https://manaenadu.com/account_dashboard, https://manaenadu.com/users/60349912/emails and https://manaenadu.com/users/60349912/offers/purchased and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=223000730&tm=gtm002&Ver=2&mid=18336c59-6180-48c1-8001-560cd3262dbf&bo=2&sid=70f830c0dcc511f1b90ddd8aaa9ca303&vid=70f84580dcc511f1a7fe19aa6908155a&vids=1&msclkid=N&gtm_.

25 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 549 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 10 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.