Website review, no card needed

adamjeeinsurance.com logo

adamjeeinsurance.com website review

Visit site (opens in a new tab)Reviewed 1 November 202650 issues · 92 checks

This review found 50 issues worth fixing on adamjeeinsurance.com, 14 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. 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.5 s2.3 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
124 ms114 msMay 9Oct 24119 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026115 ms
May 16, 2026117 ms
May 23, 2026118 ms
May 30, 2026118 ms
Jun 6, 2026117 ms
Jun 13, 2026120 ms
Jun 20, 2026118 ms
Jun 27, 2026118 ms
Jul 4, 2026119 ms
Jul 11, 2026117 ms
Jul 18, 2026117 ms
Jul 25, 2026117 ms
Aug 1, 2026118 ms
Aug 8, 2026120 ms
Aug 15, 2026121 ms
Aug 22, 2026123 ms
Aug 29, 2026121 ms
Sep 5, 2026119 ms
Sep 12, 2026119 ms
Sep 19, 2026119 ms
Sep 26, 2026121 ms
Oct 3, 2026123 ms
Oct 10, 2026123 ms
Oct 17, 2026122 ms
Oct 24, 2026119 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 adamjeeinsurance.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adamjeeinsurance.com at 1.3 s1.3 s
  2. adamjeeinsurance.com at 2.6 s2.6 s
  3. adamjeeinsurance.com at 3.9 s3.9 s
  4. adamjeeinsurance.com at 5.2 s5.2 s
  5. adamjeeinsurance.com at 6.5 s6.5 s
  6. adamjeeinsurance.com at 7.8 s7.8 s
  7. adamjeeinsurance.com at 9.1 s9.1 s
  8. adamjeeinsurance.com at 10.4 s10.4 s

Speed

12 to fix57
  • Use efficient cache lifetimes

    1.9 s · 3.9 MB

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

  • Render-blocking requests

    3.3 s

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

  • Reduce unused CSS

    1.2 s · 224 KiB

    About 224 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Improve image delivery

    500 ms · 920 KiB

    15 images could be 920 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Reduce unused JavaScript

    600 ms · 613 KiB

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

  • Mobile performance score: 57

    57/100

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

  • Font display

    750 ms

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

  • Document request latency

    600 ms · 93 KiB

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

  • Reduce initial server response time

    580 ms

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

  • Minify JavaScript

    546 KiB

    546 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 272 ms

    272 ms

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

  • Server response: 680 ms

    680 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google CDN and others), adding 719 KiB and 350 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Duplicated JavaScript

    150 ms · 14 KiB

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

  • Legacy JavaScript

    45 KiB

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

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

1 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 296 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

9 to fix67
  • 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: 10.9 s

    10.9 s

    Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (4.5 s).

  • Speed Index: 13.7 s

    13.7 s

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

  • Time to Interactive: 23.5 s

    23.5 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 23 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-24, 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).

4 checks passed
  • Real-user INP: 117 ms

    117 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Total Blocking Time: 109 ms

    109 ms

    Scripts block the page for only 109 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 4.7 MB in 61 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 61 requests on a phone: images 2.6 MB (29), scripts 1.4 MB (16) and fonts 270 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    2.webp weighs 560 KiB. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (677 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.

  • 6 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.33 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 7485
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 3 text elements with low contrast

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

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 2 images without alt text

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

  • All page content should be contained by landmarks (25 elements)

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

  • No main landmark

    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)

    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.

  • 37 form fields without a label

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

  • 6 links without text

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

  • Headings skip levels

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

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

8 to fixGoogle 8373
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“MAKING SURE YOU'RE INSURED!” and “NEWSLETTER”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • Meta description is long (245 characters)

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

  • No social preview image

    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

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 1 link with vague text

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

  • No X (Twitter) card tag

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

  • 54 internal links, 14 external

    The homepage links to 54 pages on adamjeeinsurance.com and 14 external pages.

2 checks passed
  • Title: 59 characters

    Your title is a healthy 59 characters: “Adamjee Insurance The Largest Insurance Company in Pakistan”.

  • robots.txt in place

    robots.txt is in place.

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.

  • No llms.txt

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

2 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 (791 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 16 pages share a title

    /, https://www.adamjeeinsurance.com/business, https://www.adamjeeinsurance.com/about-us, https://www.adamjeeinsurance.com/investor-relation, https://www.adamjeeinsurance.com/career and https://www.adamjeeinsurance.com/contact-us and 10 others all use the title “Adamjee Insurance The Largest Insurance Company in Pakistan”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.adamjeeinsurance.com/business, https://www.adamjeeinsurance.com/about-us, https://www.adamjeeinsurance.com/investor-relation, https://www.adamjeeinsurance.com/career, https://www.adamjeeinsurance.com/contact-us and https://www.adamjeeinsurance.com/car-insurance and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

3 to fixGoogle 9285
  • 14 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “telInput.intlTelInput is not a function”.

  • 3 distorted images

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 14-field form

    Your longest form asks for 14 fields (2 required). Every extra field lowers completion.

  • 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 397 words of copy

    The homepage carries about 397 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Get Quote”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Contact Us”, “Call Us: 0800 00 242” and “Call : 0800 00 242”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 4 email links.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    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.

  • 6 other companies contacted

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

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 adamjeeinsurance.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Transworld Associates Pvt. Ltd.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on adamjeeinsurance.com, including 21 speed issues, 8 SEO issues and 2 conversion gaps. 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