unifillgroupbd.com website review

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

19 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.6 s faster on a phone.

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

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

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

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

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

Reduce initial server response time. Google estimates savings of 1.4 s on a phone.

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

117 KiB could be saved by minifying CSS.

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

Cloudflare CDN costs a phone 8 ms of main-thread work and 328 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.

29 KiB could be saved by minifying JavaScript.

3 third-party services load with your homepage (jQuery CDN, Cloudflare CDN and Google Fonts), adding 468 KiB and 46 ms of main-thread time.

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

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

Your largest element takes 52.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 12.1 MB in 129 requests on a phone: images 10.0 MB (69), stylesheets 899 KiB (25) and scripts 555 KiB (24). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example iso14001.png at 2,854 px wide, shown at 241 px. Resized copies would save about 2.8 MB.

34 images (8.4 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.

35 images further down the page (8.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

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

There are 3 <h1> headlines (“Unifill Composite Dyeing MillsLimited”, “Unifill Composite Dyeing MillsLimited” and “Unifill Composite Dyeing MillsLimited”). One clear main headline is easier for people and search engines.

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

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

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

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

The homepage links to 24 pages on unifillgroupbd.com and 11 external pages.

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.

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

https://unifillgroupbd.com/about.html, https://unifillgroupbd.com/dyeing.html, https://unifillgroupbd.com/printing.html, https://unifillgroupbd.com/qms.html, https://unifillgroupbd.com/sustainability.html and https://unifillgroupbd.com/social.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://unifillgroupbd.com/contact.html has no <h1> headline, so visitors and search engines get no clear main topic.

https://unifillgroupbd.com/about.html, https://unifillgroupbd.com/dyeing.html, https://unifillgroupbd.com/printing.html, https://unifillgroupbd.com/qms.html and https://unifillgroupbd.com/social.html took over 3 s to send their HTML from our server.

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

4 images failed to load on a phone, for example https://unifillgroupbd.com/assets/images/home_one/team.jpg.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 1,217 words of visible text.

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