mcbsintl.com website review

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

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

About 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.6 s faster on a phone.

Google Tag Manager costs a phone 5.2 s of main-thread work and 3.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

YouTube costs a phone 1.3 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

Your mobile performance score is 20 (desktop: 14). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, YouTube and Google Analytics and others), adding 5.3 MB and 7.2 s of main-thread time.

Google Analytics costs a phone 696 ms of main-thread work and 39 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.

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

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

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

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

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

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

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

Scripts block taps and scrolling for 3.9 s in total while the page loads. Good is under 200 ms.

The layout shifts by 0.227 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

12 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 65.4 MB in 178 requests on a phone: images 59.8 MB (67), scripts 5.0 MB (55) and stylesheets 183 KiB (13). Under 2 MB keeps phones on slow connections fast.

17 images weigh 58.4 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example 222.png at 3,072 px wide, shown at 350 px. Resized copies would save about 11.7 MB.

25 images (59.3 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.

11 images further down the page (10.9 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 18.53 g of CO₂e: 2223.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

Your title is 119 characters, so Google will cut it off around 60: “MCBS-Manufacturer of DTH antenna, CATV Products / CCTV Products and Video/Audio Equipment…”.

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

There are 4 <h1> headlines (“Media Release”, “Hot Products” and “Our Achievements”). 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.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 93 pages on mcbsintl.com and 3 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://mcbsintl.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://mcbsintl.com/about/about-us.html and https://mcbsintl.com/contact-us/email-us.php all use the title “MCBS-Manufacturer of DTH antenna, CATV Products / CCTV Products and V…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mcbsintl.com/products/settopbox.html, https://mcbsintl.com/newmedia/ems-services.html, https://mcbsintl.com/news/scat-exhibition.html and https://mcbsintl.com/news/icas-roadshow.html use the same meta description. A description written for each page earns more clicks.

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

https://mcbsintl.com/newmedia/ems-services.html, https://mcbsintl.com/drone/drone_technology.html, https://mcbsintl.com/news/icas-roadshow.html, https://mcbsintl.com/news/hits-roadshow.html and https://mcbsintl.com/contact-us/email-us.php 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.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 (Internal Server Error)”.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 15 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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.

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