sunsboards.com website review

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

Your mobile performance score is 66 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

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

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

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

8 third-party services load with your homepage (Shopify, automizely.com and weglot.com and others), adding 1.1 MB and 281 ms of main-thread time.

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

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

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

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

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

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

36 KiB could be saved by minifying JavaScript.

11 KiB could be saved by minifying CSS.

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.

4 KiB JavaScript is shipped twice across bundles.

Your largest element takes 9.3 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 12.3 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 26.3 MB in 338 requests on a phone: media 21.6 MB (2), images 2.0 MB (30) and scripts 1.3 MB (93). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

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

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

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/suns_boards_logo_01.png")”.

Your <h1> is empty.

The homepage links to 181 pages on sunsboards.com and 12 external pages.

https://www.sunsboards.com/collections/fall-winter-26-27-man, https://www.sunsboards.com/collections/fall-winter-26-27-woman, https://www.sunsboards.com/pages/saldiss26, https://www.sunsboards.com/collections/sales30, https://www.sunsboards.com/collections/giubbotti-e-giacche-uomo and https://www.sunsboards.com/collections/parka-e-trench-uomo and 4 others use the same meta description. A description written for each page earns more clicks.

https://www.sunsboards.com/pages/saldiss26 has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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