markusraub.ch website review

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

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

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

8 third-party services load with your homepage (elfsightcdn.com, Google CDN and Google Tag Manager and others), adding 2.6 MB and 1.4 s of main-thread time.

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

elfsightcdn.com costs a phone 567 ms of main-thread work and 958 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.

9 images could be 491 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

Google Tag Manager costs a phone 242 ms of main-thread work and 401 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.

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

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

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

25 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Fotograf zu sein, bedeutet mir sehr viel. Es ist gelebte Le…”. Most of its time is element render delay (5.1 s).

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

13 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.1 MB in 115 requests on a phone: scripts 2.6 MB (44), images 1.2 MB (20) and fonts 180 KiB (6). Under 2 MB keeps phones on slow connections fast.

6 images (585 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.

3 images further down the page (332 KiB) 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 1.18 g of CO₂e: 141.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

7 links inside paragraphs rely on colour alone to stand out.

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 27 pages on markusraub.ch and 36 external pages.

There is no https://markusraub.ch/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://markusraub.ch/datenschutzerklaerung and https://markusraub.ch/impressum-2 have no meta description, so Google writes the search snippet from whatever text it finds.

https://markusraub.ch/fotoshooting-familienshooting-paarshooting and https://markusraub.ch/fotoshooting-familienshooting-paarshooting/dein-fotoshooting use the same meta description. A description written for each page earns more clicks.

https://markusraub.ch/fotograf-markus-raub, https://markusraub.ch/eventfotograf-geburtstagsfotograf-familienfeier-fotograf, https://markusraub.ch/fotoshooting-familienshooting-paarshooting, https://markusraub.ch/passfoto-visafoto-id-foto, https://markusraub.ch/babybauch-shooting-fotograf and https://markusraub.ch/baby-newborn-shooting-rheinfelden-basel and 4 others took over 3 s to send their HTML from our server.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

Large scripts ship without source maps.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 579 words of visible text.

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