reflective.berlin website review

45 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Shopify, Heroku and nfcube.com and others), adding 1.6 MB and 720 ms of main-thread time.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

Shopify costs a phone 504 ms of main-thread work and 1.3 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.

About 263 KiB of JavaScript is downloaded but never used on this page.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

28 KiB JavaScript is shipped twice across bundles.

Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need.

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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your homepage downloads 5.7 MB in 480 requests on a phone: images 3.1 MB (63), other files 1.2 MB (219) and scripts 1,020 KiB (156). Under 2 MB keeps phones on slow connections fast.

11 images (1.1 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.

2 images are downloaded at several times the size a phone draws them, for example reflective-berlin-reflektierendes-hoodie-before-desktop.jpg at 2,048 px wide, shown at 390 px. Resized copies would save about 169 KiB.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

11 visible links have no text or label, so screen readers cannot say where they go.

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

Your title is only 17 characters: “REFLECTIVE Berlin”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 251 pages on reflective.berlin and 0 external pages.

The HTML your server sends has 894 of the 1,556 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://reflective.berlin/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.

https://reflective.berlin/pages/shop, https://reflective.berlin/pages/inspiration and https://reflective.berlin/pages/info have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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 1,556 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.