pluckk.in website review

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

101 files are served with short cache lifetimes, so returning visitors download them again (5.2 MB).

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

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

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

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

8 third-party services load with your homepage (sagepilot.ai, Google Tag Manager and Facebook and others), adding 1.6 MB and 934 ms of main-thread time.

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

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

sagepilot.ai costs a phone 278 ms of main-thread work and 685 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.

Google Maps costs a phone 119 ms of main-thread work and 383 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 86 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.

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

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

Your largest element takes 16.5 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 35.9 s. Good is under 3.8 s.

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

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

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

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

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

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 13.9 MB in 303 requests on a phone: images 11.7 MB (169), scripts 1.7 MB (69) and fonts 231 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

21 images are downloaded at several times the size a phone draws them, for example city-banglore.svg at 266 px wide, shown at 85 px. Resized copies would save about 1.5 MB.

41978-main-banner-1200---2026-10-13t114143.099.png 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).

6 images (620 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.

7 images further down the page (654 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 3.93 g of CO₂e: 472.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

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

ARIA role should be appropriate for the element: 220 elements on the page fail this check, rated minor by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Your title is 70 characters, so Google will cut it off around 60: “Fresh Fruits and Vegetables: Buy Fruits and Vegetables Online | Pluckk”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.pluckk.in/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 49 pages on pluckk.in and 1 external page.

A phone browser shows 2,071 words, but the HTML your server sends has only 271. 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 https://pluckk.in/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://pluckk.in/featured-exotic-veggies and https://pluckk.in/imported-frozen-berries have no <title>, so Google invents the link text in results.

/, https://pluckk.in/our-process, https://pluckk.in/ozone-wash and https://pluckk.in/traceability-new all use the title “Fresh Fruits and Vegetables: Buy Fruits and Vegetables Online | Pluckk”. Search engines can't tell which page to show for a search, so each competes with the others.

https://pluckk.in/featured-exotic-fruits, https://pluckk.in/daily-deals, https://pluckk.in/featured-exotic-veggies and https://pluckk.in/imported-frozen-berries have no meta description, so Google writes the search snippet from whatever text it finds.

https://pluckk.in/our-process, https://pluckk.in/ozone-wash and https://pluckk.in/traceability-new use the same meta description. A description written for each page earns more clicks.

https://pluckk.in/featured-exotic-fruits, https://pluckk.in/featured-exotic-veggies, https://pluckk.in/imported-frozen-berries and https://pluckk.in/haccp have no <h1> headline, so visitors and search engines get no clear main topic.

https://pluckk.in/fruits, https://pluckk.in/organics, https://pluckk.in/our-process, https://pluckk.in/ozone-wash, https://pluckk.in/traceability-new and https://pluckk.in/veggies and 3 others took over 3 s to send their HTML from our server.

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

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

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 2,071 words of visible text.

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