burgan.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 4.3 s

  4.3 s

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

• Real-user FCP: 3.0 s

  3.0 s

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

• Real-user TTFB: 2.0 s

  2.0 s

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

• Tap response (INP) held steady for real visitors

  0%

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

• Largest content (LCP) got 13% slower for real visitors

  +13%

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

• About 0.2 g of CO₂ per visit

  0.23 g

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

• 1 button without a name

  1 button has no accessible name, so screen readers announce just “button”.

  Elements (1)

• 7 tap targets too small

  7 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

• 4 images without alt text

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

  View sourceElements (3)

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

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

  Elements (3)

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

  Elements (1)

• Zoom is disabled

  The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  Elements (1)

• 11 links without text

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

  Elements (3)

• 1 form field without a label

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

  View source

• Headings should not be empty (1 element)

  Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  Elements (1)

• Headings skip levels

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

  View sourceElements (1)

• No meta description

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

• Title is short (13 characters)

  Your title is only 13 characters: “Burgan - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• No structured data

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

• 3 H1 headlines

  There are 3 <h1> headlines (“Transfer Your Salary Today”, “Win Your Share of Kanz” and “Distances Made Shorter”). One clear main headline is easier for people and search engines.

  View source

• No canonical URL

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

• 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://burgan.com/sitemap.xml, so Google discovers your pages only by following links.

• No robots.txt

  There is no robots.txt at burgan.com/robots.txt, the first file search crawlers ask for.

• No X (Twitter) card tag

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

• 235 internal links, 9 external

  The homepage links to 235 pages on burgan.com and 9 external pages.

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

• 4 pages without a meta description

  /en/Packages-page, /en/personal/cards/burgan-cards, /en/personal/term-deposits/fixed-deposit and /en/personal/term-deposits/special-time-deposit have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (4)

• 4 pages slow to respond

  /en/Packages-page, /en/personal/cards/burgan-cards, /en/personal/term-deposits/fixed-deposit and /en/personal/term-deposits/special-time-deposit took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 2 broken external links

  2 links to other sites are dead, for example https://cards.burgan.com/rmt-web/tenant/index (500).

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• HTTP/1.1 only

  The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

• Short HSTS lifetime

  HSTS is set, but max-age is 0 days; one year is the recommended minimum.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  burgan.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  burgan.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• Only about 223 words

  The homepage has only about 223 words of visible text; thin pages give Google and first-time buyers little to go on.

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

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• Email authentication score: 100/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 2 cookies set on arrival

  2

  Opening the homepage sets 2 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.

• 3 other companies contacted

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