layinsun.com website review

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

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

20 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

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

6 third-party services load with your homepage (Shopify, Trust Pilot and Klaviyo and others), adding 709 KiB and 222 ms of main-thread time.

About 25 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 (22 KiB).

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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 9.6 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 9.6 s. Good is under 3.8 s.

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

Real visitors wait 965 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 10.9 MB in 303 requests on a phone: media 5.4 MB (1), images 3.5 MB (40) and other files 959 KiB (151). Under 2 MB keeps phones on slow connections fast.

12 images (818 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.

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

26 buttons have no accessible name, so screen readers announce just “button”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

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

There are 5 <h1> headlines (“”, “Black Friday Outdoor SaleUp to 50% off” and “Black Friday Outdoor SaleUp to 50% off”). One clear main headline is easier for people and search engines.

The homepage links to 203 pages on layinsun.com and 0 external pages.

https://www.layinsun.com/collections/all, https://www.layinsun.com/policies/shipping-policy, https://www.layinsun.com/pages/activity, https://www.layinsun.com/collections/sectional-sets, https://www.layinsun.com/collections/swivel-chairs-sets and https://www.layinsun.com/collections/fire-pit-patio-sets and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.layinsun.com/collections/all, https://www.layinsun.com/pages/activity, https://www.layinsun.com/collections/sectional-sets, https://www.layinsun.com/collections/swivel-chairs-sets, https://www.layinsun.com/collections/fire-pit-patio-sets and https://www.layinsun.com/collections/outdoor-dining-sets and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.layinsun.com/collections/outdoor-ottomans took over 3 s to send its HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

Social proof on the homepage: 64 testimonial or review blocks. 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.

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

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