Website review, no card needed

unimax.com.bd logo

unimax.com.bd website review

Visit site (opens in a new tab)Reviewed 21 November 202636 issues · 78 checks

This review found 36 issues worth fixing on unimax.com.bd, 11 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
10.0 s8.2 sSep 12Nov 149.8 s
Show as table
DateReal-visitor load time (LCP)
Sep 12, 20268.7 s
Sep 19, 20268.4 s
Sep 26, 20268.8 s
Oct 3, 20268.6 s
Oct 10, 20268.6 s
Oct 17, 20268.6 s
Oct 24, 20268.6 s
Oct 31, 20268.8 s
Nov 7, 20269.2 s
Nov 14, 20269.8 s

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 unimax.com.bd (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. unimax.com.bd at 1.8 s1.8 s
  2. unimax.com.bd at 3.6 s3.6 s
  3. unimax.com.bd at 5.4 s5.4 s
  4. unimax.com.bd at 7.1 s7.1 s
  5. unimax.com.bd at 8.9 s8.9 s
  6. unimax.com.bd at 10.7 s10.7 s
  7. unimax.com.bd at 12.5 s12.5 s
  8. unimax.com.bd at 14.3 s14.3 s

Speed

6 to fix62
  • Render-blocking requests

    3.9 s

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

  • Mobile performance score: 62

    62/100

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

  • Reduce unused CSS

    600 ms · 130 KiB

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

  • Reduce unused JavaScript

    450 ms · 77 KiB

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

  • Font display

    500 ms

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

  • Main-thread work: 2.1 s

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

  • Improve image delivery

    250 ms · 65 KiB

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

  • 5 long tasks on the main thread

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 190 KiB and 3 ms of main-thread time.

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

  • Use efficient cache lifetimes

    3 KiB

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

9 to fix50
  • 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.

  • Real-user LCP: 10.4 s

    10.4 s

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

  • Real-user FCP: 7.7 s

    7.7 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Speed Index: 18.6 s

    18.6 s

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

  • Largest Contentful Paint: 7.5 s

    7.5 s

    Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (11.5 s).

  • Time to Interactive: 7.5 s

    7.5 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 16 images without width and height

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

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

    +11%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.009

    0.009

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

  • Total Blocking Time: 35 ms

    35 ms

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

Images and page weight

2 to fix88
  • An image on the first screen is lazy-loaded

    Unimax-Logo-r.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).

  • 1 image far larger than shown

    24 KiB

    1 image is downloaded at several times the size a phone draws it, for example why-our-Product-1.webp at 1,152 px wide, shown at 310 px. Resized copies would save about 24 KiB.

  • 1 image below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.36 g

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

2 checks passed
  • Page weight: 1.3 MB in 113 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 113 requests on a phone: fonts 445 KiB (12), images 367 KiB (20) and scripts 250 KiB (24). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9696
  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

6 to fixGoogle 9270
  • No H1 headline

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

  • Title is short (20 characters)

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

  • Meta description is long (6660 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links crawlers can't follow

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

  • 15 internal links, 2 external

    The homepage links to 15 pages on unimax.com.bd and 2 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://unimax.com.bd/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://unimax.com.bd/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing name, 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.

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://unimax.com.bd/avonee has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://unimax.com.bd/avonee, https://unimax.com.bd/sisters-concern and https://unimax.com.bd/gallery have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://unimax.com.bd/avonee and https://unimax.com.bd/gallery have 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.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 3 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 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://unimax.com.bd/wp-content/plugins/elementor-pro/assets/css/widget-mega-menu.min.css…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • 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 social proof

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

  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 207 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us”.

  • Direct contact links

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

Privacy and tracking

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on unimax.com.bd, including 15 speed issues, 6 SEO issues and 6 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