galleri5.com website review

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

24 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

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

Your mobile performance score is 75 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Facebook, website-files.com and cloudfront.net and others), adding 1.8 MB and 324 ms of main-thread time.

website-files.com costs a phone 111 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.

About 146 KiB of JavaScript is downloaded but never used on this page.

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

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

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

6 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

40 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-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.3 MB in 73 requests on a phone: images 4.5 MB (37), scripts 536 KiB (10) and fonts 156 KiB (12). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example 20260318_120347_3d0b3d4f.jpeg at 893 px wide, shown at 163 px. Resized copies would save about 409 KiB.

2 images (413 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.

1 image further down the page (49 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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.

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

Your title is 66 characters, so Google will cut it off around 60: “galleri5 — India's #1 AI Studio for Film, TV & Visual Storytelling”.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 185 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

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

The homepage links to 58 pages on galleri5.com and 19 external pages.

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.

The HTML your server sends has 814 of the 1,814 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.galleri5.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.

Your homepage links to https://www.galleri5.com/drafts/blog and https://www.galleri5.com/drafts/faq, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.galleri5.com/our-work and https://www.galleri5.com/in-the-news have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.galleri5.com/old-home, https://www.galleri5.com/social-intelligence, https://www.galleri5.com/about, https://www.galleri5.com/request-demo, https://www.galleri5.com/ai-studio and https://www.galleri5.com/terms-of-service and 1 other use the same meta description. A description written for each page earns more clicks.

https://www.galleri5.com/our-work, https://www.galleri5.com/about and https://www.galleri5.com/in-the-news have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.galleri5.com/our-work has 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 11 pages linked from your homepage and read each the way a search engine does.

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

Large scripts ship without source maps.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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