versible.eu website review

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

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google CDN, Unpkg and Cloudflare CDN and others), adding 62.9 MB and 205 ms of main-thread time.

bubble.io costs a phone 18 ms of main-thread work and 62.1 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.

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

14 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

The page has 1,570 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google CDN costs a phone 71 ms of main-thread work and 349 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 35 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.

5 KiB could be saved by minifying CSS.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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.

8 images weigh 74.4 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 54.2 MB in 139 requests on a phone: images 50.7 MB (78), scripts 2.7 MB (28) and fonts 506 KiB (17). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example Copy of MVP PITCH DECK - 2023-10-17T135854.767.svg at 1,920 px wide, shown at 20 px. Resized copies would save about 22.0 MB.

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

1 image (50 KiB) is 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 15.35 g of CO₂e: 1842.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

128 buttons have no accessible name, so screen readers announce just “button”.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No XML sitemap at https://www.versible.eu/sitemap.xml, so Google discovers your pages only by following links.

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

A phone browser shows 966 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.versible.eu/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.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

7 of 13 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 “ResizeObserver loop completed with undelivered notifications.”.

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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 966 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (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 7 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.