grandecosmetics.ca website review

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

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

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

8 third-party services load with your homepage (chatra.io, Hotjar and Google Tag Manager and others), adding 1.3 MB and 1.1 s of main-thread time.

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

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

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

chatra.io costs a phone 390 ms of main-thread work and 386 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.

3 images could be 27 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

Your largest element takes 12.9 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.047 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.0 MB in 305 requests on a phone: scripts 1.7 MB (75), other files 1,015 KiB (194) and stylesheets 138 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

15 elements have a tabindex above 0, which scrambles the keyboard order.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Some list items are not inside a list.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“”, “America's #1 Lash & Brow Serum Brand*” and “Alicia Grande”). One clear main headline is easier for people and search engines.

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

2 links have no real href, so search engines can't follow them.

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

The homepage links to 30 pages on grandecosmetics.ca and 15 external pages.

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.

Your homepage links to https://grandecosmetics.ca/pages/contact, which answers with an error. Visitors hit a dead end and search engines drop it.

https://grandecosmetics.ca/pages/press, https://grandecosmetics.ca/policies/terms-of-service and https://grandecosmetics.ca/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot set properties of null (setting 'innerHTML')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

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

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