issada.com website review

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

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

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

8 third-party services load with your homepage (vitals.app, Shopify and Clarity and others), adding 2.0 MB and 732 ms of main-thread time.

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

About 628 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

vitals.app costs a phone 194 ms of main-thread work and 635 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.

Shopify costs a phone 142 ms of main-thread work and 666 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 167 ms. During a long task the page ignores taps.

52 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need.

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 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

Your homepage downloads 5.0 MB in 442 requests on a phone: scripts 2.1 MB (186), images 1.8 MB (80) and other files 827 KiB (150). Under 2 MB keeps phones on slow connections fast.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

Your title is 70 characters, so Google will cut it off around 60: “ISSADA Mineral Makeup & Cosmeceutical Skincare – ISSADA Cosmeceuticals”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 357 pages on issada.com and 18 external pages.

https://issada.com/collections/issada-christmas-packs-2026 and https://issada.com/collections/all-skincare have no meta description, so Google writes the search snippet from whatever text it finds.

https://issada.com/collections/all, https://issada.com/collections/issada-christmas-packs-2026, https://issada.com/collections/all-skincare and https://issada.com/collections/skincare-value-packs have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/Product/313106245/244959900/square.jpg?1761627929.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

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

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.

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

The homepage carries about 1,362 words of visible text.

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