caprilina.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Bugsnag and route.com and others), adding 2.5 MB and 1.2 s of main-thread time.

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

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

Google Tag Manager costs a phone 420 ms of main-thread work and 653 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.

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

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

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

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

route.com costs a phone 220 ms of main-thread work and 542 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.

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

The layout shifts by 0.308 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 631 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 98 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 4.7 MB in 395 requests on a phone: scripts 2.6 MB (132), other files 1.1 MB (211) and images 594 KiB (22). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Blankets_square_1024x1024.jpg at 1,024 px wide, shown at 140 px. Resized copies would save about 123 KiB.

6 images further down the page (332 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 66 characters, so Google will cut it off around 60: “Caprilina | Personalized Newborn Going Home Outfits & Baby Clothes”.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 186 pages on caprilina.com and 1 external page.

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://www.caprilina.com/collections/baby-clothes, https://www.caprilina.com/collections/bubbles, https://www.caprilina.com/collections/knitted-sets, https://www.caprilina.com/collections/kimonos, https://www.caprilina.com/collections/onesies and https://www.caprilina.com/collections/children-clothes and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://www.caprilina.com/.

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

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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