sunbray.com website review

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

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

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

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

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

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

Klaviyo costs a phone 167 ms of main-thread work and 520 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.

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

7 images could be 157 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

6 third-party services load with your homepage (Klaviyo, Shopify and squarecdn.com and others), adding 1,001 KiB and 286 ms of main-thread time.

About 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.

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

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

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

3 KiB could be saved by minifying JavaScript.

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

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

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

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 2.9 MB in 315 requests on a phone: scripts 1.0 MB (136), other files 873 KiB (124) and images 675 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

Your <h1> is empty.

The homepage links to 73 pages on sunbray.com and 10 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://sunbray.com/pages/shipping has no meta description, so Google writes the search snippet from whatever text it finds.

https://sunbray.com/collections/sunglasses/products/the-dawson-tortoise and https://sunbray.com/collections/sunglasses/products/the-dawson-black use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://sunbray.com/collections/sunglasses/products/the-dawson-tortoise, whose canonical is https://sunbray.com/products/the-dawson-tortoise. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://sunbray.com/collections/sunglasses, https://sunbray.com/collections/the-whistler, https://sunbray.com/collections/the-dawson, https://sunbray.com/collections/the-maybury, https://sunbray.com/collections/the-fullbrook and https://sunbray.com/pages/about-sunbray and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

10 of 30 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.

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

The homepage has only about 196 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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