Website review, no card needed

howdenindia.in logo

howdenindia.in website review

Visit site (opens in a new tab)Reviewed 3 November 202632 issues · 80 checks

This review found 32 issues worth fixing on howdenindia.in, 13 of them high impact, across 80 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.9 s2.4 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
143 ms127 msMay 16Oct 31136 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026133 ms
May 30, 2026137 ms
Jun 6, 2026140 ms
Jun 13, 2026140 ms
Jun 20, 2026141 ms
Jun 27, 2026139 ms
Jul 4, 2026138 ms
Jul 11, 2026140 ms
Jul 18, 2026140 ms
Jul 25, 2026139 ms
Aug 1, 2026141 ms
Aug 8, 2026140 ms
Aug 15, 2026139 ms
Aug 22, 2026138 ms
Aug 29, 2026136 ms
Sep 5, 2026134 ms
Sep 12, 2026132 ms
Sep 19, 2026134 ms
Sep 26, 2026136 ms
Oct 3, 2026137 ms
Oct 10, 2026137 ms
Oct 17, 2026137 ms
Oct 24, 2026135 ms
Oct 31, 2026136 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of howdenindia.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. howdenindia.in at 0.6 s0.6 s
  2. howdenindia.in at 1.3 s1.3 s
  3. howdenindia.in at 1.9 s1.9 s
  4. howdenindia.in at 2.5 s2.5 s
  5. howdenindia.in at 3.2 s3.2 s
  6. howdenindia.in at 3.8 s3.8 s
  7. howdenindia.in at 4.5 s4.5 s
  8. howdenindia.in at 5.1 s5.1 s

Speed

8 to fix49
  • Improve image delivery

    1.8 s · 994 KiB

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

  • Reduce unused JavaScript

    2.3 s · 452 KiB

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

  • Mobile performance score: 49

    49/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, iubenda and cloudflare.com and others), adding 890 KiB and 1.1 s of main-thread time.

  • Google Tag Manager adds 920 ms

    920 ms

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

  • Use efficient cache lifetimes

    150 ms · 350 KiB

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

  • Main-thread work: 3.0 s

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

  • Render-blocking requests

    300 ms

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

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 38 KiB

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

  • Reduce unused CSS

    150 ms · 33 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 16.9 s

    16.9 s

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

  • Time to Interactive: 18.2 s

    18.2 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Total Blocking Time: 559 ms

    559 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 145 ms

    145 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix25
  • Page weight: 7.6 MB in 100 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 100 requests on a phone: media 2.9 MB (1), other files 1.5 MB (11) and images 1.1 MB (57). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    14_unsplash_fineartandspecie.jpg weighs 644 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    668 KiB

    2 images are downloaded at several times the size a phone draws them, for example 14_unsplash_fineartandspecie.jpg at 2,000 px wide, shown at 350 px. Resized copies would save about 668 KiB.

  • 2 images in older formats

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

  • 1 image below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.15 g

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

Accessibility

5 to fixGoogle 9393
  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 60 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • Meta description is long (182 characters)

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 186 internal links, 13 external

    The homepage links to 186 pages on howdenindia.in and 13 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Global insurance group”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Howden Insurance India - Specialist Broker”.

  • Canonical URL set

    The canonical URL is https://www.howdengroup.com/in-en.

  • Structured data in place

    Structured data found: WebPage.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.howdengroup.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (845 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.howdengroup.com/llms.txt (1 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 14 pages without a meta description

    https://www.howdengroup.com/in-en/solutions/services/claims-management, https://www.howdengroup.com/in-en/solutions/liability/international-business, https://www.howdengroup.com/in-en/solutions/services/risk-management, https://www.howdengroup.com/in-en/contact, https://www.howdengroup.com/in-en/industry-expertise/aviation-and-aerospace and https://www.howdengroup.com/in-en/industry-expertise/chemicals-and-pharmaceuticals and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.howdengroup.com/in-en/contact has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.howdengroup.com/in-en/industry-expertise/chemicals-and-pharmaceuticals, https://www.howdengroup.com/in-en/industry-expertise/infrastructure, https://www.howdengroup.com/in-en/ecommerce and https://www.howdengroup.com/in-en/industry-expertise/oil-and-energy took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 3 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No call to action on the first screen

    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 risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 388 words of copy

    The homepage carries about 388 words of visible text.

5 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact”, “Contact our Network” and “Contact us”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies (measured from a US location before any click).

  • 9 other companies contacted

    Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at howdenindia.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Hyve Ltd

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on howdenindia.in, including 16 speed issues, 1 SEO issue and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25