thegrowingsofa.com website review

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

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

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

5 third-party services load with your homepage (Shopify, JSDelivr CDN and Other Google APIs/SDKs and others), adding 10.1 MB and 98 ms of main-thread time.

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

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

About 330 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

37 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 400 ms faster on a phone.

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

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

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

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

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

Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner de sofá”.

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

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

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

8 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 17.9 MB in 275 requests on a phone: media 10.5 MB (3), images 5.6 MB (106) and other files 923 KiB (113). Under 2 MB keeps phones on slow connections fast.

faq_sofa.webp weighs 5.3 MB. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example faq_sofa.webp at 2,432 px wide, shown at 350 px. Resized copies would save about 5.5 MB.

24 images (8.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.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 16 characters: “The Growing Sofa”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 237 pages on thegrowingsofa.com and 11 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to https://thegrowingsofa.com/collections/promocoes, which answers with an error. Visitors hit a dead end and search engines drop it.

https://thegrowingsofa.com/collections/montessori-bed, https://thegrowingsofa.com/collections/zimma, https://thegrowingsofa.com/pages/reseller, https://thegrowingsofa.com/pages/sales, https://thegrowingsofa.com/pages/growtech-technology and https://thegrowingsofa.com/pages/about-us have no meta description, so Google writes the search snippet from whatever text it finds.

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

2 images failed to load on a phone, for example https://thegrowingsofa.com/.

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 1,265 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 13 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.