sunrise.ch website review

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

Google Tag Manager costs a phone 1.4 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, gsitrix.com and Facebook and others), adding 2.5 MB and 2.9 s of main-thread time.

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

gsitrix.com costs a phone 564 ms of main-thread work and 122 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.

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

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

Facebook costs a phone 312 ms of main-thread work and 289 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.

sprinklr.com costs a phone 174 ms of main-thread work and 388 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.

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

About 44 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.

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

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

11 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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.32 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.949 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Eine neue Art, iPhone zu erleben.”. Most of its time is resource load delay (3.5 s).

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 259 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

10 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-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.6 MB in 254 requests on a phone: scripts 3.1 MB (92), media 1.7 MB (1) and images 360 KiB (58). Under 2 MB keeps phones on slow connections fast.

filters:format(webp):quality(90) is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (58 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Some list items are not inside a list.

1 frame has no title, so screen-reader users cannot tell what it contains.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 195 pages on sunrise.ch and 11 external pages.

There is no https://www.sunrise.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://www.sunrise.ch/de/allgemein/immobilien/liegenschaftsverwaltung and https://www.sunrise.ch/de/allgemein/sunrise-empfehlen are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.sunrise.ch/de/allgemein/immobilien/liegenschaftsverwaltung, https://www.sunrise.ch/de/allgemein/sunrise-shops and https://www.sunrise.ch/go/cockpit have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.sunrise.ch/en/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/, https://www.sunrise.ch/business/de/home, https://www.sunrise.ch/go/cockpit, https://www.sunrise.ch/de/internet-tv/internet-abo, https://www.sunrise.ch/de/internet-tv/kombi-abo and https://www.sunrise.ch/de/mobile/mobile-daten and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sunrise.ch/go/cockpit has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.sunrise.ch/go/cockpit took over 3 s to send its HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Permissions policy violation: accelerometer is not allowed in this document.”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 8 customer or partner logos. 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.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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