pitambari.com website review

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

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

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

7 third-party services load with your homepage (Google Maps, Google CDN and Google Tag Manager and others), adding 1.4 MB and 960 ms of main-thread time.

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

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

Google CDN costs a phone 364 ms of main-thread work and 741 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 383 ms of main-thread work and 483 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.

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

8 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 33 KiB of CSS is downloaded but never applied on this page.

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

5 KiB could be saved by minifying JavaScript.

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 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.

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

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

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

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

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

Your homepage downloads 7.3 MB in 111 requests on a phone: media 3.9 MB (2), scripts 1.5 MB (37) and images 1.3 MB (46). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (162 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (37 KiB) is 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.

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

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

3 elements hidden from screen readers can still receive keyboard focus.

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

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

The homepage links to 48 pages on pitambari.com and 18 external pages.

There is no https://pitambari.com/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://pitambari.com/about-us.html, https://pitambari.com/products.html, https://pitambari.com/partner-us/shoppy-franchise.html, https://pitambari.com/partner-us/nursery-franchise.html, https://pitambari.com/global-presence.html and https://pitambari.com/research-development.html and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pitambari.com/products.html has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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

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