monastery.com.co website review

19 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Clarity, Shopify and Google Tag Manager and others), adding 1.4 MB and 479 ms of main-thread time.

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

Shopify costs a phone 108 ms of main-thread work and 786 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,809 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

bonloyalty.com costs a phone 32 ms of main-thread work and 358 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.

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

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

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

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 9.2 MB in 323 requests on a phone: images 6.4 MB (40), scripts 1.7 MB (82) and other files 992 KiB (171). Under 2 MB keeps phones on slow connections fast.

BANNER_PRINCIPAL_vertical_Paginaweb.jpg 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).

2 images are downloaded at several times the size a phone draws them, for example TYROL_BLACK_FRENTE_40b8b27c-d082-487c-aa8e-43e67558af79.jpg at 390 px wide, shown at 20 px. Resized copies would save about 289 KiB.

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

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

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

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.

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

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

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

Structured data found (BreadcrumbList, ClothingStore, Organization and Store) but with 1 problem, for example “Organization: url points at a different host (https://monasterycouture.com.co)”.

The homepage links to 204 pages on monastery.com.co and 14 external pages.

Your homepage links to https://monastery.com.co/collections/new-release-men, https://monastery.com.co/collections/new-release-women, https://monastery.com.co/collections/imperium and https://monastery.com.co/collections/camisetas-monastery, which answer with an error. Visitors hit a dead end and search engines drop them.

https://monastery.com.co/collections/looks-para-mujer, https://monastery.com.co/collections/summit, https://monastery.com.co/collections/dominus, https://monastery.com.co/collections/hoodies-and-sweatshirts and https://monastery.com.co/collections/jackets-bombers-and-sport-jackets have no meta description, so Google writes the search snippet from whatever text it finds.

https://monastery.com.co/collections/looks-para-mujer, https://monastery.com.co/collections/summit, https://monastery.com.co/collections/dominus, https://monastery.com.co/collections/men, https://monastery.com.co/collections/polo-shirts and https://monastery.com.co/collections/hoodies-and-sweatshirts and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://monastery.com.co/collections/dominus took over 3 s to send its HTML from our server.

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

25 of 91 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 “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 page uses urgency cues (a countdown or limited-time wording).

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