reyns.com website review

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

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

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

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

Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (negate.io, Google Tag Manager and Yotpo and others), adding 4.1 MB and 2.2 s of main-thread time.

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

negate.io costs a phone 918 ms of main-thread work and 40 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.

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

Google Tag Manager costs a phone 319 ms of main-thread work and 505 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 123 ms of main-thread work and 2.4 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.

Yotpo costs a phone 256 ms of main-thread work and 297 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.

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

rebuyengine.com costs a phone 223 ms of main-thread work and 492 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.

14 KiB could be saved by minifying CSS.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

22 KiB could be saved by minifying JavaScript.

12 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

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

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

Real visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 23.6 MB in 379 requests on a phone: media 14.7 MB (1), images 4.7 MB (112) and scripts 2.3 MB (111). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example molokai-channel-boxer-brief-royal.jpg at 1,800 px wide, shown at 22 px. Resized copies would save about 257 KiB.

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

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No XML sitemap at https://www.reynspooner.com/sitemap.xml, so Google discovers your pages only by following links.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 267 pages on reyns.com and 0 external pages.

https://www.reynspooner.com/pages/2026-holiday-gift-guide has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.reynspooner.com/collections/best-sellers, https://www.reynspooner.com/pages/2026-holiday-gift-guide, https://www.reynspooner.com/pages/christmas-collections-2026, https://www.reynspooner.com/pages/celebrating-70-years-of-aloha, https://www.reynspooner.com/collections/new-arrivals and https://www.reynspooner.com/collections/men have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.reynspooner.com/collections/men has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Boost > [ERROR] Failed to load themeCSS Error: Timeout loading asset themeCSS”.

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 1,149 words of visible text.

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