linenshed.pt website review

5 images could be 340 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

About 353 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Shopify costs a phone 1.3 s of main-thread work and 745 KiB 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.

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

8 third-party services load with your homepage (Shopify, Google CDN and codeblackbelt.com and others), adding 886 KiB and 1.4 s of main-thread time.

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

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

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

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

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

12 KiB could be saved by minifying JavaScript.

7 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

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

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

26 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 3.0 MB in 212 requests on a phone: other files 940 KiB (102), images 848 KiB (23) and scripts 808 KiB (65). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

There are 2 <h1> headlines (“A arte da roupa de casa em linho pela Linenshed” and “Tratamos do que fazemos.”). One clear main headline is easier for people and search engines.

Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 234 pages on linenshed.pt and 13 external pages.

https://linenshed.pt/collections/fronhas-em-linho, https://linenshed.pt/collections/capas-de-edredao-em-linho, https://linenshed.pt/collections/lencol-capa-em-linho, https://linenshed.pt/collections/lencol-simples-em-linho, https://linenshed.pt/collections/conjunto-de-cama-em-linho and https://linenshed.pt/collections/jogo-de-lencois-em-linho and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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,052 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 9 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.