manilagrace.com website review

iubenda costs a phone 1.1 s of main-thread work and 124 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

3 third-party services load with your homepage (iubenda, Shopify and shop.app), adding 246 KiB and 1.1 s of main-thread time.

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

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

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

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

About 80 KiB of JavaScript is downloaded but never used on this page.

About 11 KiB of CSS is downloaded but never applied on this page.

Desktop scores 60 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 JavaScript is shipped twice across bundles.

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

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

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

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

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

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

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

Your homepage downloads 9.0 MB in 267 requests on a phone: images 3.9 MB (40), media 3.5 MB (1) and other files 968 KiB (140). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example borse-01_1008a180-71c9-419a-9fad-9e8867a26313.jpg at 480 px wide, shown at 16 px. Resized copies would save about 120 KiB.

2 images (102 KiB) are 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 2.55 g of CO₂e: 306.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

1 link inside paragraphs relies on colour alone to stand out.

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

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.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 68 characters, so Google will cut it off around 60: “Manila Grace Official Store | Women's Clothing, Bags and Accessories”.

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

The homepage links to 175 pages on manilagrace.com and 11 external pages.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies (measured from a US location before any click).

Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.