imagine.com.bn website review

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

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

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

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

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

The page has 2,105 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

4 third-party services load with your homepage (Google Tag Manager, wpmucdn.com and JSDelivr CDN and others), adding 329 KiB and 230 ms of main-thread time.

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (9 KiB).

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.

Your largest element takes 27.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “dLink-mesh-mobile-banner”.

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

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

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

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

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

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

Your homepage downloads 5.9 MB in 121 requests on a phone: images 5.1 MB (49), scripts 622 KiB (25) and fonts 133 KiB (4). Under 2 MB keeps phones on slow connections fast.

12 images (1.2 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.

telco-awards-web-768x73.png 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).

5 images are downloaded at several times the size a phone draws them, for example 5-768x768.png at 390 px wide, shown at 93 px. Resized copies would save about 142 KiB.

1 image further down the page (22 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.68 g of CO₂e: 201.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 14 characters: “Home | imagine”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 131 pages on imagine.com.bn and 33 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/consumer/broadband and /broadband all use the title “Consumer | Broadband | imagine”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/i-sadaqah has no meta description, so Google writes the search snippet from whatever text it finds.

/consumer/broadband and /broadband use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /broadband, whose canonical is /consumer/broadband. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/enterprise, /help, /consumer/fibre-everywhere, /imacare, /consumer/mobile/esim and /sms-booster-guide and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

/i-sadaqah 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.

/help, /consumer/broadband, /broadband and /consumer/landline took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 33 found) 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”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

imagine.com.bn 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.

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

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

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

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

DMARC is set to p=none, so mail pretending to be imagine.com.bn is still delivered. Reports are on, so moving to quarantine is the next step.

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.

Before a visitor clicks anything, the page loads 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.

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