pragatilife.com website review

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

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

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

The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 775 ms on a phone.

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

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

38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.

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

Your server takes 875 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

6 third-party services load with your homepage (Unpkg, JSDelivr CDN and Cloudflare CDN and others), adding 344 KiB and 220 ms of main-thread time.

37 KiB could be saved by minifying CSS.

1 long task block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.

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.

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Family Image”. Most of its time is resource load delay (3.6 s).

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

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

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

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

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

27 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-24, real Chrome visitors' tap response (inp) went from 118 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.7 MB in 99 requests on a phone: images 5.1 MB (51), scripts 276 KiB (14) and HTML 187 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

6 images are downloaded at several times the size a phone draws them, for example IMAGE_1.png at 1,536 px wide, shown at 358 px. Resized copies would save about 2.1 MB.

11 images further down the page (4.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Education.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).

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

12 buttons have no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 27 characters: “Pragati Life Insurance PLC.”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 5 <h1> headlines (“নিশ্চিন্ত জীবনের নিশ্চয়তায় প্রগতি লাইফ ইন্স্যুর…”, “শিক্ষা বৃত্তি বীমা” and “প্রগতি লাইফের বীমা পলিসি কিনুন আমাদের পার্টনার ব্…”). One clear main headline is easier for people and search engines.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 108 pages on pragatilife.com and 13 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.

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

/, https://pragatilife.com/policy-ledger, https://pragatilife.com/premium-calculator, https://pragatilife.com/office-information, https://pragatilife.com/media-center and https://pragatilife.com/abouts and 10 others all use the title “Pragati Life Insurance PLC.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://pragatilife.com/policy-ledger, https://pragatilife.com/premium-calculator, https://pragatilife.com/office-information, https://pragatilife.com/media-center, https://pragatilife.com/abouts and https://pragatilife.com/chairman/message and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pragatilife.com/premium-calculator, https://pragatilife.com/media-center, https://pragatilife.com/abouts and https://pragatilife.com/chairman/message took over 3 s to send their HTML from our server.

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to find a valid digest in the 'integrity' attribute for resource 'https://cdnjs.cloudflare.com/ajax/libs/font-aw…”.

19 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

Social proof on the homepage: 13 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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