phool.co website review

11 images could be 617 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, shiprocket.in and pickrr.com and others), adding 25.1 MB and 1.5 s of main-thread time.

About 3.0 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.

Shopify costs a phone 164 ms of main-thread work and 22.3 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.

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

Google Tag Manager costs a phone 342 ms of main-thread work and 720 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 103 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.

pickrr.com costs a phone 250 ms of main-thread work and 1.3 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.

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

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

shiprocket.in costs a phone 297 ms of main-thread work and 120 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 2,319 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google CDN costs a phone 98 ms of main-thread work and 297 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.

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

9 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Phool Ram Darbar Diwali Decor Gift Box with Candle Spinner”.

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

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

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

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

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

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

19 images weigh 71.5 MB together. On a phone connection a single image that size takes seconds.

19 images are downloaded at several times the size a phone draws them, for example availableon-15.webp at 4,268 px wide, shown at 171 px. Resized copies would save about 67.8 MB.

Your homepage downloads 27.4 MB in 233 requests on a phone: images 22.9 MB (36), scripts 2.7 MB (66) and other files 1.2 MB (104). Under 2 MB keeps phones on slow connections fast.

26 images (72.7 MB) 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.

mobile_1_c08a672b-452c-4594-9fb1-7b03389b1230.webp 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 further down the page (604 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 7.77 g of CO₂e: 932.8 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”.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

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

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

74 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 71 pages on phool.co and 14 external pages.

https://phool.co/collections/reed-diffuser has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'getRegistration')”.

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

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.

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 shows no opening hours. If customers visit or call, show when.

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 homepage carries about 1,006 words of visible text.

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 and Meta 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 13 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.