sorgen.co website review

24 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Google Tag Manager, breeze.in and Shopify and others), adding 1.5 MB and 647 ms of main-thread time.

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

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

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

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

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

breeze.in costs a phone 165 ms of main-thread work and 727 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.

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

About 83 KiB of CSS is downloaded but never applied on this page.

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

Polyfills for old browsers add 9 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.

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

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

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

5 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-31, real Chrome visitors' tap response (inp) went from 158 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 images weigh 16.6 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 6.3 MB in 245 requests on a phone: images 3.8 MB (54), scripts 1.6 MB (95) and other files 625 KiB (65). Under 2 MB keeps phones on slow connections fast.

7 images (16.7 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.

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

Leg_Wellness_Festival__Buy_3_Get_1_Free.png 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).

4 images are downloaded at several times the size a phone draws them, for example WhatsApp_Image_2024-12-27_at_10.57.47_AM.jpg at 1,600 px wide, shown at 171 px. Resized copies would save about 419 KiB.

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

8 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

7 elements hidden from screen readers can still receive keyboard focus.

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

7 images have no alt text, which hurts accessibility and image search.

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

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

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

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

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (21 elements).

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

Your title is 66 characters, so Google will cut it off around 60: “Sports & Medical Compression Stockings for Women & Men – Sorgen.Co”.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 281 pages on sorgen.co and 3 external pages.

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

1 image is served at too low a resolution for sharp phone screens.

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: 19 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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