sitikhadijah.com website review

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

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

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

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Shopify and dotdigital.com and others), adding 3.8 MB and 1.3 s of main-thread time.

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

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

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

YouTube costs a phone 412 ms of main-thread work and 1,019 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 312 ms of main-thread work and 1.8 MB 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.

dotdigital.com costs a phone 267 ms of main-thread work and 398 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.

ZenDesk costs a phone 192 ms of main-thread work and 431 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.

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

84 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 9 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.

3 KiB JavaScript is shipped twice across bundles.

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 611 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

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

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

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

Your homepage downloads 16.6 MB in 550 requests on a phone: media 8.9 MB (1), scripts 3.4 MB (233) and images 2.1 MB (43). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 1 element on the page fails 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.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 25 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.

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

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

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

Your <h1> is empty.

The homepage links to 70 pages on sitikhadijah.com and 0 external pages.

A phone browser shows 871 words, but the HTML your server sends has only 111. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://sitikhadijah.com/pages/buy-now-pay-later, https://sitikhadijah.com/pages/maybank-ezypay, https://sitikhadijah.com/collections/teman, https://sitikhadijah.com/collections/kids, https://sitikhadijah.com/collections/lifestyle and https://sitikhadijah.com/pages/gifting-sale and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://sitikhadijah.com/pages/buy-now-pay-later, https://sitikhadijah.com/pages/maybank-ezypay, https://sitikhadijah.com/collections/telekung, https://sitikhadijah.com/collections/sejadah, https://sitikhadijah.com/collections/teman and https://sitikhadijah.com/collections/koleksi-wanita and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sitikhadijah.com/pages/buy-now-pay-later, https://sitikhadijah.com/pages/maybank-ezypay, https://sitikhadijah.com/collections/lifestyle and https://sitikhadijah.com/pages/gifting-sale have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

6 third-party cookies are 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 “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Requests the geolocation permission on page load.

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

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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