raincaper.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Help Scout and others), adding 1.1 MB and 873 ms of main-thread time.

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

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

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

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

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

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

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

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

11 KiB could be saved by minifying JavaScript.

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.

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

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

For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 6.7 MB in 279 requests on a phone: images 4.6 MB (60), scripts 994 KiB (95) and other files 895 KiB (110). Under 2 MB keeps phones on slow connections fast.

RainCaper_Collection_Image_RC-M61_Front_600x800_f9d859aa-d2b 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).

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

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

21 elements hidden from screen readers can still receive keyboard focus.

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

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: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

5 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 is no <h1>, so neither visitors nor Google get a clear main headline.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 321 pages on raincaper.com and 9 external pages.

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

16 of 56 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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

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

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

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